draft-ietf-ecrit-car-crash-23.txt   rfc8148.txt 
ECRIT R. Gellens Internet Engineering Task Force (IETF) R. Gellens
Internet-Draft Core Technology Consulting Request for Comments: 8148 Core Technology Consulting
Intended status: Standards Track B. Rosen Category: Standards Track B. Rosen
Expires: July 23, 2017 NeuStar, Inc. ISSN: 2070-1721 NeuStar, Inc.
H. Tschofenig H. Tschofenig
Individual Individual
January 19, 2017 May 2017
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-23.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 emergency calls placed mechanisms to support the next generation of emergency calls placed
by vehicles (automatically in the event of a crash or serious by vehicles (automatically in the event of a crash or serious
incident, or manually invoked by a vehicle occupant) and conveying incident, or manually invoked by a vehicle occupant) and conveying
vehicle, sensor, and location data related to the crash or incident. vehicle, sensor, and location data related to the crash or incident.
Such calls are often referred to as "Automatic Crash Notification" Such calls are often referred to as "Automatic Crash Notification"
(ACN), or "Advanced Automatic Crash Notification" (AACN), even in the (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the
case of manual trigger. The "Advanced" qualifier refers to the case of manual trigger. The "Advanced" qualifier refers to the
ability to carry a richer set of data. ability to carry a richer set of data.
This document also registers a MIME media type and Emergency Call This document also registers a MIME media type and Emergency Call
Additional Data Block for the vehicle, sensor, and location data Data Type for the vehicle, sensor, and location data (often referred
(often referred to as "crash data" even though there is not to as "crash data" even though there is not necessarily a crash) and
necessarily a crash) and a SIP INFO package to enable carrying this an INFO package to enable carrying this and related data in SIP INFO
and related data in SIP INFO requests. An external specification for requests. An external specification for the data format, contents,
the data format, contents, and structure are referenced in this and structure is referenced in this document.
document.
This document reuses the technical aspects of next-generation pan- This document reuses the technical aspects of next-generation Pan-
European eCall (a mandated and standardized system for emergency European eCall (a mandated and standardized system for emergency
calls by in-vehicle systems within Europe and other regions). calls by in-vehicle systems (IVSs) within Europe and other regions).
However, this document specifies use of a different set of vehicle However, this document specifies use of a different set of vehicle
(crash) data, specifically, the Vehicle Emergency Data Set (VEDS) (crash) data, specifically, the Vehicle Emergency Data Set (VEDS)
rather than the eCall Minimum Set of Data (MSD). This document is an rather than the eCall Minimum Set of Data (MSD). This document is an
extension of the IETF eCall document, with the primary differences extension of the IETF eCall document, with the primary differences
being that this document makes the MSD data set optional and VEDS being that this document makes the MSD data set optional and VEDS
mandatory, and adds attribute values to the metadata/control object mandatory, and it adds attribute values to the metadata/control
to permit greater functionality. This document registers a new SIP object to permit greater functionality. This document registers a
INFO package (identical to that registered for eCall but with the new INFO package (identical to that registered for eCall but with the
addition of the VEDS MIME type). This document also describes legacy addition of the VEDS MIME type). This document also describes legacy
(circuit-switched) ACN systems and their migration to next-generation (circuit-switched) ACN systems and their migration to next-generation
emergency calling, to provide background information and context. emergency calling, to provide background information and context.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on July 23, 2017. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc8148.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8
4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8
5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9 5. Migration to Next Generation . . . . . . . . . . . . . . . . 10
6. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13 7. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 14
8. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 16
9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 16 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17
9.1. New values for the 'action' attribute' . . . . . . . . . 17 9.1. New Values for the "action" Attribute . . . . . . . . . . 18
9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 18 9.2. Example <request> Element . . . . . . . . . . . . . . . . 19
9.3. The <ack> element . . . . . . . . . . . . . . . . . . . . 19 9.3. The <ack> Element . . . . . . . . . . . . . . . . . . . . 19
9.4. The <capabilities> element . . . . . . . . . . . . . . . 20 9.4. The <capabilities> Element . . . . . . . . . . . . . . . 20
10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 21 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 11. Example Call Initiation . . . . . . . . . . . . . . . . . . . 22
12. Security Considerations . . . . . . . . . . . . . . . . . . . 27 12. Security Considerations . . . . . . . . . . . . . . . . . . . 27
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 28 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 28
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
14.1. MIME Media Type Registration for 14.1. MIME Media Type Registration for
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 28 application/EmergencyCall.VEDS+xml . . . . . . . . . . . 28
14.2. Registration of the 'VEDS' entry in the Emergency Call 14.2. Registration of the "VEDS" Entry in the Emergency Call
Data Types registry . . . . . . . . . . . . . . . . . . 30 Data Types Registry . . . . . . . . . . . . . . . . . . 30
14.3. New Action Values . . . . . . . . . . . . . . . . . . . 30 14.3. New Action Values . . . . . . . . . . . . . . . . . . . 30
14.4. Emergency Call Static Message Registry . . . . . . . . . 30 14.4. Emergency Call Static Messages Registry . . . . . . . . 31
14.5. Emergency Call Vehicle Lamp ID Registry . . . . . . . . 31 14.5. Emergency Call Vehicle Lamp IDs Registry . . . . . . . . 32
14.6. Emergency Call Vehicle Camera ID Registry . . . . . . . 32 14.6. Emergency Call Vehicle Camera IDs Registry . . . . . . . 33
14.7. The emergencyCallData.eCall.VEDS SIP INFO package . . . 33 14.7. The EmergencyCallData.VEDS INFO Package . . . . . . . . 35
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 38
16. Changes from Previous Versions . . . . . . . . . . . . . . . 37 15.1. Normative References . . . . . . . . . . . . . . . . . . 38
16.1. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 37 15.2. Informative references . . . . . . . . . . . . . . . . . 39
16.2. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 37 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 40
16.3. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
16.4. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 37
16.5. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 37
16.6. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 37
16.7. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 37
16.8. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38
16.9. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38
16.10. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38
16.11. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38
16.12. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38
16.13. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 38
16.14. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 38
16.15. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
16.16. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39
16.17. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39
16.18. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 39
16.19. Changes from draft-gellens-01 to -02 . . . . . . . . . . 39
16.20. Changes from draft-gellens-00 to -01 . . . . . . . . . . 39
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
17.1. Normative References . . . . . . . . . . . . . . . . . . 40
17.2. Informative references . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012].
Additionally, we use the following abbreviations:
+--------+----------------------------------------------------------+
| Term | Expansion |
+--------+----------------------------------------------------------+
| 3GPP | 3rd Generation Partnership Project |
| AACN | Advanced Automatic Crash Notification |
| ACN | Automatic Crash Notification |
| APCO | Association of Public-Safety Communications Officials |
| EENA | European Emergency Number Association |
| ESInet | Emergency Services IP network |
| GNSS | Global Navigation Satellite System (which includes |
| | various systems such as the Global Positioning System or |
| | GPS) |
| IVS | In-Vehicle System |
| MNO | Mobile Network Operator |
| MSD | eCall Minimum Set of Data |
| NENA | National Emergency Number Association |
| NG | Next-Generation |
| POTS | Plain Old Telephone Service (normal, circuit-switched |
| | voice calls) |
| PSAP | Public Safety Answering Point |
| TSP | Telematics Service Provider |
| VEDS | Vehicle Emergency Data Set |
+--------+----------------------------------------------------------+
Because the endpoints of a Next-Generation ACN call are a PSAP and an
IVS or TSP, to avoid receptively writing "IVS or TSP", the term "IVS"
is used to represent either an IVS or TSP when discussing signaling
behavior (e.g., sending VEDS data, sending a SIP INVITE request,
receiving a SIP INFO request, etc.).
2. Introduction 1. Introduction
Emergency calls made by in-vehicle systems (e.g., automatically in Emergency calls made by in-vehicle systems (e.g., automatically in
the event of a crash or serious incident or manually by a vehicle the event of a crash or serious incident or manually by a vehicle
occupant) assist in significantly reducing road deaths and injuries occupant) assist in significantly reducing road deaths and injuries
by allowing emergency services to respond quickly and appropriately by allowing emergency services to respond quickly and appropriately
to the specifics of the incident, often with better location to the specifics of the incident, often with better location
accuracy. accuracy.
Drivers often have a poor location awareness, especially outside of Drivers often have a poor location awareness, especially outside of
major cities, at night and when away from home (especially abroad). major cities, at night, and when away from home (especially abroad).
In the most crucial cases, the victim(s) might not be able to call In the most crucial cases, the victim(s) might not be able to call
because they have been injured or trapped. because they have been injured or trapped.
For more than two decades, some vehicles have been equipped with For more than two decades, some vehicles have been equipped with
telematics systems which, among other features, place an emergency telematics systems that, among other features, place an emergency
call automatically in the event of a crash or manually in response to call automatically in the event of a crash or manually in response to
an emergency call button. Such systems generally have on-board an emergency call button. Such systems generally have on-board
location determination systems that make use of satellite-based location determination systems that make use of satellite-based
positioning technology, inertial sensors, gyroscopes, etc., which can positioning technology, inertial sensors, gyroscopes, etc., which can
provide an accurate position for the vehicle. Such built-in systems provide an accurate position for the vehicle. Such built-in systems
can take advantage of the benefits of being integrated into a can take advantage of the benefits of being integrated into a
vehicle, such as more power capacity, ability to have larger or vehicle, such as more power capacity, ability to have larger or
specialized antenna, ability to be engineered to avoid or minimise specialized antenna, ability to be engineered to avoid or minimize
degradation by vehicle glass coatings, interference from other degradation by vehicle glass coatings, interference from other
vehicle systems, etc. Thus, the PSAP can be provided with a good vehicle systems, etc. Thus, the Public Safety Answering Point (PSAP)
estimate of where the vehicle is during an emergency. Vehicle can be provided with a good estimate of where the vehicle is during
manufacturers are increasingly adopting such systems, both for the an emergency. Vehicle manufacturers are increasingly adopting such
safety benefits and for the additional features and services they systems, both for the safety benefits and for the additional features
enable (e.g., remote engine diagnostics, remote door unlock, stolen and services they enable (e.g., remote engine diagnostics, remote
vehicle tracking and disabling, etc.). door unlock, stolen vehicle tracking and disabling, etc.).
The general term for such systems is Automatic Crash Notification A common term for such systems is Automatic Crash Notification (ACN)
(ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is or Advanced Automatic Crash Notification (AACN). Sometimes the word
used in this document as a general term. ACN systems transmit some "Collision" is used instead of "Crash." In this document, "ACN" is
amount of data specific to the incident, referred to generally as used as a general term. ACN systems transmit some amount of data
"crash data" (the term is commonly used even though there might not specific to the incident, referred to generally as "crash data" (the
have been a crash). While different systems transmit different term is commonly used even though there might not have been a crash).
amounts of crash data, standardized formats, structures, and While different systems transmit different amounts of crash data,
mechanisms are needed to provide interoperability among systems and standardized formats, structures, and mechanisms are needed to
PSAPs. provide interoperability among systems and PSAPs.
As of the date of this document, currently deployed in-vehicle As of the date of this document, currently deployed in-vehicle
telematics systems are circuit-switched and lack a standards-based telematics systems are circuit-switched and lack a standards-based
ability to convey crash data directly to the PSAP (generally relying ability to convey crash data directly to the PSAP (generally relying
on either a human advisor or an automated text-to-speech system to on either a human advisor or an automated text-to-speech system to
provide the PSAP call taker with some crash data orally, or in some provide the PSAP call taker with some crash data orally, or in some
cases via a proprietary mechanism). In most cases, the PSAP call cases via a proprietary mechanism). In most cases, the PSAP call
taker needs to first realize that the call is related to a vehicle taker needs to first realize that the call is related to a vehicle
incident, and then listen to the data and transcribe it. Circuit- incident, and then listen to the data and transcribe it. Circuit-
switched ACN systems are referred to here as CS-ACN. switched ACN systems are referred to here as "CS-ACN".
The transition to next-generation calling in general, and for The transition to next-generation emergency calling provides an
emergency calling in particular, provides an opportunity to vastly opportunity to vastly improve the scope, breadth, reliability, and
improve the scope, breadth, reliability and usefulness of crash data usefulness of crash data by transmitting a standardized set during
during an emergency by allowing a standardized set to be transmitted call setup; the data can be processed by the PSAP in an integrated,
during call set-up; to be automatically processed by the PSAP and automated way and made available to the call taker at call
made available to the call taker in an integrated, automated way; as presentation. It also provides the ability for the call taker to
well as provide the ability for a PSAP call taker to request that a request that a vehicle take certain actions, such as flashing lights
vehicle take certain actions, such as flashing lights or unlocking or unlocking doors. In addition, vehicle manufacturers are provided
doors. In addition, vehicle manufacturers are provided an an opportunity to take advantage of the same standardized mechanisms
opportunity to take advantage of the same standardized mechanisms for for data transmission and request processing for internal use if they
data transmission and request processing for internal use if they
wish (such as telemetry between the vehicle and a service center for wish (such as telemetry between the vehicle and a service center for
both emergency and non-emergency uses, including location-based both emergency and non-emergency uses, including location-based
services, multi-media entertainment systems, remote door unlocking, services, multimedia entertainment systems, remote door unlocking,
remote diagnostics, and road-side assistance applications). remote diagnostics, and roadside assistance applications).
Next-generation ACN provides an opportunity for such calls to be Next-generation ACN provides an opportunity for such calls to be
recognized and processed as such during call set-up, and routed to an recognized and processed as such during call setup, and routed to an
equipped PSAP where the vehicle data is available to assist the call equipped PSAP where the vehicle data is available to assist the call
taker in assessing and responding to the situation. Next-generation taker in assessing and responding to the situation. Next-generation
(IP-based) ACN systems are referred to here as NG-ACN. (IP-based) ACN systems are referred to here as NG-ACN.
An ACN call can be initiated by a vehicle occupant or automatically An ACN call can be initiated by a vehicle occupant or automatically
initiated by vehicle systems in the event of a serious incident. initiated by vehicle systems in the event of a serious incident.
(The "A" in "ACN" does stand for "Automatic," but the term is broadly (The "A" in "ACN" does stand for "Automatic", but the term is broadly
used to refer to the class of calls that are placed by an in-vehicle used to refer to the class of calls that are placed by an in-vehicle
system (IVS) or Telematics Service Providers (TSP) and that carry system (IVS) or by Telematics Service Providers (TSPs) and that carry
incident-related data as well as voice.) Automatically triggered incident-related data as well as voice.) Automatically triggered
calls indicate a car crash or some other serious incident (e.g., a calls indicate a car crash or some other serious incident (e.g., a
fire). Manually triggered calls include reports of observed crashes fire). Manually triggered calls include reports of observed crashes
or serious hazards (such as impaired drivers or roadway debris). or serious hazards (such as impaired drivers or roadway debris),
requests for medical assistance, etc.
The Association of Public-Safety Communications Officials (APCO) and The Association of Public-Safety Communications Officials (APCO) and
the National Emergency Number Association (NENA) have jointly the National Emergency Number Association (NENA) have jointly
developed a standardized set of incident-related vehicle data for ACN developed a standardized set of incident-related vehicle data for ACN
use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data
is often referred to as crash data although it is applicable in is often referred to as crash data although it is applicable in
incidents other than crashes. incidents other than crashes.
This document describes how the IETF mechanisms for IP-based This document describes how the IETF mechanisms for IP-based
emergency calls are used to provide the realization of next- emergency calls are used to provide the realization of next-
generation ACN. Although this specification is designed with the generation ACN. Although this specification is designed with the
requirements for North America ACN in mind (and both APCO and NENA requirements for North America ACN in mind (and both APCO and NENA
are based in the U.S.), it is specified generically such that the are based in the U.S.), it is specified generically such that the
technology can be re-used or extended to suit requirements in other technology can be reused or extended to suit requirements in other
regions. regions.
This document reuses the technical aspects of next-generation pan- This document reuses the technical aspects of next-generation Pan-
European eCall (a mandated and standardized system for emergency European eCall (a mandated and standardized system for emergency
calls by in-vehicle systems within Europe), as described in calls by in-vehicle systems within Europe), as described in
[I-D.ietf-ecrit-ecall]. However, this document specifies use of a [RFC8147]. However, this document specifies use of a different set
different set of vehicle (crash) data, specifically, the Vehicle of vehicle (crash) data, specifically, VEDS rather than the eCall
Emergency Data Set (VEDS) rather than the eCall Minimum Set of Data Minimum Set of Data (MSD). This document is an extension of
(MSD). This document is an extension of [I-D.ietf-ecrit-ecall], with [RFC8147], with the differences being that this document makes the
the differences being that this document makes the MSD data set MSD data set optional and VEDS mandatory, and it adds new attribute
optional and VEDS mandatory, and adds new attribute values to the values to the metadata/control object defined in that document. This
metadata/control object defined in that document. This document also document also registers a new INFO package (identical to that defined
registers a new SIP INFO package (identical to that defined in in [RFC8147] with the addition of the VEDS MIME type).
[I-D.ietf-ecrit-ecall] with the addition of the VEDS MIME type).
This document registers the 'application/EmergencyCallData.VEDS+xml' This document registers the application/EmergencyCallData.VEDS+xml
MIME media type, registers the 'VEDS' entry in the Emergency Call MIME media type, the VEDS Emergency Call Data Type, and the
Data Types registry, and registers a SIP INFO package to enable EmergencyCallData.VEDS INFO package to enable carrying this and
carrying this and related data in SIP INFO requests. related data in SIP INFO requests.
Section 6 introduces VEDS. Section 7 describes how VEDS data and Section 6 introduces VEDS. Section 7 describes how VEDS data and
metadata/control blocks are transported within NG-ACN calls. metadata/control blocks are transported within NG-ACN calls.
Section 8 describes how such calls are placed. Section 8 describes how such calls are placed.
These mechanisms are used to place emergency calls that are These mechanisms are used to place emergency calls that are
identifiable as ACN calls and that carry standardized crash data in identifiable as ACN calls and that carry standardized crash data in
an interoperable way. an interoperable way.
Calls by in-vehicle systems are placed using cellular networks, which Calls by in-vehicle systems are placed using cellular networks, which
might ignore location information sent by an originating device in an might ignore location information sent by an originating device in an
emergency call INVITE, instead substituting their own location emergency call INVITE, instead substituting their own location
information (often determined in cooperation with the originating information (although often determined in cooperation with the
device). Standardized crash data structures often include location originating device). Standardized crash data structures typically
as determined by the IVS. A benefit of this is that it allows the include location as determined by the IVS. A benefit of this is that
PSAP to see both the location as determined by the cellular network it allows the PSAP to see both the location as determined by the
(often in cooperation with the originating device) and the location cellular network and the location as determined by the IVS.
as determined by the IVS.
This specification inherits the ability to utilize test call This specification inherits the ability to utilize test call
functionality from Section 15 of [RFC6881]. functionality from Section 15 of [RFC6881].
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
This document reuses terminology defined in Section 3 of [RFC5012].
Additionally, we use the following abbreviations:
3GPP: 3rd Generation Partnership Project
AACN: Advanced Automatic Crash Notification
ACN: Automatic Crash Notification
APCO: Association of Public-Safety Communications Officials
EENA: European Emergency Number Association
ESInet: Emergency Services IP network
GNSS: Global Navigation Satellite System (which includes
various systems such as the Global Positioning System or
GPS)
IVS: In-Vehicle System
MNO: Mobile Network Operator
MSD: Minimum Set of Data
NENA: National Emergency Number Association
NG: Next Generation
POTS: Plain Old Telephone Service (normal, circuit-switched
voice calls)
PSAP: Public Safety Answering Point
TSP: Telematics Service Provider
VEDS: Vehicle Emergency Data Set
Because the endpoints of a next-generation ACN call are a PSAP and
either an IVS or a TSP, to avoid repetitively writing "IVS or TSP",
the term "IVS" is used to represent either an IVS or a TSP when
discussing signaling behavior (e.g., sending VEDS data, sending a SIP
INVITE request, receiving a SIP INFO request, etc.).
3. Document Scope 3. Document Scope
This document is focused on how an ACN emergency call is setup and This document is focused on how an ACN emergency call is set up and
incident-related data (including vehicle, sensor, and location data) incident-related data (including vehicle, sensor, and location data)
is transmitted to the PSAP using IETF specifications. For the direct is transmitted to the PSAP using IETF specifications. For the direct
model, this is the end-to-end description (between the vehicle and model, this is the end-to-end description (between the vehicle and
the PSAP). For the TSP model, this describes the call leg between the PSAP). For the TSP model, this describes the call leg between
the TSP and the PSAP, leaving the call leg between the vehicle and the TSP and the PSAP, leaving the call leg between the vehicle and
the TSP up to the entities involved (i.e., IVS and TSP vendors) who the TSP up to the entities involved (i.e., IVS and TSP vendors) who
are then free to use the same mechanism as for the other leg or not. are free to use the same mechanism for both legs, or not.
Note that Europe has a mandated and standardized system for emergency Note that Europe has a mandated and standardized system for emergency
calls by in-vehicle systems. This pan-European system is known as calls by in-vehicle systems. This Pan-European system is known as
"eCall" and is the subject of a separate document, "eCall" and is the subject of a separate document, [RFC8147], which
[I-D.ietf-ecrit-ecall], which this document builds on. Vehicles this document builds on. Vehicles designed to operate in multiple
designed to operate in multiple regions might need to support eCall regions might need to support eCall as well as NG-ACN as described
as well as NG-ACN as described here. A vehicle IVS might determine here. A vehicle IVS might determine whether to use eCall or ACN by
whether to use eCall or ACN by first determining the region or first determining the region or country in which it is located (e.g.,
country in which it is located (e.g., from a GNSS location estimate from a GNSS location estimate and/or identity of or information from
and/or identity of or information from an MNO). If other regions an MNO). If other regions adopt other data formats, a multi-region
adopt other data formats, a multi-region vehicle might need to vehicle might need to support those as well. This document adopts
support those as well. This document adopts the call set-up and the call setup and other technical aspects of [RFC8147], which uses
other technical aspects of [I-D.ietf-ecrit-ecall], which uses
[RFC7852]; this makes it straightforward to use a different data set [RFC7852]; this makes it straightforward to use a different data set
while keeping other technical aspects unchanged. Hence, both NG- while keeping other technical aspects unchanged. Hence, both next-
eCall and the NG-ACN mechanism described here are compatible, generation eCall (NG-eCall) and the NG-ACN mechanism described here
differing primarily in the specific data block that is sent (the are compatible, differing primarily in the specific data block that
eCall MSD in the case of NG-eCall, and the APCO/NENA VEDS used in is sent (the eCall MSD in the case of NG-eCall and VEDS in this
this document), and some additions to the metadata/control data document) and some additions to the metadata/control data block. If
block. If other regions adopt their own vehicle data sets, this can other regions adopt their own vehicle data sets, this can be
be similarly accomodated without changing other technical aspects. similarly accommodated without changing other technical aspects.
Note that any additional data formats require a new SIP INFO package Note that any additional data formats require a new INFO package to
to permit transport within SIP INFO requests. permit transport within SIP INFO requests.
4. Overview of Legacy Deployment Models 4. Overview of Legacy Deployment Models
Legacy (circuit-switched) systems for placing emergency calls by in- Legacy (circuit-switched) systems for placing emergency calls by
vehicle systems generally have some ability to convey at least in-vehicle systems generally have some ability to convey at least
location and in some cases telematics data to the PSAP. Most such location and in some cases telematics data to the PSAP. Most such
systems use one of three architectural models, which are described systems use one of three architectural models, which are described
here as: "Telematics Service Provider" (TSP), "direct", and "paired". here as: "TSP", "direct", and "paired". These three models are
These three models are illustrated below. illustrated below.
In the TSP model, both emergency and non-emergency calls are placed In the TSP model, both emergency and routine TSP service calls are
to a Telematics Service Provider (TSP); a proprietary technique is placed to a TSP; a proprietary technique (e.g., a proprietary in-band
used for data transfer (such as a proprietary in-band modem) between modem) is used for data transfer between the TSP and the vehicle.
the TSP and the vehicle.
In an emergency, generally the TSP call taker bridges in the PSAP and In an emergency, typically a TSP agent verifies the emergency,
communicates location, crash data (such as impact severity and trauma bridges in the PSAP, and communicates location, crash data (such as
prediction), and other data (such as the vehicle description) to the impact severity and trauma prediction), and other data (such as the
PSAP call taker verbally (in some cases, a proprietary out-of-band vehicle description) to the PSAP call taker orally (in some cases, a
interface is used). Since the TSP knows the location of the vehicle proprietary out-of-band interface is used). Since the TSP knows the
(from on-board GNSS and sensors), location-based routing is usually location of the vehicle (from on-board GNSS and sensors), location-
used to route to the appropriate PSAP. In some cases, the TSP is based routing is usually used to route to the appropriate PSAP. In
able to transmit location automatically, using similar techniques as some cases, the TSP is able to transmit location automatically, using
for wireless calls. Typically, a three-way voice call is established similar techniques as for wireless calls. A three-way voice call is
between the vehicle, the TSP, and the PSAP, allowing communication generally established between the vehicle, the TSP, and the PSAP,
between the PSAP call taker, the TSP call taker, and the vehicle allowing communication between the PSAP call taker, the TSP agent,
occupants (who might be unconscious). and the vehicle occupants (who might be unconscious).
///----\\\ proprietary +------+ 911 trunk or POTS +------+ ///----\\\ proprietary +-----+ 911 trunk or POTS +------+
||| IVS |||-------------->+ TSP +------------------->+ PSAP | ||| IVS |||-------------->| TSP |--------------------->| PSAP |
\\\----/// crash data +------+ location via trunk +------+ \\\----/// crash data +-----+ location via trunk +------+
Figure 1: Legacy TSP Model. Figure 1: Legacy TSP Model
In the paired model, the IVS uses a local link (typically Bluetooth In the paired model, the IVS uses a local link (typically Bluetooth
[Bluetooth]) with a previously-paired handset to establish an [Bluetooth]) with a previously paired handset to establish an
emergency call with the PSAP (by dialing a standard emergency number; emergency call with the PSAP (by dialing a standard emergency number;
9-1-1 in North America), and then communicates location data to the 9-1-1 in North America) and then communicates location data to the
PSAP via text-to-speech; crash data might or might not be conveyed PSAP via text-to-speech; crash data might or might not be conveyed
also using text-to-speech. Some such systems use an automated voice also using text-to-speech. Some such systems use an automated voice
prompt menu for the PSAP call taker (e.g., "this is an automatic prompt menu for the PSAP call taker (e.g., "this is an automatic
emergency call from a vehicle; press 1 to open a voice path to the emergency call from a vehicle; press 1 to open a voice path to the
vehicle; press 2 to hear the location read out") to allow the call vehicle; press 2 to hear the location read out") to allow the call
taker to request location data via text-to-speech. taker to request location data via text-to-speech.
+---+ ///----\\\ +----+ 911/etc. voice call via handset +------+
///----\\\ | H | 911/etc voice call via handset +------+ ||| IVS |||-->| HS |----------------------------------->| PSAP |
||| IVS |||-->| S +----------------------------------->+ PSAP | \\\----/// +----+ location via text-to-speech +------+
\\\----/// +---+ location via text-to-speech +------+
(Note: "HS" is handset.)
Figure 2: Legacy Paired Model Figure 2: Legacy Paired Model
In the direct model, the IVS directly places an emergency call with In the direct model, the IVS directly places an emergency call with
the PSAP by dialing a standard emergency number (9-1-1 in North the PSAP by dialing a standard emergency number (9-1-1 in North
America). Such systems might communicate location data to the PSAP America). Such systems might communicate location data to the PSAP
via text-to-speech; crash data might or might not be conveyed using via text-to-speech; crash data might or might not be conveyed using
text-to-speech. Some such systems use an automated voice prompt menu text-to-speech. Some such systems use an automated voice prompt menu
(e.g., "this is an automatic emergency call from a vehicle; press 1 (e.g., "this is an automatic emergency call from a vehicle; press 1
to open a voice path to the vehicle; press 2 to hear the location to open a voice path to the vehicle; press 2 to hear the location
read out") to allow the call taker to request location data via text- read out") to allow the call taker to request location data via
to-speech. text-to-speech.
///----\\\ 911/etc voice call via IVS +------+ ///----\\\ 911/etc. voice call via IVS +------+
||| IVS |||---------------------------------------->+ PSAP | ||| IVS |||---------------------------------------->| PSAP |
\\\----/// location via text-to-speech +------+ \\\----/// location via text-to-speech +------+
Figure 3: Legacy Direct Model Figure 3: Legacy Direct Model
5. Migration to Next-Generation 5. Migration to Next Generation
Migration of emergency calls placed by in-vehicle systems to next- The migration of emergency calls placed by in-vehicle systems to
generation (all-IP) technology per this document provides a next-generation (all-IP) technology per this document provides a
standardized mechanism to identify such calls and to convey crash standardized mechanism to identify such calls and to convey crash
data with the call setup, as well as enabling additional data with the call setup, as well as enabling additional
communications modalities and enhanced functionality. This allows communications modalities and enhanced functionality. This allows
ACN calls and crash data to be automatically processed by the PSAP ACN calls and crash data to be automatically processed by the PSAP
and made available to the call taker in an integrated, automated way. and made available to the call taker in an integrated, automated way.
Because the crash data is carried in the initial SIP INVITE (per Because the crash data is carried in the initial SIP INVITE (per
[RFC7852]) the PSAP can present it to the call taker simultaneously [RFC7852]) the PSAP can present it to the call taker simultaneously
with the appearance of the call. The PSAP can also process the data with the appearance of the call. The PSAP can also process the data
to take other actions (e.g., if multiple calls from the same location to take other actions (e.g., if multiple calls from the same location
arrive when the PSAP is busy and a subset of them are NG-ACN calls, a arrive when the PSAP is busy and a subset of them are NG-ACN calls, a
PSAP might choose to store the information and reject the calls, PSAP might choose to store the information and reject the calls,
since the IVS will receive confirmation that the information has been since the IVS will receive confirmation that the information has been
successfully received; a PSAP could also choose to include a message successfully received; a PSAP could also choose to include a message
stating that it is aware of the incident and responders are on the stating that it is aware of the incident and responders are on the
way; a PSAP could call the vehicle back when a call taker is way, and a PSAP could call the vehicle back when a call taker is
available). available).
The migration of origination devices and networks, PSAPs, emergency The migration of origination devices and networks, PSAPs, emergency
services networks, and other telephony environments to next- services networks, and other telephony environments to next
generation provides enhanced interoperability and functionality, generation technology provides enhanced interoperability and
especially for emergency calls carrying additional data such as functionality, especially for emergency calls carrying additional
vehicle crash data. (In the U.S., a network specifically for data such as vehicle crash data. (In the U.S., a network
emergency responders is being developed. This network, FirstNet, specifically for emergency responders is being developed. This
will be next-generation from the start, enhancing the ability for network, FirstNet, will be next generation from the start, enhancing
data exchange between PSAPs and responders.) the ability for data exchange between PSAPs and responders.)
NG-ACN calls can be recognized as originating from a vehicle, routed NG-ACN calls can be recognized as such during call set-up; they can
to a PSAP prepared both technically and operationally to handle such be routed to a PSAP that is prepared both technically and
calls, and the vehicle-determined location and crash data made operationally to handle such calls, and the vehicle-determined
available to the call taker simultaneously with the call appearance. location and crash data can be processed automatically by the PSAP
The PSAP can take advantage of enhanced functionality, including the and made available to the call taker simultaneously with the call
ability to request the vehicle to take an action, such as sending an appearance. Enhanced functionality includes the ability for the PSAP
updated set of data, converying a message to the occupants, flashing call taker to request the vehicle to take an action, such as sending
lights, unlocking doors, etc. an updated set of data, conveying a message to the occupants,
flashing lights, unlocking doors, etc.
Vehicle manufacturers using the TSP model can choose to take Vehicle manufacturers using the TSP model can choose to take
advantage of the same mechanism to carry telematics data and requests advantage of the same mechanism to carry telematics data and requests
and responses between the vehicle and the TSP for both emergency and and responses between the vehicle and the TSP for both emergency and
non-emergency calls as are used for the interface with the PSAP. non-emergency calls as are used for the interface with the PSAP.
A next-generation IVS establishes a next-generation emergency call An IVS establishes a next-generation emergency call (see [RFC6443]
(see [RFC6443] and [RFC6881]), with an initial INVITE containing a and [RFC6881]) with an initial INVITE containing a Request-URI
Request-URI indicating an ACN type of emergency call and Call-Info indicating an ACN emergency call and Call-Info header fields
header fields indicating that both vehicle crash and capabilities indicating that both vehicle crash and capabilities data are
data are included; the IVS typically does not perform routing or included; the IVS typically does not perform routing or location
location queries but relies on the carrier for this. queries (relying on the MNO for this).
[RFC8147] registers new service URN children within the "sos"
subservice. These URNs request NG-ACN resources and differentiate
between manually and automatically triggered NG-ACN calls (which
might be subject to different treatment depending on policy). The
two service URNs registered in [RFC8147] are
"urn:service:sos.ecall.automatic" and "urn:service:sos.ecall.manual".
The same service URNs are used for ACN as for eCall since in any
region only one of these is supported, making a distinction
unnecessary. (Further, PSAP equipment might support multiple data
formats, allowing a PSAP to handle a vehicle that erroneously sent
the wrong data object.)
[I-D.ietf-ecrit-ecall] registers new service URN children within the
"sos" subservice. These URNs request NG-ACN resources, and
differentiate between manually and automatically triggered NG-ACN
calls (which might be subject to different treatment depending on
policy). The two service URNs registered in [I-D.ietf-ecrit-ecall]
are "urn:service:sos.ecall.automatic" and
"urn:service:sos.ecall.manual". The same service URNs are used for
ACN as for eCall since in any region only one of these is supported,
making a distinction unnecessary. (Further, PSAP equipment might
support multiple data formats, allowing a PSAP to handle a vehicle
that erroneously sent the wrong data object.)
Note that in North America, routing queries performed by clients Note that in North America, routing queries performed by clients
outside of an ESInet typically treat all sub-services of "sos" outside of an ESInet typically treat all sub-services of "sos"
identically to "sos" with no sub-service. However, the Request-URI identically to "sos" with no sub-service. However, the Request-URI
header field retains the full sub-service; route and handling header field retains the full sub-service; route and handling
decisions within an ESInet or PSAP can take the sub-service into decisions within an ESInet or PSAP can take the sub-service into
account. For example, in a region with multiple cooperating PSAPs, account. For example, in a region with multiple cooperating PSAPs,
an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or
one that specializes in vehicle-related incidents. one that specializes in vehicle-related incidents.
Migration of the three architectural models to next-generation (all- Migration of the three architectural models to next generation
IP) is described below. (all-IP) is described below.
In the TSP model, the IVS transmits crash and location data to the In the TSP model, the IVS transmits crash and location data to the
TSP either by re-using the mechanisms and data objects described in TSP either by reusing the mechanisms and data objects described in
this document, or using a proprietary mechanism. In an emergency, this document or by using a proprietary mechanism. In an emergency,
the TSP bridges in the PSAP and the TSP transmits crash and other the TSP bridges in the PSAP, and the TSP transmits crash and other
data to the PSAP using the mechanisms and data objects described in data to the PSAP using the mechanisms and data objects described in
this document. There is a three-way call between the vehicle, the this document. There is a three-way call between the vehicle, the
TSP, and the PSAP, allowing communication between the PSAP call TSP, and the PSAP, allowing communication between the PSAP call
taker, the TSP call taker, and the vehicle occupants (who might be taker, the TSP agent, and the vehicle occupants (who might be
unconscious). The TSP relays PSAP requests and vehicle responses. unconscious). The TSP relays PSAP requests and vehicle responses.
proprietary proprietary
///----\\\ or standard +------+ standard +------+ ///----\\\ or standard +-----+ standard +------+
||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | ||| IVS |||------------------->| TSP |------------------->| PSAP |
\\\----/// crash + other data +------+ crash + other data +------+ \\\----/// crash+other data +-----+ crash+other data +------+
Figure 4: Next-Generation TSP Model Figure 4: Next-Generation TSP Model
The vehicle manufacturer and the TSP can choose to use the same The vehicle manufacturer and the TSP can choose to use the same
mechanisms and data objects on the left call leg in Figure 4 as on mechanisms and data objects on the left call leg in Figure 4 as on
the right. (Note that the TSP model can be more difficult when the the right. (Note that the TSP model can be more difficult when the
vehicle is in a different country than the TSP (e.g., a US resident vehicle is in a different country than the TSP (e.g., a US resident
driving in Canada) because of the additional complexity in choosing driving in Canada) because of the additional complexity in choosing
the correct PSAP based on vehicle location performed by a TSP in a the correct PSAP based on vehicle location performed by a TSP in a
different country.) different country.)
In the direct model, the IVS communicates crash data to the PSAP In the direct model, the IVS communicates crash data to the PSAP
directly using the mechanisms and data objects described in this directly using the mechanisms and data objects described in this
document. document.
///----\\\ NG emergency call +------+ ///----\\\ NG emergency call +------+
||| IVS |||----------------------------------------->+ PSAP | ||| IVS |||----------------------------------------->| PSAP |
\\\----/// crash + other data +------+ \\\----/// crash + other data +------+
Figure 5: Next-Generation Direct Model Figure 5: Next-Generation Direct Model
In the paired model, the IVS uses a Bluetooth link to a previously- In the paired model, the IVS uses a local link to a previously paired
paired handset to establish an emergency call with the PSAP; it is handset to establish an emergency call with the PSAP; it is unclear
unclear what facilities are or will be available for transmitting what facilities are or will be available for transmitting crash data
crash data through the Bluetooth link to the handset for inclusion in through the link to the handset for inclusion in an NG emergency call
an NG emergency call. Hence, manufacturers that use the paired model and receiving additional data items from the response. Hence,
for legacy calls might choose to adopt either the direct or TSP manufacturers that use the paired model for legacy calls might choose
models for next-generation calls. to adopt either the direct or TSP model for next-generation calls.
+---+ ///----\\\ (undefined) +----+ standard +------+
///----\\\ (undefined) | H | standard +------+ ||| IVS |||----------------->| HS |--------------------->| PSAP |
||| IVS |||------------------>| S +------------------->+ PSAP | \\\----/// (undefined) +----+ crash + other data +------+
\\\----/// (undefined) +---+ crash + other data +------+
Figure 6: Next-Generation Paired Model Figure 6: Next-Generation Paired Model
If the call is routed to a PSAP that is not capable of processing the Regardless of model, if the call is routed to a PSAP that is not
vehicle data, the PSAP ignores (or does not receive) the vehicle NG-ACN capable, the PSAP ignores (or does not receive) the vehicle
data. This is detectable by the IVS or TSP when the status response data. This is detectable by the IVS or TSP when the status response
to the INVITE (e.g., 200 OK) lacks a metadata/control structure to the INVITE (e.g., 200 OK) lacks a metadata/control structure
acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or acknowledging receipt of the data [RFC8147]. The IVS or TSP then
TSP then proceeds as it would for a CS-ACN call (e.g., verbal proceeds as it would for a CS-ACN call (e.g., oral conveyance of
conveyance of data) data).
6. Vehicle Data 6. Vehicle Data
The Association of Public-Safety Communications Officials (APCO) and APCO and NENA have jointly developed a standardized set of incident-
the National Emergency Number Association (NENA) have jointly related vehicle data for ACN use, called the Vehicle Emergency Data
developed a standardized set of incident-related vehicle data for ACN Set (VEDS) [VEDS]. Such data is often referred to as crash data
use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data although it is applicable in incidents other than crashes.
is often referred to as crash data although it is applicable in
incidents other than crashes.
VEDS provides a standard data set for the transmission, exchange, and VEDS provides a standard data set for the transmission, exchange, and
interpretation of vehicle-related data. A standard data format interpretation of vehicle-related data. A standard data format
allows the data to be generated by an IVS or TSP and interpreted by allows the data to be generated by an IVS or TSP and interpreted by
PSAPs, emergency responders, and medical facilities. It includes PSAPs, emergency responders, and medical facilities. It includes
incident-related information such as airbag deployment, location and incident-related information such as airbag deployment, location and
compass orientation of the vehicle, spatial orientation of the compass orientation of the vehicle, spatial orientation of the
vehicle (e.g., upright, on its side or roof or a bumper), various vehicle (e.g., upright, on a side, roof, or bumper), sensor data that
sensor data that can indicate the potential severity of the crash and can indicate the potential severity of the crash and the likelihood
the likelihood of severe injuries to the vehicle occupants, etc. of severe injuries to the vehicle occupants, etc. This data better
This data better informs the PSAP and emergency responders as to the informs the PSAP and emergency responders as to the type of response
type of response that might be needed. Some of this information has that might be needed. Some of this information has been included in
been included in U.S. government guidelines for field triage of U.S. government guidelines for field triage of injured patients
injured patients [triage-2008] [triage-2011]. These guidelines are [triage-2008] [triage-2011]. These guidelines are designed to help
designed to help responders identify the potential existence of responders identify the potential existence of severe internal
severe internal injuries and to make critical decisions about how and injuries and to make critical decisions about how and where a patient
where a patient needs to be transported. needs to be transported.
VEDS is an XML structure (see [VEDS]) transported in SIP using the VEDS is an XML structure (see [VEDS]) transported in SIP using the
'application/EmergencyCallData.VEDS+xml' MIME media type. application/EmergencyCallData.VEDS+xml MIME media type.
If new data blocks are needed (e.g., in other regions or for enhanced If new data blocks are needed (e.g., in other regions or for enhanced
data), the steps required during standardization are briefly data), the steps required during standardization are briefly
summarized below: summarized below:
o A set of data is standardized by an SDO or appropriate o A set of data is standardized by a Standards Development
organization Organization (SDO) or appropriate organization.
o A MIME media type for the crash data set is registered with IANA o A MIME media type for the crash data set is registered with IANA
* If the data is specifically for use in emergency calling, the * If the data is specifically for use in emergency calling, the
MIME media type is normally under the 'application' type with a MIME media type is normally under the application type with a
subtype starting with 'EmergencyCallData.' subtype starting with EmergencyCallData.
* If the data format is XML, then by convention the name has a * If the data format is XML, then by convention the name has a
suffix of '+xml' suffix of "+xml".
o The item is registered in the Emergency Call Data Types registry,
as defined in Section 11.1.9 of [RFC7852] o The item is registered in the "Emergency Call Data Types"
registry, as defined in Section 11.1.9 of [RFC7852].
* For emergency-call-specific formats, the registered name is the * For emergency-call-specific formats, the registered name is the
root of the MIME media type (not including the root of the MIME media type (not including the
'EmergencyCallData' prefix and any suffix such as '+xml') as EmergencyCallData prefix and any suffix such as "+xml") as
described in Section 4.1 of [RFC7852]. described in Section 4.1 of [RFC7852].
o A new SIP INFO package is registered that permits carrying the new
media type, the metadata/control object (defined in o A new INFO package is registered that permits carrying the new
[I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS media type, the metadata/control object (defined in [RFC8147]),
objects, in SIP INFO requests. and for compatibility, the MSD and VEDS objects, in SIP INFO
requests.
7. Data Transport 7. Data Transport
[RFC7852] establishes a general mechanism for including blocks of [RFC7852] establishes a general mechanism for including blocks of
data within a SIP emergency call. This document makes use of that data within a SIP emergency call. This document makes use of that
mechanism. This document also registers a SIP INFO package (in mechanism. This document also registers an INFO package (in
Section 14.7) to enable NG-ACN related data blocks to be carried in Section 14.7) to enable NG-ACN-related data blocks to be carried in
SIP INFO requests (per [RFC6086], new SIP INFO method usages require SIP INFO requests (per [RFC6086], new SIP INFO method usages require
the definition of a SIP INFO package). the definition of an INFO package).
The Vehicle Emergency Data Set (VEDS) is an XML structure defined by VEDS is an XML structure defined by APCO and NENA [VEDS]. It is
the Association of Public-Safety Communications Officials (APCO) and carried in a body part with MIME media type application/
the National Emergency Number Association (NENA) [VEDS]. It is EmergencyCallData.VEDS+xml.
carried in a body part with MIME media type 'application/
EmergencyCallData.VEDS+xml'.
An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) An IVS transmits a VEDS data block (see [VEDS]) by including it as a
by including it as a body part of a SIP message per [RFC7852]. The body part of a SIP message per [RFC7852]. The body part is
body part is identified by its MIME media type ('application/ identified by its MIME media type (application/
emergencyCallData.VEDS+xml') in the Content-Type header field of the EmergencyCallData.VEDS+xml) in the Content-Type header field of the
body part. The body part is assigned a unique identifier which is body part. The body part is assigned a unique identifier that is
listed in a Content-ID header field in the body part. The SIP listed in a Content-ID header field in the body part. The SIP
message is marked as containing the VEDS data by adding (or appending message is marked as containing the VEDS data by adding (or appending
to) a Call-Info header field at the top level of the SIP message. to) a Call-Info header field at the top level of the SIP message.
This Call-Info header field contains a CID URL referencing the body This Call-Info header field contains a Content Identifier (CID) URL
part's unique identifier, and a 'purpose' parameter identifying the referencing the body part's unique identifier and a "purpose"
data as a VEDS data block per the Emergency Call Additional Data parameter identifying the data as a VEDS data block per the
Types registry entry; the 'purpose' parameter's value is "Emergency Call Data Types" registry entry; the "purpose" parameter's
'emergencyCallData.VEDS'. A VEDS data block is carried in a SIP INFO value is "EmergencyCallData.VEDS". A VEDS data block is carried in a
request by using the SIP INFO package defined in Section 14.7. SIP INFO request by using the INFO package defined in Section 14.7.
A PSAP or IVS transmits a metadata/control object (see A PSAP or IVS transmits a metadata/control object (see [RFC8147]) by
[I-D.ietf-ecrit-ecall]) by including it in a SIP message as a MIME including it in a SIP message as a MIME body part per [RFC7852]. The
body part per [RFC7852]. The body part is identified by its MIME body part is identified by its MIME media type (application/
media type ('application/emergencyCallData.control+xml') in the EmergencyCallData.Control+xml) in the Content-Type header field of
Content-Type header field of the body part. The body part is the body part. The body part is assigned a unique identifier that is
assigned a unique identifier which is listed in a Content-ID header listed in a Content-ID header field in the body part. The SIP
field in the body part. The SIP message is marked as containing the message is marked as containing the metadata/control block by adding
metadata/control block by adding (or appending to) a Call-Info header (or appending to) a Call-Info header field at the top level of the
field at the top level of the SIP message. This Call-Info header SIP message. This Call-Info header field contains a CID URL
field contains a CID URL referencing the body part's unique referencing the body part's unique identifier and a "purpose"
identifier, and a 'purpose' parameter identifying the data as a parameter identifying the data as a metadata/control block per the
metadata/control block per the Emergency Call Additional Data Types "Emergency Call Data Types" registry entry; the "purpose" parameter's
registry entry; the 'purpose' parameter's value is value is "EmergencyCallData.Control". A metadata/control object is
'emergencyCallData.control'. A metadata/control object is carried in carried in a SIP INFO request by using the INFO package defined in
a SIP INFO request by using the SIP INFO package defined in
Section 14.7. Section 14.7.
A body part containing a VEDS or metadata/control object has a A body part containing a VEDS or metadata/control object has a
Content-Disposition header field value containing "By-Reference" and Content-Disposition header field value containing "By-Reference" and
is always enclosed in a multipart body part (even if it would is always enclosed in a multipart body part (even if it would
otherwise be the only body part in the SIP message), since as of the otherwise be the only body part in the SIP message).
date of this document, the use of Content-ID as a SIP header field is
not defined (while it is defined for use as a MIME header field).
An In-Vehicle System (IVS) initiating an NG-ACN call includes in the An IVS initiating an NG-ACN call includes in the initial INVITE a
initial INVITE a VEDS data block and a metadata/control object VEDS data block and a metadata/control object informing the PSAP of
informing the PSAP of its capabilities. The VEDS and metadata/ its capabilities. The VEDS and metadata/control body parts (and
control body parts (and PIDF-LO) have a Content-Disposition header Presence Information Data Format Location Object (PIDF-LO)) have a
field with the value "By-Reference; handling=optional". Specifying Content-Disposition header field with the value "By-Reference;
handling=optional prevents the INVITE from being rejected if it is handling=optional". Specifying handling=optional prevents the INVITE
processed by a legacy element (e.g., a gateway between SIP and from being rejected if it is processed by a legacy element (e.g., a
circuit-switched environments) that does not understand the VEDS or gateway between SIP and circuit-switched environments) that does not
metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/ understand the VEDS or metadata/control (or PIDF-LO) objects. The
control object acknowledging receipt of the VEDS data and includes it PSAP creates a metadata/control object acknowledging receipt of the
in the SIP final response to the INVITE. The metadata/control object VEDS data and includes it in the SIP final response to the INVITE.
is not included in provisional (e.g., 180) responses. The metadata/control object is not included in provisional (e.g.,
180) responses.
If the IVS receives an acknowledgment for a VEDS data object with If the IVS receives an acknowledgment for a VEDS data object with
received=false, this indicates that the PSAP was unable to properly received=false, this indicates that the PSAP was unable to properly
decode or process the VEDS. The IVS action is not defined (e.g., it decode or process the VEDS. The IVS action is not defined (e.g., it
might only log an error). Since the PSAP is able to request an might only log an error). Since the PSAP is able to request an
updated VEDS during the call, if an initial VEDS is unsatisfactory in updated VEDS during the call, if an initial VEDS is unsatisfactory in
any way, the PSAP can choose to request another one. any way, the PSAP can choose to request another one.
A PSAP can request that the vehicle send an updated VEDS data block A PSAP can request that the vehicle send an updated VEDS data block
during a call. To do so, the PSAP creates a metadata/control object during a call. To do so, the PSAP creates a metadata/control object
requesting VEDS data and includes it as a body part of a SIP INFO requesting VEDS data and includes it as a body part of a SIP INFO
request sent within the dialog. The IVS then includes an updated request sent within the dialog. The IVS then includes an updated
VEDS data object as a body part of a SIP INFO request and sends it VEDS data object as a body part of a SIP INFO request and sends it
within the dialog. If the IVS is unable to send the VEDS, it instead within the dialog. If the IVS is unable to send the VEDS for any
sends a metadata/control object acknowledging the request with the reason, it instead sends a metadata/control object containing an
'success' parameter set to 'false' and a 'reason' parameter (and <ack> element acknowledging the request and containing an
optionally a 'details' parameter) indicating why the request cannot <actionResult> element with the "success" parameter set to "false"
be accomplished. Per [RFC6086], metadata/control objects and VEDS and a "reason" parameter (and optionally a "details" parameter)
data are sent using the SIP INFO package defined in Section 14.7. In indicating why the request cannot be accomplished. Per [RFC6086],
addition, to align with the way a VEDS or metadata/control block is metadata/control objects and VEDS data are sent using the INFO
transmitted in a SIP message other than a SIP INFO request, one or package defined in Section 14.7. In addition, to align with the way
more Call-Info header fields are included in the SIP INFO request a VEDS or metadata/control block is transmitted in a SIP message
referencing the VEDS or metadata/control block. See Section 14.7 for other than a SIP INFO request, one or more Call-Info header fields
more information on the use of SIP INFO requests within NG-ACN calls. are included in the SIP INFO request referencing the VEDS or
metadata/control block. See Section 14.7 for more information on the
use of SIP INFO requests within NG-ACN calls.
Any metadata/control object sent by a PSAP can request that the Any metadata/control object sent by a PSAP can request that the
vehicle perform an action (such as sending a data block, flashing vehicle perform an action (such as sending a data block, flashing
lights, providing a camera feed, etc.) The vehicle sends an lights, providing a camera feed, etc.). The IVS sends an
acknowledgement for any request other than a successfully executed acknowledgment for any request other than a successfully executed
send-data action. Multiple requests with the same 'action' value send-data action. Multiple requests with the same "action:" value
MUST be sent in separate body parts (to avoid any ambiguity in the MUST be sent in separate metadata/control body parts (to avoid any
acknowledgement). ambiguity in the acknowledgment). For each metadata/control block
received containing one or more <request> elements (except for
successfully executed send-data requests), the IVS sends a metadata/
control object containing an <ack> element acknowledging the received
metadata/control block, containing an <actionResult> element per
<request> element.
If the IVS is aware that VEDS data it sent previously has changed, it If the IVS is aware that VEDS data it sent previously has changed, it
MAY send an unsolicited VEDS in any convenient SIP message, including MAY send an unsolicited VEDS in any convenient SIP message, including
a SIP INFO request during the call. The PSAP sends an acknowledgment a SIP INFO request during the call. The PSAP sends an acknowledgment
for an unsolicited VEDS object (if the IVS sent the unsolicited VEDS for an unsolicited VEDS object; if the IVS sent the unsolicited VEDS
in a SIP INFO request, the acknowledgment is sent in a new SP INFO in a SIP INFO request, the acknowledgment is sent in a new SIP INFO
request, otherwise it is sent in the reply to the SIP request request; otherwise, it is sent in the reply to the SIP request
containing the VEDS). containing the VEDS.
8. Call Setup 8. Call Setup
A next-generation In-Vehicle System (IVS) initiating an NG-ACN call An IVS initiating an NG-ACN call sends a SIP INVITE request using one
sends a SIP INVITE request using one of the SOS sub-services of the SOS sub-services "SOS.ecall.automatic" or "SOS.ecall.manual"
"SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI. This in the Request-URI. This SIP INVITE request includes standard sets
SIP INVITE request includes standard sets of both crash and of both crash and capabilities data as described in Section 7.
capabilities data as described in Section 7.
Entities along the path between the vehicle and the PSAP are able to Entities along the path between the vehicle and the PSAP are able to
identify the call as an ACN call and handle it appropriately. The identify the call as an ACN call and handle it appropriately. The
PSAP is able to identify the crash and capabilities data included in PSAP is able to identify the crash and capabilities data included in
the SIP INVITE request by examining the Call-Info header fields for the SIP INVITE request by examining the Call-Info header fields for
'purpose' parameters whose values start with 'EmergencyCallData.' "purpose" parameters whose values start with EmergencyCallData. The
The PSAP is able to access the data it is capable of handling and is PSAP is able to access the data it is capable of handling and is
interested in by checking the 'purpose' parameter values. interested in by checking the "purpose" parameter values.
This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- This document extends [RFC8147] by reusing the call setup and other
up and other normative requirements with the exception that in this normative requirements with the exception that in this document,
document, support for the eCall MSD is OPTIONAL and support for VEDS support for the eCall MSD is OPTIONAL and support for VEDS is
in REQUIRED. This document also adds new attribute values to the REQUIRED. This document also adds new attribute values to the
metadata/control object defined in [I-D.ietf-ecrit-ecall]. metadata/control object defined in [RFC8147].
9. New Metadata/Control Values 9. New Metadata/Control Values
This document adds new attribute values to the metadata/control This document adds new attribute values to the metadata/control
structure defined in [I-D.ietf-ecrit-ecall]. structure defined in [RFC8147].
In addition to the base usage from the PSAP to the IVS to In addition to the base usage from the PSAP to the IVS to acknowledge
acknowledge receipt of crash data, the <ack> element is also receipt of crash data, the <ack> element is also contained in a
contained in a metadata/control block sent by the IVS to the PSAP. metadata/control block sent by the IVS to the PSAP. This is used by
This is used by the IVS to acknowledge receipt of a request by the the IVS to acknowledge receipt of a request by the PSAP and indicate
PSAP and indicate if the request was carried out when that request if the request was carried out when that request would not otherwise
would not otherwise be acknowledged (if the PSAP requests the be acknowledged (if the PSAP requests the vehicle to send data and
vehicle to send data and the vehicle does so, the data serves as a the vehicle does so, the data serves as a success acknowledgment);
success acknowledgement). see Section 8 for details.
The <capabilities> element is used in a metadata/control block
sent from the IVS to the PSAP (e.g., in the initial INVITE) to The <capabilities> element is used in a metadata/control block sent
inform the PSAP of the vehicle capabilities. Child elements from the IVS to the PSAP (e.g., in the initial INVITE) to inform the
contain all actions and data types supported by the vehicle and PSAP of the vehicle capabilities. Child elements contain all actions
all available lamps (lights) and cameras. and data types supported by the vehicle and all available lamps
New request values are added to the <request> element to enable (lights) and cameras.
the PSAP to request the vehicle to perform actions.
New request values are added to the <request> element to enable the
PSAP to request the vehicle to perform additional actions.
Mandatory Actions (the IVS and the PSAP MUST support): Mandatory Actions (the IVS and the PSAP MUST support):
o Transmit data object (VEDS MUST be supported; MSD MAY be o Transmit data object (VEDS MUST be supported; MSD MAY be
supported) supported)
Optional Actions (the IVS and the PSAP MAY support): Optional Actions (the IVS and the PSAP MAY support):
o Play and/or display static (pre-defined) message o Display and/or play static (pre-defined) message
o Speak/display dynamic text (text supplied in action) o Display and/or speak dynamic text (text supplied in action)
o Flash or turn on or off a lamp (light) o Flash or turn on or off a lamp (light)
o Honk horn o Honk horn
o Lock or unlock doors o Lock or unlock doors
o Enable a camera o Enable a camera
The <ack> element indicates the object being acknowledged (i.e., a The <ack> element indicates the object being acknowledged (i.e., a
data object or a metadata/control block containing <request> data object or a metadata/control block containing <request>
elements), and reports success or failure. elements) and reports success or failure.
The <capabilities> element has child <request> elements indicating The <capabilities> element has child <request> elements indicating
the actions supported by the IVS. the actions (including data types, lamps (lights), and cameras)
supported by the IVS.
The <request> element contains attributes to indicate the request and The <request> element contains attributes to indicate the request and
to supply any needed information, and MAY contain a <text> child to supply any needed information, and it MAY contain a <text> child
element to contain the text for a dynamic message. The 'action' element to contain the text for a dynamic message. The "action"
attribute is mandatory and indicates the specific action. attribute is mandatory and indicates the specific action. [RFC8147]
[I-D.ietf-ecrit-ecall] established an IANA registry to contain the established an IANA registry to contain the allowed values; this
allowed values; this document adds new values to that registry in document adds new values to that registry in Table 1.
Table 2.
Per [I-D.ietf-ecrit-ecall], the PSAP sends a metadata/control block
in response to the VEDS data sent by the IVS in SIP requests other
than INFO (e.g., the INVITE). This metadata/control block is sent in
the SIP response to the request (e.g., the INVITE response). When
the PSAP needs to send a control block that is not an immediate
response to a VEDS or other data sent by the IVS, the metadata/
control block is transmitted from the PSAP to the IVS in a SIP INFO
request within the established dialog. The IVS sends the requested
data (e.g., the VEDS) or an acknowledgment (for requests other than
to send data or to indicate an inability to send the requested data)
in a new SIP INFO request. This mechanism flexibly allows the PSAP
to send metadata/control data to the IVS and the IVS to respond. If
a metadata/control block sent in a SIP response message requests the
IVS to send a new VEDS or other data block, or to perform an action
other than sending data, the IVS sends the requested data or an
acknowledgment regarding the action in a SIP INFO request within the
dialog.
9.1. New values for the 'action' attribute' 9.1. New Values for the "action" Attribute
The following new "action" values are defined: The following new "action" values are defined:
msg-static displays or plays a predefined message (translated as msg-static: displays or plays a pre-defined message (translated as
appropriate for the language of the vehicle's interface). A appropriate for the language of the vehicle's interface). A
registry is created in Section 14.4 for messages and their IDs. registry is created in Section 14.4 for messages and their IDs.
Vehicles include the highest registered message in their Vehicles include the highest registered message in their
<capabilities> element to indicate support for all messages up to <capabilities> element to indicate support for all messages up to
and including the indicated value. A registry of message and including the indicated value. A registry of message
identification values is defined in Section 14.4. There is only identification values is defined in Section 14.4. There is only
one static message initially defined (listed in Table 3). Because one static message initially defined (listed in Table 2). Because
all compliant vehicles are expected to support all static messages all compliant vehicles are expected to support all static messages
translated into all languages supported by the vehicle, it is translated into all languages supported by the vehicle, it is
important to limit the number of such messages. Therefore, this important to limit the number of such messages. Therefore, this
registry operates under "Specification Required" rules as defined registry operates under "Specification Required" rules as defined
in [RFC5226], which require a stable, public document and implies in [RFC5226], which requires a stable, public document and implies
expert review of the publication. expert review of the publication.
msg-dynamic displays or speaks (via text-to-speech) a dynamic msg-dynamic: displays or speaks (via text-to-speech) a message
message contained in a child <text> element within the request. contained in a child <text> element within the request.
honk sounds the horn. honk: sounds the horn.
lamp turns a lamp (light) on, off, or flashes. The lamp is lamp: flashes a lamp (light) or turns it on or off. The lamp is
identified by a lamp ID token contained in an "element-id" identified by a lamp ID token contained in an "element-id"
attribute of the request. The desired state of the lamp is either attribute of the request. The desired state of the lamp is either
"on", "off", or "flash" as indicated in a "requested-state" "on", "off", or "flash" as indicated in a "requested-state"
attribute. The duration of the lamp's requested state is attribute. The duration of the lamp's requested state is
specified in a "persistence" attribute. A registry of lamp specified in a "persistence" attribute. A registry of lamp
identification values is defined in Section 14.5. The initial identification values is defined in Section 14.5. The initial
values (listed in Table 4) are head, interior, fog-front, fog- values (listed in Table 3) are head, interior, fog-front,
rear, brake, brake-center, position-front, position-rear, turn- fog-rear, brake, brake-center, position-front, position-rear,
left, turn-right, and hazard. turn-left, turn-right, and hazard.
enable-camera adds a one-way media stream (established via SIP re- enable-camera: adds a one-way media stream (established via SIP
INVITE sent by the vehicle) to enable the PSAP call taker to view re-INVITE sent by the vehicle) to enable the PSAP call taker to
a feed from a camera. A registry of camera identification values view a feed from a camera. A registry of camera identification
is defined in Section 14.6. The initial values (listed in values is defined in Section 14.6. The initial values (listed in
Table 5) are backup, left-rear, right-rear, forward, rear-wide, Table 4) are backup, left-rear, right-rear, forward, rear-wide,
lane, interior, night-front, night-rear, night-left, and night- lane, interior, night-front, night-rear, night-left, and night-
right. right.
door-lock locks or unlocks all door locks. A "requested-state" door-lock: locks or unlocks all door locks. A "requested-state"
attribute contains either "locked" or "unlocked" to indicate if attribute contains either "locked" or "unlocked" to indicate if
the doors are to be locked or unlocked. the doors are to be locked or unlocked.
Note that there is no 'request' action to play dynamic media (such as Note that there is no "request" action to play dynamic media (such as
an audio message). The PSAP can send a SIP re-INVITE to establish a an audio message). The PSAP can send a SIP re-INVITE to establish a
one-way media stream for this purpose. one-way media stream for this purpose.
9.2. Request Example 9.2. Example <request> Element
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.control <EmergencyCallData.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<request action="send-data" datatype="VEDS"/> <request action="send-data" datatype="VEDS"/>
<request action="lamp" element-id="hazard" <request action="lamp" element-id="hazard"
requested-state="flash" persistence="PT1H"/> requested-state="flash" persistence="PT1H"/>
<request action="msg-static" int-id="1"/> <request action="msg-static" int-id="1"/>
<request action="msg-dynamic"> <request action="msg-dynamic">
<text>Remain calm. Help is on the way.</text> <text>Remain calm. Help is on the way.</text>
</request> </request>
</EmergencyCallData.control> </EmergencyCallData.Control>
Figure 7: Request Example Figure 7: <request> Example
9.3. The <ack> element 9.3. The <ack> Element
In [I-D.ietf-ecrit-ecall], the <ack> element is transmitted by the The <ack> element is transmitted by the PSAP to acknowledge
PSAP to acknowledge the MSD. Here, the <ack> element is also unsolicited data sent by the IVS and transmitted by the IVS to
transmitted by the PSAP to acknowledge the VEDS data and by the IVS acknowledge receipt of a <request> element other than a successfully
to acknowledge receipt of a <request> element that requested the IVS performed "send-data" request (e.g., a request to display a message
to perform an action other than transmitting a data object (e.g., a to the vehicle occupants is acknowledged, but a request to transmit
request to display a message would be acknowledged, but a request to VEDS data is not, since the transmitted VEDS serves as
transmit VEDS data would not result in a separate <ack> element being acknowledgment). An <ack> element sent by an IVS references the
sent, since the data object itself serves as acknowledgment.) An unique ID of the metadata/control object containing the request(s),
<ack> element sent by an IVS references the unique ID of the and for each request being acknowledged, it indicates whether the
metadata/control object containing the request(s) and indicates request was successfully performed, and if not, it indicates why not.
whether the request was successfully performed, and if not,
optionally includes an explanation. 9.3.1. Examples of the <ack> Element
9.3.1. Ack Examples
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.control <EmergencyCallData.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ack ref="1234567890@atlanta.example.com"> <ack ref="1234567890@atlanta.example.com">
<actionResult action="msg-dynamic" success="true"/> <actionResult action="msg-dynamic" success="true"/>
<actionResult action="lamp" success="false" reason="unable" <actionResult action="lamp" success="false" reason="unable"
details="The requested lamp is inoperable"/> details="The requested lamp is inoperable"/>
</ack> </ack>
</EmergencyCallData.control> </EmergencyCallData.Control>
Figure 8: Ack Example from IVS to PSAP Figure 8: Example <ack> from IVS to PSAP
9.4. The <capabilities> element 9.4. The <capabilities> Element
The <capabilities> element ([I-D.ietf-ecrit-ecall]) is transmitted by The <capabilities> element [RFC8147] is transmitted by the IVS to
the IVS to indicate its capabilities to the PSAP. indicate its capabilities to the PSAP.
The <capabilities> element contains a <request> child element per The <capabilities> element contains a <request> child element per
action supported by the vehicle. The vehicle MUST support sending action supported by the vehicle. The vehicle MUST support sending
the VEDS data object and so includes at a minimum a <request> child the VEDS data object and so includes at a minimum a <request> child
element with the 'action' attribute set to "send-data" and the element with the "action" attribute set to "send-data" and the
'supported-values' attribute containing all data blocks supported by "supported-values" attribute containing all data blocks supported by
the IVS, which MUST include 'VEDS'. All other actions are OPTIONAL. the IVS, which MUST include "VEDS". All other actions are OPTIONAL.
If the "msg-static" action is supported, a <request> child element If the "msg-static" action is supported, a <request> child element
with the 'action' attribute set to "msg-static" is included, with the with the "action" attribute set to "msg-static" is included, with the
'int-id' attribute set to the highest supported static message "int-id" attribute set to the highest supported static message
supported by the vehicle. A registry is created in Section 14.4 to supported by the vehicle. A registry is created in Section 14.4 to
map 'int-id' values to static text messages. By sending the highest map "int-id" values to static text messages. By sending the highest
supported static message number in its <capabilities> element, the supported static message number in its <capabilities> element, the
vehicle indicates its support for all static messages in the registry vehicle indicates its support for all static messages in the registry
up to and including that value. up to and including that value.
If the "lamp" action is supported, a <request> child element with the If the "lamp" action is supported, a <request> child element with the
'action' attribute set to "lamp" is included, with the 'supported- "action" attribute set to "lamp" is included, with the "supported-
values' attribute set to all supported lamp IDs. A registry is values" attribute set to all supported lamp IDs. A registry is
created in Section 14.5 to contain lamp ID values. created in Section 14.5 to contain lamp ID values.
If the "enable-camera" action is supported, a <request> child element If the "enable-camera" action is supported, a <request> child element
with the 'action' attribute set to "enable-camera" is included, with with the "action" attribute set to "enable-camera" is included, with
the 'supported-values' attribute set to all supported camera IDs. A the "supported-values" attribute set to all supported camera IDs. A
registry is created in Section 14.6 to contain camera ID values. registry is created in Section 14.6 to contain camera ID values.
9.4.1. Capabilities Example 9.4.1. Example <capabilities> Element
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.control <EmergencyCallData.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<capabilities> <capabilities>
<request action="send-data" supported-values="VEDS"/> <request action="send-data" supported-values="VEDS"/>
<request action="lamp" <request action="lamp"
supported-values="head;interior;fog-front; supported-values="head;interior;fog-front;
fog-rear;brake;position-front;position-rear; fog-rear;brake;position-front;position-rear;
turn-left;turn-right;hazard"/> turn-left;turn-right;hazard"/>
<request action="msg-static" int-id="3"/> <request action="msg-static" int-id="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<request action="enable-camera" <request action="enable-camera"
supported-values="backup; interior"/> supported-values="backup; interior"/>
<request action="door-lock"/> <request action="door-lock"/>
</capabilities> </capabilities>
</EmergencyCallData.control> </EmergencyCallData.Control>
Figure 9: Capabilities Example Figure 9: <capabilities> Example
10. Test Calls 10. Test Calls
An NG-ACN test call is a call that is recognized and treated to some An NG-ACN test call is a call that is recognized and treated to some
extent as an NG-ACN call but not given emergency call treatment and extent as an NG-ACN call but is not given emergency call treatment
not handled by a call taker. The specific handling of test NG-ACN nor handled by a PSAP call taker. The specific handling of test
calls is not itself standardized; the test call facility is intended NG-ACN calls is outside the scope of this document; typically, the
to allow the IVS, user, or TSP to verify that an NG-ACN call can be test call facility allows the IVS, user, or TSP to verify that an
successfully established with voice and/or other media communication. NG-ACN call can be successfully established with voice and/or other
The IVS might also be able to verify that the crash data was media communication. The IVS might also be able to verify that the
successfully received. crash data was successfully received.
This document builds on [I-D.ietf-ecrit-ecall], which inherits the This document builds on [RFC8147], which inherits the ability to
ability to utilize test call functionality from Section 15 of utilize test call functionality from Section 15 of [RFC6881]. A
[RFC6881]. A service URN starting with "test." indicates a test service URN starting with "test." indicates a test call. Per
call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" [RFC8147], "urn:service:test.sos.ecall" is used for test NG-ACN
for test calls. calls.
MNOs, emergency authorities, ESInets, and PSAPs determine how to MNOs, emergency authorities, ESInets, and PSAPs handle a vehicle call
treat a vehicle call requesting the "test" service URN so that the requesting the "test" service URN so that the desired functionality
desired functionality is tested, but this is outside the scope of is tested, but this is outside the scope of this document. (One
this document. (One possibility is that MNOs route such calls as possibility is that MNOs route such calls as non-emergency calls to
non-emergency calls to an ESInet, which routes them to a PSAP that an ESInet, which routes them to a PSAP that supports NG-ACN calls;
supports NG-ACN calls; the PSAP accepts test calls, sends a crash the PSAP accepts test calls, sends a crash data acknowledgment, and
data acknowledgment, and plays an audio clip (for example, saying plays an audio clip (for example, saying that the call reached an
that the call reached an appropriate PSAP and the vehicle data was appropriate PSAP and the vehicle data was successfully processed) in
successfully processed) in addition to supporting media loopback per addition to supporting media loopback per [RFC6881].)
[RFC6881]).
Note that since test calls are placed using "test" as the parent Note that since test calls are placed using "test" as the parent
service URN and "sos" as a child, such calls are not treated as an service URN and "sos" as a child, such calls are not treated as an
emergency call and so some functionality might not apply (such as emergency call, so some functionality might not apply (such as
preemption or service availability for devices lacking service ("non- preemption or availability for devices lacking service
service-initialized" or "NSI" devices) if those are available for ("non-service-initialized" (NSI) devices) if those are available for
emergency calls). emergency calls).
11. Example 11. Example Call Initiation
Figure 10 shows an NG-ACN call routing. The mobile network operator Figure 10 shows an NG-ACN call initiation. The vehicle initiates an
(MNO) routes the call to an Emergency services IP Network (ESInet), NG-ACN call using an MNO. The MNO routes the call to an ESInet, as
as for any emergency call. The ESInet routes the call to an for any emergency call. The ESInet routes the call to an appropriate
appropriate NG-ACN-capable PSAP (using location information and the NG-ACN-capable PSAP (using location information and the fact that it
fact that that it is an NG-ACN call). The call is processed by the is an NG-ACN call). The call is processed by the Emergency Services
Emergency Services Routing Proxy (ESRP), as the entry point to the Routing Proxy (ESRP), as the entry point to the ESInet. The ESRP
ESInet. The ESRP routes the call to an appropriate NG-ACN-capable routes the call to an appropriate NG-ACN-capable PSAP, where the call
PSAP, where the call is received by a call taker. (In deployments is handled by a call taker. (In deployments where there is no
where there is no ESInet, the MNO itself routes the call directly to ESInet, the MNO itself routes the call directly to an appropriate
an appropriate NG-ACN-capable PSAP.) NG-ACN-capable PSAP.)
+---------------------------------------+ +---------------------------------------+
| | | |
+------------+ | +-------+ | +------------+ | +-------+ |
| | | | PSAP2 | | | | | | PSAP2 | |
| | | +-------+ | | | | +-------+ |
| Originating| | | | Originating| | |
| Mobile | | +------+ +-------+ | | Mobile | | +------+ +----------------------+ |
Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | Vehicle-->| Network |--|->| ESRP |--->| PSAP1 --> Call Taker | |
| | | +------+ +-------+ | | | | +------+ +----------------------+ |
| | | | | | | |
+------------+ | +-------+ | +------------+ | +-------+ |
| | PSAP3 | | | | PSAP3 | |
| +-------+ | | +-------+ |
| | | |
| | | |
| | | |
| ESInet | | ESInet |
+---------------------------------------+ +---------------------------------------+
Figure 10: Example of Vehicle-Placed Emergency Call Message Flow Figure 10: Example Call Initiation
The example, shown in Figure 11, illustrates a SIP emergency call Figure 11 illustrates an example SIP emergency call INVITE request as
INVITE request with location information (a PIDF-LO), VEDS crash data generated by the IVS. It includes a PIDF-LO with vehicle-determined
(a VEDS data block), and capabilities data (a metadata/control block location information, a VEDS block with crash data, and a metadata/
with extensions defined in this document) included in the SIP INVITE control block with capabilities data. The INVITE has a request URI
request message. The INVITE has a request URI containing the containing the urn:service:sos.ecall.automatic service URN. For
'urn:service:sos.ecall.automatic' service URN. brevity, the example VEDS block does not show VEDS location
information, although this is generally present.
The example VEDS data structure shows information about a crashed The example VEDS data structure shows information about a crashed
vehicle. The example communicates that the car is a model year 2015 vehicle. The example communicates that the car is a model year 2015
Saab 9-5 (a car which does not exist). The front airbag deployed as Saab 9-5 (a car that does not exist). The front airbag deployed as a
a consequence of the crash. The 'VehicleBodyCategoryCode' indicates consequence of the crash. The <VehicleBodyCategoryCode> indicates
that the crashed vehicle is a passenger car (the code is set to that the crashed vehicle is a passenger car (the code is set to
'101') and that it is not a convertible (the 'ConvertibleIndicator' "101") and that it is not a convertible (the <ConvertibleIndicator>
value is set to 'false'). value is set to "false").
The 'VehicleCrashPulse' element provides further information about The <VehicleCrashPulse> element provides further information about
the crash, namely that the force of impact based on the change in the crash, namely that the force of impact based on the change in
velocity over the duration of the crash pulse was 100 MPH. The velocity over the duration of the crash pulse was 100 MPH. The
principal direction of the force of the impact is set to '12' (which principal direction of the force of the impact is set to "12" (which
refers to 12 O'Clock, corresponding to a frontal collision). This refers to 12 o'clock, corresponding to a frontal collision). This
value is described in the 'CrashPulsePrincipalDirectionOfForceValue' value is in the <CrashPulsePrincipalDirectionOfForceValue> element.
element.
The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of The <CrashPulseRolloverQuarterTurnsValue> indicates the number of
quarter turns in concert with a rollover expressed as a number; in quarter turns in concert with a rollover expressed as a number; in
our case 1. our case 1.
No roll bar was deployed, as indicated in No roll bar was deployed, as indicated in
'VehicleRollbarDeployedIndicator' being set to 'false'. <VehicleRollbarDeployedIndicator> being set to "false".
Next, there is information indicating seatbelt and seat sensor data Next, there is information indicating seat belt and seat sensor data
for individual seat positions in the vehicle. In our example, for individual seat positions in the vehicle. In our example,
information from the driver seat is available (value '1' in the information from the driver seat is available (value "1" in the
'VehicleSeatLocationCategoryCode' element), that the seatbelt was <VehicleSeatLocationCategoryCode> element) showing that the seat belt
monitored ('VehicleSeatbeltMonitoredIndicator' element), that the was monitored (<VehicleSeatbeltMonitoredIndicator> element), the seat
seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) belt was fastened (<VehicleSeatbeltFastenedIndicator> element), and
and the seat sensor determined that the seat was occupied the seat sensor determined that the seat was occupied
('VehicleSeatOccupiedIndicator' element). (<VehicleSeatOccupiedIndicator> element).
Finally, information about the weight of the vehicle, which is 600 The weight of the vehicle when empty is listed as 600 kilograms in
kilogram in our example. our example.
In addition to the information about the vehicle, further indications The <SevereInjuryIndicator> element is set to "true", indicating a
are provided, namely the presence of fuel leakage likelihood that a vehicle occupant has suffered a severe injury
('FuelLeakingIndicator' element), an indication whether the vehicle requiring immediate trauma care.
was subjected to multiple impacts ('MultipleImpactsIndicator'
Additional information is provided, including the presence of fuel
leakage (<FuelLeakingIndicator> element), an indication whether the
vehicle was subjected to multiple impacts (<MultipleImpactsIndicator>
element), the orientation of the vehicle at final rest element), the orientation of the vehicle at final rest
('VehicleFinalRestOrientationCategoryCode' element) and an indication (<VehicleFinalRestOrientationCategoryCode> element), and an
that there are no parts of the vehicle on fire (the indication that no parts of the vehicle are currently detected as
'VehicleFireIndicator' element). being on fire (the <VehicleFireIndicator> element).
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.VEDS purpose=EmergencyCallData.VEDS
Call-Info: <cid:1234567892@atlanta.example.com>; Call-Info: <cid:1234567892@atlanta.example.com>;
purpose=emergencyCallData.control purpose=EmergencyCallData.Control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.control+xml application/EmergencyCallData.Control+xml
Recv-Info: emergencyCallData.eCall Recv-Info: EmergencyCallData.eCall
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
CSeq: 31862 INVITE CSeq: 31862 INVITE
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
skipping to change at page 25, line 5 skipping to change at page 25, line 5
xmlns:gs="http://www.opengis.net/pidflo/1.0" xmlns:gs="http://www.opengis.net/pidflo/1.0"
entity="sip:+13145551111@example.com"> entity="sip:+13145551111@example.com">
<dm:device id="123"> <dm:device id="123">
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"> <gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-34.407 150.883</gml:pos> <gml:pos>-34.407 150.883</gml:pos>
</gml:Point> </gml:Point>
<dyn:Dynamic> <dyn:Dynamic>
<dyn:heading>278</dyn:heading> <dyn:heading>278</dyn:heading>
<dyn:direction><dyn:direction> <dyn:direction></dyn:direction>
</dyn:Dynamic> </dyn:Dynamic>
</gp:location-info> </gp:location-info>
<gp:usage-rules/> <gp:usage-rules/>
<method>gps</method> <method>gps</method>
</gp:geopriv> </gp:geopriv>
<timestamp>2012-04-5T10:18:29Z</timestamp> <timestamp>2012-04-5T10:18:29Z</timestamp>
<dm:deviceID>1M8GDM9A_KP042788</dm:deviceID> <dm:deviceID>1M8GDM9A_KP042788</dm:deviceID>
</dm:device> </dm:device>
</presence> </presence>
--boundary1 --boundary1
Content-Type: application/EmergencyCallData.VEDS+xml Content-Type: application/EmergencyCallData.VEDS+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@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"?>
<AutomatedCrashNotification xmlns="http://www.veds.org/acn/1.0" <AutomatedCrashNotification xmlns="http://www.veds.org/acn/1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Crash> <Crash>
<CrashVehicle> <CrashVehicle>
<ItemMakeName xmlns="http://niem.gov/niem/niem-core/2.0"> <ItemMakeName xmlns="http://niem.gov/niem/niem-core/2.0">
Saab Saab
</ItemMakeName> </ItemMakeName>
<ItemModelName xmlns="http://niem.gov/niem/niem-core/2.0"> <ItemModelName xmlns="http://niem.gov/niem/niem-core/2.0">
9-5 9-5
</ItemModelName> </ItemModelName>
<ItemModelYearDate <ItemModelYearDate
skipping to change at page 26, line 49 skipping to change at page 26, line 49
<FuelLeakingIndicator>true</FuelLeakingIndicator> <FuelLeakingIndicator>true</FuelLeakingIndicator>
<MultipleImpactsIndicator>false</MultipleImpactsIndicator> <MultipleImpactsIndicator>false</MultipleImpactsIndicator>
<SevereInjuryIndicator>true</SevereInjuryIndicator> <SevereInjuryIndicator>true</SevereInjuryIndicator>
<VehicleFinalRestOrientationCategoryCode>Driver <VehicleFinalRestOrientationCategoryCode>Driver
</VehicleFinalRestOrientationCategoryCode> </VehicleFinalRestOrientationCategoryCode>
<VehicleFireIndicator>false</VehicleFireIndicator> <VehicleFireIndicator>false</VehicleFireIndicator>
</Crash> </Crash>
</AutomatedCrashNotification> </AutomatedCrashNotification>
--boundary1 --boundary1
Content-Type: application/emergencyCallData.control+xml Content-Type: application/EmergencyCallData.Control+xml
Content-ID: <1234567892@atlanta.example.com> Content-ID: <1234567892@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.control <EmergencyCallData.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<capabilities> <capabilities>
<request action="send-data" supported-datatypes="VEDS"/> <request action="send-data" supported-datatypes="VEDS"/>
<request action="lamp" <request action="lamp"
supported-values="head;interior;fog-front;fog-rear; supported-values="head;interior;fog-front;fog-rear;
brake;position-front;position-rear;turn-left; brake;position-front;position-rear;turn-left;
turn-right;hazard"/> turn-right;hazard"/>
<request action="msg-static" int-id="3"/> <request action="msg-static" int-id="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<request action="enable-camera" <request action="enable-camera"
supported-values="backup;interior"/> supported-values="backup;interior"/>
<request action="door-lock"/> <request action="door-lock"/>
</capabilities> </capabilities>
</EmergencyCallData.control> </EmergencyCallData.Control>
--boundary1-- --boundary1--
Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call Figure 11: SIP INVITE for a Vehicle-Initiated Emergency Call
12. Security Considerations 12. Security Considerations
Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], Since this document relies on [RFC8147] and [RFC7852], the security
the security considerations described there and in [RFC5069] apply considerations described in those specifications apply here. The
here. Implementors are cautioned to read and understand the security considerations of [RFC5069] apply as well. Implementors are
discussion in those documents. cautioned to read and understand the discussion in those documents.
As with emergency service systems where location data is supplied or In emergency service systems where location data is supplied or
determined with the assistance of an end host, there is the determined with the assistance of an end host, it is possible that
possibility that that location is incorrect, either intentially the location is incorrect, either intentionally (e.g., in a denial-
(e.g., in a denial of service attack against the emergency services of-service attack against the emergency services infrastructure) or
infrastructure) or due to a malfunctioning device. The reader is due to a malfunctioning device. The reader is referred to [RFC7378]
referred to [RFC7378] for a discussion of some of these for a discussion of some of these vulnerabilities.
vulnerabilities.
In addition to the security considerations discussion specific to the In addition to the security considerations discussion specific to the
metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles metadata/control object in [RFC8147], note that vehicles MAY decline
MAY decline to carry out any requested action (e.g., if the vehicle to carry out any requested action (e.g., if the vehicle requires but
requires but is unable to verify the certificate used to sign the is unable to verify the certificate used to sign the request). The
request). The vehicle MAY use any value in the reason registry to vehicle MAY use any value in the reason registry to indicate why it
indicate why it did not take an action (e.g., the generic "unable" or did not take an action (e.g., the generic "unable" or the more
the more specific "security-failure"). Because some actions carry specific "security-failure"). Because some actions carry more
more potential risk than others (e.g., unlocking a door versus potential risk than others (e.g., unlocking a door versus flashing
flashing lights), vehicle policy MAY decline to carry out some lights), vehicle policy MAY decline to carry out some requests in
requests in some circumstances (e.g., declining a request to unlock some circumstances (e.g., decline a request to unlock doors, send an
doors, send an updated VEDS, or enable a camera received in a updated VEDS, or enable a camera received in a vehicle-terminated
vehicle-terminated call while carrying out such requests received in call while carrying out such requests received in a vehicle-initiated
a vehicle-initiated emergency call). emergency call).
13. Privacy Considerations 13. Privacy Considerations
Since this document builds on [I-D.ietf-ecrit-ecall], which itself Since this document builds on [RFC8147], which itself builds on
builds on [RFC7852], the data structures specified there, and the [RFC7852], the data structures specified there, and the corresponding
corresponding privacy considerations discussed there, apply here as privacy considerations discussed there, apply here as well. The VEDS
well. The VEDS data structure contains optional elements that can data structure contains optional elements that can carry identifying
carry identifying and personal information, both about the vehicle and personal information, both about the vehicle and about the owner,
and about the owner, as well as location information, and so needs to as well as location information, so it needs to be protected against
be protected against unauthorized disclosure, as discussed in unauthorized disclosure, as discussed in [RFC7852]. Local
[RFC7852]. Local regulations may impose additional privacy regulations may impose additional privacy protection requirements.
protection requirements.
The additional functionality enabled by this document, such as access The additional functionality enabled by this document, such as access
to vehicle camera streams, carries a burden of protection and so to vehicle camera streams, carries a burden of protection, so
implementations need to be careful that access is only provided implementations need to be careful that access is only provided
within the context of an emergency call or to an emergency services within the context of an emergency call or to an emergency services
provider (e.g., by verifying that the request for camera access is provider (e.g., by verifying that the request for camera access is
signed by a certificate issued by an emergency services registrar). signed by a certificate issued by an emergency services registrar).
14. IANA Considerations 14. IANA Considerations
This document registers the 'application/EmergencyCall.VEDS+xml' MIME This document registers the application/EmergencyCallData.VEDS+xml
media type, and adds "VEDS" to the Emergency Call Data Types MIME media type and adds "VEDS" to the "Emergency Call Data Types"
registry. This document adds to and creates sub-registries in the registry. This document adds to and creates sub-registries in the
"Emergency Call Metadata/Control Data" registry created in "Emergency Call Metadata/Control Data" registry created in [RFC8147].
[I-D.ietf-ecrit-ecall]. This document registers a new SIP INFO In addition, this document registers a new INFO package.
package.
14.1. MIME Media Type Registration for 'application/ 14.1. MIME Media Type Registration for application/
EmergencyCall.VEDS+xml' EmergencyCall.VEDS+xml
This specification requests the registration of a new MIME media type IANA has registered a new MIME media type according to the procedures
according to the procedures of RFC 6838 [RFC6838] and guidelines in of [RFC6838] and guidelines in [RFC7303].
RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.VEDS+xml MIME subtype name: EmergencyCallData.VEDS+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of enclosed XML. Indicates the character encoding of enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations:
characters, depending on the character encoding used. See Uses XML, which can employ 8-bit characters, depending on the
Section 3.2 of RFC 7303 [RFC7303]. character encoding used. See Section 3.2 of RFC 7303
[RFC7303].
Security considerations: Security considerations:
This media type is designed to carry vehicle crash data
during an emergency call.
This media type is designed to carry vehicle crash data during This data can contain personal information including vehicle
an emergency call. VIN, location, direction, etc. Appropriate precautions need
to be taken to limit unauthorized access, inappropriate
This data can contain personal information including vehicle disclosure to third parties, and eavesdropping of this
VIN, location, direction, etc. Appropriate precautions need to information. Please refer to Sections 9 and 10 of [RFC7852]
be taken to limit unauthorized access, inappropriate disclosure for more information.
to third parties, and eavesdropping of this information.
Please refer to Section 9 and Section 10 of [RFC7852] for more
information.
When this media type is contained in a signed or encrypted body When this media type is contained in a signed or encrypted
part, the enclosing multipart (e.g., multipart/signed or body part, the enclosing multipart (e.g., multipart/signed
multipart/encrypted) has the same Content-ID as the data part. or multipart/encrypted) has the same Content-ID as the data
This allows an entity to identify and access the data blocks it part. This allows an entity to identify and access the data
is interested in without having to dive deeply into the message blocks it is interested in without having to dive deeply
structure or decrypt parts it is not interested in. (The into the message structure or decrypt parts it is not
'purpose' parameter in a Call-Info header field identifies the interested in. (The "purpose" parameter in a Call-Info
data, and the CID URL points to the data block in the body, header field identifies the data, and the CID URL points to
which has a matching Content-ID body part header field). the data block in the body, which has a matching Content-ID
body part header field.)
Interoperability considerations: None Interoperability considerations: None
Published specification: [VEDS] Published specification: [VEDS]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: None Additional information: None
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: TEXT
Persons and email addresses for further information: Randall Persons and email addresses for further information:
Gellens rg+ietf@randy.pensive.org; Hannes Tschofenig, Randall Gellens, rg+ietf@randy.pensive.org;
Hannes.Tschofenig@gmx.net Hannes Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author:
working group, with mailing list address <ecrit@ietf.org>. This specification is a work item of the IETF ECRIT working
group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
14.2. Registration of the 'VEDS' entry in the Emergency Call Data Types 14.2. Registration of the "VEDS" Entry in the Emergency Call Data Types
registry Registry
This specification requests IANA to add the 'VEDS' entry to the IANA has added "VEDS" to the "Emergency Call Data Types" registry,
Emergency Call Data Types registry, with a reference to this with a reference to this document; the "Data About" value is "The
document; the 'Data About' value is 'The Call'. The Emergency Call Call". The "Emergency Call Data Types" registry was established by
Data types registry was established by [RFC7852]. [RFC7852].
14.3. New Action Values 14.3. New Action Values
This document adds new values for the 'action' attribute of the This document adds new values for the "action" attribute of the
<request> element in the "Emergency Call Action" registry created by <request> element in the "Emergency Call Action" registry created by
[I-D.ietf-ecrit-ecall]. [RFC8147].
+---------------+-------------------------------------+ +---------------+-------------------------+
| Name | Description | | Name | Description |
+---------------+-------------------------------------+ +---------------+-------------------------+
| msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | | msg-static | Section 9.1 of RFC 8148 |
| | | | | |
| msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | | msg-dynamic | Section 9.1 of RFC 8148 |
| | | | | |
| honk | Section 9.1 of [TBD: THIS DOCUMENT] | | honk | Section 9.1 of RFC 8148 |
| | | | | |
| lamp | Section 9.1 of [TBD: THIS DOCUMENT] | | lamp | Section 9.1 of RFC 8148 |
| | | | | |
| enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | | enable-camera | Section 9.1 of RFC 8148 |
| | | | | |
| door-lock | Section 9.1 of [TBD: THIS DOCUMENT] | | door-lock | Section 9.1 of RFC 8148 |
+---------------+-------------------------------------+ +---------------+-------------------------+
Table 2: Emergency Call Action Registry New Values Table 1: Emergency Call Action Registry New Values
14.4. Emergency Call Static Message Registry 14.4. Emergency Call Static Messages Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Static Message" in the "Emergency Call Metadata/Control Data" Static Messages" in the "Emergency Call Metadata/Control Data"
registry established by [I-D.ietf-ecrit-ecall]. Because all registry established by [RFC8147]. Because compliant vehicles are
compliant vehicles are expected to support all static messages expected to support all static messages translated into all languages
translated into all languages supported by the vehicle, it is supported by the vehicle, it is important to limit the number of such
important to limit the number of such messages. As defined in messages. As defined in [RFC5226], this registry operates under
[RFC5226], this registry operates under "Specification Required" "Specification Required", which requires a stable, public document
rules, which require a stable, public document and implies expert and implies expert review of the publication. The expert should
review of the publication. The expert should determine that the determine that the document has been published by an appropriate
document has been published by an appropriate emergency services emergency services organization (e.g., NENA, EENA, or APCO) or by the
organization (e.g., NENA, EENA, APCO) or by the IETF with input from IETF with input from an emergency services organization, and that the
an emergency services organization, and that the proposed message is proposed message is sufficiently distinguishable from other messages.
sufficiently distinguishable from other messages.
The contents of this registry are: The contents of this registry are:
ID: An integer identifier to be used in the 'int-id' attribute of a ID: An integer identifier to be used in the "int-id" attribute of a
metadata/control <request> element. metadata/control <request> element.
Message: The text of the message. Messages are listed in the Message: The text of the message. Messages are listed in the
registry in English; vehicles are expected to implement registry in English; vehicles are expected to implement
translations into languages supported by the vehicle. translations into languages supported by the vehicle.
When new messages are added to the registry, the message text is When new messages are added to the registry, the message text is
determined by the registrant; IANA assigns the IDs. Each message is determined by the registrant; IANA assigns the IDs. Each message is
assigned a consecutive integer value as its ID. This allows an IVS assigned a consecutive integer value as its ID. This allows an IVS
to indicate by a single integer value that it supports all messages to indicate by a single integer value that it supports all messages
with that value or lower. with that value or lower. The value 0 is reserved; usable messages
start with 1.
The initial set of values is listed in Table 3. The initial set of values is listed in Table 2.
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| ID | Message | | ID | Message |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| 0 | Reserved |
| | |
| 1 | Emergency services has received your information and | | 1 | Emergency services has received your information and |
| | location, but cannot speak with you right now. We will get | | | location but cannot speak with you right now. We will get |
| | help to you as soon as possible. | | | help to you as soon as possible. |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
Table 3: Emergency Call Static Message Registry Initial Values Table 2: Emergency Call Static Messages Registry Initial Values
14.5. Emergency Call Vehicle Lamp ID Registry 14.5. Emergency Call Vehicle Lamp IDs Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Vehicle Lamp ID" in the "Emergency Call Metadata/Control Data" Vehicle Lamp IDs" in the "Emergency Call Metadata/Control Data"
registry established by [I-D.ietf-ecrit-ecall]. This new sub- registry established by [RFC8147]. This new sub-registry uniquely
registry uniquely identifies the names of automotive lamps (lights). identifies the names of automotive lamps (lights). As defined in
As defined in [RFC5226], this registry operates under "Expert Review" [RFC5226], this registry operates under "Expert Review" rules. The
rules. The expert should determine that the proposed lamp name is expert should determine that the proposed lamp name is clearly
clearly understandable and is sufficiently distinguishable from other understandable and is sufficiently distinguishable from other lamp
lamp names. names.
The contents of this registry are: The contents of this registry are:
Name: The identifier to be used in the 'element-id' attribute of a Name: The identifier to be used in the "element-id" attribute of a
metadata/control <request> element. metadata/control <request> element.
Description: A description of the lamp (light). Description: A description of the lamp (light).
The initial set of values is listed in Table 4. The initial set of values is listed in Table 3.
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
| Name | Description | | Name | Description |
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
| head | The main lamps used to light the road ahead | | head | The main lamps used to light the road ahead |
| | | | | |
| interior | Interior lamp, often at the top center | | interior | Interior lamp, often at the top center |
| | | | | |
| fog-front | Front fog lamps | | fog-front | Front fog lamps |
| | | | | |
| fog-rear | Rear fog lamps | | fog-rear | Rear fog lamps |
| | | | | |
| brake | Brake indicator lamps | | brake | Brake indicator lamps |
| | | | | |
| brake-center | Center High Mounted Stop Lamp | | brake-center | Center high-mounted stop lamp |
| | | | | |
| position-front | Front position/parking/standing lamps | | position-front | Front position/parking/standing lamps |
| | | | | |
| position-rear | Rear position/parking/standing lamps | | position-rear | Rear position/parking/standing lamps |
| | | | | |
| turn-left | Left turn/directional lamps | | turn-left | Left turn/directional lamps |
| | | | | |
| turn-right | Right turn/directional lamps | | turn-right | Right turn/directional lamps |
| | | | | |
| hazard | Hazard/four-way lamps | | hazard | Hazard/four-way lamps |
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
Table 4: Emergency Call Lamp ID Registry Initial Values Table 3: Emergency Call Lamp ID Registry Initial Values
14.6. Emergency Call Vehicle Camera ID Registry 14.6. Emergency Call Vehicle Camera IDs Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Vehicle Camera ID" in the "Emergency Call Metadata/Control Data" Vehicle Camera IDs" in the "Emergency Call Metadata/Control Data"
registry established by [I-D.ietf-ecrit-ecall]. This new sub- registry established by [RFC8147]. This new sub-registry uniquely
registry uniquely identifies automotive cameras. As defined in identifies automotive cameras. As defined in [RFC5226], this
[RFC5226], this registry operates under "Expert Review" rules. The registry operates under "Expert Review" rules. The expert should
expert should determine that the proposed camera name is clearly determine that the proposed camera name is clearly understandable and
understandable and is sufficiently distinguishable from other camera is sufficiently distinguishable from other camera names.
names.
The contents of this registry are: The contents of this registry are:
Name: The identifier to be used in the 'element-id' attribute of a Name: The identifier to be used in the "element-id" attribute of a
control <request> element. control <request> element.
Description: A description of the camera. Description: A description of the camera.
The initial set of values is listed in Table 5. The initial set of values is listed in Table 4.
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
| Name | Description | | Name | Description |
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
| backup | Shows what is behind the vehicle, e.g., often used | | backup | Shows what is behind the vehicle, e.g., often used |
| | for driver display when the vehicle is in reverse. | | | for driver display when the vehicle is in reverse. |
| | Also known as rearview, reverse, rear visibility, | | | Also known as rearview, reverse, rear visibility, |
| | etc. | | | etc. |
| | | | | |
| left-rear | Shows view to the left and behind (e.g., left side | | left-rear | Shows view to the left and behind (e.g., left-side |
| | rear-view mirror or blind spot view) | | | rearview mirror or blind spot view) |
| | | | | |
| right-rear | Shows view to the right and behind (e.g., right | | right-rear | Shows view to the right and behind (e.g., right- |
| | side rear-view mirror or blind spot view) | | | side rearview mirror or blind spot view) |
| | | | | |
| forward | Shows what is in front of the vehicle | | forward | Shows what is in front of the vehicle |
| | | | | |
| rear-wide | Shows what is behind vehicle (e.g., used by rear- | | rear-wide | Shows what is behind the vehicle (e.g., used by |
| | collision detection systems), separate from backup | | | rear-collision detection systems), separate from |
| | view | | | backup view |
| | | | | |
| lane | Used by systems to identify road lane and/or | | lane | Used by systems to identify road lane and/or |
| | monitor vehicle's position within lane | | | monitor the vehicle's position within lane |
| | | | | |
| interior | Shows the interior (e.g., driver) | | interior | Shows the interior (e.g., driver) |
| | | | | |
| night-front | Night-vision view of what is in front of the | | night-front | Night-vision view of what is in front of the |
| | vehicle | | | vehicle |
| | | | | |
| night-rear | Night-vision view of what is behind the vehicle | | night-rear | Night-vision view of what is behind the vehicle |
| | | | | |
| night-left | Night-vision view of what is to the left of the | | night-left | Night-vision view of what is to the left of the |
| | vehicle | | | vehicle |
| | | | | |
| night-right | Night-vision view of what is to the right of the | | night-right | Night-vision view of what is to the right of the |
| | vehicle | | | vehicle |
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
Table 5: Emergency Call Vehicle Camera ID Registry Initial Values Table 4: Emergency Call Vehicle Camera IDs Registry Initial Values
14.7. The emergencyCallData.eCall.VEDS SIP INFO package 14.7. The EmergencyCallData.VEDS INFO Package
This document registers the 'emergencyCallData.eCall.VEDS' SIP INFO This document registers the EmergencyCallData.VEDS INFO package in
package. the "Info Packages Registry".
Both endpoints (the IVS and the PSAP equipment) include Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.VEDS' in a Recv-Info header field per "EmergencyCallData.VEDS" in a Recv-Info header field per [RFC6086] to
[RFC6086] to indicate ability to receive SIP INFO messages carrying indicate the ability to receive SIP INFO messages carrying data as
data as described here. described here.
Support for the 'emergencyCallData.eCall.VEDS' SIP INFO package Support for the EmergencyCallData.VEDS INFO package indicates the
indicates the ability to receive NG-ACN related body parts as ability to receive NG-ACN-related body parts as specified in this
specified in [TBD: THIS DOCUMENT]. document.
A SIP INFO request message carrying data related to an emergency call A SIP INFO request message carrying data related to an emergency call
as described in [TBD: THIS DOCUMENT] has an Info-Package header field as described in this document has an Info-Package header field set to
set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. "EmergencyCallData.VEDS" per [RFC6086].
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.
14.7.1. Overall Description 14.7.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 User Agents (UAs) can use the INFO
package.
SIP INFO requests associated with the emergencyCallData.eCall.VEDS SIP INFO requests associated with the EmergencyCallData.VEDS INFO
SIP INFO package carry data associated with emergency calls as package carry data associated with emergency calls as defined in this
defined in [TBD: THIS DOCUMENT]. The application is vehicle- document. The application is vehicle-initiated emergency calls
initiated emergency calls established using SIP. The functionality established using SIP. The functionality is to carry vehicle data
is to carry vehicle data and metadata/control information between and metadata/control information between vehicles and PSAPs.
vehicles and PSAPs. Refer to [TBD: THIS DOCUMENT] for more
information.
14.7.2. Applicability 14.7.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 the SIP INFO method is based on an analysis of the The use of the SIP INFO method is based on an analysis of the
requirements against the intent and effects of the INFO method versus requirements against the intent and effects of the INFO method versus
other approaches (which included the SIP MESSAGE method, SIP OPTIONS other approaches (which included the SIP MESSAGE method, SIP OPTIONS
method, SIP re-INVITE method, media plane transport, and non-SIP method, SIP re-INVITE method, media-plane transport, and non-SIP
protocols). In particular, the transport of emergency call data protocols). In particular, the transport of emergency call data
blocks occurs within a SIP emergency dialog, per Section 7, and is blocks occurs within a SIP emergency dialog, per Section 7, and is
normally carried in the initial INVITE request and its response; the normally carried in the initial INVITE request and its response; the
use of the INFO method only occurs when emergency-call-related data use of the INFO method only occurs when emergency-call-related data
needs to be sent mid-call. While the SIP MESSAGE method could be needs to be sent mid call. While the SIP MESSAGE method could be
used, it is not tied to a SIP dialog as is the INFO method and thus used, it is not tied to a SIP dialog as is the INFO method and thus
might not be associated with the dialog. Both the SIP OPTIONS or re- might not be associated with the dialog. Both the SIP OPTIONS or
INVITE methods could also be used, but is seen as less clean than the re-INVITE methods could also be used, but they are seen as less clean
INFO method. The SIP SUBSCRIBE/NOTIFY method could be coerced into than the INFO method. The SIP SUBSCRIBE/NOTIFY method could be
service, but the semantics are not a good fit, e.g., the subscribe/ coerced into service, but the semantics are not a good fit, e.g., the
notify mechanism provides one-way communication consisting of (often subscribe/notify mechanism provides one-way communication consisting
multiple) notifications from notifier to subscriber indicating that of (often multiple) notifications from notifier to subscriber
certain events in notifier have occurred, whereas what's needed here indicating that certain events in the notifier have occurred, whereas
is two-way communication of data related to the emergency dialog. what's needed here is two-way communication of data related to the
Use of the media plane mechanisms was discounted because the number emergency dialog. Use of media-plane mechanisms was discounted
of messages needing to be exchanged in a dialog is normally zero or because the number of messages needing to be exchanged in a dialog is
very few, and the size of the data is likewise very small. The normally zero or very few, and the size of the data is likewise very
overhead caused by user plane setup (e.g., to use MSRP as transport) small. The overhead caused by user-plane setup (e.g., to use the
would be disproportionately large. Message Session Relay Protocol (MSRP) as transport) would be
disproportionately large.
Based on the analyses, the SIP INFO method was chosen to provide for Based on the analyses, the SIP INFO method was chosen to provide for
mid-call data transport. mid-call data transport.
14.7.3. Info Package Name 14.7.3. INFO Package Name
The SIP INFO package name is emergencyCallData.eCall.VEDS The INFO package name is EmergencyCallData.VEDS.
14.7.4. Info Package Parameters 14.7.4. INFO Package Parameters
None None
14.7.5. SIP Option-Tags 14.7.5. SIP Option-Tags
None None
14.7.6. INFO Request Body Parts 14.7.6. INFO Request Body Parts
The body of an emergencyCallData.eCall.VEDS SIP INFO package is a The body of an EmergencyCallData.VEDS INFO package is a multipart
multipart body which MAY contain zero or one application/ body containing zero or one application/EmergencyCallData.VEDS+xml
emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part, parts (containing a VEDS data block), zero or more application/
zero or more application/emergencyCallData.control+xml (containing a EmergencyCallData.Control+xml (containing a metadata/control object)
metadata/control object) parts, and zero or one application/ parts, and zero or one application/EmergencyCallData.eCall.MSD parts
emergencyCallData.eCall.MSD+per (containing an MSD) part. At least (containing an MSD). At least one VEDS, MSD, or metadata/control
one VEDS, MSD, or metadata/control body part is expected; the body part is expected; the behavior upon receiving a SIP INFO request
behavior upon receiving a SIP INFO request with none is undefined. with none is undefined.
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. The body part has a Content-
Disposition header field set to "By-Reference".
A VEDS or metadata/control block is always enclosed in a multipart The body parts are sent per [RFC6086]; in addition, to align with how
body part (even if it would otherwise be the only body part in the these body parts are sent in non-INFO messages, each associated body
SIP message), since as of the date of this document, the use of part is referenced by a Call-Info header field at the top level of
Content-ID as a SIP header field is not defined (while it is defined the SIP message. The body part has a Content-Disposition header
for use as a MIME header field). The innermost multipart that field set to "By-Reference".
contains only body parts associated with the SIP INFO package has a
Content-Disposition value of Info-Package.
Service providers are not expected to add [RFC7852] Additional Data A VEDS, metadata/control block, or MSD is always enclosed in a
to SIP INFO requests. multipart body part (even if it would otherwise be the only body part
in the SIP message). The outermost multipart that contains only body
parts associated with the INFO package has a Content-Disposition
value of "Info-Package".
See [TBD: THIS DOCUMENT] for more information. Service providers in the call path are not expected to add Additional
Data [RFC7852] to SIP INFO requests (as they would to an initial
INVITE request).
14.7.7. Info Package Usage Restrictions 14.7.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]. this document.
14.7.8. Rate of INFO Requests 14.7.8. Rate of INFO Requests
The SIP INFO request is used within an established emergency call The SIP INFO request is used within an established emergency call
dialog for the PSAP to request the IVS to send an updated data set, dialog to send requests, updated data, or an acknowledgment. Because
and for the IVS to send the requested data set. Because this is requests are normally sent only on manual action of the PSAP call
normally done only on manual request of the PSAP call taker (who taker (who suspects some aspect of the vehicle state has changed) and
suspects some aspect of the vehicle state has changed), the rate of updated data is sent only when an aspect of previously sent data has
SIP INFO requests associated with the emergencyCallData.eCall.VEDS changed, the rate of SIP INFO requests associated with the
SIP INFO package is normally quite low (most dialogs are likely to EmergencyCallData.VEDS INFO package is normally quite low (most
contain zero SIP INFO requests, while others can be expected to carry dialogs are likely to contain zero SIP INFO requests, while others
an occasional request). can be expected to carry an occasional request).
14.7.9. Info Package Security Considerations 14.7.9. INFO Package Security Considerations
The MIME media type registations for the data blocks that can be The MIME media type registrations for the data blocks that can be
carried using this SIP INFO package contains a discussion of the carried using this INFO package contains a discussion of the security
security and/or privacy considerations specific to that data block. and/or privacy considerations specific to that data block. See
The "Security Considerations" and "Privacy Considerations" sections Sections 12 and 13 for information on the security and privacy
of [TBD: THIS DOCUMENT] discuss security and privacy considerations considerations of the data carried in vehicle-initiated emergency
of the data carried in vehicle-initiated emergency calls as described calls.
in that document.
14.7.10. Implementation Details 14.7.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details. See Sections 7 and 8 for protocol details.
14.7.11. Examples 14.7.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples. See Section 11 for protocol examples.
15. Acknowledgements
We would like to thank Lena Chaponniere, Alissa Cooper, Stephen Edge,
Christer Holmberg, Allison Mankin, and Dan Romascanu for their review
and suggestions; Robert Sparks and Paul Kyzivat for their help with
the SIP mechanisms; Michael Montag, Arnoud van Wijk, Ban Al-Bakri,
Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback;
and Ulrich Dietz for his help with earlier versions of the original
version of this document.
16. Changes from Previous Versions
RFC Editor: Please remove this section prior to publication.
16.1. Changes from draft-ietf-18 to draft-ietf-19
o Fixed various nits
16.2. Changes from draft-ietf-17 to draft-ietf-18
o Added additional text to "Rate of Info Requests"
o Further corrected "content type" to "media type"
16.3. Changes from draft-ietf-16 to draft-ietf-17
o Clarified that an INFO request is expected to have at least one
VEDS, MSD or metadata/control body part
o Corrected "content type" to "media type"
16.4. Changes from draft-ietf-14 to draft-ietf-15
o Moved VEDS text from Introduction to new Vehicle Data section
o Various clarifications and simplifications
16.5. Changes from draft-ietf-13 to draft-ietf-14
o Body parts now always sent enclosed in multipart (even if only
body part in SIP message) and hence always have a Content-
Disposition of By-Reference
o Fixed typos.
16.6. Changes from draft-ietf-11 to draft-ietf-13
o Fixed typos
16.7. Changes from draft-ietf-10 to draft-ietf-11
o Clarifications suggested by Christer
o Corrections to Content-Disposition text and examples as suggested
by Paul Kyzivat
o Clarifications to Content-Disposition text and examples to clarify
that handling=optional is only used in the initial INVITE
16.8. Changes from draft-ietf-09 to draft-ietf-10
o Fixed errors in examples found by Dale in eCall draft
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 Other text changes per comments received from Christer and Ivo
against eCall draft.
16.9. Changes from draft-ietf-08 to draft-ietf-09
o Added INFO package registration for eCall.VEDS
o Moved <capabilities> element and other extension points back to
eCall document so that extension points are in base spec (and also
to get XML schema to compile)
o Text changes for clarification.
16.10. Changes from draft-ietf-07 to draft-ietf-08
o Moved much of the metadata/control object from
[I-D.ietf-ecrit-ecall] to this document as extensions
o Editorial clarifications and simplifications
o Moved "Call Routing" to be a subsection of "Call Setup"
o Deleted "Profile" section and moved some of its text into
"Introduction"
16.11. Changes from draft-ietf-06 to draft-ietf-07
o Minor editorial changes
16.12. Changes from draft-ietf-05 to draft-ietf-06
o Added clarifying text regarding signed and encrypted data
o Additional informative text in "Migration to Next-Generation"
section
o Additional clarifying text regarding security and privacy.
16.13. Changes from draft-ietf-04 to draft-ietf-05
o Reworded security text in main document and in MIME registration
for the VEDS object
16.14. Changes from draft-ietf-03 to draft-ietf-04
o Added example VEDS object
o Additional clarifications and corrections
o Removed references from Abstract
o Moved Document Scope section to follow Introduction
16.15. Changes from draft-ietf-02 to draft-ietf-03
o Additional clarifications and corrections
16.16. Changes from draft-ietf-01 to draft-ietf-02
o This document now refers to [I-D.ietf-ecrit-ecall] for technical
aspects including the service URN; this document no longer
proposes a unique service URN for non-eCall NG-ACN calls; the same
service URN is now used for all NG-ACN calls including NG-eCall
and non-eCall
o Added discussion of an NG-ACN call placed to a PSAP that doesn't
support it
o Minor wording improvements and clarifications
16.17. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls
o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other
crash notification specifications such as eCall
o Minor wording improvements and clarifications
16.18. Changes from draft-gellens-02 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf-
o Added text to Introduction to clarify that during a CS ACN, the
PSAP call taker usually needs to listen to the data and transcribe
it
16.19. Changes from draft-gellens-01 to -02
o Fixed case of 'EmergencyCallData', in accordance with changes to
[RFC7852]
16.20. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to [RFC7852]
o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear
17. References
17.1. Normative References 15. References
[I-D.ietf-ecrit-ecall] 15.1. Normative References
Gellens, R. and H. Tschofenig, "Next-Generation Pan-
European eCall", draft-ietf-ecrit-ecall-24 (work in
progress), January 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
skipping to change at page 40, line 48 skipping to change at page 38, line 43
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
DOI 10.17487/RFC7303, July 2014, DOI 10.17487/RFC7303, July 2014,
<http://www.rfc-editor.org/info/rfc7303>. <http://www.rfc-editor.org/info/rfc7303>.
[RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
J. Winterbottom, "Additional Data Related to an Emergency J. Winterbottom, "Additional Data Related to an Emergency
Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, Call", RFC 7852, DOI 10.17487/RFC7852, July 2016,
<http://www.rfc-editor.org/info/rfc7852>. <http://www.rfc-editor.org/info/rfc7852>.
[VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ [RFC8147] Gellens, R. and H. Tschofenig, "Next-Generation Pan-
NENA Data Standardization Workgroup, , "Vehicular European eCall", RFC 8147, DOI 10.17487/RFC8147, May 2017,
Emergency Data Set (VEDS) version 3", July 2012, <http://www.rfc-editor.org/info/rfc8147>.
<https://www.apcointl.org/resources/telematics/aacn-and-
veds.html>.
17.2. Informative references [VEDS] APCO International, "Vehicular Emergency Data Set (VEDS)",
Version 3.0, Prepared by the Advanced Automatic Crash
Notification (AACN) Joint APCO/NENA Data Standardization
Working Group, February 2012, <https://www.apcointl.org/
resources/telematics/aacn-and-veds.html>.
15.2. Informative references
[Bluetooth] [Bluetooth]
Bluetooth Special Interest Group, , "Bluetooth Bluetooth Special Interest Group (SIG), "Bluetooth
Specifications", <https://https://www.bluetooth.com/ Specifications", <https://www.bluetooth.com/
specifications>. specifications>.
[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>.
[RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M.
Shanmugam, "Security Threats and Requirements for Shanmugam, "Security Threats and Requirements for
Emergency Call Marking and Mapping", RFC 5069, Emergency Call Marking and Mapping", RFC 5069,
skipping to change at page 41, line 33 skipping to change at page 39, line 33
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, DOI 10.17487/RFC6443, December Multimedia", RFC 6443, DOI 10.17487/RFC6443, December
2011, <http://www.rfc-editor.org/info/rfc6443>. 2011, <http://www.rfc-editor.org/info/rfc6443>.
[RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed.,
"Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378,
December 2014, <http://www.rfc-editor.org/info/rfc7378>. December 2014, <http://www.rfc-editor.org/info/rfc7378>.
[triage-2008] [triage-2008]
National Center for Injury Prevention and Control, and National Center for Injury Prevention and Control,
Centers for Disease Control and Prevention,
"Recommendations from the Expert Panel: Advanced Automatic "Recommendations from the Expert Panel: Advanced Automatic
Collision Notification and Triage of the Injured Patient", Collision Notification and Triage of the Injured Patient",
2008, <https://stacks.cdc.gov/view/cdc/5304/>. Centers for Disease Control and Prevention, 2008,
<https://stacks.cdc.gov/view/cdc/5304/>.
[triage-2011] [triage-2011]
National Center for Injury Prevention and Control, and National Center for Injury Prevention and Control,
Centers for Disease Control and Prevention, "Guidelines "Guidelines for Field Triage of Injured Patients:
for field triage of injured patients: recommendations of Recommendations of the National Expert Panel on Field
the National Expert Panel on Field Triage", January 2012, Triage", Centers for Disease Control and Prevention,
<https://www.researchgate.net/journal/1545-8601_MMWR_Recom January 2012, <https://www.cdc.gov/mmwr/preview/mmwrhtml/
mendations_and_reports_Morbidity_and_mortality_weekly_repo rr6101a1.htm>.
rt_Recommendations_and_reports_Centers_for_Disease_Control
>. Acknowledgments
We would like to thank Lena Chaponniere, Alissa Cooper, Stephen Edge,
Christer Holmberg, Allison Mankin, and Dan Romascanu for their review
and suggestions; Robert Sparks and Paul Kyzivat for their help with
the SIP mechanisms; Michael Montag, Arnoud van Wijk, Ban Al-Bakri,
Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback;
and Ulrich Dietz for his help with preliminary draft versions of the
original document that later evolved into this document.
Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
Core Technology Consulting Core Technology Consulting
Email: rg+ietf@randy.pensive.org Email: rg+ietf@coretechnologyconsulting.com
URI: http://www.coretechnologyconsulting.com
Brian Rosen Brian Rosen
NeuStar, Inc. NeuStar, Inc.
470 Conrad Dr 470 Conrad Dr
Mars, PA 16046 Mars, PA 16046
US United States of America
Email: br@brianrosen.net Email: br@brianrosen.net
Hannes Tschofenig Hannes Tschofenig
Individual Individual
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
 End of changes. 245 change blocks. 
999 lines changed or deleted 830 lines changed or added

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