ETSI TS 103 478 V1.3.1 (2025-07)

Emergency Communications (EMTEL); Pan-European Mobile Emergency Application

RTS/EMTEL-00078

General Information

• Status: Not Published
• Technical Committee: EMTEL - Emergency Communications
• Current Stage: 12 - Citation in the OJ (auto-insert)
• Due Date: 14-Aug-2025
• Completion Date: 31-Jul-2025

Standards Content (Sample)

TECHNICAL SPECIFICATION
Emergency Communications (EMTEL);
Pan-European Mobile Emergency Application

2 ETSI TS 103 478 V1.3.1 (2025-07)

Reference
RTS/EMTEL-00078
Keywords
application, emergency
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2025.
All rights reserved.
ETSI
3 ETSI TS 103 478 V1.3.1 (2025-07)

Contents
Intellectual Property Rights . 7
Foreword . 7
Modal verbs terminology . 7
Executive summary . 7
Introduction . 8
1 Scope . 9
2 References . 9
2.1 Normative references . 9
2.2 Informative references . 10
3 Definition of terms, symbols and abbreviations . 10
3.1 Terms . 10
3.2 Symbols . 11
3.3 Abbreviations . 11
4 PEMEA architecture and functional entities . 12
4.1 Introduction . 12
4.2 Functional entities overview. 12
4.2.0 PEMEA Registration Authority . 12
4.2.1 Application (App) . 12
4.2.2 Application Provider (AP) . 13
4.2.3 PSAP Service Provider (PSP) . 13
4.2.4 Aggregating Service Provider (ASP) . 13
4.2.5 PSAP Interface Module (PIM). 13
4.3 Interface definitions . 15
4.3.1 Application Interface (Pa) . 15
4.3.2 Application Provider to PSAP Service Provider Interface (Ps) . 15
4.3.3 PSAP Service Provider Interface to Aggregating Service Provider Interface (Pr) . 15
4.3.4 PSAP Service Provider to PSAP Interface (Pp) . 15
5 PEMEA functional entity requirements . 15
5.1 Introduction . 15
5.2 Application requirements . 16
5.3 Application provider requirements . 16
5.4 PSAP service provider requirements . 16
5.5 Aggregating service provider requirements. 17
6 PEMEA Message Element Definitions . 17
6.1 Introduction . 17
6.2 emergencyDataSend Information Elements . 18
6.3 emergencyDataReceived Information Elements . 19
6.4 error Information Elements . 19
6.5 PEMEA Confirmation Messages . 19
7 PEMEA Message Flows . 20
7.1 Introduction . 20
7.2 Ps message flows . 20
7.2.1 Ps message flow description . 20
7.2.2 Ps basic flow . 20
7.2.3 Ps error flow . 21
7.2.4 Ps routing flow . 22
7.3 Pr message flows . 23
7.3.1 Pr message flow description . 23
7.3.2 Pr terminating-PSP basic flow . 23
7.3.3 Pr error flow . 24
7.3.4 Pr end to end routing flow . 26
ETSI
4 ETSI TS 103 478 V1.3.1 (2025-07)

