hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3ca377d4c5751335835aa6befc637a62 | 103 840 | 7 oneM2M2 CSE Performance Descriptor (OCPD) | The objective of the OCPD sub-model on figure 4 is to describe the service layer. To do this, it describes the interconnection between CSEs (IN-CSE, MN-CSE, ASN), the impact of the implementation choices of a CSE by a supplier, the deployment on equipment taking into account their processing capabilities, their memory ... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 8 oneM2M2 Solution Deployment Descriptor (OSDD) | The OSDD model on figure 5 describes the hardware platform that hosts the IoT application. This infrastructure is made of multiple nodes of different types, interconnected by a network. This model quantifies the capacities (memory storage, processing capabilities, location) of the physical nodes and the underlying comm... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 9 Example of instantiation | The MM proposed in the present document is instantiated to represent the traffic lights use case of document [i.5]. It includes a simple execution infrastructure, the deployment of CSEs and the oneM2M resources necessary to represent this scenario. The instance of the meta-model can be presented using different views. ... |
3ca377d4c5751335835aa6befc637a62 | 103 840 | 10 Conclusions | The present document gives a detailed view of a model able to describe at a high level, a oneM2M IoT system and to evaluate the performance of such a system. The meta model developed in clause 4 gives an overview of the model. The different parts are detailed in clauses 6, 7 and 8. This meta model makes it possible to ... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 1 Scope | The present document specifies the transmission of IPv6 packets over the ETSI GeoNetworking protocol for ITS-G5 and as defined in ETSI TS 103 836-4-1 [6] via a protocol adaptation sub-layer referred to as the GN6ASL (GeoNetworking to IPv6 Adaptation Sub-Layer). The scope of the present document is limited to the GN6ASL... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 2 References | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 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... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 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... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 3 Definition of terms, symbols and abbreviations | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 836-3 [4], IETF RFC 4861 [10], IETF RFC 8504 [i.3], IETF RFC 4885 [i.2] and the following apply: geographical virtual link: link-local multicast-capable virtual link spanning multiple physical links with geographically scoped boundaries GN6 adapta... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: GEOMAX Size of the largest GeoNetworking header GN_SAP GeoNetworking Service Access Point MTUAL Maximum transmission unit offered by the protocol layer below GeoNetworking MTUGN6 Maximum transmission unit offered by GN6ASL to IPv6 MTUVI Typical maxi... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AL Access Layer ASN.1 Abstract Syntax Notation One BER Basic Encoding Rules CGA Cryptographically Generated Addresses DGVL Dynamic Geographical Virtual Link EDCA Enhanced Distributed Channel Access EGN6 Extended GeoNetworking-IPv6 EIID Extende... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 4 GN6ASL in the ITS station architecture | With respect to the ITS station reference architecture, the present document only affects the Networking & Transport layer. As depicted in figure 1, within the Networking & Transport layer, the present document introduces GN6ASL, an adaptation sub-layer for the transmission of IPv6 packets over the GeoNetworking protoc... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5 IPv6 link models and interfaces | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.1 Rationale | The Neighbor Discovery (ND) protocol specified in IETF RFC 4861 [10] is a mandatory part of IPv6 stacks that includes functionalities such as Router and Prefix Discovery as well as Address Resolution and Neighbor Unreachability Detection. Some of ND's services use link-layer multicast addresses. This implies that the l... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.2 Properties of supported IPv6 link models | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.2.1 Geographical virtual links | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.2.1.0 Overview | A Geographical Virtual Link (GVL) is a link-local multicast-capable virtual link spanning multiple physical links with geographically scoped boundaries. GN6ASL of a GeoAdhoc router shall support GVLs. Each GVL shall be associated with one single GeoNetworking GEOBROADCAST/GEOANYCAST area (also called geoarea in ETSI TS... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.2.1.1 Static geographical virtual links | A Static Geographical Virtual Link (SGVL) is a GVL whose GVL Area shall be: • derived from a received GeoNetworking header encapsulating a Router Advertisements (RA) message (see IETF RFC 4861 [10]) as described in clause 10.2.1; or • assigned by the ITS station management entity only in roadside ITS stations. When no ... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.2.1.2 Dynamic geographical virtual links | A Dyamic Geographical Virtual Link (DGVL) is a GVL whose GVL Area may be modified. If the default SAP described in clause C.1 is adopted (GN6_SAP), the GVL Area shall be assigned by the ITS station management entity. If the experimental SAP described in clause C.2 is adopted (EGN6_SAP), the GVL Area shall be assigned o... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.2.2 Topological virtual links | A Topological Virtual Link (TVL) is a link-local multicast-capable virtual link spanning multiple physical links with topologically scoped boundaries. One and only one TVL shall exist per ItsGnIfEntry. The TVL shall be automatically created when the interface associated to the ItsGnIfEntry is enabled. The TVL does not ... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.2.3 Virtual links indexing | Given an ItsGnIfEntry, each virtual link shall be uniquely identified by the index itsGn6aslVLIndex. The TVL shall have itsGn6aslVLIndex equal to 0. The DGVL shall have itsGn6aslVLIndex equal to 1. SGVLs shall have itsGn6aslVLIndex values between 2 and itsGn6aslVLIndexMax. When enabled, a SGVL shall be assigned the low... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.3 Properties of virtual interfaces | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.3.1 Number and types of virtual interfaces | The IPv6 virtual link types described in clause 5.2 shall be provided by GN6ASL to IPv6 in the form of virtual network interfaces. Virtual network interfaces may be associated to either GVLs or TVLs. One single virtual interface shall be associated to one GVL or one TVL. One or several virtual interfaces can be associa... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.3.2 Usage of specific virtual interfaces | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 5.3.2.1 Ethernet V2.0/IEEE 802.3 LAN virtual interfaces | Virtual network interfaces of type Ethernet V2.0/IEEE 802.3 LAN as specified in IEEE 802.3:2008 [30] shall be supported by GN6ASL for the transmission of IPv6 packets over GeoNetworking protocol specified in ETSI TS 103 836-4-1 [6]. The transmission of IPv6 packets over GeoNetworking protocol specified in ETSI TS 103 8... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 6 Bridging support | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 6.1 Rationale | In the ETSI ITS GeoNetworking network architecture specified in ETSI TS 103 836-3 [4], IP connectivity of ITS stations is provided by mobile routers and access routers. In particular, an access router provides an ad hoc network with access to the Internet (see ETSI TS 103 836-3 [4]), while a mobile router provides IP c... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 6.2 Required properties | A GeoAdhoc router where the GeoNetworking protocol runs on top of a link-layer protocol that supports an integration function in accordance with IEEE 802.11:2020 [28] and IEEE 802.11bd:2022 [29] for passing bridge packets, shall provide at least one virtual interface that supports the same integration function at least... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 6.3 Media-dependent implementations | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 6.3.1 IEEE 802 integration service | IEEE 802.11:2020 [28] and IEEE 802.11bd:2022 [29] specify an integration service, which is a simplified version of the full 802.1D bridge functionality specified in IEEE 802.11Q:2014 [27] and supports the translation of IEEE 802.11:2020 [28]/IEEE 802.11bd:2022 [29] frames from/into Ethernet V2.0/IEEE 802.3:2008 [30] LA... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 8 Encapsulation characteristics | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 8.1 Maximum transmission unit | The MTU of a virtual interface associated with a GVL or TVL (MTUGN6) shall be set to a value that depends on the MTU of the access layer technology that transports the GeoNetworking protocol (MTUAL). In particular, MTUGN6 shall be less than or equal to MTUAL reduced by the size of the largest GeoNetworking protocol hea... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 8.2 Packet delivery | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 8.2.1 Outbound traffic | The following list describes the steps that shall be undertaken by the GN6ASL upon the transmission of an IPv6 packet over the GeoNetworking protocol. The procedure applies to both IPv6 packets generated by the ITS station itself and packets being forwarded by the IPv6 protocol layer residing in the ITS station. The fo... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 8.2.2 Inbound traffic | The following list describes the steps that shall be undertaken by the GN6ASL upon the reception of a GeoNetworking header transporting an IPv6 header. The following procedure only describes the logical steps that shall be undertaken by the GN6ASL and not the steps undertaken by the virtual interfaces (which are implem... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 8.3 Frame format | The present document does not introduce new frame formats. Neither modifications to the IPv6 headers defined in IETF RFC 8200 [7], IETF RFC 4291 [8], IETF RFC 4007 [9], IETF RFC 4861 [10] and IETF RFC 4862 [12] are introduced, nor changes to the format of the GeoNetworking header as defined in ETSI TS 103 836-4-1 [6] a... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9 IPv6 multicast and anycast support | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9.1 Overview | This clause describes how standard IPv6 multicast addressing is supported over the GeoNetworking protocol. Standard IPv6 multicast addressing refers to non-geographic IPv6 multicast addressing, i.e. multicast addresses that are created according to IPv6 specifications and that do not embed any sort of specification of ... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9.2 IPv6 multicast support | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9.2.1 IPv6 link-local multicast | IPv6 link-local multicast traffic may be transmitted via the GN6ASL on GVLs or TVL. An IPv6 packet with a link-local multicast destination address being transmitted via a GVL shall be transmitted by the GeoNetworking protocol using a GEOBROADCAST header as defined in ETSI TS 103 836-4-1 [6]. The fields describing the d... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9.2.2 IPv6 wider-scope multicast | IPv6 multicast traffic with scope wider than link-local shall be transmitted over the GeoNetworking protocol only on GVLs. The GN6ASL specified in the present document is affected by the transmission of wider-scope IPv6 multicast traffic only with regard to the multicasting of this traffic on a GVL. In fact, the IPv6 p... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9.2.3 Geocasting of IPv6 multicast traffic | Based on the properties of GVLs, it is possible to realize geocasting of IPv6 traffic without introducing new IPv6 multicast groups or address types. Both link-local and wider-scope multicast IPv6 traffic can be used. With the first, any GeoAdhoc router attached to a shared GVL can geocast IPv6 traffic by simply addres... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9.3 IPv6 anycast support | IPv6 anycast traffic addressed to IPv6 addresses different than the IPv6 reserved subnet anycast address specified in IETF RFC 2526 [25] containing the anycast identifier itsGn6aslGeoAnycastID cannot be distinguished from IPv6 unicast traffic. Therefore the same procedures described in clause 8.2 for IPv6 unicast traff... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 9.4 Geographic IPv6 anycast support | The present document introduces the usage of an IPv6 reserved subnet anycast address specified in IETF RFC 2526 [25] for geographic IPv6 anycast support. This IPv6 reserved subnet anycast address is characterized by the anycast identifier to be assigned by IANA here referred to as itsGn6aslGeoAnycastID. IPv6 anycast tr... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10 IPv6 neighbor discovery support | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.1 On-link determination | The IPv6 on-link determination is defined in IETF RFC 4861 [10] and updated in IETF RFC 5942 [11]. IPv6 determines a prefix to be on-link if it is included in the Prefix List specified in IETF RFC 4861 [10] for that link. A prefix is added to the Prefix List upon the receipt of a valid Router Advertisement (RA) that sp... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.2 Address configuration | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.2.1 Stateless address autoconfiguration | IPv6 SLAAC as specified in IETF RFC 4862 [12] shall be supported by ITS stations compliant to the present document. The IPv6 router issuing Router Advertisements is typically the access router defined in ETSI TS 103 836-3 [4]. In a typical scenario, this access router is part of the road-side ITS station and allows veh... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.2.2 Stateful address configuration | IPv6 stateful address configuration should not be used in deployments of the present specification because of the higher latency due to the several round-trip signalling messages and the higher administrative effort required for the management of IPv6 routers. |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.2.3 Manual address configuration | In operational deployments, IPv6 addresses shall not be manually added to any virtual interface. Manually configured addresses shall only be used with administratively configured SGVLs on road-side ITS stations. NOTE: The usage of manually configured addresses might decrease the effectiveness of pseudonym change scheme... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.3 Address resolution | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.3.1 Non-ND-based address resolution | According to IPv6 ND as outlined in IETF RFC 4861 [10], address resolution is performed only on non-multicast addresses that are determined to be on-link and for which the sender does not know the corresponding link-layer address. In the case of transmission of IPv6 packets via the GN6ASL, whenever the IPv6 address of ... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.3.2 ND-based address resolution | An ITS station compliant with the present document should use IPv6 addresses containing IIDs that directly resolve to GN_Addr, such that non-ND-based address resolution described in clause 10.3.1 can be applied. When this is not possible, an implementation of the present document may adopt ND-based address resolution o... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.4 Neighbor unreachability detection | When IPv6 packets are transmitted over the GeoNetworking protocol via the GN6ASL, the IPv6 next hop may be several physical hops away from the source. In some deployments, e.g. where the connectivity is intermittent and available for short time intervals, frequent execution of the NUD procedure as specified in IETF RFC... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 10.5 Protocol constants | IPv6 ND protocol constants are listed in IETF RFC 4861 [10], clause 10. Implementations of the present document may utilize different values of these parameters in a technology- and scenario-specific way. System specifications for the implementation of the present document shall provide such values. NOTE: It is recomme... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 11 Support for pseudonym change | |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 11.1 Rationale | Location privacy concerns may arise due to the GVLs' binding between geographical areas and IPv6 prefixes. This means that a node, whose IID suffix is statically and permanently configured, could be geographically tracked by an attacker located in the Internet that gets to know the binding for a set of areas/IPv6 prefi... |
82687c5c9bd00915b3b61f5bde78f307 | 103 836-6-1 | 11.2 Required operations | In an implementation-specific way, the GN6ASL shall be notified every time the GN_Addr in use by the GeoNetworking protocol entity changes. Upon such a notification, the GN6ASL shall immediately modify the MAC address of each virtual interface. If NEMO BS is supported by the ITS station implementing the GN6ASL and a vi... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 1 Scope | The present document describes the PEMEA Real-Time Text (RTT) 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 unde... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 2 References | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 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... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 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... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 3 Definition of terms, symbols and abbreviations | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 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 ... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 3.2 Symbols | Void. |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 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 BEL audible Bell sound BS Back Space CPE Customer Premises Equipm... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 4 PEMEA capability extensions | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 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 Provide... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 4.2 Service support indication and response | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 4.2.1 Service definition | ETSI TS 103 478 [1] defines the Real-Time Text, "RTT", typeOfInfo in Table 10, but does not elaborate further on protocols in Table 11. The present document provides a concrete definition of the "RTT" typeOfInfo in PEMEA through the present document of a protocol value. The definition in Table 1 shall be considered as ... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 4.2.2 Service support indication | An AP needing to indicate that the Application it is serving can support Real-Time Text using the PEMEA protocol would include the following information element in the apMoreInformation element of the EDS associated with the emergency session: <information typeOfInfo="RTT" protocol="PEMEA"> https://ap.example.pemea.hel... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 4.2.3 Service support response | A terminating node that can support the "RTT" "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 "RTT" "PEMEA" provided in the example below: <apMoreInformation xmlns="urn:p... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 4.2.4 Auto response service | The original intent of many emergency applications was to provide ancillary data to the PSAP that was associated with an emergency voice call that the PSAP had, or soon would, receive. As a consequence, a PIM or tPSP usually notifies the PSAP-CPE when an EDS has arrived, but does not respond to the AP until a PSAP call... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 5 Mapping to T.140 | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 5.1 T.140 special character support | Recommendation ITU-T T.140 [3] defines requirements and procedures for RTT systems. For the most part these are mapped directly. With the movement to modern communications system however, some of the requirements in Recommendation ITU-T T.140 [3] are no longer relevant. In other cases, functionality is not provided as ... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 5.2 ESC character sequence support | ESC character sequences in the present document are a set of characters bounded by ESC characters (0x1B) on either side. For example 0x1B:)0x1B may display a smiley face. The present document does not define any ESC character sequences nor does it provide any guidance on rendering or interpretation beyond all character... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 6 Security | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 6.1 Transport security | The RTT 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 RTT service using a Bearer token in the HTTP Authentication header field as describ... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 6.2 Security token usage | The HTTP Authorization header field is defined in IETF RFC 2617 [5] 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... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7 Procedures and signalling | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.1 Service invocation | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.1.1 Service invocation procedures | Once the terminating PSP or PSAP has responded to the AP that it can support the PEMEA RTT 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 RTT service invocation from the PIM or tPSP that sent the onCapSupportPost message. The PSAP invo... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.1.2 Service invocation object | The PIM/tPSP invokes the RTT PEMEA service in the AP by posting to the URI provided in the RTT 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 RTT-session room URI as well as a security token and correspo... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.2 RTT-session room creation and deletion | The RTT-session room is created by the RTT server under direction of the PSAP call-taker via the PIM or tPSP. When the RTT-session room is created, a logging function shall be created with it to scribe all messages into and out of the room. This flow is shown in Figure 1. ETSI ETSI TS 103 871 V1.2.1 (2024-08) 14 Figure... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.3.1 Semantics | The figures in the following sub-clauses show the signalling involved in establishing and subsequently joining a PEMEA RTT 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 ... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.3.2 RTT service invocation | Figure 2: RTT service invocation 1) App initiates an emergency session with the AP over the Pa interface indicating that it can support the RTT/PEMEA capability. 2) The AP creates an EDS message from the data provided by the App and includes the RTT/PEMEA protocol capability. The AP then sends the EDS into the PEMEA ne... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.3.3 JOIN message flow | Figure 3: RTT JOIN message flow Once the RTT/PEMEA service has been invoked in the AP, then the PSAP call-taker and Caller join the RTT-Session: 1) The PSAP call-taker connects to the RTT-Session room passing in their authentication token in the Authorization HTTP header field in accordance with clause 6.2. 2) RTT-Sess... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.3.4 ERROR message flow | The RTT-session room sending, and user receiving, a USER_LIST message indicates a successful joining of the RTT session, a join request may also be rejected by the RTT-session room by sending an ERROR message. A JOIN message shall be rejected by the RTT-session room if the uniqueId is already in use by an active/ONLINE... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.3.5 TEXT_MESSAGE flow | Figure 4: TEXT_MESSAGE signalling flow Once the AP has joined the RTT-Session room it is able to send characters to the other participants in the session. This is done using the TEXT_MESSAGE. The App shall send characters one at a time to the AP. The AP may buffer characters into a single TEXT_MESSAGE, but shall send t... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 7.4 Disconnects and reconnects | Despite communications networks 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 RTT are described in the present document. The present document describes communication between the authorized e... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8 RTT PEMEA message and type definitions | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.1 Overview | The RTT PEMEA protocol messages are defined as a series of JSON documents exchanged between the AP or PEMEA terminating node and an "RTT-session room" established inside the secure emergency network. The RTT-session room is established solely for communications with a single emergency session. Each emergency session re... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.2 Data types | |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.2.1 language | Is the language that the user will be communicating in through the RTT session. The language may be any of the pertinent languages from the IANA language subtag registry [4]. |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.2.2 room | Is a unique string providing a name for the RTT-session room. This is usually the URI used to specify the room attachment provided when the RTT service is invoked by the PSAP. |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.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. |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.2.4 user | Defines a user in the RTT-session room. It consists of: • name; • role; • uniqueId. 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 th... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.2.5 userInfo | Is used to combine information about the user: • user: defined in clause 8.2.4; • language: defined in clause 8.2.1; • status. The status field is used to describe what the user is doing. Table 6: UserInfo status values Status Description ONLINE The user is in the RTT-session. This may be a new user joining the RTT-ses... |
56af5b2eee68df16f6b1017582fa4ab5 | 103 871 | 8.2.6 Void |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.