< draft-ietf-ecrit-ecall-11.txt   draft-ietf-ecrit-ecall-12.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: February 2, 2017 Individual Expires: March 25, 2017 Individual
August 1, 2016 September 21, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-11.txt draft-ietf-ecrit-ecall-12.txt
Abstract Abstract
This document describes how to use IP-based emergency services This document describes how to use IP-based emergency services
mechanisms to support the next generation of the Pan European in- mechanisms to support the next generation of the Pan European in-
vehicle emergency call service defined under the eSafety initiative vehicle emergency call service defined under the eSafety initiative
of the European Commission (generally referred to as "eCall"). eCall of the European Commission (generally referred to as "eCall"). eCall
is a standardized and mandated system for a special form of emergency is a standardized and mandated system for a special form of emergency
calls placed by vehicles, providing real-time communications and an calls placed by vehicles, providing real-time communications and an
integrated set of related data. integrated set of related data.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 2, 2017. This Internet-Draft will expire on March 25, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 20 skipping to change at page 2, line 20
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4 2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6 4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6
5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Call Routing . . . . . . . . . . . . . . . . . . . . . . 9 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 10 9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 10
9.1. The eCall Control Block . . . . . . . . . . . . . . . . . 12 9.1. The eCall Control Block . . . . . . . . . . . . . . . . . 12
9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 12 9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 13
9.1.1.1. Attributes of the <ack> element . . . . . . . . . 12 9.1.1.1. Attributes of the <ack> element . . . . . . . . . 13
9.1.1.2. Child Element of the <ack> element . . . . . . . 13 9.1.1.2. Child Element of the <ack> element . . . . . . . 13
9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 14 9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 14
9.1.2. The <capabilities> element . . . . . . . . . . . . . 14 9.1.2. The <capabilities> element . . . . . . . . . . . . . 15
9.1.2.1. Child Elements of the <capabilities> element . . 14 9.1.2.1. Child Elements of the <capabilities> element . . 15
9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 15 9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 15
9.1.3. The <request> element . . . . . . . . . . . . . . . . 15 9.1.3. The <request> element . . . . . . . . . . . . . . . . 15
9.1.3.1. Attributes of the <request> element . . . . . . . 15 9.1.3.1. Attributes of the <request> element . . . . . . . 16
9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 17 9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 17
10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 17 10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 17
10.1. INFO Package Requirements . . . . . . . . . . . . . . . 17 10.1. Overall Description . . . . . . . . . . . . . . . . . . 18
10.1.1. Overall Description . . . . . . . . . . . . . . . . 18 10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 18
10.1.2. Applicability . . . . . . . . . . . . . . . . . . . 18 10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19
10.1.3. Info Package Name . . . . . . . . . . . . . . . . . 18 10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19
10.1.4. Info Package Parameters . . . . . . . . . . . . . . 19 10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19
10.1.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 19 10.6. INFO Message Body Parts . . . . . . . . . . . . . . . . 19
10.1.6. INFO Message Body Parts . . . . . . . . . . . . . . 19 10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20
10.1.7. Info Package Usage Restrictions . . . . . . . . . . 19 10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20
10.1.8. Rate of INFO Requests . . . . . . . . . . . . . . . 19 10.9. Info Package Security Considerations . . . . . . . . . . 20
10.1.9. Info Package Security Considerations . . . . . . . . 19 10.10. Implementation Details . . . . . . . . . . . . . . . . . 20
10.1.10. Implementation Details . . . . . . . . . . . . . . . 19 10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1.11. Examples . . . . . . . . . . . . . . . . . . . . . . 19 11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 20
11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 19 12. Security Considerations . . . . . . . . . . . . . . . . . . . 26
12. Security Considerations . . . . . . . . . . . . . . . . . . . 25 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26 14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 27
14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 15.1. Service URN Registrations . . . . . . . . . . . . . . . 30
15.1. Service URN Registrations . . . . . . . . . . . . . . . 29
15.2. MIME Content-type Registration for 15.2. MIME Content-type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 30 'application/emergencyCallData.eCall.MSD+per' . . . . . 31
15.3. MIME Content-type Registration for 15.3. MIME Content-type Registration for
'application/emergencyCallData.eCall.control+xml' . . . 31 'application/emergencyCallData.eCall.control+xml' . . . 32
15.4. Registration of the 'eCall.MSD' entry in the Emergency 15.4. Registration of the 'eCall.MSD' entry in the Emergency
Call Additional Data Blocks registry . . . . . . . . . . 32 Call Additional Data Blocks registry . . . . . . . . . . 33
15.5. Registration of the 'eCall.control' entry in the 15.5. Registration of the 'eCall.control' entry in the
Emergency Call Additional Data Blocks registry . . . . . 33 Emergency Call Additional Data Blocks registry . . . . . 34
15.6. Registration of the emergencyCallData.eCall Info Package 33 15.6. Registration of the emergencyCallData.eCall Info Package 34
15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 33 15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34
15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 33 15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34
15.7.2. Registration for 15.7.2. Registration for
urn:ietf:params:xml:ns:eCall:control . . . . . . . . 34 urn:ietf:params:xml:ns:eCall:control . . . . . . . . 35
15.8. Registry creation . . . . . . . . . . . . . . . . . . . 34 15.8. Registry creation . . . . . . . . . . . . . . . . . . . 35
15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 34 15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 35
15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 35 15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 36
16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 36 16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 37
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36 17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
18. Changes from Previous Versions . . . . . . . . . . . . . . . 36 18. Changes from Previous Versions . . . . . . . . . . . . . . . 37
18.1. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 36 18.1. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 37
18.2. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 37 18.2. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 38
18.3. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 37 18.3. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38
18.4. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 37 18.4. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38
18.5. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38 18.5. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 39
18.6. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 38 18.6. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 39
18.7. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 38 18.7. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39
18.8. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 38 18.8. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39
18.9. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 38 18.9. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
18.10. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39 18.10. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39
18.11. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 39 18.11. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40
18.12. Changes from draft-gellens-02 to -03 . . . . . . . . . . 39 18.12. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 40
18.13. Changes from draft-gellens-01 to -02 . . . . . . . . . . 39 18.13. Changes from draft-gellens-02 to -03 . . . . . . . . . . 40
18.14. Changes from draft-gellens-00 to -01 . . . . . . . . . . 39 18.14. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 18.15. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40
19.1. Normative References . . . . . . . . . . . . . . . . . . 40 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
19.2. Informative references . . . . . . . . . . . . . . . . . 41 19.1. Normative References . . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 19.2. Informative references . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
Additionally, we use the following abbreviations: Additionally, we use the following abbreviations:
skipping to change at page 6, line 27 skipping to change at page 6, line 27
A transition period will exist during which time the various entities A transition period will exist during which time the various entities
involved in initiating and handling an eCall might support next- involved in initiating and handling an eCall might support next-
generation eCall, legacy eCall, or both. The issues of migration and generation eCall, legacy eCall, or both. The issues of migration and
co-existence during the transition period are outside the scope of co-existence during the transition period are outside the scope of
this document. this document.
The MSD is carried in the MIME type 'application/ The MSD is carried in the MIME type 'application/
emergencyCallData.eCall.MSD+per' and the metadata/control block is emergencyCallData.eCall.MSD+per' and the metadata/control block is
carried in the MIME type 'application/ carried in the MIME type 'application/
emergencyCallData.eCall.control+xml' (both of which are registered in emergencyCallData.eCall.control+xml' (both of which are registered in
this document). Section 15) An INFO package is defined (in Section 10) to enable
these MIME types to be carried in INFO messages.
4. eCall Requirements 4. eCall Requirements
eCall requirements are specified by CEN in [EN_16072] and by 3GPP in eCall requirements are specified by CEN in [EN_16072] and by 3GPP in
[TS22.101] clauses 10.7 and A.27. Requirements specific to vehicle [TS22.101] clauses 10.7 and A.27. Requirements specific to vehicle
data are contained in EN 15722 [msd]. data are contained in EN 15722 [msd].
5. Vehicle Data 5. Vehicle Data
Pan-European eCall provides a standardized and mandated set of Pan-European eCall provides a standardized and mandated set of
skipping to change at page 7, line 16 skipping to change at page 7, line 16
used.) used.)
See Section 6 for a discussion of how the MSD vehicle data is See Section 6 for a discussion of how the MSD vehicle data is
conveyed in an NG-eCall. conveyed in an NG-eCall.
6. Data Transport 6. Data Transport
[RFC7852] establishes a general mechanism for attaching blocks of [RFC7852] establishes a general mechanism for attaching blocks of
data to a SIP emergency call. This mechanism permits certain data to a SIP emergency call. This mechanism permits certain
emergency call MIME types to be attached to SIP messages. This emergency call MIME types to be attached to SIP messages. This
document makes use of that mechanism. document makes use of that mechanism. This document also registers
an INFO package (in Section 10) to enable eCall related data blocks
to be carried in INFO messages.
Note that if additional data sets are defined and registered (e.g., Note that if other data sets need to be transmitted in the future,
in the future or in other regions) and transmitted using the same the appropriate signalling mechanism for such data needs to be
mechanisms, the size and frequency of transmission during a dialog evaluated, including factors such as the size and frequency of such
need to be evaluated to be sure it is appropriate to use the data.
signaling channel.
An In-Vehicle System (IVS) transmits the MSD (see Section 5) by An In-Vehicle System (IVS) transmits the MSD (see Section 5) by
encoding it per Annex A of EN 15722 [msd] and attaching it to a SIP encoding it per Annex A of EN 15722 [msd] and attaching it to a SIP
message as a MIME body part per [RFC7852]. The body part is message as a MIME body part per [RFC7852]. The body part is
identified by its MIME content-type ('application/ identified by its MIME content-type ('application/
emergencyCallData.eCall.MSD+per') in the Content-Type header field of emergencyCallData.eCall.MSD+per') in the Content-Type header field of
the body part. The body part is assigned a unique identifier which the body part. The body part is assigned a unique identifier which
is listed in a Content-ID header field in the body part. The SIP is listed in a Content-ID header field in the body part. The SIP
message is marked as containing the MSD by adding (or appending to) a message is marked as containing the MSD by adding (or appending to) a
Call-Info header field at the top level of the SIP message. This Call-Info header field at the top level of the SIP message. This
Call-Info header field contains a CID URL referencing the body part's Call-Info header field contains a CID URL referencing the body part's
unique identifier, and a 'purpose' parameter identifying the data as unique identifier, and a 'purpose' parameter identifying the data as
the eCall MSD per the Emergency Call Additional Data Blocks registry the eCall MSD per the Emergency Call Additional Data Blocks registry
entry; the 'purpose' parameter's value is entry; the 'purpose' parameter's value is
'emergencyCallData.eCall.MSD'. 'emergencyCallData.eCall.MSD'. The body part has a Content-
Disposition header field value of "By-Reference; handling=optional".
An MSD is carried in an INFO message by using the INFO package
registration (defined in Section 10).
A PSAP or IVS transmits a metadata/control object (see Section 9) by A PSAP or IVS transmits a metadata/control object (see Section 9) by
encoding it per the description in this document and attaching it to encoding it per the description in this document and attaching it to
a SIP message as a MIME body part per [RFC7852]. The body part is a SIP message as a MIME body part per [RFC7852]. The body part is
identified by its MIME content-type ('application/ identified by its MIME content-type ('application/
emergencyCallData.eCall.control+xml') in the Content-Type header emergencyCallData.eCall.control+xml') in the Content-Type header
field of the body part. The body part is assigned a unique field of the body part. The body part is assigned a unique
identifier which is listed in a Content-ID header field in the body identifier which is listed in a Content-ID header field in the body
part. The SIP message is marked as containing the metadata/control part. The SIP message is marked as containing the metadata/control
object by adding (or appending to) a Call-Info header field at the object by adding (or appending to) a Call-Info header field at the
top level of the SIP message. This Call-Info header field contains a top level of the SIP message. This Call-Info header field contains a
CID URL referencing the body part's unique identifier, and a CID URL referencing the body part's unique identifier, and a
'purpose' parameter identifying the data as an eCall metadata/control 'purpose' parameter identifying the data as an eCall metadata/control
block per the Emergency Call Additional Data Blocks registry entry; block per the Emergency Call Additional Data Blocks registry entry;
the 'purpose' parameter's value is 'emergencyCallData.eCall.control'. the 'purpose' parameter's value is 'emergencyCallData.eCall.control'.
The body part has a Content-Disposition header field value of "By-
Reference; handling=optional". A metadata/control object is carried
in an INFO message by using the INFO package registration (defined in
Section 10).
As is standard practice, if an MSD or a metadata/control block is
sent in the same message with another body part, a multipart/mixed
body part encloses all body parts.
An In-Vehicle System (IVS) initiating an NG-eCall attaches the MSD to An In-Vehicle System (IVS) initiating an NG-eCall attaches the MSD to
the initial INVITE and optionally attaches a metadata/control object the initial INVITE and optionally attaches a metadata/control object
informing the PSAP of its capabilities. The PSAP creates a metadata/ informing the PSAP of its capabilities. The PSAP creates a metadata/
control object acknowledging receipt of the MSD and attaches it to control object acknowledging receipt of the MSD and attaches it to
the SIP response to the INVITE. the SIP final response to the INVITE. The metadata/control object is
not attached to provisional (e.g., 180) responses.
A PSAP can request the vehicle to send an updated MSD during a call. If the IVS receives an acknowledgment for an MSD with received=false,
The PSAP creates a metadata/control object requesting the MSD and it indicates some fault with the transfer of the MSD, the MSD
attaches it to a SIP INFO message which it sends within the dialog. content, or the PSAP's ability to properly receive, decode and act on
The IVS then attaches an updated MSD to a SIP INFO message and sends the MSD. The IVS action is not defined (e.g., it might only log an
it within the dialog. The metadata/control object and the MSD are error). Since the PSAP is able to request an updated MSD during the
attached to an INFO message in the same way they are attached to call, if an initial MSD is unsatisfactory in any way, the PSAP can
other messages (such as the INVITE and the reply to the INVITE as choose to request another one.
discussed above). INFO messages are sent using an appropriate INFO
Package. See Section 10 for information about the use of INFO
messages to carry data within an eCall.
When data is being carried in an INFO request message, the body part A PSAP can request that the vehicle send an updated MSD during a
also carries a Content-Disposition header field set to "Info- call. To do so, the PSAP creates a metadata/control object
Package". requesting an MSD and attaches it to a SIP INFO message which it
sends within the dialog. The IVS then attaches an updated MSD to a
SIP INFO message and sends it within the dialog. The metadata/
control object and the MSD are both associated with the INFO package
registered by this document, and hence sent with normal INFO
semantics. In addition, for consistency with the way an MSD or
metadata/control block is transmitted in a non-INFO message, one or
more Call-Info header fields are included in the INFO message to
reference the MSD or metadata/control block. If the body part
containing the MSD or metadata/control block is the only body part,
it has a Content-Disposition header field value of "Info-Package;
handling=optional". If it is contained within a multipart body part,
it has a Content-Disposition header field value of "By-Reference;
handling=optional". See Section 10 for information about the use of
INFO messages to carry data within an eCall.
The IVS is not expected to send an unsolicited MSD during the call.
Indicating "handling=optional" in the Content-Disposition header
field value protects the body part from being discarded by
intermediate entities that do not support it.
Support for the data blocks defined in [RFC7852] is NOT REQUIRED for Support for the data blocks defined in [RFC7852] is NOT REQUIRED for
conformance with this document. conformance with this document.
7. Call Setup 7. Call Setup
In circuit-switched eCall, the IVS places a special form of a 112 In circuit-switched eCall, the IVS places a special form of a 112
emergency call which carries an eCall flag (indicating that the call emergency call which carries an eCall flag (indicating that the call
is an eCall and also if the call was manually or automatically is an eCall and also if the call was manually or automatically
triggered); the mobile network operator (MNO) recognizes the eCall triggered); the mobile network operator (MNO) recognizes the eCall
skipping to change at page 9, line 24 skipping to change at page 10, line 5
This document registers new service URN children within the "sos" This document registers new service URN children within the "sos"
subservice. These URNs provide the mechanism by which an eCall is subservice. These URNs provide the mechanism by which an eCall is
identified, and differentiate between manually and automatically identified, and differentiate between manually and automatically
triggered eCalls (which might be subject to different treatment, triggered eCalls (which might be subject to different treatment,
depending on policy). The two service URNs are: depending on policy). The two service URNs are:
urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual, urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual,
which requests resources associated with an emergency call placed by which requests resources associated with an emergency call placed by
an in-vehicle system, carrying a standardized set of data related to an in-vehicle system, carrying a standardized set of data related to
the vehicle and incident. the vehicle and incident.
7.1. Call Routing Call routing is outside the scope of this document.
The routing applied to eCalls might differ from those of other
emergency calls, as eCalls are intended to be handled by PSAPs that
support eCall. In regions without ESInets, typically the emergency
services authorities and the originating network determine how such
calls are routed. In a region that uses ESInets, the originating
network passes all types of emergency calls to an ESInet (calls which
have a request URI containing the "SOS" service URN). The ESInet is
then responsible for routing such calls to the appropriate PSAP.
8. Test Calls 8. Test Calls
eCall requires the ability to place test calls (see [TS22.101] clause eCall requires the ability to place test calls (see [TS22.101] clause
10.7 and [EN_16062] clause 7.2.2). These are calls that are 10.7 and [EN_16062] clause 7.2.2). These are calls that are
recognized and treated to some extent as eCalls but are not given recognized and treated to some extent as eCalls but are not given
emergency call treatment and are not handled by call takers. The emergency call treatment and are not handled by call takers. The
specific handling of test eCalls is not itself standardized; specific handling of test eCalls is not itself standardized;
typically, the test call facility allows the IVS or user to verify typically, the test call facility allows the IVS or user to verify
that an eCall can be successfully established with voice that an eCall can be successfully established with voice
skipping to change at page 11, line 17 skipping to change at page 11, line 38
block, it indicates that the SIP dialog is not an NG-eCall (e.g., block, it indicates that the SIP dialog is not an NG-eCall (e.g.,
some part of the call is being handled as a legacy call). When the some part of the call is being handled as a legacy call). When the
IVS sends a solicited MSD (e.g., in a SIP INFO request sent following IVS sends a solicited MSD (e.g., in a SIP INFO request sent following
receipt of a SIP INFO request containing a metadata/control block receipt of a SIP INFO request containing a metadata/control block
requesting an MSD), the PSAP does not send a metadata/control block requesting an MSD), the PSAP does not send a metadata/control block
indicating successful or unsuccessful receipt of the MSD. (Normal indicating successful or unsuccessful receipt of the MSD. (Normal
SIP retransmission handles non-receipt of requested data; if the IVS SIP retransmission handles non-receipt of requested data; if the IVS
sends a requested MSD in an INFO request and does not receive a SIP sends a requested MSD in an INFO request and does not receive a SIP
status message for the INFO request, it resends it; if the PSAP status message for the INFO request, it resends it; if the PSAP
requests an MSD and does not receive a SIP status message for the requests an MSD and does not receive a SIP status message for the
INFO request, it resends it.) INFO request, it resends it.) If the IVS receives a request to send
an MSD but it is unable to do so for any reason, the IVS sends a
metadata/control object acknowledging the request and containing
"success=false" and "reason" set to an appropriate code.
This provides flexibility to handle various circumstances. For This provides flexibility to handle various circumstances. For
example, if a PSAP is unable to accept an eCall (e.g., due to example, if a PSAP is unable to accept an eCall (e.g., due to
overload or too many calls from the same location), it can reject the overload or too many calls from the same location), it can reject the
INVITE. Since a metadata/control object is also included in the SIP INVITE. Since a metadata/control object is also included in the SIP
response that rejects the call, the IVS knows if the PSAP received response that rejects the call, the IVS knows if the PSAP received
the MSD, and can inform the vehicle occupants that the PSAP the MSD, and can inform the vehicle occupants that the PSAP
successfully received the vehicle location and information but can't successfully received the vehicle location and information but can't
talk to the occupants at that time. Especially for SIP response talk to the occupants at that time. Especially for SIP response
codes that indicate an inability to conduct a call (as opposed to a codes that indicate an inability to conduct a call (as opposed to a
skipping to change at page 11, line 42 skipping to change at page 12, line 18
the PSAP wants to reject a call but inform the vehicle occupants that the PSAP wants to reject a call but inform the vehicle occupants that
it is aware of the situation. (Note that there could be edge cases it is aware of the situation. (Note that there could be edge cases
where the PSAP response is not received by the IVS, e.g., if an where the PSAP response is not received by the IVS, e.g., if an
intermediary sends a CANCEL, and an error response is forwarded intermediary sends a CANCEL, and an error response is forwarded
towards the IVS before the error response from the PSAP is received, towards the IVS before the error response from the PSAP is received,
the response will be dropped, but these are unlikely to occur here.) the response will be dropped, but these are unlikely to occur here.)
The metadata/control block is carried in the MIME type 'application/ The metadata/control block is carried in the MIME type 'application/
emergencyCallData.eCall.control+xml'. emergencyCallData.eCall.control+xml'.
The metadata/control block is designed for use with with pan-European The metadata/control block is designed for use with pan-European
eCall and also eCall-like systems (i.e., in other regions), and has eCall and also eCall-like systems (i.e., in other regions), and has
extension points to accomodate variances. Note that eCall-like extension points to accomodate variances. Note that eCall-like
systems might define their own vehicle data blocks, and so might need systems might define their own vehicle data blocks, and so might need
to register a new INFO package to accomodate the new data MIME type to register a new INFO package to accomodate the new data content
and the metadata/control object. type and the metadata/control object.
9.1. The eCall Control Block 9.1. The eCall Control Block
The eCall control block is an XML data structure allowing for The eCall control block is an XML data structure allowing for
acknowledgments, requests, and capabilities information. It is acknowledgments, requests, and capabilities information. It is
carried in a SIP body part with a specific MIME content type. Three carried in a SIP body part with a specific MIME content type. Three
elements are defined for use within an eCall control block: elements are defined for use within an eCall control block:
ack Acknowledges receipt of data or a request. ack Acknowledges receipt of data or a request.
skipping to change at page 12, line 41 skipping to change at page 13, line 13
Section 15.8.1 to contain the allowed values. Section 15.8.1 to contain the allowed values.
The <capabilities> element has child <request> elements to indicate The <capabilities> element has child <request> elements to indicate
the actions supported by the IVS. the actions supported by the IVS.
9.1.1. The <ack> element 9.1.1. The <ack> element
The <ack> element acknowledges receipt of an eCall data object or The <ack> element acknowledges receipt of an eCall data object or
request. An <ack> element references the unique ID of the data request. An <ack> element references the unique ID of the data
object being acknowledged. The PSAP MUST send an <ack> element object being acknowledged. The PSAP MUST send an <ack> element
acknowledging reeipt of an unsolicited MSD (e.g., sent by the IVS in acknowledging receipt of an unsolicited MSD (e.g., sent by the IVS in
the INVITE); this <ack> element indicates if the PSAP considers the the INVITE); this <ack> element indicates if the PSAP considers the
MSD successfully received or not. An <ack> element is not sent for a MSD successfully received or not. An <ack> element is not sent for a
<capabilities> element. <capabilities> element.
The <ack> element has the following attributes: The <ack> element has the following attributes:
9.1.1.1. Attributes of the <ack> element 9.1.1.1. Attributes of the <ack> element
The <ack> element has the following attributes: The <ack> element has the following attributes:
Name: ref Name: ref
Usage: Mandatory Usage: Mandatory
Type: anyURI Type: anyURI
Direction: In this document, sent from the PSAP to the IVS Direction: In this document, sent from the PSAP to the IVS
Description: References the Content-ID of the body part being Description: References the Content-ID of the body part being
acknowledged. acknowledged.
Example: <ack received="yes" ref="1234567890@atlanta.example.com"/> Example: <ack received="true" ref="1234567890@atlanta.example.com"/>
Name: received Name: received
Usage: Conditional: mandatory in an >ack< element sent by a PSAP Usage: Conditional: mandatory in an >ack< element sent by a PSAP
Type: Boolean Type: Boolean
Direction: In this document, sent from the PSAP to the IVS Direction: In this document, sent from the PSAP to the IVS
Description: Indicates if the referenced object was considered Description: Indicates if the referenced object was considered
successfully received or not successfully received or not.
Example: <ack received="yes" ref="1234567890@atlanta.example.com"/> Example: <ack received="true" ref="1234567890@atlanta.example.com"/>
9.1.1.2. Child Element of the <ack> element 9.1.1.2. Child Element of the <ack> element
For extensibility, the <ack> element has the following child element: For extensibility, the <ack> element has the following child element:
Name: actionResult Name: actionResult
Usage: Optional Usage: Optional
Direction: Provided for extension, sent from the IVS to the PSAP Direction: Provided for extension, sent from the IVS to the PSAP
Description: An <actionResult> element indicates the result of an Description: An <actionResult> element indicates the result of an
action (other than a 'send-data' action). When an <ack> element action (other than a 'send-data' action). When an <ack> element
skipping to change at page 13, line 43 skipping to change at page 14, line 15
Name: action Name: action
Usage: Mandatory Usage: Mandatory
Type: token Type: token
Direction: In this document, sent from the PSAP to the IVS Direction: In this document, sent from the PSAP to the IVS
Description: Contains the value of the 'action' attribute of the Description: Contains the value of the 'action' attribute of the
<request> element <request> element
Name: success Name: success
Usage: Mandatory Usage: Mandatory
Type: Boolean Type: Boolean
Direction: Provided for extension, sent from the IVS to the PSAP Direction: Sent from the IVS to the PSAP
Description: Indicates if the action was successfully Description: Indicates if the action was successfully
accomplished accomplished
Name: reason Name: reason
Usage: Conditional Usage: Conditional
Type: token Type: token
Direction: Provided for extension, sent from the IVS to the PSAP Direction: Sent from the IVS to the PSAP
Description: Used when 'success' is "False", this attribute Description: Used when 'success' is "false", this attribute
contains a reason code for a failure. A registry for reason contains a reason code for a failure. A registry for reason
codes is defined in Section 15.8.2. codes is defined in Section 15.8.2.
Name: details Name: details
Usage: optional Usage: optional
Type: string Type: string
Direction: Provided for extension, sent from the IVS to the PSAP Direction: Sent from the IVS to the PSAP
Description: Contains further explanation of the circumstances of Description: Contains further explanation of the circumstances of
a success or failure. The contents are implementation-specific a success or failure. The contents are implementation-specific
and human-readable. and human-readable.
9.1.1.3. Ack Examples 9.1.1.3. Ack Examples
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCall.Control <EmergencyCallData.eCall.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
skipping to change at page 17, line 36 skipping to change at page 18, line 11
This document registers the 'emergencyCallData.eCall.MSD' INFO This document registers the 'emergencyCallData.eCall.MSD' INFO
package. package.
Both endpoints (the IVS and the PSAP equipment) include Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.MSD' in a Recv-Info header field per 'emergencyCallData.eCall.MSD' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO messages carrying data [RFC6086] to indicate ability to receive INFO messages carrying data
as described here. as described here.
Support for the 'emergencyCallData.eCall.MSD' INFO package indicates Support for the 'emergencyCallData.eCall.MSD' INFO package indicates
the ability to receive the MSD and metadata/control body parts as the ability to receive eCall related body parts as specified in [TBD:
specified in [TBD: THIS DOCUMENT]. THIS DOCUMENT].
An INFO request message carrying body parts related to an emergency An INFO request message carrying body parts related to an emergency
call as described in [TBD: THIS DOCUMENT] has an Info-Package header call as described in [TBD: THIS DOCUMENT] has an Info-Package header
field set to 'emergencyCallData.eCall.MSD' per [RFC6086]. field set to 'emergencyCallData.eCall.MSD' per [RFC6086].
10.1. INFO Package Requirements
The requirements of Section 10 of [RFC6086] are addressed in the The requirements of Section 10 of [RFC6086] are addressed in the
following sections. following sections.
10.1.1. Overall Description 10.1. Overall Description
This section describes "what type of information is carried in INFO This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package." applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall.MSD INFO INFO requests associated with the emergencyCallData.eCall.MSD INFO
package carry data associated with emergency calls as defined in package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs. data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information. Refer to [TBD: THIS DOCUMENT] for more information.
10.1.2. Applicability 10.2. Applicability
This section describes "why the Info Package mechanism, rather than This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...." some other mechanism, has been chosen for the specific use-case...."
The use of INFO is based on an analysis of the requirements against The use of INFO is based on an analysis of the requirements against
the intent and effects of INFO versus other approaches (which the intent and effects of INFO versus other approaches (which
included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane
transport, and non-SIP protocols). In particular, the transport of transport, and non-SIP protocols). In particular, the transport of
emergency call data blocks occurs within a SIP emergency dialog, per emergency call data blocks occurs within a SIP emergency dialog, per
Section 6, and is normally carried in the initial INVITE and its Section 6, and is normally carried in the initial INVITE and its
skipping to change at page 18, line 48 skipping to change at page 19, line 15
is two-way communication of data related to the emergency dialog. is two-way communication of data related to the emergency dialog.
Use of the media plane mechanisms was discounted because the number Use of the media plane mechanisms was discounted because the number
of messages needing to be exchanged in a dialog is normally zero or of messages needing to be exchanged in a dialog is normally zero or
very few, and the size of the data is likewise very small. The very few, and the size of the data is likewise very small. The
overhead caused by user plane setup (e.g., to use MSRP as transport) overhead caused by user plane setup (e.g., to use MSRP as transport)
would be disproportionately large. would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport. for mid-call data transport.
10.1.3. Info Package Name 10.3. Info Package Name
The info package name is emergencyCallData.eCall.MSD The info package name is emergencyCallData.eCall.MSD
10.1.4. Info Package Parameters 10.4. Info Package Parameters
None None
10.1.5. SIP Option-Tags 10.5. SIP Option-Tags
None None
10.1.6. INFO Message Body Parts 10.6. INFO Message Body Parts
The 'application/emergencyCallData.eCall.MSD+per' and 'application/ The body for an emergencyCallData.eCall.MSD info package is:
emergencyCallData.eCall.control+xml' MIME types are associated with
this INFO package. See [TBD: THIS DOCUMENT] for more information.
10.1.7. Info Package Usage Restrictions o an application/emergencyCallData.eCall.MSD+per (containing an
MSD), or
o an application/emergencyCallData.eCall.control+xml (containing a
metadata/control object), or
o a multipart body containing:
* zero or one application/emergencyCallData.eCall.MSD+per part
(containing an MSD),
* zero or more application/emergencyCallData.eCall.control+xml
(containing a metadata/control object),
The body parts are sent per [RFC6086], and in addition, to align with
with how these body parts are sent in non-INFO messages, each
associated body part is referenced by a Call-Info header field at the
top level of the SIP message. If the body part is the only body
part, it has a Content-Disposition header field value of "INFO-
Package; handling=optional". If the body part is contained within a
multipart body part, it has a Content-Disposition header field value
of "By-Reference; handling=optional" (the top-level multipart body
part has "INFO-Package" in its Content-Disposition value).
See [TBD: THIS DOCUMENT] for more information.
10.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
10.1.8. Rate of INFO Requests 10.8. Rate of INFO Requests
The rate of SIP INFO requests associated with the The rate of SIP INFO requests associated with the
emergencyCallData.eCall.MSD info package is normally quite low (most emergencyCallData.eCall.MSD info package is normally quite low (most
dialogs are likely to contain zero INFO requests, while others can be dialogs are likely to contain zero INFO requests, while others can be
expected to carry an occasional request). expected to carry an occasional request).
10.1.9. Info Package Security Considerations 10.9. Info Package Security Considerations
The MIME content type registations for the data blocks that can be The MIME content type registations for the data blocks that can be
carried using this IFO package contains a discussion of the security carried using this INFO package contains a discussion of the security
and/or privacy considerations specific to that data block. The and/or privacy considerations specific to that data block. The
"Security Considerations" and "Privacy Considerations" sections of "Security Considerations" and "Privacy Considerations" sections of
[TBD: THIS DOCUMENT] discuss security and privacy considerations of [TBD: THIS DOCUMENT] discuss security and privacy considerations of
the data carried in eCalls. the data carried in eCalls.
10.1.10. Implementation Details 10.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details. See [TBD: THIS DOCUMENT] for protocol details.
10.1.11. Examples 10.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples. See [TBD: THIS DOCUMENT] for protocol examples.
11. Examples 11. Examples
Figure 6 illustrates an eCall. The call uses the request URI Figure 6 illustrates an eCall. The call uses the request URI
'urn:service:sos.ecall.automatic' service URN and is recognized as an 'urn:service:sos.ecall.automatic' service URN and is recognized as an
eCall, and further as one that was invoked automatically by the IVS eCall, and further as one that was invoked automatically by the IVS
due to a crash or other serious incident. In this example, the due to a crash or other serious incident. In this example, the
originating network routes the call to an ESInet which routes the originating network routes the call to an ESInet which routes the
skipping to change at page 22, line 11 skipping to change at page 23, line 11
blocks added by the IVS or the originating mobile network. Because blocks added by the IVS or the originating mobile network. Because
the MSD is encoded in ASN.1 PER, which is a binary encoding, its the MSD is encoded in ASN.1 PER, which is a binary encoding, its
contents cannot be included in a text document. contents cannot be included in a text document.
INVITE urn:service:sos.ecall.automatic SIP/2.0 INVITE urn:service:sos.ecall.automatic SIP/2.0
To: urn:service:sos.ecall.automatic To: urn:service:sos.ecall.automatic
From: <sip:+13145551111@example.com>;tag=9fxced76sl From: <sip:+13145551111@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Geolocation: <cid:target123@example.com> Geolocation: <cid:target123@example.com>
Geolocation-Routing: no Geolocation-Routing: no
Call-Info: cid:1234567890@atlanta.example.com; Call-Info: <cid:1234567890@atlanta.example.com>;
purpose=emergencyCallData.eCall.MSD; purpose=emergencyCallData.eCall.MSD
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml application/emergencyCallData.eCall.control+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall.MSD Recv-Info: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...Session Description Protocol (SDP) goes here... ...Session Description Protocol (SDP) goes here...
--boundary1 --boundary1
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD+per
Content-ID: 1234567890@atlanta.example.com Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
Content-Transfer-Encoding: binary
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundary1-- --boundary1--
Figure 8: SIP NG-eCall INVITE Figure 8: SIP NG-eCall INVITE
Continuing the example, Figure 9 illustrates a SIP 200 OK response to Continuing the example, Figure 9 illustrates a SIP 200 OK response to
the INVITE of Figure 8, containing an eCall control block the INVITE of Figure 8, containing an eCall control block
acknowledging successful receipt of the eCall MSD. (For simplicity, acknowledging successful receipt of the eCall MSD. (For simplicity,
the example does not show all SIP headers.) the example does not show all SIP headers.)
SIP/2.0 200 OK SIP/2.0 200 OK
To: <sip:+13145551111@example.com>;tag=9fxced76sl To: <sip:+13145551111@example.com>;tag=9fxced76sl
From: Exemplar PSAP <urn:service:sos.ecall.automatic> From: Exemplar PSAP <urn:service:sos.ecall.automatic>
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: cid:2345678901@atlanta.example.com; Call-Info: <cid:2345678901@atlanta.example.com>;
purpose=emergencyCallData.eCall.control; purpose=emergencyCallData.eCall.control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml, application/emergencyCallData.eCall.control+xml,
application/emergencyCallData.eCall.MSD+per application/emergencyCallData.eCall.MSD+per
CSeq: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall.MSD Recv-Info: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: multipart/mixed; boundary=boundaryX Content-Type: multipart/mixed; boundary=boundaryX
Content-Length: ... Content-Length: ...
--boundaryX --boundaryX
Content-Type: application/sdp Content-Type: application/sdp
...Session Description Protocol (SDP) goes here... ...Session Description Protocol (SDP) goes here...
--boundaryX --boundaryX
Content-Type: application/EmergencyCallData.eCall.control+xml Content-Type: application/EmergencyCallData.eCall.control+xml
Content-ID: 2345678901@atlanta.example.com Content-ID: <2345678901@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCall.Control <EmergencyCallData.eCall.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control">
<ack received="true" ref="1234567890@atlanta.example.com"/> <ack received="true" ref="1234567890@atlanta.example.com"/>
skipping to change at page 24, line 8 skipping to change at page 25, line 8
Figure 9: 200 OK response to INVITE Figure 9: 200 OK response to INVITE
Figure 10 illustrates an INFO message containing an eCall metadata/ Figure 10 illustrates an INFO message containing an eCall metadata/
control block requesting an eCall MSD. (For simplicity, the example control block requesting an eCall MSD. (For simplicity, the example
does not show all SIP headers.) does not show all SIP headers.)
INFO sip:+13145551111@example.com SIP/2.0 INFO sip:+13145551111@example.com SIP/2.0
To: <sip:+13145551111@example.com>;tag=9fxced76sl To: <sip:+13145551111@example.com>;tag=9fxced76sl
From: Exemplar PSAP <urn:service:sos.ecall.automatic> From: Exemplar PSAP <urn:service:sos.ecall.automatic>
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: cid:3456789012@atlanta.example.com; Call-Info: <cid:3456789012@atlanta.example.com>;
purpose=emergencyCallData.eCall.control; purpose=emergencyCallData.eCall.control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml, application/emergencyCallData.eCall.control+xml,
application/emergencyCallData.eCall.MSD+per application/emergencyCallData.eCall.MSD+per
CSeq: 41862 INFO CSeq: 41862 INFO
Recv-Info: emergencyCallData.eCall.MSD Info-Package: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Disposition: info-package; handling=optional
Content-Type: application/EmergencyCallData.eCall.control+xml Content-Type: application/EmergencyCallData.eCall.control+xml
Content-ID: 3456789012@atlanta.example.com Content-ID: <3456789012@atlanta.example.com>
Content-Disposition: info-package
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCall.Control <EmergencyCallData.eCall.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"> "urn:ietf:params:xml:ns:EmergencyCallData:eCall:control">
<request action="send-data" datatype="eCall.MSD"/> <request action="send-data" datatype="eCall.MSD"/>
skipping to change at page 25, line 9 skipping to change at page 26, line 9
Figure 11 illustrates a SIP eCall INFO that contains an MSD. For Figure 11 illustrates a SIP eCall INFO that contains an MSD. For
simplicity, the example does not show all SIP headers. Because the simplicity, the example does not show all SIP headers. Because the
MSD is encoded in ASN.1 PER, which is a binary encoding, its contents MSD is encoded in ASN.1 PER, which is a binary encoding, its contents
cannot be included in a text document. cannot be included in a text document.
INFO urn:service:sos.ecall.automatic SIP/2.0 INFO urn:service:sos.ecall.automatic SIP/2.0
To: urn:service:sos.ecall.automatic To: urn:service:sos.ecall.automatic
From: <sip:+13145551111@example.com>;tag=9fxced76sl From: <sip:+13145551111@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: cid:4567890123@atlanta.example.com; Call-Info: <cid:4567890123@atlanta.example.com>;
purpose=emergencyCallData.eCall.MSD; purpose=emergencyCallData.eCall.MSD
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control+xml application/emergencyCallData.eCall.control+xml
CSeq: 51862 INFO CSeq: 51862 INFO
Recv-Info: emergencyCallData.eCall.MSD Info-Package: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD+per
Content-ID: 4567890123@atlanta.example.com Content-ID: <4567890123@atlanta.example.com>
Content-Disposition: info-package Content-Disposition: info-package; handling=optional
Content-Transfer-Encoding: binary
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
Figure 11: INFO containing MSD Figure 11: INFO containing MSD
12. Security Considerations 12. Security Considerations
The security considerations described in [RFC5069] apply here. The security considerations described in [RFC5069] apply here.
In addition to any network-provided location (which might be In addition to any network-provided location (which might be
skipping to change at page 36, line 40 skipping to change at page 37, line 40
feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith
Drage, Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, and Drage, Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, and
James Winterbottom for their review and comments; Robert Sparks and James Winterbottom for their review and comments; Robert Sparks and
Paul Kyzivat for their help with the SIP mechanisms. We would like Paul Kyzivat for their help with the SIP mechanisms. We would like
to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and
Ulrich Dietz for their help with the original document upon which Ulrich Dietz for their help with the original document upon which
this document is based. this document is based.
18. Changes from Previous Versions 18. Changes from Previous Versions
18.1. Changes from draft-ietf-09 to draft-ietf-11 18.1. Changes from draft-ietf-11 to draft-ietf-12
o Fixed errors in examples found by Dale
o Removed enclosing sub-section of INFO package registration section
o Added text per Christer and Dale's suggestions that the MSD and
metadata/control blocks are sent in INFO with a Call-Info header
field referencing them
o Deleted Call Routing section (7.1) in favor of a statement that
call routing is outside the scope of the document
o Other text changes per comments received from Christer and Ivo.
18.2. Changes from draft-ietf-09 to draft-ietf-11
o Renamed INFO package to emergencyCallData.eCall.MSD o Renamed INFO package to emergencyCallData.eCall.MSD
o Changed INFO package to only permit MSD and metadata/control MIME o Changed INFO package to only permit MSD and metadata/control MIME
types types
o Moved <capabilities> element back from car-crash but made it o Moved <capabilities> element back from car-crash but made it
OPTIONAL OPTIONAL
o Moved other extension points back from car-crash so that extension o Moved other extension points back from car-crash so that extension
points are in base spec (and also to get XML schema to compile) points are in base spec (and also to get XML schema to compile)
o Text changes for clarification. o Text changes for clarification.
18.2. Changes from draft-ietf-08 to draft-ietf-09 18.3. Changes from draft-ietf-08 to draft-ietf-09
o Created a new "Data Transport" section that describes how the MSD o Created a new "Data Transport" section that describes how the MSD
and metadata/control blocks are attached, and then referred to and metadata/control blocks are attached, and then referred to
that section rather than repeat the information about the CID and that section rather than repeat the information about the CID and
Call-Info and so forth, which means most references to the Call-Info and so forth, which means most references to the
additional-data draft have now been deleted additional-data draft have now been deleted
o Mentioned edge cases where a PSAP response to INVITE isn't o Mentioned edge cases where a PSAP response to INVITE isn't
received by the IVS received by the IVS
o Reworded description of which status codes are used when a PSAP o Reworded description of which status codes are used when a PSAP
wishes to reject a call but inform the vehicle occupants that it wishes to reject a call but inform the vehicle occupants that it
is aware of the situation to be more definite is aware of the situation to be more definite
o Added examples showing INFO o Added examples showing INFO
o Added references for eCall test call requirement o Added references for eCall test call requirement
o Described meaning of eCall URNs in Section 8 as well as in IANA o Described meaning of eCall URNs in Section 8 as well as in IANA
registration registration
18.3. Changes from draft-ietf-07 to draft-ietf-08 18.4. Changes from draft-ietf-07 to draft-ietf-08
o eCall MSD now encoded as ASN.1 PER, using binary content transfer o eCall MSD now encoded as ASN.1 PER, using binary content transfer
encoding encoding
o Added text to point out aspects of call handling and metadata/ o Added text to point out aspects of call handling and metadata/
control usage, such as use in rejected calls, and solicited MSDs control usage, such as use in rejected calls, and solicited MSDs
o Revised use of INFO to require that when a request for an MSD is o Revised use of INFO to require that when a request for an MSD is
sent in INFO, the MSD sent in response is in its own INFO, not the sent in INFO, the MSD sent in response is in its own INFO, not the
response to the requesting INFO response to the requesting INFO
o Added material to INFO package registation to comply with o Added material to INFO package registation to comply with
Section 10 of [RFC6086] Section 10 of [RFC6086]
o Moved material not required by 3GPP into o Moved material not required by 3GPP into
[I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/ [I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/
control elements, attributes, and values control elements, attributes, and values
o Revised test call wording to clarify that specific handling is out o Revised test call wording to clarify that specific handling is out
of scope of scope
o Revised wording throughout the document to simplify o Revised wording throughout the document to simplify
o Moved new Section Section 7.1 to be a subsection of Section 7 o Moved new Section 7.1 to be a subsection of 7
o Moved new Section Section 10 to be a main section instead of a o Moved new Section Section 10 to be a main section instead of a
subsection of Section 9 subsection of Section 9
o Revised SIP INFO usage and package registration per advice from o Revised SIP INFO usage and package registration per advice from
Robert Sparks and Paul Kyzivat Robert Sparks and Paul Kyzivat
18.4. Changes from draft-ietf-06 to draft-ietf-07 18.5. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.5. Changes from draft-ietf-05 to draft-ietf-06 18.6. Changes from draft-ietf-05 to draft-ietf-06
o Added additional security and privacy clarifications regarding o Added additional security and privacy clarifications regarding
signed and encrypted data signed and encrypted data
o Additional security and privacy text o Additional security and privacy text
o Deleted informative section on ESINets as unnecessary. o Deleted informative section on ESINets as unnecessary.
18.6. Changes from draft-ietf-04 to draft-ietf-05 18.7. Changes from draft-ietf-04 to draft-ietf-05
o Reworked the security and privacy considerations material in the o Reworked the security and privacy considerations material in the
document as a whole and in the MIME registation sections of the document as a whole and in the MIME registation sections of the
MSD and control objects MSD and control objects
o Clarified that the <actionResult> element can appear multiple o Clarified that the <actionResult> element can appear multiple
times within an <ack> element times within an <ack> element
o Fixed IMS definition o Fixed IMS definition
o Added clarifying text for the 'msgid' attribute o Added clarifying text for the 'msgid' attribute
18.7. Changes from draft-ietf-03 to draft-ietf-04 18.8. Changes from draft-ietf-03 to draft-ietf-04
o Added Privacy Considerations section o Added Privacy Considerations section
o Reworded most uses of non-normative "may", "should", "must", and o Reworded most uses of non-normative "may", "should", "must", and
"recommended." "recommended."
o Fixed nits in examples o Fixed nits in examples
18.8. Changes from draft-ietf-02 to draft-ietf-03 18.9. Changes from draft-ietf-02 to draft-ietf-03
o Added request to enable cameras o Added request to enable cameras
o Improved examples and XML schema o Improved examples and XML schema
o Clarifications and wording improvements o Clarifications and wording improvements
18.9. Changes from draft-ietf-01 to draft-ietf-02 18.10. Changes from draft-ietf-01 to draft-ietf-02
o Added clarifying text reinforcing that the data exchange is for o Added clarifying text reinforcing that the data exchange is for
small blocks of data infrequently transmitted small blocks of data infrequently transmitted
o Clarified that dynamic media is conveyed using SIP re-INVITE to o Clarified that dynamic media is conveyed using SIP re-INVITE to
establish a one-way media stream establish a one-way media stream
o Clarified that the scope is the needs of eCall within the SIP o Clarified that the scope is the needs of eCall within the SIP
emergency call environment emergency call environment
o Added informative statement that the document may be suitable for o Added informative statement that the document may be suitable for
reuse by other ACN systems reuse by other ACN systems
o Clarified that normative language for the control block applies to o Clarified that normative language for the control block applies to
both IVS and PSAP both IVS and PSAP
o Removed 'ref', 'supported-mime', and <media> elements o Removed 'ref', 'supported-mime', and <media> elements
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.10. Changes from draft-ietf-00 to draft-ietf-01 18.11. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications in addition to eCall crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME content type for the eCall o Added IANA registration for the MIME content type for the eCall
control object control object
o Added IANA registries for protocol elements and tokens used in the o Added IANA registries for protocol elements and tokens used in the
eCall control object eCall control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.11. Changes from draft-gellens-03 to draft-ietf-00 18.12. Changes from draft-gellens-03 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf-. o Renamed from draft-gellens- to draft-ietf-.
o Added mention of and reference to ETSI TR "Mobile Standards Group o Added mention of and reference to ETSI TR "Mobile Standards Group
(MSG); eCall for VoIP" (MSG); eCall for VoIP"
o Added text to Introduction regarding migration/co-existence being o Added text to Introduction regarding migration/co-existence being
out of scope out of scope
o Added mention in Security Considerations that even if the network- o Added mention in Security Considerations that even if the network-
supplied location is just the cell site, this can be useful as a supplied location is just the cell site, this can be useful as a
sanity check on the IVS-supplied location sanity check on the IVS-supplied location
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.12. Changes from draft-gellens-02 to -03 18.13. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.13. Changes from draft-gellens-01 to -02 18.14. Changes from draft-gellens-01 to -02
o Minor wording improvements o Minor wording improvements
o Removed ".automatic" and ".manual" from o Removed ".automatic" and ".manual" from
"urn:service:test.sos.ecall" registration and discussion text. "urn:service:test.sos.ecall" registration and discussion text.
18.14. Changes from draft-gellens-00 to -01 18.15. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to [RFC7852] MIME subtypes, in accordance with changes to [RFC7852]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
19. References 19. References
19.1. Normative References 19.1. Normative References
[EN_16062] [EN_16062]
CEN, , "Intelligent transport systems - eSafety - eCall CEN, , "Intelligent transport systems - eSafety - eCall
High Level Application Requirements (HLAP) Using GSM/UMTS High Level Application Requirements (HLAP) Using GSM/UMTS
Circuit Switched Networks, EN 16062", April 2015. Circuit Switched Networks, EN 16062", April 2015.
[EN_16072] [EN_16072]
CEN, , "Intelligent transport systems - eSafety - Pan- CEN, , "Intelligent transport systems - eSafety - Pan-
European eCall operating requirements, EN 16072", April European eCall operating requirements, EN 16072", April
skipping to change at page 41, line 27 skipping to change at page 42, line 32
principles". principles".
19.2. Informative references 19.2. Informative references
[CEN] "European Committee for Standardization", [CEN] "European Committee for Standardization",
<http://www.cen.eu>. <http://www.cen.eu>.
[I-D.ietf-ecrit-car-crash] [I-D.ietf-ecrit-car-crash]
Gellens, R., Rosen, B., and H. Tschofenig, "Next- Gellens, R., Rosen, B., and H. Tschofenig, "Next-
Generation Vehicle-Initiated Emergency Calls", draft-ietf- Generation Vehicle-Initiated Emergency Calls", draft-ietf-
ecrit-car-crash-08 (work in progress), July 2016. ecrit-car-crash-09 (work in progress), August 2016.
[MSG_TR] ETSI, , "ETSI Mobile Standards Group (MSG); eCall for [MSG_TR] ETSI, , "ETSI Mobile Standards Group (MSG); eCall for
VoIP", ETSI Technical Report TR 103 140 V1.1.1 (2014-04), VoIP", ETSI Technical Report TR 103 140 V1.1.1 (2014-04),
April 2014. April 2014.
[RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, DOI 10.17487/RFC5012, January 2008, RFC 5012, DOI 10.17487/RFC5012, January 2008,
<http://www.rfc-editor.org/info/rfc5012>. <http://www.rfc-editor.org/info/rfc5012>.
 End of changes. 77 change blocks. 
159 lines changed or deleted 217 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/