8 PEMEA alignment with ETSI TS 103 479 . 28
8.1 General alignment . 28
8.2 PEMEA to border control function . 28
8.3 PEMEA to Legacy Network Gateway . 30
9 Message transportation and processing . 31
9.1 HTTP usage . 31
9.2 Authenticating and authorizing PEMEA entities . 32
9.3 PEMEA Securing a PSAP Retrieving Data By Reference or a reach-back URI . 32
9.4 PEMEA XML Processing Rules . 33
10 PEMEA XML structures and messages . 33
10.1 Ps Introduction . 33
10.2 Timestamps . 33
10.3 General types . 34
10.3.1 pemea:posIntType . 34
10.3.2 pemea:nodeType . 34
10.3.3 pemea:hopsType . 34
10.3.4 pemea:routeType . 34
10.3.5 pemea:destinationType . 35
10.3.6 pemea:destinationNodeType. 35
10.3.7 pemea:deliveryType. 35
10.3.8 pemea:typeOfCallerIdType. 35
10.3.9 pemea:callerIdType . 35
10.3.10 pemea:callerIdListType . 36
10.3.11 pemea:informationType . 36
10.3.12 pemea:ap MoreInfoT ype . 37
10.3.13 pemea:accessDataType . 38
10.3.13.1 pemea:accessDataType structure . 38
10.3.13.2 network . 38
10.3.13.3 wifi . 39
10.3.14 pemea:accessData . 39
10.3.15 pemea:msgInfoType . 40
10.3.16 pemea:cell2g . 40
10.3.17 pemea:cell3g . 41
10.3.18 pemea:cell4g . 41
10.3.19 pemea:cell5g . 42
10.3.20 pemea:cellId5NRType . 42
11 PEMEA Message Definition . 42
11.1 emergencyDataSend Message . 42
11.1.1 emergencyDataSend message structure . 42
11.1.2 emergencyDataSend example . 44
11.1.3 onErrorPost usage details . 46
11.1.4 onCapSupportPost usage details . 46
11.1.5 onClosePost usage details . 47
11.1.6 subscribeClosePost usage details . 48
11.2 emergencyDataReceived message . 49
11.2.1 emergencyDataReceived message structure . 49
11.2.2 emergencyDataReceived example . 50
11.3 error message . 50
12 PEMEA PIDF-LO Profiling . 52
12.1 Rationale. 52
12.2 entity . 52
12.3 tuple . 52
12.4 status . 52
12.5 geopriv . 53
12.5.1 geopriv element profile . 53
12.5.2 location-info . 53
12.5.2.1 location-info profile . 53
12.5.2.2 Confidence . 53
12.5.3 usage-rules . 54
ETSI
5 ETSI TS 103 478 V1.3.1 (2025-07)

12.5.4 method . 54
12.5.5 provided-by . 54
12.6 timestamp . 54
12.7 PIDF-LO example . 54
13 PEMEA Additional-Data Profiling . 55
13.1 Rationale. 55
13.2 Additional-Data: provided-by . 55
13.3 EmergencyCallDataValue . 55
13.4 EmergencyCallData.ProviderInfo . 55
13.4.1 EmergencyCallData.ProviderInfo profile . 55
13.4.2 DataProviderContact: vcard . 56
13.4.2.1 DataProviderContact: vcard profile . 56
13.4.2.2 DataProviderContact: org . 56
13.4.2.3 DataProviderContact: adr . 57
13.4.2.4 DataProviderContact: email . 58
13.4.2.5 DataProviderContact: URL . 58
13.4.3 EmergencyCallData.ProviderInfo: Complete Example . 58
13.5 EmergencyCallData.DeviceInfo . 59
13.6 EmergencyCallData.SubscriberData . 59
13.6.1 EmergencyCallData.SubscriberData profile . 59
13.6.2 SubscriberData: vcard . 60
13.6.2.1 SubscriberData: vcard profile. 60
13.6.2.2 SubscriberData: Caller's name . 60
13.6.2.3 SubscriberData: home address . 61
13.6.2.4 SubscriberData: language . 61
13.6.2.5 SubscriberData: gender . 62
13.6.2.6 SubscriberData: bday . 62
13.6.2.7 SubscriberData: tel . 62
13.6.2.8 SubscriberData: email . 63
13.6.2.9 SubscriberData: Emergency Family Contacts . 63
13.6.3 EmergencyCallData.SubscriberData: Complete Example . 65
13.7 Additional-Data: EmergencyCallDataRe ference . 66
13.8 provided-by: Complete Examples . 66
14 Operating Procedures . 67
14.1 Application Provider Operating Procedures . 67
14.1.1 AP sending an EDS to the PSP . 67
14.1.2 AP reach-back URI queries . 69
14.1.3 Call termination (ending) and URI invalidation . 69
14.1.4 Call termination (ending) by the PSAP. 70
14.2 PSAP Service Provider Operating Procedures . 70
14.2.1 PSP receiving an EDS message over Ps . 70
14.2.2 PSP sending an EDS message over Pr . 72
14.2.3 PSP receiving an EDS message over Pr. 72
14.2.4 Call termination (ending) by the caller . 73
14.2.5 Call termination (ending) by the PSAP. 74
14.3 Aggregating Service Provider Operating Procedures . 74
14.3.1 Overview of Pr . 74
14.3.2 ASP receiving an EDS message over Pr . 74
14.3.3 ASP sending an EDS message over Pr . 75
15 Example message Flows . 75
15.1 Description . 75
15.2 AP to PSP EDS . 75
15.3 oPSP to AP EDR . 77
15.4 oPSP to ASP EDS . 77
15.5 ASP to oPSP EDR . 79
15.6 ASP to tPSP EDS . 79
15.7 tPSP to ASP EDR . 81
16 PEMEA Schema . 81
17 PEMEA Callback . 87
ETSI
6 ETSI TS 103 478 V1.3.1 (2025-07)

