RFC 8147: Next-Generation Pan-European eCall
In plain English — editorial summary, not part of the RFC
This document describes how to use IP-based emergency services mechanisms to support the next generation of the Pan-European in-vehicle 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. Although this specification is designed to meet the requirements of next-generation Pan-European eCall (NG-eCall), it is specified generically such that the technology can be reused or extended to suit requirements across jurisdictions.
Document record
- Document ID
- RFC8147
- Published
- May 2017
- Authors
- R. Gellens; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 43
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8148Next-Generation Vehicle-Initiated Emergency CallsCurrent
May 2017
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
- RFC 8787Location Source Parameter for the SIP Geolocation Header FieldCurrent
May 2020
- RFC 8606ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header FieldCurrent
June 2019
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
- RFC 6444Location Hiding: Problem Statement and RequirementsCurrent
January 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?