hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.4.6.2 Service interactions with other PSTN/ISDN simulation services (NGN) | |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.4.6.2.1 Terminating Identification Presentation (OIR) | See clause 8.4.1.2.4, noting that 3PTY is a special case of CONF. 8.4.6.2.2 Terminating Identification Restriction (TIR) See clause 8.4.1.2.5, noting that 3PTY is a special case of CONF. |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.4.6.2.3 Three-Party (3PTY) | A, B and C are in a three-way conversation that was created by B invoking the 3PTY service. A can create a second three-way conversation involving the original three-way conversation and D by invoking the 3PTY service. ETSI ETSI TS 181 002 V2.2.5 (2007-11) 40 |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.4.6.2.4 CONFerence (CONF) | A, B and C are involved in a conference that was created by B invoking the CONF service. A can create a three-way conversation involving the original conference call and D by invoking the 3PTY service. NOTE: It is FFS whether there is a conflict with the requirement expressed by 8.4.1.2.2, considering that 3PTY is just... |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.4.6.3 Interoperability with PSTN/ISDN | The NGN shall support the interoperability of the 3PTY service with PSTN/ISDN supplementary service 3PTY and vice-versa. The scope of this interworking may result in a limited service capability. |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.5 Concepts associated with supplementary services | Provision, Withdrawal, Registration, Erasure, Activation, Deactivation and Invocation shall be as defined in ITU-T Recommendation I.210 [2]. 8.6 Use of authorization option in relation to supplementary services |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.6.1 Definition | Some supplementary services (e.g. communication session barring) can be offered to a user with the subscription option of authorization to control the service. When this option is selected, every action (related to that supplementary service), such as registration, erasure, activation or deactivation is performed by th... |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.6.2 Description | When the subscription option authorized control of a supplementary service is provided, authentication handling is supported by the network. |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.6.3 Management - normal procedures and successful outcome | |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.6.3.1 Provision of authorization | Each supplementary service which requires authorization to control this service may be offered with the subscription option authorized control of the supplementary service. The values of this option may be: • user authentication; • by the service provider. |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.6.3.2 Withdrawal of authorization | Authorization may be withdrawn for administrative reasons or due to subscription modification. |
ae3dfca740c8c62772d38184c6500f19 | 181 002 | 8.6.3.3 Authentication requirements | The network shall provide, and allow the user to maintain, the authentication credentials. ETSI ETSI TS 181 002 V2.2.5 (2007-11) 41 Annex A (informative): General terminal guidelines A.1 Service state indication It is considered useful to indicate to the user the current state, notably the activated state of those serv... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 1 Scope | The present document defines the requirements for a videotelephony service which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities. The present document provides interoperability service requirements for interconnection between existing networks and a TISPAN ... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • ... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 3 Definitions and abbreviations | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions given in TR 180 000 [3] apply: • originating party; • terminating party. ETSI ETSI TS 181 001 V1.1.1 (2006-03) 7 |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACR Anonymous Communication Rejection AoC Advice of Charge CB Communication session Barring CCBS Communication Completion on Busy Subscriber CDIV Communication DIVersion CIF Common Intermediate Format CONF CONFerence CW Communication Waiting E... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 4 Service description | Videotelephony is a real time conversational service using video media and audio or other types of media. The service is assumed to be applicable only to dedicated terminal equipment with video capabilities. The videotelephony service may be considered as a specific instance of an IP multimedia service, or as part of t... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 5 Procedures | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 5.1 General service requirements | The videotelephony service shall conform to the requirements in TS 181 005 [2], clause 5.2.1. In particular, the following capabilities described in TS 181 005 [2] shall be applicable to this service: • Handling of an incoming session (by the terminating entity). • Presentation of session originator identity. • Negotia... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 5.3 Charging and accounting | The requirements for charging and accounting shall be as described in TS 181 005 [2]. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 6 Quality of service requirements | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 6.1 General | The quality of service requirements shall be as described in TS 181 005 [2]. The following parameters may also be taken into account: Overall Delay, Delay Variation, Differential Delay between sound and image, Sound Quality, Image Quality, Echo Cancellation, Sensitivity to Packet Loss, etc. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 6.2 Video quality | Four profiles are defined in table 1. Other enhancement or additional functions may be added. Table 1: Video quality profile Profile Description A Basic Videotelephony: PCM or equivalent telephony audio, QCIF or CIF video with limited movements capability. B Enhanced Videotelephony: wideband audio, CIF video. The servi... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 6.3 Audio quality | Videotelephony does not place any additional requirements for audio quality. ETSI ETSI TS 181 001 V1.1.1 (2006-03) 9 |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 7 Interworking considerations | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 7.1 General | An NGN shall support the interoperability of the videotelephony service with non NGN network services and vice versa. This includes interworking the audio component to the PSTN/ISDN and vice versa. The video component shall only be interworked if video is supported in the non NGN network. The scope of this interworking... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8 Interactions with PSTN/ISDN simulation services | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.1 General | A network operator may choose to offer the PSTN/ISDN simulation services as described in TS 181 002 [1] in conjunction with this videotelephony service as part of an NGN deployment scenario. The following clauses detail the use of PSTN/ISDN simulation services with this videotelephony service for this scenario. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.2 Mandatory services | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.2.1 Originating Identification Presentation (OIP) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.2.2 Originating Identification Restriction (OIR) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.2.3 Terminating Identification Presentation (TIP) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.2.4 Terminating Identification Restriction (TIR) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.2.5 Malicious Communication Identification (MCID) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.2.6 Anonymous Communication Rejection (ACR) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. ETSI ETSI TS 181 001 V1.1.1 (2006-03) 10 |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.3 Recommended Services | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.3.1 Communication DIVersion (CDIV) | In addition to the principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] the following shall also apply: User A requests a communication with user B, who has activated Communication Diversion towards user C. If either user A or C requests a video component to be added to the communicati... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.3.2 Communication Waiting (CW) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.3.3 Communication HOLD (HOLD) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.3.4 Communication Baring (CB) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.3.5 Communication Completion on Busy Subscriber (CCBS) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.3.6 Message Waiting Indication (MWI) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.4 Optional services | |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.4.1 CONFerence (CONF) | In addition to the principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] the following shall also apply. A videotelephony service shall allow a conference service. If a correspondent's terminal doesn't allow videotelephony service, this conference shall be an audio conference for this c... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.4.2 Advice of Charge (AoC) | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. ETSI ETSI TS 181 001 V1.1.1 (2006-03) 11 |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.4.3 Explicit Communication Transfer (ECT) | In addition to the principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] the following shall also apply: When the transferring user A, transfers a communication from user B to user C, which may be: • just requested; • in progress of being established; or • already established. The resul... |
5680d382a0d0da123833d6c76b3aa99f | 181 001 | 8.4.4 Reverse charging | The principles of the corresponding PSTN/ISDN simulation service defined in TS 181 002 [1] shall apply. ETSI ETSI TS 181 001 V1.1.1 (2006-03) 12 Annex A (informative): Guidelines A.1 Terminal requirements The Videotelephony service needs to have a friendly user interface allowing an easy use in a family context. The us... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 1 Scope | The present document give guidelines for the functional requirements required for a MESA system that is consistent with the Service Specification Group's Statement of Requirements (TS 170 001 [1]) and the Technical Specification Groups Network Architecture (MESA 70.015 [i.1]). The present document is intended to be the... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 170 001: "Project MESA; Service Specification... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] MESA 70.015: " Project MESA; Technical Specifica... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 3 Definitions and abbreviations | |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: airlink resources: available throughput (voice and data) for a given location that can be shared across all users ETSI ETSI TS 170 016 V3.1.1 (2009-02) 6 authorized principal: principal with permissions to perform specific action(s) or... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 3.2 Abbreviations for Requirement Identification | Requirement format is of the form: xx-xxx-nnn (where x are letters, and n are numbers). The format structure consists of a requirement classification, which is a two letter prefix identifying how the requirement will be documented; followed by three letters identifying functional categorizations of the requirements; fo... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 4 Functional Requirements | The following tables capture the Functional Requirements for the Project MESA system. ETSI ETSI TS 170 016 V3.1.1 (2009-02) 8 |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 4.1 Core Functional Requirements | Table 1 consists of the functional requirements that would apply to developing standards and specifications for a MESA system. Table 1: Functional Requirements Functional Req. ID No. Functional Requirement Text Associated Mesa SoR Sections Associated User Seq IDs FR-ASC-001 Authorized principals shall be able to add, m... |
3ae069dd79fe22a22f1ee6dbdd4dc37d | 170 016 | 4.2 Other Requirements | Table 2 consists of other requirements that were identified and are applicable to a MESA system, but do directly apply to the standards development phase. Table 2: Other Requirements Functional Req. ID No. Functional Requirement Text Associated Mesa SoR Sections Associated User Seq IDs DC-EUD-020 The device shall be er... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 1 Scope | The present document describes the basis for a functional and technical specification and standards platform that can be installed as either a private system owned by government or a governmental/commercial partnership that provides priority service to public safety agencies and possibly secondary service to other comm... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 2.1 Normative references | Not applicable. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 2.2 Informative references | [1] ETSI TR 170 002: "Project MESA; Service Specification Group - Services and Applications; Definitions, symbols and abbreviations". |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 3 Abbreviations | For the purposes of the present document, the abbreviations given in TR 170.002 [1] and the following apply: AFIS Automated Fingerprint Information System ATF U.S. Department of Treasury's Bureau of Alcohol, Tobacco, and Firearms ATL Attempt To Locate CDMV Canadian Department of Motor Vehicles ETSI ETSI TS 170 001 V3.3... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 4 Executive Summary | The Public Safety Partnership Project (PSPP), Project MESA (Mobility for Emergency and Safety Applications), is an international collaborative effort for the coordination and development of next-generation high-mobility wireless broadband data specifications, standards, and capabilities. A MESA-capable system and appli... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5 Project MESA SoR | |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.1 Objectives | The objective of the Project MESA SoR is to establish a suite of specifications that are articulated from the user's perspective. The present document will provide a profile of the common operational and functional requirements of next-generation aeronautical and terrestrial-based, mobile and fixed systems. The Project... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.2 Scope of requirements | The Project MESA SoR seeks to satisfy the current and identified common long-term needs and requirements of national and local public safety, public service, and public security communities from throughout the world. Some of these organizations do not have all these needs and requirements. Some will have additional nee... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.3 User requirements | The overall requirements of most public safety agencies in Europe and North America are included in the annexes and Appendices. The list is not exhaustive and is complete with their "Mission Statements" relative to the Project MESA SoR. The MESA SSG SA members believe the Project MESA specifications and standards creat... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.4 Use of existing protocols | The specifications and standards written to meet the Project MESA SoR should be, wherever possible, based on existing protocols. It is necessary that the proposed seamless technology specifications and standards be able to allow the transport of digital information between different transport technologies as well as di... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.5 Evolving specifications and standards | The Project MESA SoR assumes the requirements contained herein may need modification as the wireless specifications and standards evolve and develop to accommodate new technologies. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.6 Use of open architectures | The Project MESA SoR expects the specifications and standards that are created from this process will include the adoption of an Open System Architecture (OSA) and design approach, which employs "best practices" for implementation where approved standards are not yet established. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.7 Mobile computer telecommunications system | The Project MESA SoR for specifications and future standards should accommodate the creation of a new multiple- agency, multiple-function, multiple-services, mobile computer telecommunications system and associated network(s). |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.8 Local, regional and national interoperability | The specifications and standards written to meet the Project MESA SoR should ensure local, region-wide and/or nationwide interoperability between any applicable network elements. ETSI ETSI TS 170 001 V3.3.1 (2008-03) 20 |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.9 Interoperability between MESA user devices | Any specification or standard written to meet the Project MESA SoR should ensure local, region-wide and/or nation- wide interoperability between and among individual MESA-capable user devices. This includes devices that may be travelling outside of their home operational infrastructure. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.10 In building and portable service | The specifications and standards written to meet the Project MESA SoR should be driven by the objective of being able to provide a complete suite of wide area portable, "in vehicle" and "in building" services. These standards and specifications should employ an assortment of technologies. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.11 Operational compromises | It is understood by the Project MESA SSG user members that certain technological and operational compromises may be required to fully complete the wireless specifications and standards as envisioned in the present document. Each of those potential compromises will be addressed on a case-by-case basis. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.12 Compliant with the need of the participating nations | Any specifications and standards written to meet the requirements of the Project MESA SoR will also be written to comply with the regulatory requirements of the national governments participating within the Project MESA process. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.13 Pre-testing technology proposals | Any new technologies proposed to be used in response to the Project MESA SoR should be bench tested before their inclusion in a final specifications or standard. In addition, to be compliant with the SoR, and at the discretion of the SSG and Steering Committee (SC), it may be necessary to conduct actual field tests of ... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.14 Frequency neutral technology | Any specifications and standards written to meet the Project MESA SoR shall be frequency agnostic or neutral, thereby allowing standardized technology to be used in any authorized and available spectrum consistent with the required channel bandwidth. Frequency allocation, dictated by national and international regulati... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.15 Improvements in spectrum efficiencies | Affords immediate, significant and evolutionary improvements in radio bandwidth and spectrum efficiency through the cooperative use of broadband specifications and standards that optimize the use of the bandwidth allocated. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.16 Life-cycle procurements | Promotes global competition in the participant's life-cycle procurements of technology platforms and systems. ETSI ETSI TS 170 001 V3.3.1 (2008-03) 21 |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.17 Economical and ergonomically friendly design | The Project MESA SoR enables to use of ergonomically designed, human-engineered "user friendly" equipment (i.e. form factor) to meet the needs of the various Project MESA users. The proposed Project MESA specifications and related standards should also be written to ensure the hardware created from those specifications... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.18 Environmentally safe | Any specifications and standards written to meet the Project MESA SoR should be virtually free from technology that is capable of generating harmful non-ionizing radiation and primary and secondary Radio Frequency (RF) emissions that would have a negative impact on the tools used by the public safety community; includi... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.19 Adequate interference protection | Any specifications and standards written to meet the Project MESA SoR shall be developed to ensure an adequate level of interference protection to and from adjacent systems and/or channels. Adequate interference protection is defined as that which is sufficient to permit operation of a system within the specified inter... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.20 Migration | The technical specifications created for this SoR may establish, where practical, a tactical communications architecture that provides for a "migration-path" from existing public safety analogue and digital systems and platforms. While full, direct backward compatibility may not be achievable or even desirable, where p... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.21 Consistent with existing standards | Any new Project MESA specifications and standards that are developed from those existing specifications and standards should be consistent with creating full and complete interoperability with technologies built to the Project MESA specifications. Of equal importance is the need for any future Project MESA specificatio... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.22 Related documents, standards, policies or requirements | Any specifications and standards written to meet the Project MESA SoR are intended to embody the work previously done by other national and international agencies, groups of agencies or standards bodies as much as may be practical. Although all of these documents may not be directly related to the actual technical spec... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.23 Regulatory compliance | Any specifications and standards written to meet the Project MESA SoR will be written to ensure full compliance with existing European and North American, or other national or international, regulatory rules and regulations. 5.24 Compliance with national and international rules, regulations and standards Any specificat... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.25 Compatible for multiple international standards | Project MESA specifications and standards should provide a technology architecture that is transparent to the applications the technology is intended to carry and will be capable of transporting multiple international standards-based data protocols. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.26 Publication of standards and specifications | Any specifications and standards written to meet the Project MESA SoR should be published for use by any other user. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.27 Interface requirements | It is anticipated that the new Project MESA SoR technical specifications and derived standards will use existing national and/or international standards where appropriate and shall define new interface standards where necessary. It is anticipated, in particular, that new physical connection standards may be necessary f... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.28 Interface protocol requirements | The proposed Project MESA derived standards suite will include the development and/or incorporation of application layer protocols specific to PPDR not addressed by other international standards. Such protocols will be defined to support applications such as the exchange of information related to emergency incidents, f... |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.29 Transparent interfaces | The proposed Project MESA specifications and standards are intended to provide interfaces that are transparent to the wireless network, the network being interfaced, and any application protocols carried across the interface. ETSI ETSI TS 170 001 V3.3.1 (2008-03) 23 |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.30 Service platform | Any specification and standard written to meet the Project MESA SoR should accommodate both on-net and off-net services and applications. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.31 Two-way communication | Any specifications and standards written to meet the needs of Project MESA SoR should allow for the indicated manner of two-way communication at all times, such as voice communication devices or data only or converged capabilities. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.32 Traffic distribution | Any voice-related specifications and standards that are written to meet the Project MESA SoR should allow for both point-to-point and point-to-multipoint voice communications and the transfer of user defined data. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.33 Dynamic remote partitioning | Any pertaining specifications and standards written to meet the requirements of the Project MESA SoR should include the capability of remotely partitioning the network, system or bandwidth at an individual site. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.34 Dynamic transfer rates and bandwidth allocation | The choice of technologies utilized to satisfy the Project MESA SoR should allow for a dynamic information transfer rate and bandwidth allocation in order to meet user demands and priorities prevailing at that time. |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.35 Multiple levels of availability of service | Any specifications and standards written to meet the requirements of the Project MESA SoR shall allow for, but not require, different levels of service to different users (in order to meet clause 5.36). |
21679ab1a7a186a2cd8d4dd617bf673c | 170 001 | 5.36 Priority services | Any specifications and standards written to meet the Project MESA SoR should ensure public safety users can have several levels of priority services and the highest level of priority service as applicable. Priority services as defined in the present document are on-net priorities. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.