ETSI TS 103 478 V1.1.1 (2018-03)

ETSI TS 103 478 V1.1.1 (2018-03)






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

---------------------- Page: 1 ----------------------
2 ETSI TS 103 478 V1.1.1 (2018-03)



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

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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 2018.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 103 478 V1.1.1 (2018-03)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
Executive summary . 6
Introduction . 6
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 PEMEA architecture and functional entities . 11
4.1 Introduction . 11
4.2 Functional entities overview. 11
4.2.1 Application (App) . 11
4.2.2 Application Provider (AP) . 11
4.2.3 PSAP Service Provider (PSP) . 12
4.2.4 Aggregating Service Provider (ASP) . 12
4.3 Interface definitions . 12
4.3.1 Application Interface (Pa) . 12
4.3.2 Application Provider to PSAP Service Provider Interface (Ps) . 12
4.3.3 PSAP Service Provider Interface to Aggregating Service Provider Interface (Pr) . 12
4.3.4 PSAP Service Provider to PSAP Interface (Pp) . 13
5 PEMEA functional entity requirements . 13
5.1 Introduction . 13
5.2 Application requirements . 13
5.3 Application provider requirements . 14
5.4 PSAP service provider requirements . 14
5.5 Aggregating service provider requirements. 14
6 PEMEA Message Element Definitions . 15
6.1 Introduction . 15
6.2 emergencyDataSend Information Elements . 16
6.3 emergencyDataReceived Information Elements . 17
6.4 error Information Elements . 17
6.5 PEMEA Confirmation Messages . 17
7 PEMEA Message Flows . 17
7.1 Introduction . 17
7.2 Ps message flows . 18
7.2.1 Ps message flow description . 18
7.2.2 Ps basic flow . 18
7.2.3 Ps error flow . 19
7.2.4 Ps routing flow . 20
7.3 Pr message flows . 21
7.3.1 Pr message flow description . 21
7.3.2 Pr terminating-PSP basic flow . 21
7.3.3 Pr error flow . 22
7.3.4 Pr end to end routing flow . 23
8 PEMEA alignment with ETSI TS 103 479 . 25
8.1 General alignment . 25
8.2 PEMEA to border control function . 25
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 103 478 V1.1.1 (2018-03)
8.3 PEMEA to Legacy Network Gateway . 27
9 Message transportation and processing . 28
9.1 HTTP usage . 28
9.2 Authenticating and authorizing PEMEA entities . 29
9.3 PEMEA Securing a PSAP Retrieving Data By Reference or a reach-back URI . 29
9.4 PEMEA XML Processing Rules . 30
10 PEMEA XML structures and messages . 30
10.1 Ps Introduction . 30
10.2 Timestamps . 30
10.3 General types . 31
10.3.1 pemea:posIntType . 31
10.3.2 pemea:nodeType . 31
10.3.3 pemea:hopsType . 31
10.3.4 pemea:routeType . 31
10.3.5 pemea:destinationType . 32
10.3.6 pemea:destinationNodeType. 32
10.3.7 pemea:deliveryType. 32
10.3.8 pemea:typeOfCallerIdType. 32
10.3.9 pemea:callerIdType . 33
10.3.10 pemea:callerIdListType . 33
10.3.11 pemea:informationType . 33
10.3.12 pemea:ap MoreInfoT ype . 34
10.3.13 pemea:accessDataType . 35
10.3.13.1 pemea:accessDataType structure . 35
10.3.13.2 network . 35
10.3.13.3 wifi . 35
10.3.14 pemea:accessData . 36
10.3.15 pemea:msgInfoType . 36
11 PEMEA Message Definition . 36
11.1 emergencyDataSend Message . 36
11.1.1 emergencyDataSend message structure . 36
11.1.2 emergencyDataSend example . 38
11.1.3 onErrorPost usage details . 39
11.1.4 onCapSupportPost usage details . 40
11.2 emergencyDataReceived message . 41
11.2.1 emergencyDataReceived message structure . 41
11.2.2 emergencyDataReceived example . 42
11.3 error message . 42
12 PEMEA PIDF-LO Profiling . 43
12.1 Rationale. 43
12.2 entity . 44
12.3 tuple . 44
12.4 status . 44
12.5 geopriv . 44
12.5.1 geopriv element profile . 44
12.5.2 location-info . 44
12.5.2.1 location-info profile . 44
12.5.2.2 Confidence . 45
12.5.3 usage-rules . 45
12.5.4 method . 46
12.5.5 provided-by . 46
12.6 timestamp . 46
12.7 PIDF-LO example . 46
13 PEMEA Additional-Data Profiling . 46
13.1 Rationale. 46
13.2 Additional-Data :- provided-by . 47
13.3 EmergencyCallDataValue . 47
13.4 EmergencyCallData.ProviderInfo . 47
13.4.1 EmergencyCallData.ProviderInfo profile . 47
ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 103 478 V1.1.1 (2018-03)
13.4.2 DataProviderContact :- vcard . 48
13.4.2.1 DataProviderContact :- vcard profile . 48
13.4.2.2 DataProviderContact :- org . 48
13.4.2.3 DataProviderContact :- adr . 49
13.4.2.4 DataProviderContact :- email . 50
13.4.2.5 DataProviderContact :- URL . 50
13.4.3 EmergencyCallData.ProviderInfo:- Complete Example . 50
13.5 EmergencyCallData.DeviceInfo . 51
13.6 EmergencyCallData.SubscriberData . 51
13.6.1 EmergencyCallData.SubscriberData profile . 51
13.6.2 SubscriberData :- vcard . 52
13.6.2.1 SubscriberData :- vcard profile . 52
13.6.2.2 SubscriberData :- Caller's name . 52
13.6.2.3 SubscriberData :- home address . 53
13.6.2.4 SubscriberData :- language . 54
13.6.2.5 SubscriberData :- gender . 54
13.6.2.6 SubscriberData :- bday . 54
13.6.2.7 SubscriberData :- tel . 55
13.6.2.8 SubscriberData :- email . 56
13.6.2.9 SubscriberData :- Emergency Family Contacts . 56
13.6.3 EmergencyCallData.SubscriberData :- Complete Example . 57
13.7 Additional-Data :- EmergencyCallDataReference . 59
13.8 provided-by : Complete Examples . 59
14 Operating Procedures . 60
14.1 Application Provider Operating Procedures . 60
14.1.1 AP sending an EDS to the PSP . 60
14.1.2 AP reach-back URI queries . 61
14.1.3 Call termination (ending) and URI invalidation . 62
14.2 PSAP Service Provider Operating Procedures . 62
14.2.1 PSP receiving an EDS message over Ps . 62
14.2.2 PSP sending an EDS message over Pr . 64
14.2.3 PSP receiving an EDS message over Pr. 64
14.3 Aggregating Service Provider Operating Procedures . 65
14.3.1 Overview of Pr . 65
14.3.2 ASP receiving an EDS message over Pr . 65
14.3.3 ASP sending an EDS message over Pr . 66
15 Example message Flows . 67
15.1 Description . 67
15.2 AP to PSP EDS . 67
15.3 oPSP to AP EDR . 68
15.4 oPSP to ASP EDS . 68
15.5 ASP to oPSP EDR . 70
15.6 ASP to tPSP EDS . 70
15.7 tPSP to ASP EDR . 72
16 PEMEA Schema . 72
Annex A (informative): Route Determination . 77
Annex B (informative): Caller Data . 79
Annex C (informative): Additional AP Information . 80
History . 81


ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 103 478 V1.1.1 (2018-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, 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.
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 interconnect
...