tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TR 22.967 (SA1)
Transferring of emergency call data

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    26 p.
(P) V13.0.0    2016/01    26 p.
(P) V12.0.0    2014/10    26 p.
(P) V11.0.0    2012/09    26 p.
(P) V10.0.0    2011/04    26 p.
(P) V9.0.0    2009/12    26 p.
(P) V8.0.0    2009/01    26 p.
(P) V7.0.0    2006/03    26 p.


Rapporteur:  Dr. Wu, Jian (Jim) Jun
See also:  eCall-related TS/TR    


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.


 

Here          Top

 

 

1   Scope   PDF-p. 6
2   References
3   Definitions, symbols and abbreviations
4   Background   PDF-p. 7
5   Security considerations   PDF-p. 9      Up
6   Discussion of requirements identified
7   Use cases
8   Recommendations      Up
9   Considerations
10   Conclusion
A   CRs and LSs associated with the eCall investigation   PDF-p. 23
B   Change history   PDF-p. 24

Up          Top