hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.5.3 Stage matching | Stage matching depends on the value of the Stage field and the value of user settings (if provided) as shown in table 1. Table 1: Stage matching Stage User setting for this EId + IId Match for receivers in Audio mode Match for receivers in Monitor mode (see note) Level 1 Start n/a Positive Positive Level 1 Update Incid... |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.5.4 Location matching | If the alert signalling does not include any location codes, then the alert area is the entire ensemble coverage area. In this case, the location match is automatically positive. If the alert signalling includes location codes, the receiver compares the first location code in the alert set to the location code of its c... |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.6 Alert mode | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.6.1 Preparation | After an alert match is positive, the receiver shall store its functional status in memory to allow for a seamless return to that status after the alert playback is terminated. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.6.2 Tuned ensemble alerts | The receiver shall play the audio from the subchannel indicated by the Id field. To determine whether the audio is coded as DAB audio or DAB+ audio it is necessary to find the SubChId in the FIG 0/2 MCI. If the alert audio carries PAD applications (for example, dynamic label or SlideShow), or the service includes data ... |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.6.3 Other ensemble alerts | The receiver shall attempt to retune to the ensemble indicated by the Id field using the information in its tuning memory. If the ensemble cannot be tuned, the receiver shall return to the previous functional state. NOTE: Receivability matching has already been performed, so if the ensemble cannot be tuned, the receive... |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.6.4 Terminating an alert | Receivers may offer various user functions to terminate the playback of an alert before it is completed. The user functions may be: • to terminate the currently playing alert only; • to terminate the currently playing alert and engage the "dismiss repeats" function to prevent future playback of repeated messages of the... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 1 Scope | The present document specifies methods to efficiently build and instantiate Key Encapsulation Mechanisms (KEMs) with hidden access policies, while having the privacy of encapsulated keys relying on the best security of two hybridized schemes, namely with an instantiation where the privacy relies on the Computational Di... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 2 References | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 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... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 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... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 3 Definition of terms, symbols and abbreviations | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 3.1 Terms | For the purposes of the present document, the following terms apply: adversary's advantage: probability for an adversary to distinguish two distributions NOTE: Formally, for an adversary A, given two distributions D0 and D1, the advantage is defined as: Adv A = Pr A x = 1 −Pr A x = 1 = 2 . Pr , A x = b... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: 1κ The security parameter κ taken as input to an algorithm || The logical (non-exclusive) OR && The logical AND ⊕ The logical XOR x ← f(y) x is the output of the algorithm f applied to the input y. Unless stated otherwise, f is a randomized algorith... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABE Attribute-Based Encryption CCA Chosen-Ciphertext Attacks CDH Computational Diffie-Hellman CPA Chosen-Plaintext Attacks DEM Data Encryption Mechanism DNF Disjunctive Normal Form IND INDistinguishability KEM Key Encapsulation Mechanism KEMAC... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 4 Cryptographic primitives | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 4.1 Hash functions | Hash functions are used to produce a fixed length random output y from an arbitrary length input x: • H(x) → y Approved hash functions for the purpose of the present document are: • SHA-256, SHA-384, SHA-512, SHA-512/256 as defined in FIPS PUB 180-4 [4]. • SHA3-256, SHA3-384, SHA3-512 as defined in FIPS PUB 202 [5]. |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 4.2 Key Encapsulation Mechanisms (KEMs) | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 4.2.1 KEMs description | A Key Encapsulation Mechanism KEM is a public-key scheme defined by three algorithms: • KEM.KeyGen(1κ) → (pk, sk): on input of a security parameter κ, returns a public key pk and a secret key sk; • KEM.Enc(pk) → (C, K): on input of the public key pk, generates a session key K, and its encapsulation C, and returns (C, K... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 4.2.2 KEMs with Access Control (KEMAC) | When several users are in a KEM system, a KEM with Access Control (KEMAC) can issue users keys according to a key-policy Y, and encapsulate session keys with respect to an encapsulation-policy X, so that a user with key-policy Y can decapsulate if and only if R(X,Y) evaluates to 1, for a fixed Boolean rule R. Said diff... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 4.2.3 NIKE-based KEM | A Non-Interactive Key Exchange (NIKE) is defined by two algorithms: • NIKE.KeyGen(1κ) → (pk, sk): on input of a security parameter κ, returns a public key pk and a secret key sk; • NIKE.SessionKey (sk, pk') → K: on input of a secret key sk and a public key pk', generates a session key K. With the two properties: • Corr... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 4.2.4 Key-Homomorphic NIKE (KH-NIKE) | A NIKE is called key-homomorphic, if there are two internal group-laws ⊗,⊙ on the secret and the public keys that make them correspond to each other: from (pk0, sk0), (pk1, sk1) ←NIKE.KeyGen(1κ), the secret key sk ← sk0 ⊗ sk1 corresponds to the public key pk ← pk0 ⊙ pk1. So, for any scalar x, the secret key sk' ← x . s... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 5 Hybrid Traceable KEMAC (HTKEMAC) | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 5.1 Description | After the definitions given in previous clauses, this clause specifies the KEM instantiation recommended in the present document, combining hybridization, access control and traceability, from a set Ω of rights (which are combinations of attributes, as shown below) that defines the rule: for any pair , of subsets ... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 5.2 Parameter sets | Parameter sets consist of tuples of specific choices for the hash function SHAKE [3], [5], the ML-KEM [6], and the elliptic curves [1], [2]: • SHAKE128_P256_ML-KEM-512 ETSI ETSI TS 104 015 V1.1.1 (2025-02) 12 • SHAKE128_Curve25519_ML-KEM-512 • SHAKE256_P384_ML-KEM-768 • SHAKE256_Curve448_ML-KEM-768 • SHAKE256_P521_ML-K... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6 Access structure | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6.1 High-level description | The previous clause describes an access control from two subsets and of rights in associated to the encapsulations and the user's keys respectively, so that the latter can decrypt the former if and only if ∩ ≠∅. This clause explains how to transform an access structure and a Boolean policy into the set of all the p... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6.1.1 Attributes, dimensions and hierarchies | Let a dimension be a set of attributes. Each dimension is constrained to be either: • a hierarchy , which defines a set of ordered attributes: ∀!, " ∈, ! ≤" or " ≤! • an anarchy #, which defines a set of incomparable attributes: ∀!, " ∈#, ! = " or (¬ ! ≤") and ¬" ≤! A Boolean policy can then be describe... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6.2 Efficiency considerations | As explained above, a Boolean formula expresses the access control for a given encapsulation. After the DNF conversion, this leads to the set with all the clauses (or points associated to the rights) that appear in the DNF. However, building the set associated to the attributes for the user's key is more complex. |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6.2.1 Encapsulation rights | Once converted into its DNF, the Boolean formula associated to an encapsulation is a list of rights from . This is the set . |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6.2.2 User's key rights | Two additional spaces have to be defined to build the set : • the semantic space &'( , of a right is the subspace of points in which the attributes involved in this right can be expressed. EXAMPLE: In the 3-dimensional space, the semantic space of CTR::EN, associated to 1,0,0, is the 1-dimensional subspace of g... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6.2.3 Cardinality of an encapsulation | Following the previous description, the number of rights used in an encapsulation should be equal to the number of clauses in the DNF of its associated access policy, since each clause is either a broadcast to a subspace of , or to a singleton. |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 6.2.4 Cardinality of a user secret key | The number of rights associated to a user secret key is the number of points in the complementary spaces generated by the rights associated to the user. ETSI ETSI TS 104 015 V1.1.1 (2025-02) 15 |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7 Specification | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.1 Introduction | This clause specifies all the objects and functions needed to implement Covercrypt, with their input/output types, where the brackets (such as [* Name]) stand for optional components. |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.2 Access Structure | |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.2.1 Type | An AccessStructure is a set of dimensions, where a Dimension is an object that holds its name and attributes, which are themselves composed of their name and an id that is unique across this access structure: AccessStructure = Set Dimension Dimension = Hierarchy (Name * OrderedSet (Id * Name)) | Anarchy (Name * Set (Id... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.2.2 API | An object of type AccessStructure should expose the following API: • ap_to_usk_rights (AccessStructure * AccessPolicy) -> Set Right Generates the set of USK rights described by the given access policy. • ap_to_enc_rights (AccessStructure * AccessPolicy) -> Set Right Generates the set of ciphertext rights described by t... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.3 Master Secret Key | The master secret key has the following type: MSK = AccessStructure * Keypairs [* SigningKey] [* Tracers] where: • the AccessStructure is described above and contains all necessary information to validate and translate an access structure into a set of rights; • the Keypairs structure contains the history of the keypai... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.4 Master Public Key | A master public key has the following type: MPK = Version * AccessStructure * (Right -> PublicKey) [* Signature] [* TracingPoints] where: • Version holds a number that is increased at each generation of a new master public key; • AccessStructure holds all necessary information for validating and translating an access s... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.5 User Secret Key | A user secret key has the following type: USK = SecretKeys [* Signature] [* UserId] where: • SecretKeys contains the history of the secret keys associated to each right that have been given to the user; • Signature holds a publicly verifiable signature generated by the master secret key; • UserID contains a unique iden... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.6 Encapsulation | An encapsulation has the following type: XEnc = List Encapsulation * Tag [* Traps] [* Version] where: • List Encapsulation contains the encapsulation associated to each right, in a cryptographically-random order. Using a List allows serialization of this order, which is needed since it matters when recomputing the Tag;... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 7.7 Covercrypt | A Covercrypt implementation exposes the following API: • mk_gen (AccessStructure) -> MSK * MPK It takes as input the access structure and generates new master secret and public keys: omega ← ap_to_usk_rights(AccessStructure, "*") (msk, mpk) ← HTKEMAC.setup(omega) • usk_gen (MSK * U * AccessPolicy) -> USK It takes as in... |
08c7c12d92f08acc1ca41679e7fb8a4f | 104 015 | 8 Conclusion | The present document shows the construction of a KEM which achieves privacy and correctness properties, while allowing the encapsulation of keys with respect to hidden access policies. As shown in [i.1], this scheme allows an order of magnitude speedup with respect to Attribute-Based Encryption implementations in pract... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 1 Scope | The present document defines the PEMEA File Exchange (PFE) capability, and the need for this functionality. The required entities and actors are identified along with the protocol, specifying message exchanges between entities. The message formats are specified and procedural descriptions of expected behaviours under d... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 2 References | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 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... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 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... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 3 Definition of terms, symbols and abbreviations | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 3.1 Terms | For the purposes of the present document, the following terms apply: security: techniques and methods used to ensure: • authentication of entities accessing resources or data; • authorization of authenticated entities prior to accessing or obtaining resources and/or data; • privacy of user data ensuring access only to ... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 3.2 Symbols | Void. |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AEAD Authenticated Encryption with Associated Data AES Advanced Encryption Standard AESGCM Advanced Encryption Standard key used with GCM AP Application Provider App Application CPE Customer Premises Equipment DHE Diffie-Hellman key Exchange E... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 4 PEMEA capability extensions | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 4.1 Overview of extension in PEMEA | PEMEA extension capabilities are defined in ETSI TS 103 478 [1] and are implemented through the use of "reach- back" URIs. The Application Provider (AP) node advertises capabilities as part of the initial forward message through the network, the Emergency Data Send (EDS) message, and the terminating PSAP Service Provid... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 4.2 Service support indication and response | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 4.2.1 Service definition | The present document provides a concrete definition of the "File_Exchange" typeOfInfo in PEMEA through the present document of a protocol value. The definition in Table 1 shall be considered as an extension to Table 11 in ETSI TS 103 478 [1]. Table 1: Extended AP Information Type Protocol Registry Info type Value Proto... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 4.2.2 Service support indication | An AP needing to indicate that the Application it is serving can support file exchange using the PEMEA protocol would include the following information element in the apMoreInformation element of the EDS associated with the emergency session: <information typeOfInfo="File_Exchange" protocol="PEMEA"> https://ap.example.... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 4.2.3 Service support response | A terminating node that can support the "File_Exchange" "PEMEA" capability includes this capability in the apMoreInformation element returned to the AP in the onCapSupportPost, as defined in clause 11.1.4 of ETSI TS 103 478 [1], with the value for "File_Exchange" "PEMEA" provided in the example below. <apMoreInformatio... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 5 Architecture | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 5.1 Overview | The PEMEA File Exchange (PFE) capability defines a protocol to exchange files between Apps and PSAPs with a PEMEA emergency request. In order to exchange the files, a file server is needed, and the present document defines all the interfaces and procedures that the file server shall provide. This also helps to understa... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 5.2 Architecture and high-level flows | PEMEA is structured around the AP being the gateway between the App and the PSAP. This model requires communications to occur, first between the App and the AP over the proprietary Pa interface and then between the AP and the associated PSAP service using the protocol mechanisms defined in the specific extension capabi... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 6 Security | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 6.1 Transport security | The PEMEA File Exchange (PFE) session is identified as an HTTPS URI. The requests should be made using TLS 1.3 but may be made using 1.2 and this shall not support fallback below TLS 1.2. All requests shall authenticate to the File Exchange Server using a Bearer token in the HTTP Authentication header field as defined ... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 6.2 Security token usage | The HTTP Authorization header field is defined in IETF RFC 2617 [2] and it specifies that the usage is a scheme followed by a value, where the value may have a structure, as is the case for the digest authentication scheme. Security token usage in the HTTP Authorization header field was originally specified for use wit... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7 Procedures and signalling | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.1 Overview | In order to be able to exchange files using PEMEA File Exchange (PFE) capability the App, AP, PIM and PSAP have to follow the procedures and signalling specified in clause 7 of the present document. Where the procedures defined in clause 7 refer to the PSAP Interface Module (PIM) PEMEA node, they may be performed by a ... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.2 Service invocation | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.2.1 Service invocation procedures | Once the PIM has responded to the AP that it can support the PEMEA File Exchange (PFE) service with the procedures defined in clause 4.2, then the AP shall be capable of accepting a service invocation on the provided URI at any time. The AP shall only accept a PFE service invocation from the PIM that sent the onCapSupp... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.2.2 Service invocation object | The PIM invokes the PEMEA File Exchange (PFE) service in the AP by posting to the URI provided in the File_Exchange information element included in the apMoreInformation contained in the EDS. The POST message includes a body containing a JSON object. The JSON object provides the File_Exchange session URI as well as a s... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.2.3 File Exchange session creation and deletion | The File Exchange session is created by the File Exchange Server under direction of the PSAP Call-Taker via the PIM as defined in clause 7.2. Once the File Exchange session is created it remains active as long as the PIM maintains a context for the EDS. |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3 File Exchange operations | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.1 Overview | The File Exchange session provides a RESTful interface to perform the operations defined in clause 7.3. All the operations shall be authenticated as defined in clause 6. |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.2 List files | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.2.1 Description | Participants can list the available files in the File Exchange session. This allows to check what files had been uploaded to the File Exchange session. To list the available files the participants shall make an HTTP GET request to the URI of the File Exchange session. The HTTP request shall have the following headers: ... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.2.2 Example | HTTP request: GET /session/534wafds21s21fdf HTTPS/1.1 Host: file_exchange_server.example.com Accept: application/json Authorization: Bearer PPtzs5zzG5Pkf61KPz51 HTTP response: HTTPS/1.1 200 OK Content-Type: application/json; charset=utf-8 [ { "name":"example.png", "size":328049, "timestamp":1574092280231, "type":"image... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.3 Upload file | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.3.1 Description | Participants can upload a file to the File Exchange session. This operation adds a new file to the files of the File Exchange session. To upload a file the participants shall make an HTTP PUT request to the URI of the File Exchange session. The HTTP request shall have the following headers: • Accept: The value shall be... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.3.2 Example | HTTP request: PUT /session/534wafds21s21fdf HTTPS/1.1 Host: file_exchange_server.example.com Accept: application/json Authorization: Bearer PPtzs5zzG5Pkf61KPz51 Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryDRKRUlAriyYJ28VG ------WebKitFormBoundaryDRKRUlAriyYJ28VG Content-Disposition: form-data; nam... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.4 Download file | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.4.1 Description | Participants can download a file from the File Exchange session. To download a file the participants shall make an HTTP GET request to the URL of the file they want to download. The URL is obtained using the list files or the upload file operations defined in clauses 7.3.2 and 7.3.3. The HTTP request shall have the fol... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.3.4.2 Example | HTTP request: GET /session/534wafds21s21fdf/example%20(1).png HTTPS/1.1 Host: file_exchange_server.example.com Authorization: Bearer PPtzs5zzG5Pkf61KPz51 HTTP response: HTTPS/1.1 200 OK Content-Disposition: attachment; filename="captura-de-pantalla-2024-03-11-143604 (1).png" Content-Type: image/png <binary> ETSI ETSI T... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4 Notifications channel | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.1 Overview | The operations defined in clause 7.3 allow users to upload files, download files and get the list of uploaded files. With these operations a participant can only know when another participant has uploaded a new file by polling with the list files operation, i.e. by making periodic HTTP requests at a certain time interv... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.2 Subscribe to the File Exchange session | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.2.1 Description | Participants can subscribe to events produced in a File Exchange session by opening a Server-Sent Event (SSE) connection to the File Exchange session URI as defined in HTML Living Standard [10]. To open the SSE connection a participant shall make an HTTP GET request to the URI of the File Exchange session. The HTTP req... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.2.2 Example | HTTP request: GET /session/534wafds21s21fdf HTTPS/1.1 Host: file_exchange_server.example.com Accept: text/event-stream Authorization: Bearer PPtzs5zzG5Pkf61KPz51 HTTP response: HTTPS/1.1 200 OK Content-Type: text/event-stream ETSI ETSI TS 104 014 V1.1.1 (2024-07) 22 |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3 Receive notification events | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3.1 Overview | Once the SSE connection is established as defined in clause 7.4.2 the File Exchange Server can send messages over the opened HTTP connection as it is defined in clause 9.2 of HTML Living Standard [10]. The data transmitted shall be encoded as UTF-8. The data shall be separated by lines, and in each line an event may be... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3.2 File uploaded to the File Exchange session | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3.2.1 Description | Whenever a new file is successfully uploaded to a File Exchange session the File Exchange Server shall send a notification to all participants subscribed to the File Exchange session. It is done by sending a FILE_UPLOADED event which is a JSON object which structure is defined in clause 10.3. Figure 7 provides the sequ... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3.2.2 Example | Subscription is done as defined in clause 7.4.2, so the HTTP request would be opened and only the SSE messages would be sent, but for clarification the HTTP request is written again in this example. HTTP request: GET /session/534wafds21s21fdf HTTPS/1.1 Host: file_exchange_server.example.com Accept: text/event-stream Au... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3.3 File Exchange session closed by the File Exchange Server | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3.3.1 Description | Whenever a File Exchange session is closed as described in clause 9 the File Exchange Server shall send a notification to all participants subscribed to the File Exchange session before closing all the subscriptions. It is done by sending a FOLDER_CLOSED event which is a JSON object which structure is defined in clause... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.3.3.2 Example | Subscription is done as defined in clause 7.4.2, so the HTTP request would be opened and only the SSE messages would be sent, but for clarification the HTTP request is written again in this example. HTTP request: GET /session/534wafds21s21fdf HTTPS/1.1 Host: file_exchange_server.example.com Accept: text/event-stream Au... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.4.4 Unsubscribe from the File Exchange session | To end the subscription the HTTP connection that established the SSE channel shall be closed. This can be done either by the participants or by the File Exchange Server. The File Exchange Server shall only close the SSE connections when a File Exchange session is closed as described in clause 9 and the File Exchange Se... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.5 Errors | |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.5.1 Description | The File Exchange Server may encounter various situations where a request results in an error, these errors may occur because the schemas and operations defined in the present document are not followed or by circumstances that are out of control of the File Exchange Server. When the File Exchange Server shall return an... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 7.5.2 Example | HTTP request: GET /session/534wafds21s21fdf/unknown.png HTTPS/1.1 Host: file_exchange_server.example.com Authorization: PPtzs5zzG5Pkf61KPz51 HTTP response: HTTPS/1.1 404 Not Found Content-Type: application/json; charset=utf-8 { "error":"Not Found", "message":"File Not Found", "path":"/session/534wafds21s21fdf/unknown.p... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 8 Add participants to the File Exchange session | The ability to add participants into the emergency session is important as it brings additional expertise to the emergency situation that is able to assist in providing a successful outcome. The general concept for linking in third-parties is that the PSAP Call-Taker instructs the PIM to obtain additional security acce... |
a4c69013c9592b3b49c0122983240b32 | 104 014 | 9 File Exchange session closure | The File Exchange session can be closed though the tPSP/PIM by the PSAP-CPE. The present document does not instruct when the tPSP/PIM should close the File Exchange session and this decision shall be made by the PSAP-CPE. In most of the cases it can be done when the PSAP Call-Taker considers the emergency session to be... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.