Next-Generation Vehicle-Initiated Emergency Calls
RFC 8148

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18
• 19
• 20
• 21
• 22
• 23

Internet Engineering Task Force (IETF)                        R. Gellens
Request for Comments: 8148                    Core Technology Consulting
Category: Standards Track                                       B. Rosen
ISSN: 2070-1721                                            NeuStar, Inc.
                                                           H. Tschofenig
                                                              Individual
                                                                May 2017

           Next-Generation Vehicle-Initiated Emergency Calls

Abstract

   This document describes how to use IP-based emergency services
   mechanisms to support the next generation of emergency calls placed
   by vehicles (automatically in the event of a crash or serious
   incident, or manually invoked by a vehicle occupant) and conveying
   vehicle, sensor, and location data related to the crash or incident.
   Such calls are often referred to as "Automatic Crash Notification"
   (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the
   case of manual trigger.  The "Advanced" qualifier refers to the
   ability to carry a richer set of data.

   This document also registers a MIME media type and Emergency Call
   Data Type for the vehicle, sensor, and location data (often referred
   to as "crash data" even though there is not necessarily a crash) and
   an INFO package to enable carrying this and related data in SIP INFO
   requests.  An external specification for the data format, contents,
   and structure is referenced in this document.

   This document reuses the technical aspects of next-generation Pan-
   European eCall (a mandated and standardized system for emergency
   calls by in-vehicle systems (IVSs) within Europe and other regions).
   However, this document specifies use of a different set of vehicle
   (crash) data, specifically, the Vehicle Emergency Data Set (VEDS)
   rather than the eCall Minimum Set of Data (MSD).  This document is an
   extension of the IETF eCall document, with the primary differences
   being that this document makes the MSD data set optional and VEDS
   mandatory, and it adds attribute values to the metadata/control
   object to permit greater functionality.  This document registers a
   new INFO package (identical to that registered for eCall but with the
   addition of the VEDS MIME type).  This document also describes legacy
   (circuit-switched) ACN systems and their migration to next-generation
   emergency calling, to provide background information and context.

Gellens, et al.              Standards Track                    [Page 1]
RFC 8148            Vehicle-Initiated Emergency Calls           May 2017

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8148.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Gellens, et al.              Standards Track                    [Page 2]
RFC 8148            Vehicle-Initiated Emergency Calls           May 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   8
   4.  Overview of Legacy Deployment Models  . . . . . . . . . . . .   8
   5.  Migration to Next Generation  . . . . . . . . . . . . . . . .  10
   6.  Vehicle Data  . . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Data Transport  . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  Call Setup  . . . . . . . . . . . . . . . . . . . . . . . . .  16
   9.  New Metadata/Control Values . . . . . . . . . . . . . . . . .  17
     9.1.  New Values for the "action" Attribute . . . . . . . . . .  18
     9.2.  Example <request> Element . . . . . . . . . . . . . . . .  19