hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 3 Definition of terms, symbols and abbreviations | |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [i.1]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [i.1]. Implementation Under Test (IUT): Refer to ISO/IEC 9646-1 [i.1]. Test Purpose (TP): Refer to ISO/IEC 9646-1 [i.1]. DNS64: Refer to IETF... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 3.2 Symbols | Void. |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 123 501 [9], IETF RFC 6147 [i.2], IETF RFC 6877 [5] and the following apply: 3GPP 3rd Generation Partnership Project ATS Abstract Test Suite HR Home Routing IP Internet Protocol IUT Implementation Under Test LBO Local Breakout SUT System Under... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4 Test Environment | |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.1 Introduction | The following architectural test configurations are referenced in interoperability TDs of IPv6-only services over 5G, which uses 464XLAT + DNS64 protocols in 5G standalone network to provide IPv6-only services. They are intended to give a general rather than a specific view of required connections among SUTs. To fully ... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.2 Test configuration/architecture | |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.2.1 Configuration CF_5G_IPv6only_NRMI | Figure 1: Configuration CF_5G_IPv6only_NRMI Configuration CF_5G_IPv6only_NRMI is used for a network where users are registered to their home network. The suffix NRMI stands for non-roaming scenario. PDU session establishment procedures of UEs are performed locally in their own home network. Configuration CF_5G_IPv6only... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.2.2 Configuration CF_5G_IPv6only_RMIL | Figure 2: Configuration CF_5G_IPv6only_RMIL Configuration CF_5G_IPv6only_RMIL describes the roaming scenario with Local Breakout (LBO). UE connects to the visited network 5GC_A. In the case of LBO, the PDU session establishment procedure is as in the case of non-roaming with the difference that the AMF, the SMF, the UP... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.2.3 Configuration CF_5G_IPv6only_RMIH | Figure 3: Test configuration CF_5G_IPv6only_RMIH Configuration CF_5G_IPv6only_RMIH describes the Home-Routed (HR) roaming scenario. UE connects to the visited network 5GC_A. The PDU session is supported by a SMF function under control of the HPLMN, by a SMF function under control of the VPLMN, by at least one UPF under... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3 Test infrastructure | |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.1 Introduction | The present clause covers the list of relevant components used for testing interoperability in 5G. For components that are not present, standard functionality is assumed. This infrastructure consists 5G system components and 464XLAT+DNS64 architecture to provide IPv6-only connectivity. NOTE: The components for 464XLAT+... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2 Test component descriptions | |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.1 CLAT (IPv6-only) | The customer-side translator (CLAT) is a translating function that provides connectivity between IPv6 and IPv4, complying with Stateless IP/ICMP Translation Algorithm (SIIT) defined in IETF RFC 7915 [8]. It algorithmically translates 1:1 private IPv4 addresses to global IPv6 addresses according to the algorithm defined... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.2 PLAT/NAT64 (IPv6-only) | The provider-side translator (PLAT) is a translating function that provides connectivity between IPv6 and IPv4, which is also called stateful Network Address Protocol Translation (NAT64) function defined in IETF RFC 6146 [4]. The translation is done by translating the packet headers according to the IP/ICMP Translation... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.3 DNS64 (IPv6-only) | The Domain Name Service Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers (DNS64) is considered as a key point entity in the present document to provide IPv4 servers address and IPv6 prefix used for translation. DNS64 is a mechanism for synthesizing AAAA Resource Records (RRs) from A RRs. The... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.4 User Equipments (5G) | The test infrastructure shall contain User Equipments (UEs). These are represented by client devices or simulators, capable of performing the 5GC procedures. The test descriptions are focusing only on the full message exchange details at the observation point at one client device. |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.5 AMF (5GC) | Access and Mobility Management Functionality (AMF) is the key control-node for the 5G access-network. It is responsible for Registration Management, Connection Management, Reachability Management, and Mobility Management. UE registration is the fundamental procedures before it creates a PDU session. |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.6 SMF (5GC) | The Session Management Function (SMF) is a fundamental element of the 5G system. The SMF is primarily responsible for interacting with the decoupled data plane, creating, updating and removing Protocol Data Unit (PDU) sessions and managing session context with the User Plane Function (UPF). The Test Descriptions are fo... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.7 UPF (5GC) | The User Plane Function (UPF) plays the most critical role in data transfer. It is responsible for providing connectivity between the UE and external packet data networks. The test descriptions are focusing only on allocation of UE IP address/prefix (if supported) in response to SMF request and packet routing & forward... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.2.8 UDM (5GC) | The Unified Data Management (UDM) manages data for access authorization, user registration, and data network profiles. Subscriber data is provided to the Session Management Function (SMF), which allocates IP addresses and manages user sessions on the network. To provide this functionality, the UDM uses subscription dat... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.3.3 Applicable 3GPP Release Number | Considering that the purposes of these tests is to prove base IOP in 5G SA systems from potentially different vendors, the functionality has been limited to common/typical procedures, while exhaustive conformance testing is out of the scope of the present document. The present document is aimed at 5G SA network, Releas... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.4 Test pre-requisites | 5G system provides IPv6 protocol functionality and has a selectable DNN which PDU session type is only IPv6. |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.5 Test description overview | The test descriptions are documented in clauses 5, 6 and 7. Clause 5 represents test descriptions in the single network (non-roaming) case and clauses 6 and 7 in the roaming case. For each clause, the test descriptions are presented in the following groupings: • UE IPv6 address allocation; • DNS/DNS64 address allocatio... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 4.6 TD naming convention | TDs are numbered, starting at 01, within each group. ETSI ETSI TS 103 878-2 V1.1.1 (2025-05) 11 Table 1: TD identifier naming convention scheme Identifier: <TD>_<group>_<scope>_<nn> <td> = Test Description: fixed to "TD" <group> = Test Group: RMIL – roaming with local breakout RMIH - roaming with home routed NRMI - non... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5 Test Descriptions (Non-roaming) | |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5.1 General | The Interoperability Test Descriptions (TDs) defined in the following clauses are derived from the Test Purposes (TPs) specified in ETSI TS 103 878-1 [1], where each TD may realize one or more TPs. Each TD contains three parts: 1) The TD itself in tabular format. 2) The call flow associated to the TD. 3) A textual desc... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5.2 Test Descriptions | |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5.2.1 UE IPv6 address allocation | Interoperability Test Description Identifier: TD_NRMI_IPAA_01 Objective: To perform that UE can only get IPv6 prefix from 5GC while PDU session is created. Summary: On successful PDU session establishment, the UE should only get IPv6 prefix. CLAT generates an IPv4 address using IPv4 prefix 192.0.0.0/29. The session may... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5.2.2 DNS/DNS64 address allocation | Interoperability Test Description Identifier: TD_NRMI_ DNSAA _01 Objective: To perform that UE gets DNS64 server address from 5GC while PDU session is created. The session may be initiated by a UE or a network. Summary: On successful PDU session establishment, the UE should get DNS/DNS64 IP address. Configuration: CF_5... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5.2.3 NAT64 prefix discovery | Interoperability Test Description Identifier: TD_NRMI_PRFD_01 Objective: To demonstrate UE gets NAT64 prefix from DNS64 server Summary: On a successful DNS query, UE gets information about the presence (or absence) of NAT64, and one or more NAT64 prefix used for protocol translation Configuration: CF_5G_IPv6only_NRMI S... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5.2.4 Access of Internet IPv4 servers | Interoperability Test Description Identifier: TD_NRMI_AC4_01 Objective: To demonstrate that UE connects to IPv4 HTTP servers in the case of that UE learned the server's IPv6 address with a DNS query for IPv4 server's domain name. Summary: On the successful access to Internet IPv4 servers, UE should get IPv4-embedded IP... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 5.2.5 Access of Internet IPv6 servers | Interoperability Test Description Identifier: TD_NRMI_AC6_01 Objective: To demonstrate that UE connects to IPv6 HTTP servers in the case of that UE learned the server's IPv6 address with a DNS query for IPv6 server's domain name. Summary: On the successful access of Internet HTTP IPv6 servers, UE reaches the IPv6 serve... |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 6 Test Descriptions (Roaming with local breakout) | Since the interfaces are same with test descriptions for non-roaming test configuration. Test descriptions described in clause 5 for CF_5G_IPv6only_NRMI can be reused for configuration CF_5G_IPv6only_RMIL. |
63cc86bf1814592b7f8fcca71e064a3f | 103 878-2 | 7 Test Descriptions (Roaming with home routed) | Since the interfaces are same with test descriptions for non-roaming test configuration. Test descriptions described in clause 5 for CF_5G_IPv6only_NRMI can be reused for configuration CF_5G_IPv6only_RMIH. ETSI ETSI TS 103 878-2 V1.1.1 (2025-05) 19 History Document history V1.1.1 May 2025 Publication |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 1 Scope | The present document describes the PEMEA Instant Message capability for PEMEA 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 ... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 2 References | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 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... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 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... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 3 Definition of terms, symbols and abbreviations | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 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 ... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 3.2 Symbols | Void. |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Application Provider App Application EDS Emergency Data Send (message) ETSI European Telecommunications Standards Institute HELD HTTP-Enabled Location Delivery HTTP Hyper-Text Transfer Protocol IETF Internet Engineering Task Force IM Instan... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 4 PEMEA capability extensions | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 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... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 4.2 Service support indication and response | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 4.2.1 Service definition | ETSI TS 103 478 [1] defines the instant message, "IM", typeOfInfo in Table 10, but does not elaborate further on protocols in Table 11. The present document provides a concrete definition of the "IM" typeOfInfo in PEMEA through the specification of a protocol value. Table 1: Extended AP Information Type Protocol Regist... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 4.2.2 Service support indication | AP needing to indicate that the Application it is serving can support instant messaging using the PEMEA protocol would include the following information element in the apMoreInformation element of the EDS associated with the emergency session: <information typeOfInfo="IM" protocol="PEMEA"> https://ap.example.pemea.help... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 4.2.3 Service support response | A terminating node that can support the "IM" "PEMEA" capability includes this capability in the apMoreInformation element returned to the AP in the onCapSupportPost. This is described in clause 11.1.4 of ETSI TS 103 478 [1] with the value for "IM" "PEMEA" provided in the example below. <apMoreInformation xmlns="urn:pem... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 5 Security | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 5.1 Transport security | The chat-room service is identified to potential room participants as an HTTPS URI. The connection is made using TLS 1.3 but may be made using TLS 1.2 but shall not fallback below TLS 1.2. The connecting participant shall authenticate to the chat-room service using domain certificates and a Bearer token [4]. Once the c... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 5.2 Security token usage | The HTTP Authorization header field is defined in IETF RFC 2617 [3] 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... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6 Procedures and signalling | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.1 Service invocation | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.1.1 Service invocation procedures | Once the terminating PSP or PSAP has responded to the AP that it can support the PEMEA IM service then the AP shall be capable of accepting a service invocation on the provided URI at any time. The AP shall only accept an IM service invocation from the PIM or tPSP that sent the onCapSupportPost message. ETSI ETSI TS 10... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.1.2 Service invocation object | The PIM/tPSP invokes the IM service in the AP by posting to the URI provided in the IM 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 chat room URI as well as indicates how the AP should authenticate its... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.2 Chat-room creation and deletion | The chat-room is created by the chat-server under direction of the PSAP call-taker via the PIM or tPSP. When the chat-room is created, a logging function shall be created with it to scribe all messages into and out of the chat-room. The chat-room may also contain a chat-bot that is used to invoke services, such as tran... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.3 Chat-room creation, JOIN, and ERROR signalling | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.3.1 Semantics | The figure in the following sub clauses show the signalling involved in establishing and subsequently joining a PEMEA chat session. By necessity the diagrams show four distinctive types of signalling: • Semantic signalling across the Pa interface between the App and the AP is explicitly not defined in PEMEA. So, while ... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.3.2 IM service invocation | Figure 2: IM service invocation 1) App initiates and emergency session with the AP over the Pa interface indicating that it can support the Instant messaging. 2) The AP creates an EDS message from the data provided by the App and includes the PEMEA instant messaging protocol capability. The AP then sends the EDS into t... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.3.3 JOIN message flow | Figure 3: IM JOIN flow Once the IM service has been invoked in the AP, then the PSAP call-taker and Caller join the chat-room: 1) The PSAP call-taker joins the chat-room. 2) The chat-room writes a log to the chat-log indicating that the PSAP has joined the chat-room. 3) The chat-room responds to the PSAP with the curre... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.3.4 ERROR message flow | The error message is sent from the chat-room to a participant in two circumstance: 1) When the username and role received in a JOIN message are already in use by an active user in the chat-room. In this case, the user of the App is informed by the AP and selects a new username before attempting to re-join the room. ETS... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.4 TEXT_MESSAGE flow | Figure 5: TEXT_MESSAGE signalling flow Once the AP has joined the chat-room it is able to send text messages to the other participants in the room: 1) The App user sends the test message (e.g. "Help Me") to the AP over the Pa interface. 2) The AP takes the user's message and creates a TEXT_MESSAGE for transmission to t... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.5 REPLY message signalling | The REPLY message allows a user to respond to a specific message. This ensures that the context of the response is maintained in the event that subsequent text messages have been exchanged. A REPLY may be sent in reference to a TEXT_MESSAGE or another REPLY message. The REPLY message is similar to the TEXT_MESSAGE but ... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.6 Message translations and signalling | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.6.1 Overview of the translation functionality | Language translation is an optional function of the chat-room. However, support of the capability is recommended given the primary function of PEMEA is to support application roaming which may result in the call-taker and caller conversing in different languages. IM functions in the AP shall accept any translation mess... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.6.2 TEXT_MESSAGE translation example | Suppose that there are three languages in use in the chat-room, English (en), Spanish (es) and French (fr), and it received the following TEXT_MESSAGE: { "id":"5dd2bd8ba5568000079fa11c", "type":"TEXT_MESSAGE", "message":{ "language":"es", "text":"hola" }, "room":"ttRRkzORz", "user":{ "name":"PSAP-XqwFbQ-A", "role":"PSA... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.6.3 REPLY message translation example | Suppose that there are three languages in use in the chat-room, English (en), Spanish (es) and French (fr), and it received the following REPLY. { "id":"5dd2bd8ba5568000079fa1kkc", "reference":"5dd2bd8ba5568000079fa11c", "type":"REPLY", "message":{ "language":"en", "text":"I need help" }, "room":"ttRRkzORz", "user":{ "... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 6.7 Disconnects and reconnects | Despite communications network being reliable, accidental disconnects owing to temporary issues do still occur. PEMEA does not define how the AP and the App communicate, though some high-level semantics for IM are described in the present document. The present document describes communication between the authorized ent... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7 IM PEMEA message and type definitions | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.1 Overview | The IM PEMEA protocol messages are defined as a series of JSON documents exchanged between the AP or PEMEA terminating node and a "chat room" established inside the secure emergency network . The chat room is established solely for communications with a single emergency session. Each emergency session requiring the use... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.2 Data types | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.2.1 languageList | Is an array containing the list of languages that the user can read and write. The languages may be any of the pertinent languages from the IANA language subtag registry [2]. At least one language shall be defined. Where more than one language is provided they should be ordered based on preference with the most preferr... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.2.2 room | Is a unique string providing a name for the chat-room. This is usually the URI used to specify the room attachment provided when the chat service is invoked by the PSAP. |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.2.3 timestamp | All messages are sent with a timestamp and to avoid offsets, time zones, daylight savings changes etc, the time is always absolute. It is specified as an integer in milliseconds since the UTC epoch of 00:00:00 1st January 1970. |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.2.4 user | Defines a user in the chat-room. It consists of: • name; • role. The name is a string that identifies a handle to which the user relates, this may be their name "George" for example, or their telephone number, tel: +34666554433 for example. The role defines the type of user that is associated with the name. The recomme... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.2.5 userInfo | Is used to combine information about the user: • user: defined in clause 7.2.4; • languages: languageList defined in clause 7.2.1; • status. The status field is used to describe what the user is doing. Table 5: UserInfo status values Status Description ONLINE The user is connected to the chat-room. This may be a new us... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.2.6 message | Is a container used to convey text and the associated language in which the text is written. Table 6: message container elements Element NAME Description text The information to be conveyed. language The language abbreviation as specified by IANA in [2] in which the text is written. ETSI ETSI TS 103 756 V1.1.1 (2021-11... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.3 JOIN message | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.3.1 Message overview | The JOIN message is the message sent from the participant to the chat-room when the user wants to join the chat. This may be the AP, the PSAP-CPE or another trusted user. The JOIN message is resent if for some reason the connection between the entity and the chat room is lost but the chat is not concluded. The JOIN mes... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.3.2 Examples | The JOIN message is also used to reconnect to the chat-room in the case that the connection terminated, AP or chat- server restarted. In this case, the AP will set the since value to be the time that the AP knew it last had a connection to the chat-room, often this will be last received message from the chat-room. On a... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.4 ERROR message | |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.4.1 Message overview | The ERROR message is the message sent from the chat-room to a participant when the chat-room is not able to process the message sent by the participant. There are two cases identified and these are described in clause 6.3.4. The ERROR message consists of the following required fields. ETSI ETSI TS 103 756 V1.1.1 (2021-... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.4.2 Examples | { "type":"ERROR", "room": "https://chatroom.example.com:2040/djhuhiuhuihbjkbjbjhywe90ruj "reasonCode":"duplicateName", "reason":"Username:John, Role:MED, already exists" "timestamp": 1574092280231 } |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.5 USER_LIST message | The USER_LIST message is sent to all participants in the chat room whenever a user enters and leaves the chat-room. Table 10: USER_LIST message fields and description Element Name Description type "USER_LIST" The message being sent by the chat-room to the participants. room String identifying the chat-room. timestamp I... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.6 TEXT_MESSAGE message | The text message is used by a chat-room participant to contribute to the chat-room dialogue. Every message has an identifier associated with chat-room so that it can be uniquely identified. This is important to allow translations and replies to be linked to the original message to which they refer. The text message is ... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.7 REPLY message | The reply message allows a participant in the chat-room to respond to a specific message sent by another user in the chat-room. This is important to ensure context between messages is maintained when there are lots of messages or more than two active participants in the chat-room. After the chat-room server receives a ... |
98eb43f62e84db41de03366d476b1a18 | 103 756 | 7.8 TRANSLATION message | The translation message is sent when the chat-room supports a translation service (this may be an automatic service). The translation message indicates which message it is translating and then includes a list of each of the translations encoded as a "message" type. The message is translated into the set of languages sp... |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 1 Scope | The present document describes interoperability, re-use and enhancement of PEMEA and Emergency Services IP network (ESInet) components to ensure seamless integration of Internet Apps and traditional telecommunications service provider solutions and future emergency services offerings. An understanding of the PEMEA arch... |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 2 References | |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 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... |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 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... |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 3 Definition of terms, symbols and abbreviations | |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 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 au... |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 3.2 Symbols | Void. |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Application Provider App Application ASP Aggregation Service Provider BCF Border Control Function ECRF Emergency Call Routing Function EDR Emergency Data Received (message) EDS Emergency Data Send (message) ESInet Emergency Services IP netw... |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 4 Integrated network view | |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 4.1 Introduction | The ESInet and PEMEA architecture have nodes that perform similar functions but in quite different ways. Consequently there is a need for some of the functions to sit side by side, while some of the more common functionalities can be shared. |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 4.2 PEMEA ESInet interworking beyond the SPIF | ETSI TS 103 478 [1] defines a basic interworking between PEMEA and SIP via an entity called the SIP PEMEA Interworking Function (SPIF). In this approach, in the absence of a global forest guide network or local public ECRF, an OTT terminal can acquire the SIP address of the local ESInet BCF using the PEMEA network. Thi... |
ce3cd8d885f774eee3b702db9e67f94c | 103 755 | 4.3 PEMEA ESInet interworking architecture | The architecture for PEMEA and ESInet node sharing is shown in Figure 1. ETSI ETSI TS 103 755 V1.1.1 (2022-06) 8 Figure 1: PEMEA and ESInet shared services network architecture The main operations and interfaces are described in more detail in subsequent clauses of the present document. The PSP acts as the gatekeeping ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.