Next-Generation Pan-European eCall

Abstract

This document describes how to use IP-based emergency services mechanisms to support the next generation of the Pan-European invehicle emergency call service defined under the eSafety initiative of the European Commission (generally referred to as "eCall"). eCall is a standardized and mandated system for a special form of emergency calls placed by vehicles, providing real-time communications and an integrated set of related data.This document also registers MIME media types and an Emergency Call Data Type for the eCall vehicle data and metadata/control data, and an INFO package to enable carrying this data in SIP INFO requests.

Next-Generation Vehicle-Initiated Emergency Calls

“…This document reuses the technical aspects of next-generation PanEuropean eCall (a mandated and standardized system for emergency calls by in-vehicle systems within Europe), as described in [RFC8147]. However, this document specifies use of a different set of vehicle (crash) data, specifically, VEDS rather than the eCall Minimum Set of Data (MSD).…”

“…However, this document specifies use of a different set of vehicle (crash) data, specifically, VEDS rather than the eCall Minimum Set of Data (MSD). This document is an extension of [RFC8147], with the differences being that this document makes the MSD data set optional and VEDS mandatory, and it adds new attribute values to the metadata/control object defined in that document. This document also registers a new INFO package (identical to that defined in [RFC8147] with the addition of the VEDS MIME type).…”

“…These URNs request NG-ACN resources and differentiate between manually and automatically triggered NG-ACN calls (which might be subject to different treatment depending on policy). The two service URNs registered in [RFC8147] are "urn:service:sos.ecall.automatic" and "urn:service:sos.ecall.manual". The same service URNs are used for ACN as for eCall since in any region only one of these is supported, making a distinction unnecessary.…”

“…A PSAP or IVS transmits a metadata/control object (see [RFC8147]) by including it in a SIP message as a MIME body part per [RFC7852]. The body part is identified by its MIME media type (application/ EmergencyCallData.Control+xml) in the Content-Type header field of the body part.…”

“…This document extends [RFC8147] by reusing the call setup and other normative requirements with the exception that in this document, support for the eCall MSD is OPTIONAL and support for VEDS is REQUIRED. This document also adds new attribute values to the metadata/control object defined in [RFC8147].…”