17.1 Overview . 87
17.2 Service support indication and response . 87
17.2.1 Service definition . 87
17.2.2 Service support indication . 88
17.2.3 Service support response . 88
17.3 Procedures and signalling . 88
17.3.1 Overview . 88
17.3.2 Service invocation . 88
17.3.3 Callback operation . 90
Annex A (informative): Route Determination . 92
Annex B (informative): Caller Data . 94
Annex C (informative): Additional AP Information . 95
History . 96

ETSI
7 ETSI TS 103 478 V1.3.1 (2025-07)

Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This Technical Specification (TS) has been produced by ETSI Special Committee Emergency Communications
(EMTEL).
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Executive summary
The Pan-European Mobile Emergency Application (PEMEA) architecture provides the requirements and architecture
for a solution to provide emergency application interconnection. It specifies the protocols and procedures enabling
interoperable implementations of the architecture and provides extension points to enable new communication
mechanisms as they evolve.
ETSI
8 ETSI TS 103 478 V1.3.1 (2025-07)

Introduction
The rise of smart devices such as smart phones, tablets and laptops has led to an explosion in communications
applications. Many of these applications aim to supplement existing communications services, such as providing caller
and location information for emergency calls, while others seek to provide alternative communication mechanisms such
as total conversation and instant messaging for example. Many of these applications already exist in limited local
capacities but lack a common framework for easy interconnection. This limitation prohibits a user's application
operating in a region other than the one it was developed in and having his/her information and accurate location
information passed to the PSAP serving their location. The Pan-European Mobile Emergency Application (PEMEA)
architecture provides a solution to interconnect these applications.

ETSI
9 ETSI TS 103 478 V1.3.1 (2025-07)

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 emergency application
architecture, the interfaces between each functional entity, and the requirements on each interface. The second part
defines the data exchanges, message, protocols and procedures used across each of the identified PEMEA interfaces.
It is recognized that many existing application implementations combine the functional entities identified in the present
document into a single entity. The most common example of combined functional entities is the combined Application
Provider (AP) and PSAP Service Provider (PSP), these are common because it is often the PSAP that writes or engages
a third-party to write a local emergency application that interfaces directly with the PSAP. The present document does
not seek to disallow integrated node implementations, however, it does not define how additional applications or
application providers using proprietary Application Programming Interfaces (APIs) and protocols can provide PEMEA
extended features, such solutions are left to the integrated node providers.
2 References
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 are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] IETF RFC 2818 (May 2000): "HTTP Over TLS".
[2] IETF RFC 2965 (October 2000): "HTTP State Management Mechanism".
[3] IETF RFC 4119 (December 2005): "A Presence-based GEOPRIV Location Object Format".
[4] IETF RFC 5491 (March 2009): "GEOPRIV Presence Information Data Format Location Object
(PIDF-LO) Usage Clarification, Considerations, and Recommendations".
[5] IETF RFC 3966 (December 2004): "The tel URI for telephone Number".
[6] IETF RFC 7459 (February 2015): "Representation of Uncertainty and Confidence in the Presence
Information Data Format Location Object (PIDF-LO)".
[7] IETF RFC 3863 (August 2004): "Presence Information Data Format (PIDF)".
[8] IETF RFC 5139 (February 2008): "Revised Civic Location Format for Presence Information Data
Format Location Object (PIDF-LO)".
[9] IETF RFC 6848 (January 2013): "Specifying Civic Address Extensions in the Presence
Information Data Format Location Object (PIDF-LO)".
[10] IANA: "Method Tokens Registry of Values".
[11] IETF RFC 7852 (July 2016): "Additional Data Related to an Emergency Call".
[12] IETF RFC 7105 (January 2014): "Using Device-Provided Location-Related Measurements in
Location Configuration Protocols".
ETSI
10 ETSI TS 103 478 V1.3.1 (2025-07)

