Tech-invite3GPP-SpecsFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

Top   in Index   Prev   Next

TR 22.967SA1
Transferring of Emergency Call Data

use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V15.0.0 (PDF)  2018/06  25 p.
V14.0.0  2017/03  26 p.
V13.0.0  2016/01  26 p.
V12.0.0  2014/10  26 p.
V11.0.0  2012/09  26 p.
V10.0.0  2011/04  26 p.
V9.0.0  2009/12  26 p.
V8.0.0  2009/01  26 p.
V7.0.0  2006/03  26 p.

Rapporteur:  Dr. Wu, Jian (Jim) Jun

During 2004 a number of discussions were held between the Commission for the European Communities (CEC), the automotive industry, the telecommunication industry and ETSI standards groups regarding the provisioning of invehicle emergency calls. This initiative was called eSafety. As part of this initiative, eCall was defined as a specific item in the scope of the eSafety initiative. eCall is intended to extend the current E112 capabilities to enable the Transferring of eCall data between the Vehicle and the Public Safety Answering Points (PSAPs).
This TR examines the issues associated with the transmission of Emergency Call Data from a vehicle to a Public Service Access Point (PSAP).
Issues associated with the content of the Emergency Call Data or the triggers of the Emergency Calls are outside the scope of this document.

full Table of Contents for  TR 22.967  Word version:   15.0.0


Here   Top


1  ScopeWord-p. 6
2  References
3  Definitions, symbols and abbreviations
4  BackgroundWord-p. 7
5  Security considerationsWord-p. 9
6  Discussion of requirements identified
7  Use cases
8  RecommendationsUp
9  Considerations
10  Conclusion
A  CRs and LSs associated with the eCall investigationWord-p. 23
B  Change historyWord-p. 24

Up   Top