hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 4.1 Background | The present document is part of a series of ETSI technical specifications specifying requirements to engineer and operate the MAP-E transition technology end to end across a cable operator's network. Its implementation would ensure the network provider can continue to provide business continuity throughout the depletio... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 4.2 General Overview | An objective of deploying the IPv6 transition technology is to provide a seamless experience to IPv4 users accessing IPv4 network services through new IPv6 only networks and to enable current and new content to be delivered seamlessly to the IPv4 users by deploying MAP-E. It should be noted that Cable broadband access ... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 5 Gap Analysis | |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 5.1 Consideration | The engineering and operational requirements applying ETSI TS 101 569-1 [1] need to be specified with the following design objective to define the logical and physical parameters to allow for customers to access the public IP Internet across an IPv6 network using MAP-E. |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 5.2 Overview | Mapping Address and Port (MAP) refers to two similar technologies. MAP is an approach that uses stateless address sharing at the service provider Border Router (BR) and stateful address sharing at the CPE; while transporting packets over IPv6: • Leveraging distributed statefulness. • Leveraging IPv6 route aggregation. ... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6 Domain Functionality | |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.1 End to End Network Domains | In order to operate the IPv6 transition technology it has to be engineered and verified end to end across the cable broadband network addressing each of the domains as illustrated in figure 2. ETSI ETSI TS 103 443-4 V1.1.1 (2016-08) 13 Figure 2: Illustration of the Cable Broadband Network Domains |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.2 CPE Home Network Domain | MAP-E enables a customer's device that is V4 to be supported across the Cable network when communicating to a V4 service. Functionality to be engineered in the cable network: • The cable residential gateway device shall have the MAP-CE function as specified by IETF RFC 7597 [18]. • IPv4 packet size is 1 500 bytes. When... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.3 Access Network Domain | Functionality to be engineered in the cable network: • The cable headend CMTS shall be capable of IPv6 connectivity for customer traffic. • The DOCSIS management between the Cable Modem and CMTS may be IPv4 or IPv6. ETSI ETSI TS 103 443-4 V1.1.1 (2016-08) 14 NOTE: There are no additional requirements on the HFC distrib... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.4 Core Network Domain | Functionality to be engineered in the cable network: • The core network routers shall support IPv6 routing and forwarding capabilities. • The MAP-BR shall be implemented as specified by IETF RFC 7597 [18]. Operation: A v6 client communicating with v6 service has direct end to end connectivity and does not utilize the M... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.5 Data Centre Domain | Functionality to be engineered in the cable network: There are no changes to the network DNS functionality required. The DNS shall be IPv6 capable. The DHCP server is inherently IPv6 only and shall include DHCP option for MAP-E as specified in IETF RFC 7598 [20]. |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.6 DMZ Service Domain | Functionality to be engineered in the cable network: • There are no specific operational requirements for the DMZ however it is strongly recommended that all services within the DMZ are IPv6 capable either by dual stack configuration or the use of V6/V4 load balancing. • V6/V4 load balancers allow V6 access to existing... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.7 Transit and Peering Service Domain | Functionality to be engineered in the cable network: There are no changes to be engineered when considering the transit and peering domain since the transmit and peering links are dual stack and support both IPv6 and IPv4 packets simultaneously and therefore no specific additional requirements are needed to be defined ... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.8 Management and Monitoring Domain | Functionality to be engineered in the cable network: • DOCSIS management between the CMTS and Cable Modem may remain deployed either using IPv4 or IPv6 addresses. • There is the additional functionality to monitor and manage the Cable Modem MAP-CE functionality. Similarly to manage and monitor the MAP-BR in order to pr... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 6.9 Security Domain | Functionality to be engineered in the cable network: • The cable modem packet classifiers shall be updated to support IPv6 filtering. • The continuity of the security of the end to end service shall be maintained when operating MAP-E, however the operational implications from MAP-E shall be minimized as specified in IE... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 7 Topologies | This clause explains the potential MAP-E domain topologies. At the time of writing, two topologies are possible, the integrated topology and the hairpin topology; however, depending on future hardware and software developments, additional topologies may be introduced. Use of the integrated topology would provide the mo... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 8 Technical Considerations | |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 8.1 General | The requirements of the MAP-E implementation are based on enabling seamless MAP connections without degradation in service, access, functionality or speed. It is currently not considered as a fully deployable solution for carrier grade networks but as experiences in its implementation evolve the support for this techno... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 8.2 LSN and CPE Requirements | The LSN device is placed in the edge of the network (IXPE) as the IPv4 gateway to perform de-capsulation on the egress from a 4in6 packet to a pure IPv4 packet. Requirement considerations for LSN are: • Hardware Topology • Logical Topology • Software/Hardware Features • Scalability • Resilience and Redundancy • IP Allo... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 8.3 CPE | The CPE is a device in customer's home to encapsulate the traffic on egress from a pure IPv4 packet to a 4in6 packet. Requirement considerations for MAP-E CPE are: • Hardware Topology • Logical Topology • Software/Hardware Features ETSI ETSI TS 103 443-4 V1.1.1 (2016-08) 17 • Scalability • Stability • IP Allocation/DHC... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 9 MAP-E Feature Requirements | The MAP-E features are as summarized in table 1 detailing for each function the requirement as required or optional with a brief description of each of the named functions. Table 1: Summary of MAP-E Features Requirements Functional Name Requirement Description MAP-E Required Main MAP-E, mapping of address & port - enca... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 10 Network Node Requirements | |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 10.1 Network node Hardware Feature/Topology | MAP-E uses an IPv4/IPv6 address and port mapping technique to associate an IPv4 address with an IPv6 address. This allows the automatic creation of tunnels between the Border Relay and the CPE Router. The format of the IPv6 address is the same as for MAP-T. In order to perform the mapping, MAP-E allows the provisioning... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 10.2 Integrated topology requirements | List of features required for both IPv4 and IPv6/L2 and L3 for an integrated topology solution: • MP BGP (as well 6PE and 6VPE) • BGP Community/32 bit AS • MPLS LDP (potentially only v4 native at present but the requirement for v6 native MPLS may become an absolute) • ECMP • QoS (v4/v6) - classification, priority queui... |
09793efbeb79348acc9dc6a73cc10991 | 103 443-4 | 10.3 Hairpin topology requirements | List of features required for both IPv4 and IPv6/L2 and L3 for a "hairpin topology" solution: • SNMP (transport over v4 and v6) v1/v2/v3 • ACLs/Prefix Listing (both v4/v6) • TACACS/RADIUS (v4/v6) • Syslog (event reporting for v4 & v6 as well as transporting over both protocols) • CoPP (v4/v6) • Netflowv9 (potentially p... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 1 Scope | The present document is divided into two parts. The first part provides the requirements and functional architecture while the second part provides the protocol and procedures for implementing the Pan-European Mobile Emergency Application (PEMEA). The first part identifies the key functional entities involved in the em... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 2 References | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 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... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 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... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 3 Definition of terms, symbols and abbreviations | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 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 ETSI ETSI TS 103 478 V1.3.1 (2025-07) 11 • privac... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 3.2 Symbols | Void. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AP Access Point AP Application Provider API Application Programming Interface App Application ASP Aggregating Service Provider BCF Border Control Function BSSID Basic Service Set IDentifier CID Cell IDentifier ECRF Emergency Call Routing Funct... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4 PEMEA architecture and functional entities | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.1 Introduction | The extensive deployment of existing mobile emergency applications and their interconnection into a Pan-European Emergency Application ecosystem has prompted the definition of entities identified in Figure 1. Figure 1: PEMEA Reference Architecture In some implementations functional entities may be owned and operated by... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.2 Functional entities overview | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.2.0 PEMEA Registration Authority | The PEMEA Registration Authority (PRA) is the entity that contains registrations for all currently valid PEMEA entities. The PRA accepts registrations from entities that conform to the PEMEA protocol and procedures and only registered entities may send or receive messages in the PEMEA network. The PRA provides a list o... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.2.1 Application (App) | Software that runs on a smartphone or mobile computing platform that is capable of making an emergency call using mobile network operator call control machinery (3G/4G/Wi-Fi®). Simultaneous to call establishment the App sends user authentication information to an Application Provider and subsequently sends location, co... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.2.2 Application Provider (AP) | The Application Provider (AP) is the entity that provides a mobile emergency application. It is responsible for authenticating the Application prior to accepting caller information from the App. The AP needs to format the data received from the App, possibly combining it with caller information stored in AP server, and... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.2.3 PSAP Service Provider (PSP) | The role of the PSAP Service Provider (PSP) is to take caller information from trusted sources and ensure that it is provided to the correct PSAP. Where the PSP directly serves the PSAP for which the information is destined, then it is referred to as the terminating-PSP (tPSP). If a PSP receives information that it kno... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.2.4 Aggregating Service Provider (ASP) | The primary role of the PSP is to ensure that accurate and trusted caller information is provided to the PSAP that is terminating an emergency call. A PSP may have knowledge of immediately adjacent terminating-PSPs but requiring a PSP to have a relationship with all other PSPs so that it can direct caller information t... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.2.5 PSAP Interface Module (PIM) | The PIM entity appears in other ETSI technical specifications involving PEMEA such as ETSI TS 103 755 [i.4], ETSI TS 103 756 [i.5], ETSI TS 103 871 [i.6], ETSI TS 103 872 [i.7], ETSI TS 103 945 [i.8] and ETSI TS 104 014 [i.9]. The PIM is a PEMEA entity which is a terminating node for the emergency communication that is... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.3 Interface definitions | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.3.1 Application Interface (Pa) | This is the interface used for communication between the Application and the Application Provider. The exact nature and communication on this interface are out of scope of the present document as this is the interface that allows Application Providers to implement and support service differentiation features in their p... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.3.2 Application Provider to PSAP Service Provider Interface (Ps) | This is the interface used by the Application Provider to push caller information to the PSAP Service Provider (PSP). This is a secure interface that requires mutual authentication between the AP and the PSP and a complying AP and PSP shall implement this interface in accordance with the details in the present document... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 4.3.4 PSAP Service Provider to PSAP Interface (Pp) | This interface is shown for completeness but is outside the scope of the present document. The PSP may provide a simple web interface to the PSAPs it serves or it may integrate the data flows into existing PSAP systems. How this is performed will vary from PSAP to PSAP and from PSP to PSP. Figure 3: Basic PEMEA PSAP In... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 5 PEMEA functional entity requirements | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 5.1 Introduction | PEMEA needs to be a secure network and it relies heavily on trust relationships between PSAPs and the entities that they allow to provide information to them. The architecture shown in Figure 1, shows applications connect to Application Providers (APs) that have trust relationships with PSAP Service Providers (PSPs) th... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 5.2 Application requirements | Even though the Application itself is out-of-scope of the present document, the Application has to fulfil the following requirements to be compliant with PEMEA: AA-1: The Application shall detect when the Application is being used and initiate an emergency call. AA-2: The Application shall authenticate itself to the AP... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 5.3 Application provider requirements | AP-1: The AP shall authenticate the application prior to accepting or processing caller information. AP-2: The AP shall procure a registered domain name and a domain certificate from a trusted certificate authority asserting ownership of the registered domain name to the AP. AP-3: The AP shall have a trust relationship... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 5.4 PSAP service provider requirements | PSP-1: A PSP shall procure a registered domain name and a domain certificate from a trusted certificate authority asserting ownership of the registered domain name to the PSP. PSP-2: The PSAP shall register the domain name with the PEMEA registration authority. PSP-3: A PSP shall identify itself to connecting entities ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 5.5 Aggregating service provider requirements | ASP-1: The ASP shall procure a registered domain name and a domain certificate from a trusted certificate authority asserting ownership of the registered domain name to the ASP. ASP-2: The ASP shall register the domain name with the PEMEA registration authority. ASP-3: The ASP shall authenticate itself to any PSP or AS... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 6 PEMEA Message Element Definitions | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 6.1 Introduction | To keep PEMEA simple there are only three required message types: 1) emergencyDataSend, used to send information from the AP ultimately to the PSP and PSAP 2) emergencyDataReceived, used by the node receiving the information that they got it and who they are sending it on to 3) error, used to indicate that something we... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 6.2 emergencyDataSend Information Elements | Table 1: emergencyDataSend message element definitions Element Inclusion Description Time To Live Mandatory Defines the number of hops allowed before message delivery stops. Receive Error Post Recommended When an entity receives an error message form the next hop and this element is provided, the entity receiving the e... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 6.3 emergencyDataReceived Information Elements | Table 4: PEMEA emergencyDataReceived information element definitions Element Inclusion Description Time Stamp Mandatory The time that this message was sent by the receiving node to the originating hop immediately preceding it. Route Mandatory Defines the nodes and the order through which the message has passed the node... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 6.4 error Information Elements | Table 5: PEMEA error information element definitions Element Inclusion Description Time Stamp Mandatory The time that this message was sent by the receiving node to the originating hop immediately preceding it. Reason Mandatory A token representing the kind of problem that occurred. Route Mandatory Defines the nodes an... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 6.5 PEMEA Confirmation Messages | The EDS, EDR and error messages described in the previous clauses are all hop-by-hop messages exchanged between adjacent nodes in order to get the caller information to the correct PSAP. PEMEA provides for extensions to enable the PSAP to request further information from the caller via the AP by including a capabilitie... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7 PEMEA Message Flows | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.1 Introduction | The Pa and Pp message flows are out of scope of the present document, so this clause only describes the Ps and Pr message flows. Establishment of the connections is assumed to occur prior to message exchanges occurring. Connection establishment procedures are covered in the detailed protocol clause. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.2 Ps message flows | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.2.1 Ps message flow description | The Ps interface is the interface between the AP and PSP. The connection originates from the AP making the AP the client and the PSP the server. The AP puts its data into an emergencyDataSend message (the precise format for this message is defined in a detailed protocol clause) and uses HTTP to deliver the message to t... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.2.2 Ps basic flow | Figure 4: Ps basic message flow In this flow the AP: 1) creates an emergencyDataSend message: - sets the time to live (ttl) to the number of hops the AP will allow before the message is dropped. The minimum value that the AP may set the ttl value to is 1 - adds its identity information to the route element - assembles ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.2.3 Ps error flow | Figure 5: Ps error flow In this flow the AP: 1) creates an emergencyDataSend message: - sets the time to live (ttl) to the number of hops the AP will allow before the message is dropped - adds its identity information to the route element - assembles and appends the location and other information - sends the message to... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.2.4 Ps routing flow | Figure 6: Ps routing flow In this flow the AP: 1) creates an emergencyDataSend message: - sets the time to live (ttl) to the number of hops the AP will allow before the message is dropped - adds its identity information to the route element - assembles and appends the location and other information - sends the message ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.3 Pr message flows | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.3.1 Pr message flow description | The Pr interface is the interface between the PSP and the ASP. The connection may be originated by either the PSP or the ASP depending on whether the PSP is forwarding the data or terminating the data. The sender (either the oPSP or the ASP) puts its data into an emergencyDataSend message (the format for this message i... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.3.2 Pr terminating-PSP basic flow | Figure 7: Pr basic message flow In this flow, the AP has sent an emergencyDataSend message to a PSP but that PSP did not serve the destination PSAP so it sent the message on to an ASP. This flow illustrates the ASP directing the emergencyDataSend message to a terminating PSP. ETSI ETSI TS 103 478 V1.3.1 (2025-07) 24 In... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.3.3 Pr error flow | Figure 8: Pr error flow In this flow the ASP: 1) receives the emergencyDataSend message from the oPSP 2) determines the correct tPSP and sends the corresponding response to the oPSP before closing the connection 3) decrements the time to live (ttl) in the received emergencyDataSend message Aggregating Service Provider ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 7.3.4 Pr end to end routing flow | Figure 9: Ps routing flow Application Provider Originating PSAP Service Provider emergencyDataSend(ttl, route:AP, Loc++) Aggregating Service Provider Determine Destination emergencyDataReceived(route:AP+oPSP, delivery) Determine Destination emergencyDataSend(ttl-1, route:AP+oPSP, Loc++) emergencyDataReceived(route:AP+o... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 8 PEMEA alignment with ETSI TS 103 479 | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 8.1 General alignment | PEMEA was intended to provide a stepping stone to the Core element for network independent access to emergency services ETSI TS 103 479 [i.1], and it does this by reusing many of the same data structure used in the IETF and 3GPP documents as well as ETSI TS 103 479 [i.1]. The core elements document [i.1] however, only ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 8.2 PEMEA to border control function | In this case the device is using SIP to make an emergency call. In order for the call to reach the correct ESInet it needs to first reach the BCF at the gateway to the ESInet. In an Over The Top (OTT) environment there is no direct association between the access network and the call service provider, so routing informa... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 8.3 PEMEA to Legacy Network Gateway | In this scenario, the call is originated through the Public Switch Telephone Network (PSTN) and needs to go through an LNG to enter the ESInet. The LNG requires a Location Interworking Function (LIF) in order to provide the location of the caller for further routing through the ESInet to the correct PSAP. The terminati... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 9 Message transportation and processing | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 9.1 HTTP usage | All messages are conveyed as XML over secure HTTP. The HTTP connection is established using mutual authentication in accordance with IETF RFC 2818 [1]. Cookies as defined in IETF RFC 2965 [2], shall not be used. Providers shall use the HTTP POST method to deliver emergencyDataSend messages in the body of the HTTP messa... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 9.2 Authenticating and authorizing PEMEA entities | All entities, APs, PSPs, PSAPs and ASPs need to have a PEMEA Identifier (PEMEA-ID) and this is provided by the PEMEA registry when an application is approved. The PEMEA registry provides a list of each entity, the entity type and entity's registered domain name. All PEMEA entities should load this information into thei... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 9.4 PEMEA XML Processing Rules | The PEMEA messages are specified as XML elements and are designed with explicit extension points. These extension points exist for two main reasons. Firstly, PEMEA needs to be capable of transferring intra-country messages between providers and agencies, and some countries and agencies have local requirements over and ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10 PEMEA XML structures and messages | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.1 Ps Introduction | This clause is broken into a series of parts, with each part describing important types and structures. It is broken down like this to try and help the reader understand how the messages are put together. Where deemed helpful in a clause an XML fragment showing how to use the structure is included. In clause 16 is the ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.2 Timestamps | PEMEA is specified using XML and timestamps are defined as XML dateTime types. While this definition does allow for the specification of timezone, all timeStamps contained in a route element shall be specified in UTC time. This ensures that if different entities in the message flow are in different timezone it is easy ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3 General types | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.1 pemea:posIntType | Type Values Description pemea:posIntType Zero and positive integers N/A |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.2 pemea:nodeType | Type Parameter Param-Type Presence Description pemea:nodeType position pemea:posIntType Mandatory A number representing the position of the node in the routing chain. The node initiating the message shall have a position of 0. timeStamp xs:dateTime Mandatory The date and time that the message was sent specified in UTC ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.3 pemea:hopsType | Type Parameter Param-Type Presence Description pemea:hopsType hop pemea:nodeType Mandatory List of nodes that the message has traversed. <hops> <hop position="0" timeStamp="2016-01-14T19:43:00.001Z"> <node>https://cooAP.example.com.be:2001/pemea/</node> </hop> <hop position="1" timeStamp="2016-01-14T19:43:00.098Z"> <no... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.4 pemea:routeType | Type Parameter Param-Type Presence Description pemea:routeType msgSeq xs:token Mandatory Message identifier provided by the initial originator of the emergencyDataSend message. In the present document this value is set by the AP. hops pemea:hopsType Mandatory The hops parameter contains the identity of each node throug... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.5 pemea:destinationType | Parameter Type Description pemea:destinationType xs:enumeration One of the following values: • PSAP • PSP • ASP |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.6 pemea:destinationNodeType | Type Param-Type Presence Description pemea:destinationNodeType xs:token Conditional If a destination node does not have a URI then it may describe itself using a name. Only a PSAP may use this option. xs:anyURI Conditional If the destination node is identifiable by a URI then it shall use this form. |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.7 pemea:deliveryType | Type Parameter Param-Type Presence Description pemea:deliveryType destType pemea:destinationType Mandatory Type of node the data was delivered: • PSAP • PSP • ASP See note. -- pemea:destinationNode Type Mandatory The name or address of the entity to which the message/data was delivered. NOTE: A PSP can deliver data to ... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.8 pemea:typeOfCallerIdType | Type Param-Type Presence Description pemea:typeOfCallerIdType xs:token Conditional If the caller identifier is not something that can be expressed as a URI, then it may use a token instead. xs:anyURI Conditional This is the normal form of caller identifier and any identifier that can be expressed as a URI shall use thi... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.9 pemea:callerIdType | Type Parameter Param-Type Presence Description pemea:callerIdType typeOfId xs:token Mandatory This is the type of identifier being used, in terms of what communications application the identifier is applicable to. Since these will grow over time, a registry of valid values is established in the present document. -- pem... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.13.1 pemea:accessDataType structure | Defines the inclusion of the network and Wi-Fi® types from HELD Measurements, IETF RFC 7105 [12]. This is defined a choice, so only one element may be present. Type Parameter Param-Type Presence Description pemea:accessDataType network cell:network (refers to urn:ietf:params:xml:ns:geopriv:lm :cell) Conditional Is pres... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.13.2 network | IETF RFC 7105 [12], clause 5.4 defines the cellular elements with the XML schema defined in clause 8.7 of IETF RFC 7105 [12]. The schema defines a number of different cell representations. Element Parameter PEMEA Presence Type Description network mcc Conditional element Mobile Country Code. A three digit code that repr... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 10.3.13.3 wifi | The elements for this clause are specified in IETF RFC 7105 [12], clause 5.3. Element Parameter PEMEA Presence Type Description wifi ap Mandatory element This element shall be present if the wifi element is included. The schema supports multiple Access Points (APs), however, only the serving AP is required. Element Par... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11 PEMEA Message Definition | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.1 emergencyDataSend Message | |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.1.1 emergencyDataSend message structure | The emergencyDataSend message is the means by which data is conveyed from the AP to the destination PSAP, all intermediary nodes transfer this type of message. Example does not show additional data. ETSI ETSI TS 103 478 V1.3.1 (2025-07) 43 Parameter Presence Type Description ttl Mandatory pemea:posIntType Indicates the... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.1.2 emergencyDataSend example | <emergencyDataSend xmlns="urn:pemea:apps:xml:ns:pemea:base" xmlns:pdf="urn:ietf:params:xml:ns:pidf" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:con="urn:ietf:params:xml:ns:geopriv:conf" xmlns:pi="urn:ietf:params:xml:ns:Emerge... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.1.3 onErrorPost usage details | The onErrorPost attribute is a URI provided by the AP to which error messages related to the delivery of an EDS message are sent. The URI is specified as an HTTPS URI and the same authentication and authorization procedures defined in clause 9.2 shall apply. Any PEMEA entity receiving a PEMEA error in response to sendi... |
e8e9f99a1701d8a353a44a6f41feafe9 | 103 478 | 11.1.4 onCapSupportPost usage details | The onCapSupportPost attribute is a URI provided by the AP to which a terminating PSAP or PSP indicates which proffered capabilities contained in the information elements of the apMoreInformation element the terminating entity supports. The URI is specified as an HTTPS URI and the same authentication and authorization ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.