hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.2.3 Running Example | To illustrate the protocol, the present document proposes a scenario used as a running example throughout the whole document. The scenario has three actors: an Issuer, a Prover and a Verifier and it is "standalone", meaning that specific integration to higher level protocols (e.g. HTTP, OAuth, etc.) is not a goal of th... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.3 Main Concepts | |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.3.1 Anonymous Credentials and Zero Knowledge Proof | Anonymous credentials initially proposed by Chaum [i.11] and firstly implemented by Camenisch and Lysyanskaya [i.12] allow users to prove the possession of a set of attributes in zero knowledge. Goldwasser, Micali, and Rakoff defined proposed the first Zero Knowledge Proof (ZKP) scheme back in 1985 [i.16] and defined Z... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.3.2 Functional Credentials | The present document aims at simplifying construction, deployment and adoption of credentials schemas supporting anonymous proof of predicates by building on encryption schemas rather than on signature-based schemas. [i.6] refers to this kind of credential as Functional credentials. A predicate encryption scheme allows... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.3.3 Presentation Policy Verification | In CP-ABE, each policy is implemented through an access structure containing attributes to be matched. A presentation policy is translated in an access structure using a compiler (the algorithm reported in Annex C is an example of a simple compiler supporting basic operators). To avoid that an attacker, impersonating t... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.3.4 Credential Revocation | The present document considers three kinds of revocation: time-based, list-based and accumulator-based. Time-based revocation uses timestamps attributes contained in the credentials. Attributes "issued at", "not before than", "expires at" defined in [11] may be used for this purpose. A Verifier shall not accept credent... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.4 Architecture and Reference Points (normative) | |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.4.1 Architecture | The system architecture presented in the present document consists of three entities: an Issue, a Prover and a Verifier. In case of CCA-secure CP-ABE based on CP-WATERS-KEM, these are mapped to an ABE Authority, a Decrypting party, and an Encrypting party. These three entities, therefore, shall be able to execute the a... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.4.2 Reference Point K (key distribution) | The Reference Point K allows the Authority to distribute secret keys to the Decrypting party. The corresponding interface shall ensure that the entity corresponding to the Authority is authenticated as well as confidentiality and integrity protection of exchanged keys and metadata. The involved parties may also mutuall... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.4.3 Reference Point P (public parameters distribution) | Reference Point P is used by the Authority which makes publicly available the master public key and any other needed public parameter (e.g. attributes, accumulators) and metadata. The corresponding interface shall ensure that the entity corresponding to the Authority is authenticated as well as integrity protection of ... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 4.4.4 Reference Point R (challenge response) | Reference Point between the Decrypting party and the Encrypting party. The corresponding interface shall execute the protocol specified in clause 4.2. The entity corresponding to the Prover (Decrypting party) may require the entity corresponding to the Verifier (Encrypting party) to authenticate. The corresponding inte... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5 Verifiable Credentials | |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.1 Introduction | This clause provides an informal outline of the Verifiable Credentials model defined in [8]. In this model: • A Verifiable Credential is a set of one or more claims made by the same entity. • A claim is a statement about a subject. A subject is a thing about which claims can be made. • Claims are expressed using subjec... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.2 Interface Implementing Reference Point K | |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.2.1 Overview | The present clause uses the definition of Verifiable Credentials (whose description and the semantics is detailed in [8]) to implement Reference Point K. While a Verifiable Credential may consist in several claims, expressed using subject-property-value relationships, this clause is not intended to report a comprehensi... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.2.2 Claim proof | This claim shall contain at least one cryptographic proof that may be used to detect tampering and verify the authorship of a credential or presentation. The proof appears is in the form of a composite object, whose specific format and semantics shall be defined by the "type" property. Credential proofs are traditional... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.2.3 Example: Verifiable Credentials (informative) | The following example refers to the sample scenario presented throughout the present document and uses BLS12-381 elliptic curves. In this example, the Prover receives attributes A and D from the Issuer. Annex B provides more details about the serialization format used to represent any point on the two elliptic curves u... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.3 Interface Implementing Reference Point P | 5.3.1 Overview The present clause defines the interface implementing Reference Point P using the definition of the "controller document" object specified in Verifiable Credentials [8]. ETSI ETSI TS 103 964 V1.1.1 (2025-02) 20 A controller document [10] shall consist in one or more "verificationMethod". Each "verificati... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.3.2 Verification Method Claims | Each "verificationMethod" shall contain the following mandatory claims: verificationMethod.Id This claim shall consist in a property whose value is a single URI identifying the "verificationMethod". verificationMethod.Controller This claim shall consist in a property whose value is a single URI identifying the Controll... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 5.3.3 Example: Controller Document (informative) | Continuing the running example, the Authority releases the master public key: MPK = g1, g1a , e(g1, g2)α, H(x) for each x in {A,B,C,D}, encodes it in the following controller document, specifies the compiler to be used to encode presentation policies and makes it publicly available at the Controller's URI. The reader m... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6 Interface Implementing Reference Point R | |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.1 Introduction | While the previous clause defined the format of verifiable credentials and presentations, together with a method to retrieve public parameters, implementing reference point K and P, the present clause focuses on the format of data at the Reference Point R. At Reference Point R, the Verifier provides the Prover with a c... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2 Challenge | |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2.1 Overview | The challenge shall be a cyphertext encoded via JSON Web Encryption (JWE) compact serialization [3], which for reference, is below reported. This serialization format is made of five Base64 URL safe encoded string segments concatenated by the dot "." character. The present document uses three out of five "segments": th... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2.2 JWE Protected Header | The "JWE Protected Header" object shall contain the following two entries defined by the JWE standard [3]: • The algorithm used to provide key encapsulation shall appear as value of the "alg" property. • The algorithm used to encrypt the ciphertext shall appear as value of the "enc" property. In addition, the present d... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2.3 JWE Encrypted Key | The "JWE Encrypted Key" object represents components of the encapsulated key generated by the CP-WATERS-KEM algorithm. These components are points over elliptic curves. The syntax presented in [2] shall be used to represent these components. To build the final JWE compact serialized object, the "JWE Encrypted Key" obje... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2.4 JWE Ciphertext | The "JWE Ciphertext" object represent the final ciphertext produced by the CP-WATERS-ABE algorithm, which shall be plain bit string made of two components: the nonce and the randomness used in the challenge-response protocol. To build the final JWE compact serialized object, the "JWE Ciphertext" string shall be encoded... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2.5 Example: JWE Protected Header | According to clause 4.1.3, the presentation policy in the example shown in the present document is: A AND (D OR (B AND C)) Therefore, the JSON representation inside the JWE Protected Header is: { "alg":"CP-WATERS-KEM", "enc":"CP-WATERS-ABE", "query":"A AND (D OR (B AND C))" } Encoding using Base64URL without padding gi... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2.6 Example: JWE Encrypted Key | In the running example presented throughout the present document, K and r are 128 bit strings, defined as bytes in hexadecimal notations as follows: K=02x000102030405060708090a0b0c0d0e0f r=02x101112131415161718191a1b1c1d1e1f Concatenating K, r and the presentation policy (the presentation policy in the example is A AND... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.2.7 Example: JWE Ciphertext and JWE object | In the running example presented throughout the present document, the element , is a group field element that is represented in towered format: [[[13a3bd4f132b2010dcb1818deed44e8c0ce0f24f9939a4fc1087c030d30d8b70c04f2ec675eddcf2191d7ca2e84372fa, 0b828dcd917be9e80c0245a07851a045afe4b4f9a2a1383adb5212ced57ad29a5ee7e5... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.3 Response | |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.3.1 Overview | The Prover's response is implemented using a Verifiable Presentation proof. The definition of the proof shall be the same as for Verifiable Credentials reported in clause 5.2, except for the property "proofValue". The "proofValue" property shall present a Base64URL string (refer to clause B.5) encoding the value matchi... |
c8aa7c7324d12a089bcbc74176078ba3 | 103 964 | 6.3.2 Example: Verifiable Presentation | Continuing the running example, the Prover responds to the challenge received by the Verifier with the following proof embedded in a Verifiable Presentation. { "proof": { "type":"FunctionalCredentialPresentation_2023_CP_WATERS_KEM", "created": "2023-01-01T00:00:01Z", "proofValue": "uAAECAwQFBgcICQoLDA0ODw", "proofPurpo... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 1 Scope | The present document provides the baseline requirements specific to optical transport network devices. The present document extends the provisions identified in the Catalogue of Requirements for Optical Network and Device Security from ETSI TS 103 924 [1] (see also Annex B of the present document) addressing the optica... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 2 References | |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 3 Definition of terms, symbols and abbreviations | |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 3.1 Terms | For the purposes of the present document, the following terms apply: canonical identifier: structured identifier that is globally unique root identity: canonical identifier of the device that is attested to in the root identity certificate of the device |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 3.2 Symbols | Void |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABAC Attribute Based Access Control CIA Confidentiality Integrity Availability C-MAC Cipher-Message Authentication Code CRA Cyber Resilience Act CRC Cyclic Redundancy Check CTR CounTeR (mode) DPIA Data Protection Impact Assessment FEC Forward ... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 4 Overview of security of functions for OTN | |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 4.1 OTN device functional model | The general provisions stated in ETSI TS 103 924 [1] and from ETSI TS 103 962 [6] apply to ON devices operating within the transport network with the additional specializations given in the present document. NOTE: Provisions extended from [1] that apply solely to access devices are described in ETSI TS 103 962 [6]. Cla... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 4.2 Trust architecture in ON transport device | Clause 4.2 of ETSI TS 103 962 [6] applies with the following clarifications and extensions. Where reference is made in ETSI TS 103 962 [6] to an Access device it shall be read as apply to an ON transport device for the present document. ETSI ETSI TS 103 963 V1.1.1 (2023-12) 9 |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 5 Identification and authentication of OTN devices | The provisions of ETSI TS 103 962 [6] apply with the replacement of the term "access" with "transport". With respect to the role and application of random numbers a reference is made to the bibliography in which a number of articles and opinions on the use of software only random numbers are cited all of which suggest ... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 6.1 General provisions - integrity | The provisions of ETSI TS 103 962 [6], clause 6.1 apply with the replacement of access device by transport device. |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 6.2 General provisions - confidentiality | The provisions of ETSI TS 103 962 [6], clause 6.2 apply with the replacement of access device by transport device and the following text applies. All transmissions between OTN devices should be protected by a confidentiality security association. Where used the security association should identify: 1) The encryption al... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 7 Secure data storage on OTN devices | |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 7.1 General provisions | For protection of management and configuration data the provisions of ETSI TS 103 961 [2] and of ETSI TS 103 962 [6] apply |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 7.2 Access control in OTN devices | The provisions identified in ETSI TS 103 924 [1], ETSI TS 103 961 [2] and ETSI TS 103 962 [6] apply with the additional detailed provisions identified in the present document (see also Annex B). ETSI ETSI TS 103 963 V1.1.1 (2023-12) 10 Consistently with ETSI TS 102 165-2 [5] the Optical transport network access control... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 7.3 Access Control rules for OTN devices | The following rules shall be implemented in OTN devices. NOTE 1: Access control rules are atomic and identify only one condition per rule. Rule CFG-AC Descriptive format: Only a device administrator shall be allowed to update, or delete, an entry in the configuration data object. • P ∃!{S∪A∪O∪C} shall be true only when... |
6c5de0d17e712b5e6bb94b48d793837e | 103 963 | 7.4 Access control policy in OTN devices | An access control policy combines rules into an overall access control condition. As above the overall policy should be defined in such a way that all rules of a policy have to pass in order to permit access. A policy shall only set access control permission to True where all rules of any policy pass (i.e. the only com... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 1 Scope | The present document specifies interoperable and accessible emergency communications, which incorporates voice, video, and real time text. Involvement of originating devices, originating service provider, packet switched emergency communications infrastructure, PSAPs, and supporting services in the emergency communicat... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 2 References | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 3 Definition of terms, symbols and abbreviations | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 3.1 Terms | For the purposes of the present document, the following terms apply: accessibility: extent to which products, systems, services, environments, and facilities can be used by people from a population with the widest range of user needs, characteristics, and capabilities, to achieve identified goals in identified contexts... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 3.2 Symbols | Void. |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP Third Generation Partnership Project AEC Accessible Emergency Communication ASR Automatic Speech Recognition EAA European Accessibility Act ESInet Emergency Services IP network GTT Global Text Telephony = RTT GTT-IP Global Text Telephony ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 4 Operational profile | The technical requirements of the present document apply under the operational profile for the equipment and services, which shall be in accordance with its intended use, but as a minimum, shall be that specified in the applicable operational scenarios for testing contained in clause B.4.2 of the present document. The ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5 Accessible Emergency Communication | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.1 General | Making sure that emergency communications are accessible to persons with a range of capabilities implies considerations on many levels. The continuation of clause 5 covers specific interoperability and accessibility aspects and functional requirements on the complete chain of emergency communication technology includin... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.2 Modality and Language | Proper support for the modalities and languages in communication managed by the user in emergency is a prerequisite for efficient emergency communications. The means for providing of such support is by the user or user equipment providing information about the preferences and capabilities and the emergency services to ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.3 User Interface and general accessibility | Emergency communications users are best provided with emergency communications when such communications are supported by the end user equipment and electronic communications used in everyday communication. The user interface and communication features used for accessible emergency communications shall: AEC-UI-01: compl... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4 Communication Features | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4.1 General | The present clause specifies general communications operations used in the processing of emergency communications. |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4.2 Session Control and emergency contextual information | Session setup in accessible emergency communications shall: AEC-SC-01: include information describing the desired media. AEC-SC-02: include accurate location information. AEC-SC-03: include an identity or address to be used for emergency call back. AEC-SC-04: support the technical possibility to handle the media, modal... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4.3 Routing | Several factors influence decisions on routing the communication to a region and to a PSAP. Factors are responsibility over the location of the emergency and the load of the PSAP. In relation to accessibility, additional factors are of concern in decision of which is the most appropriate PSAP. The additional factors ar... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4.4 Communication Transfer | When transfer of accessible emergency communications is available, the system performing the transfer shall: AEC-CT-01: have means to make attended transfer of the communication to other parties within the emergency service organization, where the: a) original party may stay as long as suitable in the transferred commu... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4.5 Conferencing | When conferencing in accessible emergency communications is available, the conferencing functions shall: AEC-CO-01: have means to invoke and support multiparty communications in an emergency communication (e.g. in case of a communication transfer or when including relay services), where the multiparty communication sha... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4.6 Call back | Accessible emergency communications shall: AEC-CB-01: be enabled to call back to the user in emergency. The call back feature shall have the following characteristics: AEC-CB-02: By default, enabling the same media as used in the incoming communication. AEC-CB-03: Having the option to vary the media composition compare... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.4.7 Charging | AEC-CG-01: The user shall not be charged specifically for accessible emergency communications. |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.5 Communication Media | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.5.1 General | Many of the accessibility considerations are related to the availability of media for the communication suitable for the capabilities of the user in emergency. The electronic communication service used by the user in an emergency shall support multiple communication participants for all media used in emergency communic... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.5.2 Audio | Audio in emergency communications is needed for spoken communication, and for providing sounds from the emergency scene for assessing the emergency. Accessible emergency communications shall: AEC-CM-01: include bidirectional audio media in the communication from the beginning of the communication. AEC-CM-02: fulfil the... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.5.3 Video | Video in emergency communications is needed for sign language communication, for enhancing understanding of spoken language, for conveying calming influence and for providing views from the scene of the emergency for efficient assessment of the emergency. Accessible emergency communications shall: AEC-CM-03; provide th... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.5.4 Real Time Text | Accessible emergency communications shall: AEC-CM-07: provide the user to include real time text media in the communication from the beginning of the communication as well as by addition during the communication. AEC-CM-08: fulfil the requirements on real time text as in ETSI EN 301 549 [1], clause 6.2. |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.5.5 Text Messaging | Accessible emergency communications may: AEC-CM-09: provide the user to include the text messaging in the communication as well as by addition during the communication. AEC-CM-10: support emergency communications that started with messaging to be upgraded to a communication with real time media by adding audio and any ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.5.6 Total Conversation | Total conversation is audio, video and real time text enabled and synchronized in a single bidirectional communication and fulfilling performance requirements on these media. The quality requirements are found in ETSI EN 301 549 [1], clause 6. NOTE: The synchronization is assumed when all three media fulfil their indiv... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.6 Relay-Service Invocation by the User in Emergency | Although it is preferable to directly contact emergency services, some users reach emergency services by first initiating communication with a relay service and then ask the relay service to initiate an emergency communication. The location of the user is then interrogated by manual means from the user in emergency by ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.7 Supporting Services | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.7.1 General | 5. |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.1 General | Some situations require support to PSAPs from other organizations or services. Such supporting services may be relay services for modality translation, language support services for language translation and expert support services for assistance in the emergency situations. See ETSI EN 301 549 [1], clause 13, and ETSI ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.7.2 Relay Services | Relay services convert between different real time communication modalities. During accessible emergency communications: AEC-SS-06: when a relay service is available to the user, the PSAP shall have the possibility to invoke the relay service in the emergency communications by a single multimedia connection. See ETSI E... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.7.3 Translation Service | Translation services translate mainly between two spoken languages. Accessible emergency communications shall: AEC-SS-12: have the technical means to invoke a translation service supporting the media used in the emergency communication. NOTE: This inclusion can be important to bridge a language gap between a PSAP and a... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 5.8 Documentation | Accessible documentation about products and services involved in emergency communication shall be provided for the following: AEC-AD-01: consumer terminal equipment with interactive computing capability, used for electronic communications services and emergency communications. AEC-AD-02: electronic communications servi... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 6 Technical Architecture | Figure 1 presents a symbolic figure over the functional entities participating in the emergency communication and the interfaces between them. The user equipment resides in an originating service domain, with an originating communication service provider. The communication service provider initiates emergency communica... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7 User equipment requirements | 7.1 General The User Equipment (UE) handles the emergency communications with the user in emergency together with the electronic communications service it resides in. The result is that the emergency communications in the interface between the service and the emergency service network are aligned with the conventions i... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.2 IMS Based User Equipment | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.2.1 General | The User Equipment (UE) handles the emergency communications with the user in emergency together with the IMS service it resides in. The result is that the emergency communications in the interface between the IMS service and the emergency service network are aligned with the conventions in that interface as specified ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.2.2 Settings | The user equipment shall enable the user to set accessibility related preferences of importance for emergency communications. The settings are stored in the communications service. These settings contain but are not limited to the following: • Preference for always including RTT initially in both outgoing and incoming ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.2.3 Initiation of emergency communications | The emergency communications shall be initiated according to the procedures specified in ETSI TS 126 114 [9], ETSI TS 122 101 [5], clause 10 except clauses 10.2 and 10.3, and ETSI TS 124 229 [8], clauses 4.7 and 5.1.6 for emergency communications in IMS. (AEC-SC-01), (AEC-SC-02), (AEC-UI-02). Dialling number 112 shall ... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.2.4 Call Back | A call back is indicated by the SIP Priority header with value "psap-callback" from the PSAP to the user equipment, as defined in IETF RFC 7090 [18]. Any call back from the emergency service shall be handled by the user equipment and indicated to the user as emergency communication. (AEC-CB-01). The media shall be hand... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.2.5 Visiting regions and networks | The IMS system includes roaming functionality, which means that user equipment in a visited network performs emergency communications through the functional entities in the visited network. That causes specific considerations in roaming conditions, specified in ETSI TS 123 167 [7] and ETSI TS 124 229 [8], clauses 4.7 a... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.2.6 Invocation of supporting services by the user | Users who find themselves in an emergency may not remember that their accessibility needs will be met efficiently if they initiate the emergency communication in the recommended way. This could especially be the case if they are used to calling support services in their daily communication. When a user invokes a suppor... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.3 SIP Based User Equipment | |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.3.1 General | User equipment called "SIP based" in the present document is user equipment using IETF RFC 3261 [10] and IETF RFC 8866 [17] for session and media control, and not included within the IP multimedia subsystem concept (IMS) ETSI TS 122 228 [i.2]. Real time text (RTT) shall be supported as specified in ETSI TS 103 479 [3],... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.3.2 Settings | The user equipment shall enable the user to set accessibility related preferences of importance for emergency communications. The settings may be stored in the user equipment or in the service as decided by the service provider. These settings comply but are not limited to the following: • Preference for always includi... |
6e676dae2fc0ed0654334f2749a7865d | 103 919 | 7.3.3 Initiation of emergency communications | The emergency communications shall be initiated according to the procedures specified in ETSI TS 103 479 [3], clause 6 except 6.1.3, 6.2, 6.3, 6.4 and 6.8. (AEC-SC-01), (AEC-UI-02). Dialling number 112 shall be among the supported ways to initiate emergency communications. The same way shall be available regardless of ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.