Skip to main content

Next-Generation Vehicle-Initiated Emergency Calls
RFC 8148

Revision differences

Document history

Date By Action
2022-05-23
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2021-03-30
(System) Received changes through RFC Editor sync (added Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document describes how to use IP-based emergency services mechanisms to support the next generation of …
Received changes through RFC Editor sync (changed abstract to '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.')
2017-05-15
(System) IANA registries were updated to include RFC8148
2017-05-12
(System)
Received changes through RFC Editor sync (created alias RFC 8148, changed abstract to 'This document describes how to use IP-based emergency services mechanisms to …
Received changes through RFC Editor sync (created alias RFC 8148, changed abstract to '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.', changed pages to 40, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-05-12, changed IESG state to RFC Published)
2017-05-12
(System) RFC published