draft-ietf-ecrit-car-crash-07.txt   draft-ietf-ecrit-car-crash-08.txt 
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Qualcomm Technologies, Inc Internet-Draft Consultant
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: August 22, 2016 NeuStar, Inc. Expires: January 7, 2017 NeuStar, Inc.
H. Tschofenig H. Tschofenig
(Individual) Individual
February 19, 2016 July 6, 2016
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-07.txt draft-ietf-ecrit-car-crash-08.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
skipping to change at page 1, line 38 skipping to change at page 1, line 38
(often referred to as "crash data" even though there is not (often referred to as "crash data" even though there is not
necessarily a crash). An external specification for the data format, necessarily a crash). An external specification for the data format,
contents, and structure are referenced in this document. contents, and structure are referenced in this 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 within Europe and other regions).
However, this document specifies a different set of vehicle (crash) However, this document specifies a different set of vehicle (crash)
data, specifically, the Vehicle Emergency Data Set (VEDS) rather than data, specifically, the Vehicle Emergency Data Set (VEDS) rather than
the eCall Minimum Set of Data (MSD). This document is an extension the eCall Minimum Set of Data (MSD). This document is an extension
of the eCall document, with the differences being that this document of the eCall document, with the primary differences being that this
makes the MSD data set optional and VEDS mandatory. This document document makes the MSD data set optional and VEDS mandatory, and
also discusses legacy (curcuit-switched) ACN systems and their extends the eCall metadata/control object to permit greater
migration to next-generation emergency calling. functionality. This document also describes legacy (circuit-
switched) ACN systems and their migration to next-generation
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 Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 22, 2016. This Internet-Draft will expire on January 7, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8
4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 9
5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10
6. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.1. Call Routing . . . . . . . . . . . . . . . . . . . . . . 15
8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 15 7. eCall Metadata/Control Extensions . . . . . . . . . . . . . . 16
9. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 16 7.1. New values for the 'action' attribute' . . . . . . . . . 17
10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 7.2. <ack> element extensions . . . . . . . . . . . . . . . . 17
11. Security Considerations . . . . . . . . . . . . . . . . . . . 21 7.3. The <capabilities> element . . . . . . . . . . . . . . . 19
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21 7.4. <request> element extensions . . . . . . . . . . . . . . 21
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 23
13.1. MIME Content-type Registration for 9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 22 10. Security Considerations . . . . . . . . . . . . . . . . . . . 30
13.2. Registration of the 'VEDS' entry in the Emergency Call 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 30
Additional Data registry . . . . . . . . . . . . . . . . 23 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 12.1. MIME Content-type Registration for
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 31
16. Changes from Previous Versions . . . . . . . . . . . . . . . 23
16.1. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 23 12.2. Registration of the 'VEDS' entry in the Emergency Call
16.2. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 24 Additional Data registry . . . . . . . . . . . . . . . . 32
16.3. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 24 12.3. Additions to the eCall Control Extension Registry . . . 32
16.4. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 24 12.4. eCall Action Extensions . . . . . . . . . . . . . . . . 34
16.5. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 24 12.5. eCall Static Message Registry . . . . . . . . . . . . . 34
16.6. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 24 12.6. eCall Reason Registry . . . . . . . . . . . . . . . . . 35
16.7. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 24 12.7. eCall Lamp ID Registry . . . . . . . . . . . . . . . . . 36
16.8. Changes from draft-gellens-01 to -02 . . . . . . . . . . 24 12.8. eCall Camera ID Registry . . . . . . . . . . . . . . . . 37
16.9. Changes from draft-gellens-00 to -01 . . . . . . . . . . 25 13. eCall Control Block Schema . . . . . . . . . . . . . . . . . 38
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 41
17.1. Normative References . . . . . . . . . . . . . . . . . . 25 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41
17.2. Informative references . . . . . . . . . . . . . . . . . 26 16. Changes from Previous Versions . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 16.1. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 41
16.2. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 42
16.3. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 42
16.4. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 42
16.5. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 42
16.6. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 42
16.7. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 42
16.8. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 42
16.9. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 43
16.10. Changes from draft-gellens-01 to -02 . . . . . . . . . . 43
16.11. Changes from draft-gellens-00 to -01 . . . . . . . . . . 43
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
17.1. Normative References . . . . . . . . . . . . . . . . . . 43
17.2. Informative references . . . . . . . . . . . . . . . . . 44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
Additionally, we use the following abbreviations: Additionally, we use the following abbreviations:
+--------+----------------------------------------------------------+ +--------+----------------------------------------------------------+
| Term | Expansion | | Term | Expansion |
+--------+----------------------------------------------------------+ +--------+----------------------------------------------------------+
| 3GPP | 3rd Generation Partnership Project | | 3GPP | 3rd Generation Partnership Project |
| AACN | Advanced Automatic Crash Notification | | AACN | Advanced Automatic Crash Notification |
| ACN | Automatic Crash Notification | | ACN | Automatic Crash Notification |
| APCO | Association of Public-Safety Communications Officials | | APCO | Association of Public-Safety Communications Officials |
| EENA | European Emergency Number Association | | EENA | European Emergency Number Association |
| ESInet | Emergency Services IP network | | ESInet | Emergency Services IP network |
| GNSS | Global Satellite Navigation System (which includes the | | GNSS | Global Navigation Satellite System (which includes |
| | various such systems including the Global Positioning | | | various systems such as the Global Positioning System or |
| | System or GPS) | | | GPS) |
| IVS | In-Vehicle System | | IVS | In-Vehicle System |
| MNO | Mobile Network Operator | | MNO | Mobile Network Operator |
| MSD | eCall Minimum Set of Data |
| NENA | National Emergency Number Association | | NENA | National Emergency Number Association |
| POTS | Plain Old Telephone Service (normal, circuit-switched |
| | voice calls) |
| PSAP | Public Safety Answering Point |
| TSP | Telematics Service Provider | | TSP | Telematics Service Provider |
| VEDS | Vehicle Emergency Data Set | | VEDS | Vehicle Emergency Data Set |
+--------+----------------------------------------------------------+ +--------+----------------------------------------------------------+
2. Introduction 2. Introduction
Emergency calls made by in-vehicle systems (e.g., in the event of a Emergency calls made by in-vehicle systems (e.g., automatically in
crash) assist in significantly reducing road deaths and injuries by the event of a crash or serious incident or manually by a vehicle
allowing emergency services to respond quickly and often with better occupant) assist in significantly reducing road deaths and injuries
location. by allowing emergency services to respond quickly and appropriately
to the specifics of the incident, often with better location
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 a decade, some vehicles have been equipped with For more than two decades, some vehicles have been equipped with
telematics systems that, 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., to positioning technology, inertial sensors, gyroscopes, etc., which can
provide a fairly accurate position for the vehicle. Such built-in provide an accurate position for the vehicle. Such built-in systems
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 reliable power, 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 minimise
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 PSAP can be provided with a good
estimate of where the vehicle is during an emergency. Vehicle estimate of where the vehicle is during an emergency. Vehicle
manufacturers are increasingly adopting such systems, both for the manufacturers are increasingly adopting such systems, both for the
safety benefits and for the additional features and services they safety benefits and for the additional features and services they
enable (e.g., remote engine diagnostics, remote door unlock, stolen enable (e.g., remote engine diagnostics, remote door unlock, stolen
vehicle tracking and disabling, etc.). vehicle tracking and disabling, etc.).
The general term for such systems is Automatic Crash Notification The general term for such systems is Automatic Crash Notification
skipping to change at page 4, line 41 skipping to change at page 5, line 24
amount of data specific to the incident, referred to generally as amount of data specific to the incident, referred to generally as
"crash data" (the term is commonly used even though there might not "crash data" (the term is commonly used even though there might not
have been a crash). While different systems transmit different have been a crash). While different systems transmit different
amounts of crash data, standardized formats, structures, and amounts of crash data, standardized formats, structures, and
mechanisms are needed to provide interoperability among systems and mechanisms are needed to provide interoperability among systems and
PSAPs. 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 call taker or an automated system to provide the on either a human advisor or an automated text-to-speech system to
PSAP call taker with some crash data orally, or possibly a provide the PSAP call taker with some crash data orally, or in some
proprietary mechanism). The PSAP call taker needs to first realize cases via a proprietary mechanism). In most cases, the PSAP call
that the call is related to a vehicle incident, and in most cases taker needs to first realize that the call is related to a vehicle
must then listen to the data and transcribe it. incident, and then listen to the data and transcribe it. Circuit-
switched ACN systems are referred to here as CS-ACN.
The transition to next-generation calling in general, and emergency The transition to next-generation calling in general, and emergency
calling in particular, provides an opportunity to vastly improve the calling in particular, provides an opportunity to vastly improve the
scope, breadth, reliability and usefulness of crash data during an scope, breadth, reliability and usefulness of crash data during an
emergency by allowing it to be presented alongside the call, and to emergency by allowing it to be transmitted during call set-up, and to
be automatically processed by the PSAP and made available to the call be automatically processed by the PSAP and made available to the call
taker in an integrated, automated way. In addition, vehicle taker in an integrated, automated way, as well as provide the ability
for a PSAP call taker to request that a vehicle take certain actions,
such as flashing lights or unlocking doors. In addition, vehicle
manufacturers are provided an opportunity to take advantage of the manufacturers are provided an opportunity to take advantage of the
same standardized mechanisms for data transmission for internal use same standardized mechanisms for data transmission and request
if they wish (such as telemetry between the vehicle and a service processing for internal use if they wish (such as telemetry between
center for both emergency and non-emergency uses, including location- the vehicle and a service center for both emergency and non-emergency
based services, multi-media entertainment systems, and road-side uses, including location-based services, multi-media entertainment
assistance applications). systems, remote door unlocking, and road-side 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 optionally recognized and processed as such during call set-up, and routed to an
routed to an upgraded PSAP where the vehicle data is available to equipped PSAP where the vehicle data is available to assist the call
assist the call taker in assessing and responding to the situation. taker in assessing and responding to the situation. Next-generation
(IP-based) ACN systems are referred to here as NG-ACN.
An ACN call can be either occupant-initiated or automatically An ACN call can initiated by a vehicle occupant or automatically
triggered. (The "A" in "ACN" does stand for "Automatic," but the initiated by vehicle systems in the event of a serious incident.
term is often used to refer to the class of calls that are placed by (The "A" in "ACN" does stand for "Automatic," but the term is broadly
an in-vehicle system (IVS) and that carry incident-related data as used to refer to the class of calls that are placed by an in-vehicle
well as voice.) Automatically triggered calls indicate a car crash system (IVS) or Telematics Service Providers (TSP) and that carry
or some other serious incident (e.g., a fire) and carry a greater incident-related data as well as voice.) Automatically triggered
presumption of risk of injury. Manually triggered calls are often calls indicate a car crash or some other serious incident (e.g., a
reports of serious hazards (such as impaired drivers or roadway fire). Manually triggered calls are often reports of observed
debris) and might require different responses depending on the crashes or serious hazards (such as impaired drivers or roadway
situation. Manually triggered calls are also more likely to be false debris). Depending on the design, manually triggered calls might be
(e.g., accidental) calls and so might be subject to different more likely to be accidental.
operational handling by the PSAP.
This document describes how the IETF mechanisms for IP-based This document describes how the IETF mechanisms for IP-based
emergency calls, including [RFC6443] and emergency calls, including [RFC6443] and
[I-D.ietf-ecrit-additional-data], are used to provide the realization [I-D.ietf-ecrit-additional-data], are used to provide the realization
of next-generation ACN. of next-generation ACN.
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), as calls by in-vehicle systems within Europe and other regions), as
described in [I-D.ietf-ecrit-ecall]. However, this document described in [I-D.ietf-ecrit-ecall]. However, this document
specifies a different set of vehicle (crash) data, specifically, the specifies a different set of vehicle (crash) data, specifically, the
Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set
of Data (MSD). This document is an extension of of Data (MSD). This document is an extension of
[I-D.ietf-ecrit-ecall], with the differences being that this document [I-D.ietf-ecrit-ecall], with the differences being that this document
makes the MSD data set optional and VEDS mandatory. makes the MSD data set optional and VEDS mandatory, and adds
extension elements, attributes, and values to the eCall metadata/
control object defined in that document.
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.
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, and interpreted by PSAPs, allows the data to be generated by an IVS or TSP and interpreted by
emergency responders, and medical facilities (including those capable PSAPs, emergency responders, and medical facilities. It includes
of providing trauma level patient care). It includes incident- incident-related information such as airbag deployment, location and
related information such as airbag deployment, location of the compass orientation of the vehicle, spatial orientation of the
vehicle, if the vehicle was involved in a rollover, various sensor vehicle (e.g., upright, on its side or top or a bumper), various
data that can indicate the potential severity of the crash and the sensor data that can indicate the potential severity of the crash and
likelihood of severe injuries to the vehicle occupants, etc. This the likelihood of severe injuries to the vehicle occupants, etc.
data better informs the PSAP and emergency responders as to the type This data better informs the PSAP and emergency responders as to the
of response that might be needed. This information was recently type of response that might be needed. Some of this information has
included in the federal guidelines for field triage of injured been included in U.S. government guidelines for field triage of
patients. These guidelines are designed to help responders at the injured patients [triage-2008] [triage-2011]. These guidelines are
accident scene identify the potential existence of severe internal designed to help responders identify the potential existence of
injuries and to make critical decisions about how and where a patient severe internal injuries and to make critical decisions about how and
needs to be transported. where a patient needs to be transported.
This document registers the 'application/EmergencyCallData.VEDS+xml' This document registers the 'application/EmergencyCallData.VEDS+xml'
MIME content-type, and registers the 'VEDS' entry in the Emergency MIME content-type, and registers the 'VEDS' entry in the Emergency
Call Additional Data registry. Call Additional Data registry.
VEDS is an XML structure (see [VEDS]). The 'application/ VEDS is an XML structure (see [VEDS]) transported in SIP using the
EmergencyCallData.VEDS+xml' MIME content-type is used to identify it. 'application/EmergencyCallData.VEDS+xml' MIME content-type. The
The 'VEDS' entry in the Emergency Call Additional Data registry is 'VEDS' entry in the Emergency Call Additional Data registry is used
used to construct a 'purpose' parameter value for conveying VEDS data to construct a 'purpose' parameter value to indicate VEDS data in a
in a Call-Info header (as described in Call-Info header (as described in [I-D.ietf-ecrit-additional-data]).
[I-D.ietf-ecrit-additional-data]).
VEDS is a versatile structure that can accomodate varied needs. VEDS is a versatile structure that can accomodate varied needs.
However, if additional sets of data are determined to be needed However, if additional sets of data are determined to be needed
(e.g., in the future or in different regions), the steps to enable (e.g., in the future or in different regions), the steps to enable
each data block are very briefly summarized below: each data block are very briefly summarized below:
o A standardized format and encoding (such as XML) is defined and o A standardized format and encoding (such as XML) is defined and
published by a Standards Development Organization (SDO) published by a Standards Development Organization (SDO)
o A MIME Content-Type is registered for it (typically under the o A MIME Content-Type is registered for it (typically under the
'Application' media type) with a sub-type starting with 'Application' media type) with a sub-type starting with
'EmergencyCallData.' 'EmergencyCallData.'
o An entry for the block is added to the Emergency Call Additional o An entry for the block is added to the Emergency Call Additional
Data Blocks sub-registry (established by Data Blocks sub-registry (established by
[I-D.ietf-ecrit-additional-data]); the registry entry is the root [I-D.ietf-ecrit-additional-data]); the registry entry is the root
of the MIME sub-type (not including the 'EmergencyCallData' prefix of the MIME sub-type (not including the 'EmergencyCallData' prefix
and any suffix such as '+xml') and any suffix such as '+xml')
A next-generation In-Vehicle System (IVS) transmits crash data by A next-generation In-Vehicle System (IVS) or TSP transmits crash data
encoding it in a standardized and registered format (such as VEDS) by encoding it in a standardized and registered format (such as VEDS)
and attaching it to an INVITE as a MIME body part. The body part is and attaching it to a SIP message as a MIME body part. The body part
identified by its MIME content-type (such as 'application/ is identified by its MIME content-type (such as '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 which is
listed in a Content-ID header field in the body part. The INVITE is listed in a Content-ID header field in the body part. The SIP
marked as containing the crash data by adding a Call-Info header message is marked as containing the crash data by adding a Call-Info
field at the top level of the INVITE. This Call-Info header field header field at the top level of the message. This Call-Info header
contains a CID URL referencing the body part's unique identifier, and field contains a CID URL referencing the body part's unique
a 'purpose' parameter identifying the data as the crash data per the identifier, and a 'purpose' parameter identifying the data as the
registry entry; the 'purpose' parameter's value is crash data per the registry entry. The 'purpose' parameter's value
'EmergencyCallData.' and the root of the MIME type (the is 'EmergencyCallData.' plus the value associated with the data type
'EmergencyCallData' prefix is not repeated), omitting any suffix such in the registry; for VEDS data, "purpose=EmergencyCallData.VEDS".
as '+xml' (e.g., 'purpose=EmergencyCallData.VEDS').
These mechanisms are thus used to place emergency calls that are These mechanisms are thus used to place emergency calls that are
identifiable as ACN calls and that carry one or more standardized identifiable as ACN calls and that carry one or more standardized
crash data objects in an interoperable way. crash data objects in an interoperable way.
Calls by in-vehicle systems are placed via cellular networks, which
might ignore location sent by an originating device in an emergency
call INVITE, instead attaching their own location (often determined
in cooperation with the originating device). Standardized crash data
structures often include location as determined by the IVS. A
benefit of this is that it allows the PSAP to see both the location
as determined by the cellular network (often in cooperation with the
originating device) and the location as determined by the IVS.
This specification inherits the ability to utilize test call
functionality from Section 15 of [RFC6881].
3. Document Scope 3. Document Scope
This document is focused on the interface to the PSAP, that is, how This document is focused on how an ACN emergency call is setup and
an ACN emergency call is setup and incident-related data (including incident-related data (including vehicle, sensor, and location data)
vehicle, sensor, and location data) is transmitted to the PSAP using is transmitted to the PSAP using IETF specifications. For the direct
IETF specifications. (The goal is to re-use specifications rather model, this is the end-to-end description (between the vehicle and
than to invent new.) For the direct model, this is the end-to-end the PSAP). For the TSP model, this describes the call leg between
description (between the vehicle and the PSAP). For the TSP model, the TSP and the PSAP, leaving the call leg between the vehicle and
this describes the right-hand side (between the TSP and the PSAP), the TSP up to the entities involved (i.e., IVS and TSP vendors) who
leaving the left-hand side (between the vehicle and the TSP) up to are then free to use the same mechanism as for the right-hand side or
the entities involved (i.e., IVS and TSP vendors) who are then free not.
to use the same mechanism as for the right-hand side (or not).
Note that while ACN systems in the U.S. and other regions are not Note that Europe has a mandated and standardized system for emergency
currently (as of the date of this document) mandated, Europe has a calls by in-vehicle systems. This pan-European system is known as
mandated and standardized system for emergency calls by in-vehicle "eCall" and is the subject of a separate document,
systems. This pan-European system is known as "eCall" and is the [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles
subject of a separate document, [I-D.ietf-ecrit-ecall], which this designed to operate in multiple regions might need to support eCall
document build on. Vehicles designed to operate in multiple regions as well as the ACN described here. In this case, a vehicle IVS might
might need to support eCall as well as the ACN described here. If determine whether to use eCall or ACN by first determining a region
other regions devise their own specifications or data formats, a or country in which it is located (e.g., from a GNSS location fix
multi-region vehicle might need to support those as well. This and/or identity of or information from an MNO). If other regions
document adopts the call set-up and other technical aspects of adopt other data formats, a multi-region vehicle might need to
[I-D.ietf-ecrit-ecall], which uses [I-D.ietf-ecrit-additional-data], support those as well. This document adopts the call set-up and
which makes it easy to substitute a different data set while keeping other technical aspects of [I-D.ietf-ecrit-ecall], which uses
other technical aspects unchanged. Hence, both NG-eCall and the NG- [I-D.ietf-ecrit-additional-data]; this makes it straightforward to
ACN mechanism described here are fully compatible, differing only in use a different data set while keeping other technical aspects
the specific data block that is sent (the eCall MSD in the case of unchanged. Hence, both NG-eCall and the NG-ACN mechanism described
NG-eCall, and the APCO/NENA VEDS used in this document). If other here are compatible, differing primarily in the specific data block
regions adopt their own data set, this can be similarly accomodated that is sent (the eCall MSD in the case of NG-eCall, and the APCO/
without changing other technical aspects. NENA VEDS used in this document), and some additions to the metadata/
control data block. If other regions adopt their own vehicle data
sets, this can be similarly accomodated without changing other
technical aspects.
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 in-
vehicle systems, including automatic crash notification systems, vehicle systems generally have some ability to convey at least
generally have some ability to convey at least location and in some location and in some cases telematics data to the PSAP. Most such
cases telematics data to the PSAP. Most such systems use one of systems use one of three architectural models, which are described
three architectural models, which are described here as: "Telematics here as: "Telematics Service Provider" (TSP), "direct", and "paired".
Service Provider" (TSP), "direct", and "paired". These three models These three models are illustrated below.
are illustrated below.
In the TSP model, both emergency and non-emergency calls are placed In the TSP model, both emergency and non-emergency calls are placed
to a Telematics Service Provider (TSP); a proprietary technique is to a Telematics Service Provider (TSP); a proprietary technique is
used for data transfer (such as proprietary in-band modems) to the used for data transfer (such as a proprietary in-band modem) between
TSP. the TSP and the vehicle.
In an emergency, the TSP call taker bridges in the PSAP and In an emergency, generally the TSP call taker bridges in the PSAP and
communicates location, crash data (such as impact severity and trauma communicates location, crash data (such as impact severity and trauma
prediction), and other data (such as the vehicle description) to the prediction), and other data (such as the vehicle description) to the
PSAP call taker verbally. Since the TSP knows the location of the PSAP call taker verbally (in some cases, a proprietary out-of-band
vehicle (from on-board GNSS), location-based routing is usually used interface is used). Since the TSP knows the location of the vehicle
to route to the appropriate PSAP. In some cases, the TSP is able to (from on-board GNSS and sensors), location-based routing is usually
transmit location automatically, using similar techniques as for used to route to the appropriate PSAP. In some cases, the TSP is
wireless calls. Typically, a three-way voice call is established able to transmit location automatically, using similar techniques as
for wireless calls. Typically, a three-way voice call is established
between the vehicle, the TSP, and the PSAP, allowing communication between the vehicle, the TSP, and the PSAP, allowing communication
between the PSAP call taker, the TSP call taker, and the vehicle between the PSAP call taker, the TSP call taker, and the vehicle
occupants (who might be unconscious). occupants (who might be unconscious).
///----\\\ proprietary +------+ 911 trunk +------+ ///----\\\ proprietary +------+ 911 trunk or POTS +------+
||| IVS |||-------------->+ TSP +------------------>+ PSAP | ||| IVS |||-------------->+ TSP +------------------->+ PSAP |
\\\----/// crash data +------+ +------+ \\\----/// crash data +------+ location via trunk +------+
Figure 1: Legacy TSP Model. Figure 1: Legacy TSP Model.
In the paired model, the IVS uses a Bluetooth link with a previously- In the paired model, the IVS uses a Bluetooth link with a previously-
paired handset to establish an emergency call with the PSAP (by paired handset to establish an emergency call with the PSAP (by
dialing a standard emergency number such as 9-1-1), and then dialing a standard emergency number; 9-1-1 in North America), and
communicates location data to the PSAP via text-to-speech; crash data then communicates location data to the PSAP via text-to-speech; crash
might or might not be conveyed also using text-to-speech in an data might or might not be conveyed also using text-to-speech. Some
initial voice greeting. Some such systems use an automated voice such systems use an automated voice prompt menu for the PSAP call
prompt menu for the PSAP call taker (e.g., "this is an automatic taker (e.g., "this is an automatic emergency call from a vehicle;
emergency call from a vehicle; press 1 to open a voice path to the press 1 to open a voice path to the vehicle; press 2 to hear the
vehicle; press 2 to hear the location read out") to allow the call location read out") to allow the call taker to request location data
taker to request location data via text-to-speech. via text-to-speech.
+---+ +---+
///----\\\ | H | 911/etc voice call via handset +------+ ///----\\\ | H | 911/etc voice call via handset +------+
||| IVS |||-->| S +----------------------------------->+ PSAP | ||| IVS |||-->| S +----------------------------------->+ PSAP |
\\\----/// +---+ location via text-to-speech +------+ \\\----/// +---+ location via text-to-speech +------+
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 such as 9-1-1. Such the PSAP by dialing a standard emergency number (9-1-1 in North
systems might communicate location data to the PSAP via text-to- America). Such systems might communicate location data to the PSAP
speech; crash data might or might not be conveyed using text-to- via text-to-speech; crash data might or might not be conveyed using
speech in an initial voice greeting. Some such systems use an text-to-speech. Some such systems use an automated voice prompt menu
automated voice prompt menu (e.g., "this is an automatic emergency (e.g., "this is an automatic emergency call from a vehicle; press 1
call from a vehicle; press 1 to open a voice path to the vehicle; to open a voice path to the vehicle; press 2 to hear the location
press 2 to hear the location read out") to allow the call taker to read out") to allow the call taker to request location data via text-
request location data via text-to-speech. 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- Migration of emergency calls placed by in-vehicle systems to next-
generation (all-IP) technology provides a standardized mechanism to generation (all-IP) technology per this document provides a
identify such calls and to present crash data with the call, as well standardized mechanism to identify such calls and to present crash
as enabling additional communications modalities and enhanced data with the call, as well as enabling additional communications
functionality. This allows ACN calls and crash data to be modalities and enhanced functionality. This allows ACN calls and
automatically processed by the PSAP and made available to the call crash data to be automatically processed by the PSAP and made
taker in an integrated, automated way. Because the crash data is available to the call taker in an integrated, automated way. Because
carried in the initial SIP INVITE (per the crash data is carried in the initial SIP INVITE (per
[I-D.ietf-ecrit-additional-data]) the PSAP can present it to the call [I-D.ietf-ecrit-additional-data]) the PSAP can present it to the call
taker simultaneously with the appearance of the call. taker simultaneously 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 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, since the IVS will receive confirmation that
the information has been successfully received; a PSAP could also
choose to include a message 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 available).
Origination networks, PSAPs, emergency services networks, and other Origination devices and networks, PSAPs, emergency services networks,
telephony environments are all migrating to next-generation. This and other telephony environments are migrating to next-generation.
provides opportunities for significant enhancement to
interoperability, especially for emergency calls carrying additional
data such as vehicle crash data. Note that in the U.S., a network
specifically for emergency responders is being developed. This
network, FirstNet, will be next-generation from the start, enhancing
the ability for data exchange between PSAPs and responders.
Migration to next-generation (NG) thus provides an opportunity to This provides opportunities for significant enhancement to
interoperability and functionality, especially for emergency calls
carrying additional data such as vehicle crash data. (In the U.S., a
network specifically for emergency responders is being developed.
This network, FirstNet, will be next-generation from the start,
enhancing the ability for data exchange between PSAPs and
responders.)
Migration to next-generation (NG) provides an opportunity to
significantly improve the handling and response to vehicle-initiated significantly improve the handling and response to vehicle-initiated
emergency calls. Such calls can be recognized as originating from a emergency calls. Such calls can be recognized as originating from a
vehicle, routed to a PSAP equipped both technically and operationally vehicle, routed to a PSAP equipped both technically and operationally
to handle such calls, and the vehicle-determined location and crash to handle such calls, and the vehicle-determined location and crash
data can be made available to the call taker simultaneously with the data can be made available to the call taker simultaneously with the
call appearance. call appearance. The PSAP can take advantage of enhanced
functionality, including the ability to request the vehicle to take
an action, such as sending an updated set of data, converying 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 between the advantage of the same mechanism to carry telematics data and requests
vehicle and the TSP for both emergency and non-emergency calls as are and responses between the vehicle and the TSP for both emergency and
used to convey this data to the PSAP. non-emergency calls as are used for the interface with the PSAP.
A next-generation IVS establishes an emergency call using the A next-generation IVS establishes an emergency call using the
emergency call solution as described in [RFC6443] and [RFC6881], with emergency call solution as described in [RFC6443] and [RFC6881], with
the difference that the Request-URI indicates an ACN type of the difference that the Request-URI indicates an ACN type of
emergency call and a Call-Info header field indicates that vehicle emergency call, the IVS typically does not perform routing or
crash data is attached. When an ESInet is deployed, the MNO only location queries but relies on the carrier for this, and uses Call-
needs to recognize the call as an emergency call and route it to an Info header fields to indicates that vehicle crash and capabilities
ESInet. The ESInet can recognize the call as an ACN with vehicle data is attached. When an ESInet is deployed, the MNO only needs to
data and can route the call to an NG-ACN capable PSAP. Such a PSAP recognize the call as an emergency call and route it to an ESInet.
can interpret the vehicle data sent with the call and make it The ESInet can recognize the call as an ACN with vehicle data and can
available to the call taker. route the call to an NG-ACN capable PSAP. Such a PSAP can interpret
the vehicle data sent with the call and make it available to the call
Because of the need to identify and specially process Next-Generation taker.
ACN calls (as discussed above), [I-D.ietf-ecrit-ecall] registers new
service URN children within the "sos" subservice. These URNs provide
a mechanism by which an NG-ACN call is identified, 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.)
[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 (all-
IP) is described below. 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 using either a protocol that is based on a proprietary design or TSP either by re-using the mechanisms and data objects described
one that re-uses the mechanisms and data objects described here. In here, or using a proprietary mechanism. In an emergency, the TSP
an emergency, the TSP call taker bridges in the PSAP and the TSP bridges in the PSAP and the TSP transmits crash and other data to the
transmits crash and other data to the PSAP using the mechanisms and PSAP using the mechanisms and data objects described here. There is
data objects described here. There is a three-way call between the a three-way call between the vehicle, the TSP, and the PSAP, allowing
vehicle, the TSP, and the PSAP, allowing communication between the communication between the PSAP call taker, the TSP call taker, and
PSAP call taker, the TSP call taker, and the vehicle occupants (who the vehicle occupants (who might be unconscious). The TSP relays
might be unconscious). 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 to transmit crash and location data from mechanisms and data objects on the left call leg in Figure 4 as on
the vehicle to the TSP as are described here to transmit such data the right. (Note that the TSP model can be more difficult when the
from to the PSAP. vehicle is in a different country than the TSP (e.g., a US resident
driving in Canada or Mexico) because of the additional complexity in
choosing the correct PSAP based on vehicle location performed by a
TSP in a 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 here. directly using the mechanisms and data objects described here.
///----\\\ 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
skipping to change at page 11, line 49 skipping to change at page 13, line 19
+---+ +---+
///----\\\ (undefined) | H | standard +------+ ///----\\\ (undefined) | H | standard +------+
||| IVS |||------------------>| S +------------------->+ 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 If the call is routed to a PSAP that is not capable of processing the
vehicle data, the PSAP ignores (or does not receive) the vehicle vehicle data, the PSAP ignores (or does not receive) the vehicle
data. This is detectable by the IVS or TSP when it receives a 200 OK data. This is detectable by the IVS or TSP when the status response
to the INVITE which lacks an eCall control structure acknowledging to the INVITE (e.., 200 OK) lacks an eCall control structure
receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or TSP then acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or
proceeds as it would for a non-NG ACN call (e.g., verbal conveyance TSP then proceeds as it would for a CS-ACN call (e.g., verbal
of data) conveyance of data)
6. Profile
In the context of emergncy calls placed by an in-vehicle system it is
assumed that the car is equipped with a built-in GNSS receiver. For
this reason only geodetic location information will be sent within an
emergency call. The following location shapes MUST be implemented:
2d and 3d Point (see Section 5.2.1 of [RFC5491]), Circle (see
Section 5.2.3 of [RFC5491]), and Ellipsoid (see Section 5.2.7 of
[RFC5491]). The coordinate reference systems (CRS) specified in
[RFC5491] are also mandatory for this document. The <direction>
element, as defined in [RFC5962] which indicates the direction of
travel of the vehicle, is important for dispatch and hence it MUST be
included in the PIDF-LO [RFC4119]. The <heading> element specified
in [RFC5962] MUST be implemented and MAY be included.
Calls by in-vehicle systems are placed via cellular networks, which
might ignore location sent by an originating device in an emergency
call INVITE, instead attaching their own location (often determined
in cooperation with the originating device). Standardized crash data
structures often include location as determined by the IVS. A
benefit of this is that it allows the PSAP to see both the location
as determined by the cellular network (often in cooperation with the
originating device) and the location as determined by the IVS.
This specification inherits the ability to utilize test call
functionality from Section 15 of [RFC6881].
7. Call Setup
It is important that ACN calls be easily identifiable as such at all
stages of call handling, and that automatic versus manual triggering
be known. ACN calls differ from general emergency calls in several
aspects, including the presence of standardized crash data, the fact
that the call is known to be placed by an in-vehicle system (which
has implications for PSAP operational processes), and, especially for
automatic calls, information that can indicate a likelihood of severe
injury and hence need for trauma services. Knowledge that a call is
an ACN and further that it was automatically or manually invoked
carries a range of implications about the call, the circumstances,
and the vehicle occupants. Calls by in-vehicle systems can be
considered a specific sub-class of general emergency calls and are
optimally handled by a PSAP with the technical and operational
capabilities to serve such calls. (This is especially so in
environments such as the U.S. where there are many PSAPs and where
individual PSAPs have a range of capabilities.) Technical
capabilities include the ability to recognize and process
standardized crash data. Operational capabilities include training
and processes for assessing severe injury likelihood and responding
appropriately (e.g., dispatching trauma-capable medical responders or
those trained and equipped to extract occupants from crashed vehicles
and handle gasoline or other hazardous materials, transporting
victims to a trauma center, alerting the receiving facility, etc.).
Because ACN calls differ in significant ways from general emergency 6. Call Setup
calls, and because such calls typically generally are best handled by
PSAPs equipped technically to interpet and make use of crash data,
and operationally to handle emergency calls placed by in-vehicle
systems, [I-D.ietf-ecrit-ecall] registers SOS sub-services. Using a
sub-service allows the call to be treated as an amergency call and
makes it readily obvious that the call is an ACN; a further child
element distinguishes calls automatically placed due to a crash or
other serious incident (such as a fire) from those manually invoked
by a vehicle occupant (specifically, "SOS.ecall.automatic" and
"SOS.ecall.manual"). The distinction between automatic and manual
invocation is also significant; automatically triggered calls
indicate a car crash or some other serious incident (e.g., a fire)
and carry a greater presumption of risk of injury and hence need for
specific responders (such as trauma or fire). Manually triggered
calls are often reports of serious hazards (such as impaired drivers
or roadway debris) and might require different responses depending on
the situation. Manually triggered calls also have a greater chance
of being false (e.g., accidental) calls and might thus be subject to
different handling by the PSAP.
A next-generation In-Vehicle System (IVS) transmits crash data by A next-generation In-Vehicle System (IVS) initiates an NG-ACN call
encoding it in a standardized and registered format and attaching it with a SIP INVITE using one of the SOS sub-services
to an INVITE as an additional data block as specified in Section 4.1 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI,
of [I-D.ietf-ecrit-additional-data]. As described in that document, standard sets of crash data and capabilities data encoded in
the block is identified by its MIME content-type, and pointed to by a standardized and registered formats, attached as additional data
CID URL in a Call-Info header with a 'purpose' parameter value blocks as specified in Section 4.1 of
corresponding to the block. [I-D.ietf-ecrit-additional-data]. As described in that document,
each data block is identified by its MIME content-type, and pointed
to by a CID URL in a Call-Info header with a 'purpose' parameter
value corresponding to the data block.
Specifically, the steps required during standardization are: Should new data blocks be needed (e.g., in other regions or in the
future), the steps required during standardization are:
o A set of crash data is standardized by an SDO or appropriate o A set of data is standardized by an SDO or appropriate
organization organization
o A MIME Content-Type for the crash data set is registered with IANA o A MIME Content-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 type is normally under the 'application' type with a MIME 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 Additional Data o The item is registered in the Emergency Call Additional Data
registry, as defined in Section 9.1.7 of registry, as defined in Section 9.1.7 of
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
* For emergency-call-specific formats, the registered name is the * For emergency-call-specific formats, the registered name is the
root of the MIME Content-Type (not including the root of the MIME Content-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 [I-D.ietf-ecrit-additional-data] described in Section 4.1 of [I-D.ietf-ecrit-additional-data].
When placing an emergency call: When placing an emergency call:
o The crash data set is created and encoded per its specification o The crash data set is created and encoded per its specification
o The crash data set is attached to the emergency call INVITE as o IVS capability data is encoded per the specification in
specified in Section 4.1 of [I-D.ietf-ecrit-additional-data], that [I-D.ietf-ecrit-ecall] as extended in this document
is, as a MIME body part identified by its MIME Content-Type in the
body part's Content-Type header field
o The body part is assigned a unique identifier label in a Content- o The crash data set and capabilities data are attached to the
ID header field of the body part emergency call INVITE as specified in Section 4.1 of
[I-D.ietf-ecrit-additional-data], that is, as MIME body parts
identified by the MIME Content-Type in the body part's Content-
Type header field
o A Call-Info header field at the top level of the INVITE is added o Each body part is assigned a unique identifier label in the
that references the crash data and identifies it by its MIME root Content-ID header field of the body part
(as registered in the Emergency Call Additional Data registry)
* The crash data is referenced in the Call-Info header field by a o Call-Info header fields at the top level of the INVITE are added
CID URL that contains the unique Content ID assigned to the that reference the crash data and capabilities data and identify
crash data body part each by its MIME root (as registered in the Emergency Call
Additional Data registry)
* The crash data is identified in the Call-Info header field by a * The crash and capabilities data are referenced in Call-Info
'purpose' parameter whose value is 'EmergencyCallData.' header fields by CID URLs that contain the unique Content ID
concatenated with the specific crash data entry in the assigned to the body part
Emergency Call Additional Data registry
* The Call-Info header field MAY be either solely to reference * The crash and capabilities data are identified in the Call-Info
the crash data (and hence have only the one URL) or can also header fields by a 'purpose' parameter whose value is
'EmergencyCallData.' concatenated with the specific data
block's entry in the Emergency Call Additional Data registry
* A Call-Info header field can be either solely to reference one
item of data (and hence have only the one URL) or can also
contain other URLs referencing other data contain other URLs referencing other data
o Additional crash data sets MAY be included by following the same o Any additional data sets are included by following the same steps
steps
The Vehicle Emergency Data Set (VEDS) is an XML structure defined by The Vehicle Emergency Data Set (VEDS) is an XML structure defined by
the Association of Public-Safety Communications Officials (APCO) and the Association of Public-Safety Communications Officials (APCO) and
the National Emergency Number Association (NENA) [VEDS]. The the National Emergency Number Association (NENA) [VEDS]. The
'application/EmergencyCallData.VEDS+xml' MIME content-type is used to 'application/EmergencyCallData.VEDS+xml' MIME content-type is used to
identify it. The 'VEDS' entry in the Emergency Call Additional Data identify it. The 'VEDS' entry in the Emergency Call Additional Data
registry is used to construct a 'purpose' parameter value for registry is used to construct a 'purpose' parameter value for
conveying VEDS data in a Call-Info header. conveying VEDS data in a Call-Info header.
The VEDS data is attached as a body part with MIME content type The VEDS data is attached as a body part with MIME content type
'application/EmergencyCallData.VEDS+xml' which is pointed at by a 'application/EmergencyCallData.VEDS+xml' which is pointed at by a
Call-Info URL of type CID with a 'purpose' parameter of Call-Info URL of type CID with a 'purpose' parameter of
'EmergencyCallData.VEDS'. 'EmergencyCallData.VEDS'.
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 data as well as any other PSAP is able to identify the crash data as well as any other
additional data attached to the INVITE by examining the Call-Info additional data attached to the INVITE by examining the Call-Info
header fields for 'purpose' parameters whose values start with header fields for 'purpose' parameters whose values start with
'EmergencyCallData.' The PSAP is able to access and the data it is 'EmergencyCallData.' The PSAP is able to access the data it is
capable of handling and is interested in by checking the 'purpose' capable of handling and is interested in by checking the 'purpose'
parameter values. parameter values.
This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- This document extends [I-D.ietf-ecrit-ecall] by reusing the call set-
up and other normative requirements except that in this document, up and other normative requirements with the exception that in this
support for the eCall MSD is OPTIONAL and support for VEDS in document, support for the eCall MSD is OPTIONAL and support for VEDS
REQUIRED. in REQUIRED. This document also extends the metadata/control object
defined in [I-D.ietf-ecrit-ecall] by adding new elements, attributes,
and values.
8. Call Routing 6.1. Call Routing
An Emergency Services IP Network (ESInet) is a network operated by or An Emergency Services IP Network (ESInet) is a network operated by or
on behalf of emergency services authorities. It handles emergency on behalf of emergency services authorities. It handles emergency
call routing and processing before delivery to a PSAP. In the call routing and processing before delivery to a PSAP. In the
NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2
architecture adopted by EENA, each PSAP is connected to one or more architecture adopted by EENA, each PSAP is connected to one or more
ESInets. Each originating network is also connected to one or more ESInets. Each originating network is also connected to one or more
ESInets. The ESInets maintain policy-based routing rules which ESInets. The ESInets maintain policy-based routing rules which
control the routing and processing of emergency calls. The control the routing and processing of emergency calls. The
centralization of such rules within ESInets provides for a cleaner centralization of such rules within ESInets provides for a cleaner
separation between the responsibilities of the originating network separation between the responsibilities of the originating network
and that of the emergency services network, and provides greater and that of the emergency services network, and provides greater
flexibility and control over processing of emergency calls by the flexibility and control over processing of emergency calls by the
emergency services authorities. This makes it easier to react emergency services authorities and PSAPs. This makes it easier to
quickly to unusual situations that require changes in how emergency react quickly to unusual situations that require changes in how
calls are routed or handled (e.g., a natural disaster closes a PSAP), emergency calls are routed or handled (e.g., a natural disaster
as well as ease in making long-term changes that affect such routing closes a PSAP), as well as ease in making long-term changes that
(e.g., cooperative agreements to specially handle calls requiring affect such routing (e.g., cooperative agreements to specially handle
translation or relay services). calls requiring translation or relay services).
In an environment that uses ESInets, the originating network need In an environment that uses ESInets, the originating network need
only detect that the service URN of an emergency call is or starts only detect that the service URN of an emergency call is or starts
with "sos", passing all types of emergency calls to an ESInet. The with "sos", passing all types of emergency calls to an ESInet. The
ESInet is then responsible for routing such calls to an appropriate ESInet is then responsible for routing such calls to an appropriate
PSAP. In an environment without an ESInet, the emergency services PSAP. In an environment without an ESInet, the emergency services
authorities and the originating carriers would need to determine how authorities and the originating carriers determine how such calls are
such calls are routed. routed.
9. Test Calls 7. eCall Metadata/Control Extensions
This document extends the eCall metadata/control structure defined in
[I-D.ietf-ecrit-ecall] by adding new elements, attributes, and
values.
The <ack> element is permitted in a control block sent by the IVS
to the PSAP, to acknowledge receipt of a request by the PSAP and
indicate if the request was carried out, when that request would
not otherwise be acknowledged (if the PSAP requests the vehicle to
send data and the vehicle does so, the data serves as a success
acknowledgement).
A new <capabilities> element is added; used in a control block
sent from the IVS to the PSAP (e.g., in the initial INVITE) to
inform the PSAP of the vehicle capabilities. Child elements
contain all actions and data types supported by the vehicle and
all available lamps (lights) and cameras.
New request values are added to the <request> element to enable
the PSAP to request the vehicle to perform actions.
Mandatory Actions (the IVS and the PSAP MUST support):
o Transmit data object (VEDS MUST be supported; MSD MAY be
supported)
Optional Actions (the IVS and the PSAP MAY support):
o Play and/or display static (pre-defined) message
o Speak/display dynamic text (text supplied in action)
o Flash or turn on or off a lamp (light)
o Honk horn
o Enable a camera
The <ack> element indicates the object being acknowledged (i.e., a
data object or a <request> element), and reports success or failure.
The <capabilities> element has child <request> elements to indicate
the actions supported by the IVS.
The <request> element contains attributes to indicate the request and
to supply any needed information, and MAY contain a <text> child
element to contain the text for a dynamic message. The 'action'
attribute is mandatory and indicates the specific action.
[I-D.ietf-ecrit-ecall] established an IANA registry to contain the
allowed values; this document adds new values to that registry in
Table 3.
7.1. New values for the 'action' attribute'
The following new "action" values are defined:
'msg-static' displays or plays a predefined message (translated as
appropriate for the language of the vehicle's interface). A registry
is created in Section 12.5 for messages and their IDs. Vehicles
include the highest registered message in their <capabilities>
element to indicate support for all messages up to and including the
indicated value.
'msg-dynamic' displays or speaks (via text-to-speech) a dynamic
message included in the request.
'honk' sounds the horn.
'lamp' turns a lamp (light) on, off, or flashes.
'enable-camera' adds a one-way media stream (established via SIP re-
INVITE sent by the vehicle) to enable the PSAP call taker to view a
feed from a camera.
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
one-way media stream for this purpose.
7.2. <ack> element extensions
The <ack> element is extended to be transmitted by the IVS to the
PSAP to acknowledge receipt of a <request> element that requested the
IVS to perform an action other than transmitting a data object (e.g.,
a request to display a message would be acknowledged, but a request
to transmit a data object would not result in a separate <ack>
element being sent, since the data object itself serves as
acknowledgment.) An <ack> element sent by an IVS references the
unique ID of the request being acknowledged, indicates whether the
request was successfully performed, and if not, optionally includes
an explanation.
The <ack> element has the following new child elements:
7.2.1. New Child Element of the <ack> element
The <ack> element has the following new child element:
Name: actionResult
Usage: Optional
Description: An <actionResult> element indicates the result of an
action (other than a 'send-data' action). When an <ack> element
is in response to a control object with multiple <request>
elements (that are not 'send-data' actions), the <ack> element
contains an <actionResult> element for each.
The <actionResult> element has the following
attributes:
Name: action
Usage: Mandatory
Type: token
Description: Contains the value of the 'action' attribute of the
<request> element
Name: success
Usage: Mandatory
Type: Boolean
Description: Indicates if the action was successfully
accomplished
Name: reason
Usage: Conditional
Type: token
Description: Used when 'success' is "False", this attribute
contains a reason code for a failure. A registry for reason
codes is defined in Section 12.6.
Name: details
Usage: optional
Type: string
Description: Contains further explanation of the circumstances of
a success or failure. The contents are implementation-specific
and human-readable.
Example: <actionResult action="msg-dynamic" success="true"/>
Example: <actionResult action="lamp" success="false" reason="unable"
details="The requested lamp is inoperable"/>
7.2.2. Ack Examples
<?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall:control">
<ack ref="1234567890@atlanta.example.com">
<actionResult action="msg-dynamic" success="true"/>
<actionResult action="lamp" success="false" reason="unable"
details="The requested lamp is inoperable"/>
</ack>
</EmergencyCallData.eCallControl>
Figure 7: Ack Example from IVS to PSAP
7.3. The <capabilities> element
The <capabilities> element is transmitted by the IVS to indicate to
the PSAP its capabilities. No attributes for this element are
currently defined. The following child elements are defined:
7.3.1. Child Elements of the <capabilities> element
The <capabilities> element has the following child elements:
Name: request
Usage: Mandatory
Description: The <capabilities> element contains a <request> child
element per action supported by the vehicle.
Because support for a 'send-data' action is REQUIRED, a <request>
child element with a "send-data" 'action' attribute is also
REQUIRED. The 'supported-datatypes' attribute is REQUIRED in this
<request> element within a <capabilities> element, and MUST
contain at a minimum the 'VEDS' data block value; it SHOULD
contain all data blocks supported by the IVS.
All other actions are OPTIONAL.
If the "msg-static" action is supported, a <request> child element
with a "msg-static" 'action' attribute is sent, with a 'msgid'
attribute set to the highest supported static message supported by
the vehicle. A registry is created in Section 12.5 to map 'msgid'
values to static text messages. By sending the highest supported
static message number in its <capabilities> element, the vehicle
indicates its support for all static messages in the registry up
to and including that value.
If the "lamp" action is supported, a <request> child element with
a "lamp" 'action' is sent, with a 'supported-lamps' attribute set
to all supported lamp IDs.
If the "enable-camera" action is supported, a <request> child
element with an "enable-camera" 'action' is sent, with a
'supported-cameras' attribute set to all supported camera IDs.
Examples:
<request action="send-data" supported-datatypes="VEDS"/>
<request action="send-data" supported-datatypes="VEDS; eCall.MSD"
/>
<request action="msg-dynamic"/>
<request action="msg.static" msgid="17" />
7.3.2. Capabilities Example
<?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall:control">
<capabilities>
<request action="send-data" supported-datatypes="VEDS"/>
<request action="lamp"
supported-lamps="head;interior;fog-front;fog-rear;brake;
position-front;position-rear;turn-left;turn-right;hazard"/>
<request action="msg-static" msgid="3"/>
<request action="msg-dynamic"/>
<request action="honk"/>
<request action="enable-camera" supported-cameras="backup; interior"/>
</capabilities>
</EmergencyCallData.eCallControl>
Figure 8: Capabilities Example
7.4. <request> element extensions
This document extends the <request> element to be permitted one or
more times on its own or as a child elements of a <capabilities>
element. The following new attributes, values, and child elements
are defined for the <request> element:
7.4.1. New Attributes of the <request> element
The <request> element has the following new attributes:
Name: msgid
Usage: Conditional
Type: int
Description: Mandatory with a "msg-static" action. Indicates the
identifier of the static message to be displayed and/or spoken for
the vehicle occupants. This document establishes an IANA registry
for messages and their IDs, in Section 12.5
Example: msgid="3"
Name: persistance
Usage: Optional
Type: duration
Description: Specifies how long to carry on the specified action,
for example, how long to continue honking or flashing. If absent,
the default is for the duration of the ACN call.
Example: persistance="PT1H"
Name: supported-datatypes
Usage: Conditional
Type: string
Description: Used with a 'send-data' action in a <request> element
that is a child of a <capability> element, this attribute lists
all data blocks that the vehicle can transmit, using the same
identifier as in the 'purpose' attribute in a Call-Info header
field to point to the data block. Permitted values are contained
in the 'Emergency Call Data Types' IANA registry established in
[I-D.ietf-ecrit-additional-data]. Multiple values are separated
with a semicolon.
Example: supported-datatypes="VEDS; eCall.MSD"
Name: lamp-action
Usage: Conditional
Type: token
Description: Used with a 'lamp' action, indicates if the lamp is to
be illuminated, turned off, or flashed. Permitted values are
'on', 'off', and 'flash'.
Example: lamp-action="flash"
Name: lamp-ID
Usage: Conditional
Type: token
Description: Used with a 'lamp' action, indicates which lamp the
action affects. Permitted values are contained in the registry of
lamp-ID tokens created in Section 12.7
Example: lamp-ID="hazard"
Name: supported-lamps
Usage: Conditional
Type: string
Description: Used with a 'lamp' action in a <request> element that
is a child of a <capability> element, this attribute lists all
supported lamps, using values in the registry of lamp-ID tokens
created in Section 12.7. Multiple values are separated with a
semicolon.
Example: supported-lamps="head; interior; fog-front; fog-rear;
brake; position-front; position-rear; turn-left; turn-right;
hazard"
Name: camera-ID
Usage: Conditional
Type: token
Description: Used with an 'enable-camera' action, indicates which
camera to enable. Permitted values are contained in the registry
of camera-ID tokens created in Section 12.8. When a vehicle
camera is enabled, the IVS sends a re-INVITE to negotiate a one-
way media stream for the camera.
Example: camera-ID="backup"
Name: supported-cameras
Usage: Conditional
Type: string
Description: Used with an 'enable-camera' action in a <request>
element that is a child of a <capability> element, this attribute
lists all cameras that the vehicle supports (can add as a video
feed in the current dialog), using the same identifiers as are
used in the 'camera-ID' attribute (contained in the camera ID
registry in Section 12.8). Multiple values are separated with a
semicolon.
Example: supported-cameras="backup; interior"
7.4.2. New Child Elements of the <request> element
The <request> element has the following new child elements:
Name: text
Usage: Conditional
Type: string
Description: Used within a <request action="msg-dynamic"> element to
contain the text to be displayed and/or spoken (via text-to-
speech) for the vehicle occupants.
Example: <text>Emergency authorities are aware of your incident and
location. Due to a multi-vehicle incident in your area, no one is
able to speak with you right now. Please remain calm. We will
assist you soon.</text>
7.4.3. Request Example
<?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall:control">
<request action="send-data" datatype="VEDS"/>
<request action="lamp" lamp-id="hazard"
lamp-action="flash" persistance="PT1H"/>
<request action="msg-static" msgid="1"/>
<request action="msg-dynamic">
<text>Remain calm. Help is on the way.</text>
</request>
</EmergencyCallData.eCallControl>
Figure 9: Request Example
8. Test Calls
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
not handled by a call taker. The specific handling of test NG-ACN
calls is not itself standardized; the test call facility is intended
to allow the IVS, user, or TSP to verify that an NG-ACN call can be
successfully established with voice and/or other media communication.
The IVS might also be able to verify that the crash data was
successfully received.
This document builds on [I-D.ietf-ecrit-ecall], which inherits the This document builds on [I-D.ietf-ecrit-ecall], which inherits the
ability to utilize test call functionality from Section 15 of ability to utilize test call functionality from Section 15 of
[RFC6881]. [RFC6881]. A service URN starting with "test." indicates a test
call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall"
for test calls.
A service URN starting with "test." indicates a request for an MNOs, emergency authorities, ESInets, and PSAPs determine how to
automated test. Per [I-D.ietf-ecrit-ecall], treat a vehicle call requesting the "test" service URN so that the
"urn:service:test.sos.ecall.automatic" indicates such a test feature. desired functionality is tested, but this is outside the scope of
This functionality is defined in [RFC6881]. this document. (One possibility is that MNOs route such calls as
non-emergency calls to an ESInet, which routes them to a PSAP that
supports NG-ACN calls; the PSAP accepts test calls, sends a crash
data acknowledgment, and plays an audio clip (for example, saying
that the call reached an appropriate PSAP and the vehicle data was
successfully processed) in addition to supporting media loopback per
[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 will not apply (such as emergency call and so some functionality might not apply (such as
preemption or service availability for devices lacking service ("non- preemption or service availability for devices lacking service ("non-
service-initialized" or "NSI") if those are available for emergency service-initialized" or "NSI" devices) if those are available for
calls); this is by design. MNOs can recognize test calls and treat emergency calls).
them in a way that tests as much functionality as desired, but this
is outside the scope of this document.
10. Example 9. Example
Figure 7 shows an emergency call placed by a vehicle whereby location Figure 10 shows an NG-ACN call routing. The mobile network operator
information and VEDS crash data are both attached to the SIP INVITE (MNO) routes the call to an Emergency services IP Network (ESInet),
message. The INVITE has a request URI containing the as for any emergency call. The ESInet routes the call to an
'urn:service:sos.ecall.automatic' service URN and is thus recognized appropriate NG-ACN-capable PSAP (using location information and the
as an ACN type of emergency call, and is also recognizable as an fact that that it is an NG-ACN call). The call is processed by the
emergency call because the request URI starts with 'urn:service:sos'. Emergency Services Routing Proxy (ESRP), as the entry point to the
The mobile network operator (MNO) routes the call to an Emergency ESInet. The ESRP routes the call to an appropriate NG-ACN-capable
services IP Network (ESInet), as for any emergency call. The ESInet PSAP, where the call is received by a call taker. (In deployments
processes the call as an ACN and routes the call to an appropriate where there is no ESInet, the MNO itself routes the call directly to
ACN-capable PSAP (using location information and the fact that that an appropriate NG-ACN-capable PSAP.)
it is an ACN). The call is processed by the Emergency Services
Routing Proxy (ESRP), as the entry point to the ESInet. The ESRP
routes the call to an appropriate ACN-capable PSAP, where the call is
received by a call taker. (In deployments where there is no ESInet,
the MNO itself routes the call directly to an appropriate 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 7: Example of Vehicle-Placed Emergency Call Message Flow Figure 10: Example of Vehicle-Placed Emergency Call Message Flow
The example, shown in Figure 8, illustrates a SIP emergency call The example, shown in Figure 11, illustrates a SIP emergency call
INVITE that is being conveyed with location information (a PIDF-LO) INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS
and crash data (as VEDS data). data block), and capabilities data (an eCall metadata/control block
with extensions defined in this document) attached to the SIP INVITE
message. The INVITE has a request URI containing the
'urn:service:sos.ecall.automatic' service URN.
The example VEDS data structure shows information about about a The example VEDS data structure shows information about about a
crashed vehicle. The example communicates that the car is a model crashed vehicle. The example communicates that the car is a model
year 2015 Saab 9-5 (a car which does not exist). The front airbag year 2015 Saab 9-5 (a car which does not exist). The front airbag
deployed as a consequence of the crash. The deployed as a consequence of the crash. The
'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a
passenger car (the code is set to '101') and that it is not a passenger car (the code is set to '101') and that it is not a
convertible (the 'ConvertibleIndicator' value is set to 'false'). convertible (the 'ConvertibleIndicator' value is set to 'false').
The 'VehicleCrashPulse' element provides further information about The 'VehicleCrashPulse' element provides further information about
skipping to change at page 18, line 11 skipping to change at page 26, line 14
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 seatbelt 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), that the seatbelt was
monitored ('VehicleSeatbeltMonitoredIndicator' element), that the monitored ('VehicleSeatbeltMonitoredIndicator' element), that the
seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element)
and the seat sensor determined that the seat is occupied and the seat sensor determined that the seat was occupied
('VehicleSeatOccupiedIndicator' element). ('VehicleSeatOccupiedIndicator' element).
Finally, information about the weight of the vehicle, which is 600 Finally, information about the weight of the vehicle, which is 600
kilogram in our example. kilogram in our example.
In addition to the information about the vehicle, further indications In addition to the information about the vehicle, further indications
are provided, namely the presence of fuel leakage are provided, namely the presence of fuel leakage
('FuelLeakingIndicator' element), an indication whether the vehicle ('FuelLeakingIndicator' element), an indication whether the vehicle
was subjected to multiple impacts ('MultipleImpactsIndicator' 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 indication
that there are no parts of the vehicle on fire (the that there are no parts of the vehicle on fire (the
'VehicleFireIndicator' element). '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
Accept: application/sdp, application/pidf+xml Call-Info: cid:1234567892@atlanta.example.com;
CSeq: 31862 INVITE purpose=EmergencyCallData.ecall.control
Content-Type: multipart/mixed; boundary=boundary1 Accept: application/sdp, application/pidf+xml,
Content-Length: ... application/emergencyCallData.eCall.control+xml
Recv-Info: emergencyCallData.eCall
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE
CSeq: 31862 INVITE
Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...Session Description Protocol (SDP) goes here ...Session Description Protocol (SDP) goes here
--boundary1
Content-Type: application/pidf+xml
Content-ID: <target123@atlanta.example.com>
<?xml version="1.0" encoding="UTF-8"?>
<presence
xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:dyn="urn:ietf:params:xml:ns:pidf:geopriv10:dynamic"
xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
entity="sip:+13145551111@example.com">
<dm:device id="123">
<gp:geopriv>
<gp:location-info>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-34.407 150.883</gml:pos>
</gml:Point>
<dyn:Dynamic>
<dyn:heading>278</dyn:heading>
<dyn:direction><dyn:direction>
</dyn:Dynamic>
</gp:location-info>
<gp:usage-rules/>
<method>gps</method>
</gp:geopriv>
<timestamp>2012-04-5T10:18:29Z</timestamp>
<dm:deviceID>1M8GDM9A_KP042788</dm:deviceID>
</dm:device>
</presence>
--boundary1 --boundary1
Content-Type: application/pidf+xml Content-Type: application/EmergencyCallData.VEDS+xml
Content-ID: <target123@atlanta.example.com> Content-ID: 1234567890@atlanta.example.com
Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence <AutomatedCrashNotification xmlns="http://www.veds.org/acn/1.0"
xmlns="urn:ietf:params:xml:ns:pidf" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:dyn="urn:ietf:params:xml:ns:pidf:geopriv10:dynamic"
xmlns:gml="http://www.opengis.net/gml"
xmlns:gs="http://www.opengis.net/pidflo/1.0"
entity="sip:+13145551111@example.com">
<dm:device id="123">
<gp:geopriv>
<gp:location-info>
<gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
<gml:pos>-34.407 150.883</gml:pos>
</gml:Point>
<dyn:Dynamic>
<dyn:heading>278</dyn:heading>
<dyn:direction><dyn:direction>
</dyn:Dynamic>
</gp:location-info>
<gp:usage-rules/>
<method>gps</method>
</gp:geopriv>
<timestamp>2012-04-5T10:18:29Z</timestamp>
<dm:deviceID>1M8GDM9A_KP042788</dm:deviceID>
</dm:device>
</presence>
--boundary1 <Crash>
Content-Type: application/EmergencyCallData.VEDS+xml <CrashVehicle>
Content-ID: 1234567890@atlanta.example.com <ItemMakeName xmlns="http://niem.gov/niem/niem-core/2.0">
Content-Disposition: by-reference;handling=optional Saab
</ItemMakeName>
<ItemModelName xmlns="http://niem.gov/niem/niem-core/2.0">
9-5
<?xml version="1.0" encoding="UTF-8"?> </ItemModelName>
<AutomatedCrashNotification xmlns="http://www.veds.org/acn/1.0" <ItemModelYearDate
xmlns="http://niem.gov/niem/niem-core/2.0">
2015
</ItemModelYearDate>
<Airbag>
<AirbagCategoryCode>FRONT</AirbagCategoryCode>
<AirbagDeployedIndicator>true
</AirbagDeployedIndicator>
</Airbag>
<ConvertibleIndicator>false</ConvertibleIndicator>
<PowerSourceCategoryCode>MAIN</PowerSourceCategoryCode>
<VehicleBodyCategoryCode
xmlns="http://niem.gov/niem/domains/jxdm/4.1">
101
</VehicleBodyCategoryCode>
<VehicleCrashPulse>
<CrashPulseChangeInVelocityMeasure>
<MeasurePointValue
xmlns="http://niem.gov/niem/niem-core/2.0">
100
</MeasurePointValue>
<MeasureUnitText
xmlns="http://niem.gov/niem/niem-core/2.0">
MPH</MeasureUnitText>
</CrashPulseChangeInVelocityMeasure>
<CrashPulsePrincipalDirectionOfForceValue>12
</CrashPulsePrincipalDirectionOfForceValue>
<CrashPulseRolloverQuarterTurnsValue>1
</CrashPulseRolloverQuarterTurnsValue>
</VehicleCrashPulse>
<VehicleRollbarDeployedIndicator>false
</VehicleRollbarDeployedIndicator>
<VehicleSeat>
<VehicleSeatLocationCategoryCode>1
</VehicleSeatLocationCategoryCode>
<VehicleSeatOccupiedIndicator>true
</VehicleSeatOccupiedIndicator>
<VehicleSeatbeltFastenedIndicator>true
</VehicleSeatbeltFastenedIndicator>
<VehicleSeatbeltMonitoredIndicator>true
</VehicleSeatbeltMonitoredIndicator>
</VehicleSeat>
<VehicleUnladenWeightMeasure
xmlns="http://niem.gov/niem/niem-core/2.0">
<MeasurePointValue
xmlns="http://niem.gov/niem/niem-core/2.0">
600
</MeasurePointValue>
<MeasureUnitText
xmlns="http://niem.gov/niem/niem-core/2.0">
kilogram
</MeasureUnitText>
</VehicleUnladenWeightMeasure>
</CrashVehicle>
<FuelLeakingIndicator>true</FuelLeakingIndicator>
<MultipleImpactsIndicator>false</MultipleImpactsIndicator>
<SevereInjuryIndicator>true</SevereInjuryIndicator>
<VehicleFinalRestOrientationCategoryCode>Driver
</VehicleFinalRestOrientationCategoryCode>
<VehicleFireIndicator>false</VehicleFireIndicator>
</Crash>
</AutomatedCrashNotification>
--boundary1
Content-Type: application/EmergencyCallData.ecall.control+xml
Content-ID: 1234567892@atlanta.example.com
Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall:control">
<Crash> <capabilities>
<CrashVehicle> <request action="send-data" supported-datatypes="VEDS"/>
<ItemMakeName xmlns="http://niem.gov/niem/niem-core/2.0"> <request action="lamp"
Saab supported-lamps="head;interior;fog-front;fog-rear;
</ItemMakeName> brake;position-front;position-rear;turn-left;
<ItemModelName xmlns="http://niem.gov/niem/niem-core/2.0"> turn-right;hazard"/>
9-5 <request action="msg-static" msgid="3"/>
</ItemModelName> <request action="msg-dynamic"/>
<ItemModelYearDate <request action="honk"/>
xmlns="http://niem.gov/niem/niem-core/2.0"> <request action="enable-camera"
2015 supported-cameras="backup; interior"/>
</ItemModelYearDate> </capabilities>
<Airbag>
<AirbagCategoryCode>FRONT</AirbagCategoryCode>
<AirbagDeployedIndicator>true
</AirbagDeployedIndicator>
</Airbag> </EmergencyCallData.eCallControl>
<ConvertibleIndicator>false</ConvertibleIndicator>
<PowerSourceCategoryCode>MAIN</PowerSourceCategoryCode>
<VehicleBodyCategoryCode
xmlns="http://niem.gov/niem/domains/jxdm/4.1">
101
</VehicleBodyCategoryCode>
<VehicleCrashPulse>
<CrashPulseChangeInVelocityMeasure>
<MeasurePointValue
xmlns="http://niem.gov/niem/niem-core/2.0">
100
</MeasurePointValue>
<MeasureUnitText
xmlns="http://niem.gov/niem/niem-core/2.0">
MPH</MeasureUnitText>
</CrashPulseChangeInVelocityMeasure>
<CrashPulsePrincipalDirectionOfForceValue>12
</CrashPulsePrincipalDirectionOfForceValue>
<CrashPulseRolloverQuarterTurnsValue>1
</CrashPulseRolloverQuarterTurnsValue>
</VehicleCrashPulse>
<VehicleRollbarDeployedIndicator>false
</VehicleRollbarDeployedIndicator>
<VehicleSeat>
<VehicleSeatLocationCategoryCode>1
</VehicleSeatLocationCategoryCode>
<VehicleSeatOccupiedIndicator>true
</VehicleSeatOccupiedIndicator>
<VehicleSeatbeltFastenedIndicator>true
</VehicleSeatbeltFastenedIndicator>
<VehicleSeatbeltMonitoredIndicator>true
</VehicleSeatbeltMonitoredIndicator>
</VehicleSeat>
<VehicleUnladenWeightMeasure
xmlns="http://niem.gov/niem/niem-core/2.0">
<MeasurePointValue
xmlns="http://niem.gov/niem/niem-core/2.0">
600
</MeasurePointValue>
<MeasureUnitText
xmlns="http://niem.gov/niem/niem-core/2.0">
kilogram
</MeasureUnitText>
</VehicleUnladenWeightMeasure>
</CrashVehicle>
<FuelLeakingIndicator>true</FuelLeakingIndicator>
<MultipleImpactsIndicator>false</MultipleImpactsIndicator>
<SevereInjuryIndicator>true</SevereInjuryIndicator>
<VehicleFinalRestOrientationCategoryCode>Driver
</VehicleFinalRestOrientationCategoryCode>
<VehicleFireIndicator>false</VehicleFireIndicator>
</Crash>
</AutomatedCrashNotification>
--boundary1-- --boundary1--
Figure 8: SIP INVITE indicating a Vehicule-Initated Emergency Call Figure 11: SIP INVITE indicating a Vehicule-Initated Emergency Call
11. Security Considerations 10. Security Considerations
Since this document relies on [I-D.ietf-ecrit-ecall] and Since this document relies on [I-D.ietf-ecrit-ecall] and
[I-D.ietf-ecrit-additional-data], the security considerations [I-D.ietf-ecrit-additional-data], the security considerations
described there and in [RFC5069] apply here. Implementors are described there and in [RFC5069] apply here. Implementors are
strongly cautioned to read and understand the discussion in those cautioned to read and understand the discussion in those documents.
documents.
As with emergency service systems where location data is supplied or As with 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, there is the
possibility that that location is incorrect, either intentially (in possibility that that location is incorrect, either intentially
case of an a denial of service attack against the emergency services (e.g., in a denial of service attack against the emergency services
infrastructure) or due to a malfunctioning device. The reader is infrastructure) or due to a malfunctioning device. The reader is
referred to [RFC7378] for a discussion of some of these referred to [RFC7378] for a discussion of some of these
vulnerabilities. vulnerabilities.
12. Privacy Considerations In addition to the security considerations discussion specific to the
metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles
MAY decline to carry out any requested action (e.g., if the vehicle
requires but is unable to verify the certificate used to sign the
request). The vehicle MAY use any value in the reason registry to
indicate why it did not take an action (e.g., the generic "unable" or
the more specific "security-failure").
11. Privacy Considerations
Since this document builds on [I-D.ietf-ecrit-ecall], which itself Since this document builds on [I-D.ietf-ecrit-ecall], which itself
builds on [I-D.ietf-ecrit-additional-data], the data structures builds on [I-D.ietf-ecrit-additional-data], the data structures
specified there, and the corresponding privacy considerations specified there, and the corresponding privacy considerations
discussed there, apply here as well. The VEDS data structure discussed there, apply here as well. The VEDS data structure
contains optional elements that can carry identifying and personal contains optional elements that can carry identifying and personal
information, both about the vehicle and about the owner, as well as information, both about the vehicle and about the owner, as well as
location information, and so needs to be protected against location information, and so needs to be protected against
unauthorized disclosure, as discussed in unauthorized disclosure, as discussed in
[I-D.ietf-ecrit-additional-data]. Local regulations may impose [I-D.ietf-ecrit-additional-data]. Local regulations may impose
additional privacy protection requirements. additional privacy protection requirements.
13. IANA Considerations 12. IANA Considerations
13.1. MIME Content-type Registration for 'application/
This document registers the 'application/EmergencyCall.VEDS+xml' MIME
content type, and adds "VEDS" to the Emergency Call Additional Data
registry. This document adds to and creates new sub-registries in
the 'eCall Control Data' registry created in [I-D.ietf-ecrit-ecall].
12.1. MIME Content-type Registration for 'application/
EmergencyCall.VEDS+xml' EmergencyCall.VEDS+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.VEDS+xml MIME subtype name: EmergencyCallData.VEDS+xml
skipping to change at page 23, line 12 skipping to change at page 32, line 12
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'
Person and email address for further information: Hannes Persons and email addresses for further information: Randall
Tschofenig, Hannes.Tschofenig@gmx.net Gellensm rg+ietf (at) randy.pensive.org; Hannes Tschofenig,
Hannes.Tschofenig (at) gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
13.2. Registration of the 'VEDS' entry in the Emergency Call Additional 12.2. Registration of the 'VEDS' entry in the Emergency Call Additional
Data registry Data registry
This specification requests IANA to add the 'VEDS' entry to the This specification requests IANA to add the 'VEDS' entry to the
Emergency Call Additional Data registry, with a reference to this Emergency Call Additional Data registry, with a reference to this
document. The Emergency Call Additional Data registry has been document. The Emergency Call Additional Data registry has been
established by [I-D.ietf-ecrit-additional-data]. established by [I-D.ietf-ecrit-additional-data].
12.3. Additions to the eCall Control Extension Registry
This document uses the "eCall Control Extension Registry" to add new
elements, attributes, and values to the eCall metadata/control
object, as per [I-D.ietf-ecrit-ecall]:
+-----------+---------------------+---------------------------------+
| Type | Name | Description |
+-----------+---------------------+---------------------------------+
| Attribute | msgid | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | persistance | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | supported-datatypes | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | lamp-action | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | lamp-ID | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | supported-lamps | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | camera-ID | See Section 7.2 of this |
| | | document |
| | | |
| Element | text | See Section 7.4.2 of this |
| | | document |
| | | |
| Element | actionResult | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | action | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | success | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | reason | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | details | See Section 7.2.1 of this |
| | | document |
+-----------+---------------------+---------------------------------+
Table 2: eCall Control Extension Registry New Values
12.4. eCall Action Extensions
This document adds new values for the 'action' attribute of the
<request> element in the "eCall Control Action Registry" registry
created by [I-D.ietf-ecrit-ecall].
+---------------+------------------------------+
| Name | Description |
+---------------+------------------------------+
| msg-static | Section 7.1 of this document |
| | |
| msg-dynamic | Section 7.1 of this document |
| | |
| honk | Section 7.1 of this document |
| | |
| lamp | Section 7.1 of this document |
| | |
| enable-camera | Section 7.1 of this document |
+---------------+------------------------------+
Table 3: eCall Control Action Registry New Values
12.5. eCall Static Message Registry
This document creates a new sub-registry called "eCall Static Message
Registry" in the "eCall Control Data" registry established by
[I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected
to support all static messages translated into all languages
supported by the vehicle, it is important to limit the number of such
messages. As defined in [RFC5226], this registry operates under
"Publication Required" rules, which require a stable, public document
and imply expert review of the publication. The expert should
determine that the document has been published by an appropriate
emergency services organization (e.g., NENA, EENA, APCO) or by the
IETF with input from an emergency services organization, and that the
proposed message is sufficiently distinguishable from other messages.
The content of this registry includes:
ID: An integer identifier to be used in the 'msgid' attribute of an
eCall control <request> element.
Message: The text of the message. Messages are listed in the
registry in English; vehicles are expected to implement
translations into languages supported by the vehicle.
When new messages are added to the registry, the message text is
determined by the registrant; IANA assigns the IDs. Each message is
assigned a consecutive integer value as its ID. This allows an IVS
to indicate by a single integer value that it supports all messages
with that value or lower.
The initial set of values is listed in Table 4.
+----+--------------------------------------------------------------+
| ID | Message |
+----+--------------------------------------------------------------+
| 1 | Emergency authorities are aware of your incident and |
| | location, but are unable to speak with you right now. We |
| | will help you as soon as possible. |
+----+--------------------------------------------------------------+
Table 4: eCall Static Message Registry
12.6. eCall Reason Registry
This document creates a new sub-registry called "eCall Reason
Registry" in the "eCall Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry contains values for
the 'reason' attribute of the <actionResult> element. As defined in
[RFC5226], this registry operates under "Expert Review" rules. The
expert should determine that the proposed reason is sufficiently
distinguishable from other reasons and that the proposed description
is understandable and correctly worded.
The content of this registry includes:
ID: A short string identifying the reason, for use in the 'reason'
attribute of an <actionResult> element.
Description: A description of the reason.
The initial set of values is listed in Table 5.
+------------------+------------------------------------------------+
| ID | Description |
+------------------+------------------------------------------------+
| unsupported | The 'action' is not supported. |
| | |
| unable | The 'action' could not be accomplished. |
| | |
| data-unsupported | The data item referenced in a 'send-data' |
| | request is not supported. |
| | |
| security-failure | The authenticity of the request or the |
| | authority of the requestor could not be |
| | verified. |
+------------------+------------------------------------------------+
Table 5: eCall Reason Registry
12.7. eCall Lamp ID Registry
This document creates a new sub-registry called "eCall Lamp ID
Registry" in the "eCall Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry standardizes the names
of automotive lamps (lights). As defined in [RFC5226], this registry
operates under "Expert Review" rules. The expert should determine
that the proposed lamp name is clearly understandable and is
sufficiently distinguishable from other lamp names.
The content of this registry includes:
Name: The identifier to be used in the 'lamp-ID' attribute of an
eCall control <request> element.
Description: A description of the lamp (light).
The initial set of values is listed in Table 6.
+----------------+---------------------------------------------+
| Name | Description |
+----------------+---------------------------------------------+
| head | The main lamps used to light the road ahead |
| | |
| interior | Interior lamp, often at the top center |
| | |
| fog-front | Front fog lamps |
| | |
| fog-rear | Rear fog lamps |
| | |
| brake | Brake indicator lamps |
| | |
| position-front | Front position/parking/standing lamps |
| | |
| position-rear | Rear position/parking/standing lamps |
| | |
| turn-left | Left turn/directional lamps |
| | |
| turn-right | Right turn/directional lamps |
| | |
| hazard | Hazard/four-way lamps |
+----------------+---------------------------------------------+
Table 6: eCall Lamp ID Registry Initial Values
12.8. eCall Camera ID Registry
This document creates a new sub-registry called "eCall Camera ID
Registry" in the "eCall Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry standardizes the names
of automotive camera. As defined in [RFC5226], this registry
operates under "Expert Review" rules. The expert should determine
that the proposed camera name is clearly understandable and is
sufficiently distinguishable from other camera names.
The content of this registry includes:
Name: The identifier to be used in the 'camera-ID' attribute of an
eCall control <request> element.
Description: A description of the camera.
The initial set of values is listed in Table 7.
+-------------+-----------------------------------------------------+
| Name | Description |
+-------------+-----------------------------------------------------+
| backup | Shows what is behind the vehicle, e.g., often used |
| | for driver display when the vehicle is in reverse. |
| | Also known as rearview, reverse, etc. |
| | |
| left-rear | Shows view to the left and behind (e.g., left side |
| | rear-view mirror or blind spot view) |
| | |
| right-rear | Shows view to the right and behind (e.g., right |
| | side rear-view mirror or blind spot view) |
| | |
| forward | Shows what is in front of the vehicle |
| | |
| rear-wide | Shows what is behind vehicle (e.g., used by rear- |
| | collision detection systems), separate from backup |
| | view |
| | |
| lane | Used by systems to identify road lane and/or |
| | monitor vehicle's position within lane |
| | |
| interior | Shows the interior (e.g., driver) |
| | |
| night-front | Night-vision view of what is in front of the |
| | vehicle |
+-------------+-----------------------------------------------------+
Table 7: eCall Camera ID Registry Initial Values
13. eCall Control Block Schema
This section presents an XML schema of the eCall control block after
applying the extensions defined in this document. Note that the text
is normative; this schema is informative.
<?xml version="1.0"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
<xs:element name="EmergencyCallData.eCallControl"
type="pi:eCallControlType"/>
<xs:complexType name="eCallControlType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:choice>
<xs:element name="capabilities"
type="pi:capabilitiesType"/>
<xs:element name="request" type="pi:requestType"/>
<xs:element name="ack" type="pi:ackType"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:choice>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="ackType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence minOccurs="1" maxOccurs="unbounded">
<xs:element name="actionResult" minOccurs="0"
maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="action"
type="xs:token"
use="required"/>
<xs:attribute name="success"
type="xs:boolean"
use="required"/>
<xs:attribute name="reason"
type="xs:token">
<xs:annotation>
<xs:documentation>conditionally
mandatory when @success='false"
to indicate reason code for a
failure </xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="details"
type="xs:string"/>
<xs:anyAttribute processContents="skip"/>
</xs:complexType>
</xs:element>
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="ref"
type="xs:anyURI"
use="required"/>
<xs:attribute name="received"
type="xs:boolean"/>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="capabilitiesType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence minOccurs="1" maxOccurs="unbounded">
<xs:element name="request"
type="pi:requestType"
minOccurs="1"
maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="requestType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:choice>
<xs:attribute name="action" type="xs:token" use="required"/>
<xs:attribute name="msgid" type="xs:unsignedInt"/>
<xs:attribute name="persistence" type="xs:duration"/>
<xs:attribute name="datatype" type="xs:token"/>
<xs:attribute name="supported-datatypes" type="xs:string"/>
<xs:attribute name="lamp-id" type="xs:token"/>
<xs:attribute name="lamp-action">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=""/>
<xs:pattern value=""/>
<xs:enumeration value="on"/>
<xs:enumeration value="off"/>
<xs:enumeration value="flash"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="supported-lamps" type="xs:string"/>
<xs:attribute name="camera-id" type="xs:token"/>
<xs:attribute name="supported-cameras" type="xs:string"/>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
</xs:schema>
Figure 12: eCall Control Block Schema
14. Contributors 14. Contributors
We would like to thank Ulrich Dietz for his help with earlier We would like to thank Ulrich Dietz for his help with earlier
versions of the original version of this document. versions of the original version of this document.
15. Acknowledgements 15. Acknowledgements
We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri, We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri,
Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback. Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback.
16. Changes from Previous Versions 16. Changes from Previous Versions
16.1. Changes from draft-ietf-05 to draft-ietf-06 16.1. 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.2. Changes from draft-ietf-06 to draft-ietf-07
o Minor editorial changes
16.3. Changes from draft-ietf-05 to draft-ietf-06
o Added clarifying text regarding signed and encrypted data o Added clarifying text regarding signed and encrypted data
o Additional informative text in "Migration to Next-Generation" o Additional informative text in "Migration to Next-Generation"
section section
o Additional clarifying text regarding security and privacy. o Additional clarifying text regarding security and privacy.
16.2. Changes from draft-ietf-04 to draft-ietf-05 16.4. Changes from draft-ietf-04 to draft-ietf-05
o Reworded security text in main document and in MIME registration o Reworded security text in main document and in MIME registration
for the VEDS object for the VEDS object
16.3. Changes from draft-ietf-03 to draft-ietf-04 16.5. Changes from draft-ietf-03 to draft-ietf-04
o Added example VEDS object o Added example VEDS object
o Additional clarifications and corrections o Additional clarifications and corrections
o Removed references from Abstract o Removed references from Abstract
o Moved Document Scope section to follow Introduction o Moved Document Scope section to follow Introduction
16.4. Changes from draft-ietf-02 to draft-ietf-03 16.6. Changes from draft-ietf-02 to draft-ietf-03
o Additional clarifications and corrections o Additional clarifications and corrections
16.5. Changes from draft-ietf-01 to draft-ietf-02 16.7. Changes from draft-ietf-01 to draft-ietf-02
o This document now refers to [I-D.ietf-ecrit-ecall] for technical o This document now refers to [I-D.ietf-ecrit-ecall] for technical
aspects including the service URN; this document no longer aspects including the service URN; this document no longer
proposes a unique service URN for non-eCall NG-ACN calls; the same 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 service URN is now used for all NG-ACN calls including NG-eCall
and non-eCall and non-eCall
o Added discussion of an NG-ACN call placed to a PSAP that doesn't o Added discussion of an NG-ACN call placed to a PSAP that doesn't
support it support it
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
16.6. Changes from draft-ietf-00 to draft-ietf-01 16.8. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications such as eCall crash notification specifications such as eCall
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
16.7. Changes from draft-gellens-02 to draft-ietf-00 16.9. Changes from draft-gellens-02 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf- o Renamed from draft-gellens- to draft-ietf-
o Added text to Introduction to clarify that during a CS ACN, the 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 PSAP call taker usually needs to listen to the data and transcribe
it it
16.8. Changes from draft-gellens-01 to -02 16.10. Changes from draft-gellens-01 to -02
o Fixed case of 'EmergencyCallData', in accordance with changes to o Fixed case of 'EmergencyCallData', in accordance with changes to
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
16.9. Changes from draft-gellens-00 to -01 16.11. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to MIME subtypes, in accordance with changes to
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
17. References 17. References
17.1. Normative References 17.1. Normative References
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 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", draft-ietf-ecrit-additional-data-37 (work in Call", draft-ietf-ecrit-additional-data-38 (work in
progress), October 2015. progress), April 2016.
[I-D.ietf-ecrit-ecall] [I-D.ietf-ecrit-ecall]
Gellens, R. and H. Tschofenig, "Next-Generation Pan- Gellens, R. and H. Tschofenig, "Next-Generation Pan-
European eCall", draft-ietf-ecrit-ecall-03 (work in European eCall", draft-ietf-ecrit-ecall-07 (work in
progress), July 2015. progress), February 2016.
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, Types", RFC 3023, DOI 10.17487/RFC3023, January 2001,
<http://www.rfc-editor.org/info/rfc3023>. <http://www.rfc-editor.org/info/rfc3023>.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, Format", RFC 4119, DOI 10.17487/RFC4119, December 2005,
<http://www.rfc-editor.org/info/rfc4119>. <http://www.rfc-editor.org/info/rfc4119>.
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, Registration Procedures", RFC 4288, DOI 10.17487/RFC4288,
December 2005, <http://www.rfc-editor.org/info/rfc4288>. December 2005, <http://www.rfc-editor.org/info/rfc4288>.
[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031, DOI Emergency and Other Well-Known Services", RFC 5031,
10.17487/RFC5031, January 2008, DOI 10.17487/RFC5031, January 2008,
<http://www.rfc-editor.org/info/rfc5031>. <http://www.rfc-editor.org/info/rfc5031>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
Presence Information Data Format Location Object (PIDF-LO) Presence Information Data Format Location Object (PIDF-LO)
Usage Clarification, Considerations, and Recommendations", Usage Clarification, Considerations, and Recommendations",
RFC 5491, DOI 10.17487/RFC5491, March 2009, RFC 5491, DOI 10.17487/RFC5491, March 2009,
<http://www.rfc-editor.org/info/rfc5491>. <http://www.rfc-editor.org/info/rfc5491>.
[RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M.
Thomson, "Dynamic Extensions to the Presence Information Thomson, "Dynamic Extensions to the Presence Information
Data Format Location Object (PIDF-LO)", RFC 5962, DOI Data Format Location Object (PIDF-LO)", RFC 5962,
10.17487/RFC5962, September 2010, DOI 10.17487/RFC5962, September 2010,
<http://www.rfc-editor.org/info/rfc5962>. <http://www.rfc-editor.org/info/rfc5962>.
[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>.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
<http://www.rfc-editor.org/info/rfc6881>. <http://www.rfc-editor.org/info/rfc6881>.
[VEDS] "Vehicular Emergency Data Set (VEDS) version 3", July [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/
2012, <https://www.apcointl.org/resources/telematics/aacn- NENA Data Standardization Workgroup, , "Vehicular
and-veds.html>. Emergency Data Set (VEDS) version 3", July 2012,
<https://www.apcointl.org/resources/telematics/aacn-and-
veds.html>.
17.2. Informative references 17.2. Informative references
[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, DOI Emergency Call Marking and Mapping", RFC 5069,
10.17487/RFC5069, January 2008, DOI 10.17487/RFC5069, January 2008,
<http://www.rfc-editor.org/info/rfc5069>. <http://www.rfc-editor.org/info/rfc5069>.
[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]
National Center for Injury Prevention and Control, and
Centers for Disease Control and Prevention,
"Recommendations from the Expert Panel: Advanced Automatic
Collision Notification and Triage of the Injured Patient",
2008, <https://stacks.cdc.gov/view/cdc/5304/>.
[triage-2011]
National Center for Injury Prevention and Control, and
Centers for Disease Control and Prevention, "Guidelines
for field triage of injured patients: recommendations of
the National Expert Panel on Field Triage", January 2012,
<https://www.researchgate.net/journal/1545-8601_MMWR_Recom
mendations_and_reports_Morbidity_and_mortality_weekly_repo
rt_Recommendations_and_reports_Centers_for_Disease_Control
>.
Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
Qualcomm Technologies, Inc Consultant
5775 Morehouse Drive 6755 Mira Mesa Blvd 123-151
San Diego 92651 San Diego 92121
US US
Email: rg+ietf@randy.pensive.org Email: rg+ietf@randy.pensive.org
Brian Rosen Brian Rosen
NeuStar, Inc. NeuStar, Inc.
470 Conrad Dr 470 Conrad Dr
Mars, PA 16046 Mars, PA 16046
US US
skipping to change at page 27, line 19 skipping to change at page 46, line 4
Email: rg+ietf@randy.pensive.org Email: rg+ietf@randy.pensive.org
Brian Rosen Brian Rosen
NeuStar, Inc. NeuStar, Inc.
470 Conrad Dr 470 Conrad Dr
Mars, PA 16046 Mars, PA 16046
US US
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. 114 change blocks. 
540 lines changed or deleted 1367 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/