Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-00

The information below is for an old version of the document
Document Type Active Internet-Draft (ecrit WG)
Last updated 2014-07-07
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Nov 2016 - Submit ‘Next-Generat... )
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ECRIT                                                         R. Gellens
Internet-Draft                               Qualcomm Technologies, Inc.
Intended status: Informational                             H. Tschofenig
Expires: January 5, 2015                                (no affiliation)
                                                           July 04, 2014

                   Next-Generation Pan-European eCall
                     draft-ietf-ecrit-ecall-00.txt

Abstract

   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.  eCall deployment is required by 2015 in
   European Union member states, and eCall (and eCall-compatible
   systems) are also being deployed in other regions.  eCall provides an
   integrated voice path and a standardized set of vehicle, sensor
   (e.g., crash related), and location data.  An eCall is recognized and
   handled as a specialized form of emergency call and is routed to a
   specialized eCall-capable Public Safety Answering Point (PSAP)
   capable of processing the vehicle data and trained in handling
   emergency calls from vehicles.

   Currently, eCall functions over circuit-switched cellular telephony;
   work on next-generation eCall (NG-eCall, sometimes called packet-
   switched eCall or PS-eCall) is now in process, and this document
   assists in that work by describing how to support eCall within the
   IP-based emergency services infrastructure.

   This document also registers a MIME Content Type and an Emergency
   Call Additional Data Block for the eCall vehicle data.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Gellens & Tschofenig     Expires January 5, 2015                [Page 1]
Internet-Draft            Next-Generation eCall                July 2014

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 5, 2015.

Copyright Notice

   Copyright (c) 2014 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.

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  eCall Requirements  . . . . . . . . . . . . . . . . . . . . .   5
   5.  Vehicle Data  . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Call Setup  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Call Routing  . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  ESInets . . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Test Calls  . . . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  eCall-Specific Data from PSAP to IVS  . . . . . . . . . . . .   8
   10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   11. Security Considerations . . . . . . . . . . . . . . . . . . .  11
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     12.1.  Service URN Registration . . . . . . . . . . . . . . . .  12
     12.2.  MIME Content-type Registration for
            'application/emergencyCallData.eCall.MSD+xml'  . . . . .  12
     12.3.  Registration of the 'eCall.MSD' entry in the Emergency
            Call Additional Data Blocks registry . . . . . . . . . .  13
   13. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  14
   14. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   15. Changes from Previous Versions  . . . . . . . . . . . . . . .  14
     15.1.  Changes from draft-gellens-03 to draft-ietf-00 . . . . .  14
Show full document text