[13] IANA: "Language subtag registry".
[14] ISO 639:2023: "Code for individual languages and language groups".
[15] IETF RFC 6753 (October 2012): "A Location Dereference Protocol Using HTTP-Enabled
Location Delivery (HELD)".
[16] IETF RFC 5808 (May 2010): "Requirements for a Location-by-Reference Mechanism".
[17] Open Mobile Alliance OMA-TS-MLP-V3-2-20110719-A: "Mobile Location Protocol 3.2",
July 2011.
[18] Open Mobile Alliance OMA-TS-MLP-V3-3-1-20111117-A: "Mobile Location Protocol 3.3.1",
November 2011.
[19] Open Mobile Alliance OMA-TS-MLP-V3-4-20150512-A: "Mobile Location Protocol 3.4",
May 2015.
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 included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] ETSI TS 103 479: "Emergency Communications (EMTEL); Core elements for network
independent access to emergency services".
[i.2] EENA: "Pan-European Mobile Emergency Application (PEMEA) Requirements and Functional
Architecture", Version 7, February 2015.
[i.3] Void.
[i.4] ETSI TS 103 755: "Emergency Communications (EMTEL); PEMEA ESInet Shared Services".
[i.5] ETSI TS 103 756: "Emergency Communications (EMTEL); PEMEA Instant Message Extension".
[i.6] ETSI TS 103 871: "Emergency Communications (EMTEL); PEMEA Real-Time Text Extension".
[i.7] ETSI TS 103 872: "Emergency Communications (EMTEL); PEMEA Service Discovery
Extension".
[i.8] ETSI TS 103 945: "Emergency Communications (EMTEL); PEMEA Audio Video Extension".
[i.9] ETSI TS 104 014: "Emergency Communications (EMTEL); PEMEA File Exchange Extension".
3 Definition of terms, symbols and abbreviations
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
11 ETSI TS 103 478 V1.3.1 (2025-07)

• privacy of user data ensuring access only to authenticated and authorized entities
• secrecy of information transferred between two authenticated and authorized entities
trusted: identity of entity assured through an approved authentication mechanism and the entity authorized to perform
the action
3.2 Symbols
Void.
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 Function
EDR Emergency Data Received (message)
EDS Emergency Data Send (message)
EENA European Emergency Number Association
ESInet Emergency Services IP Network
ESRP Emergency Services Routing Proxy
ETSI European Telecommunications Standards Institute
GML Geography Markup Language
GNSS Global Navigation Satellite System
HELD HTTP-Enabled Location Delivery
HTTP Hyper-Text Transfer Protocol
IETF Internet Engineering Task Force
IMEI International Mobile Equipment Identifier
IMSI International Mobile Subscriber Identifier
LIF Location Interworking Function
LIS Location Information Server
LNG Legacy Network Gateway
MAC Media Access Control
MCC Mobile Country Code
MLP Mobile Location Protocol
MNC Mobile Network Code
MSISDN Mobile Service International Subscriber Dial Number
oPSP originating PSP
OTT Over The Top
Pa PEMEA Application to AP interface
PEMEA Pan-European Mobile Emergency Application
PIDF-LO Presence Information Data Format Location Object
PIM PSAP Interface Module
Pp PEMEA PSP to PSAP interface
Pr PEMEA PSP to ASP or ASP to PS interface
PRA PEMEA Registration Authority
Ps PEMEA AP to PSP interface
PSAP Public Safety Answering Point
PSP PSAP Service Provider
PSTN Public Switched Telephone Network
RTT Real-Time Text
SIP Session Initiation Protocol
ETSI
12 ETSI TS 103 478 V1.3.1 (2025-07)

SIPS SIP Secure
tPSP terminating PSP
ttl time to live
UCF Universal Character Set
UMTS Universal Mobile Telecommunication System (cellular 3G)
URI Uniform Resource Identifier
URL Uniform Resource Locator
UTC Coordinated Universal Time
UTF UCF Transformation Format
VSP Voice Service Provider
XML eXtensible Markup Language
XSD XML Schema Definition
4 PEMEA architecture and
...