Internet DRAFT - draft-jesske-ecrit-ecall-ims
draft-jesske-ecrit-ecall-ims
Network Working Group R. Jesske
Internet-Draft Deutsche Telekom
Intended status: Informational October 27, 2014
Expires: April 30, 2015
eCall requirements for IMS backwardcompatible solution
draft-jesske-ecrit-ecall-ims-00
Abstract
This document discusses the requirements for a backward compatible
solution to address eCall / emergency call requirements of carriers
using the IMS.
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
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 April 30, 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.
Jesske Expires April 30, 2015 [Page 1]
Internet-DrafeCall requirements for IMS backwardcompatible October 2014
Table of Contents
1. Overall Applicability . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. IANA Consideration . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. Contributors and Acknowledgements . . . . . . . . . . . . . . 4
7. Normative References . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Overall Applicability
Uniform Resource Name (URN) for emergency and other Well-Known
Services are well defined within RFC5031 [2]. There are also
existing proposals for automatic and manual ecall IN-Vehicles which
defines their own URN's and additional procedures for vehicle
specific eCalls. Due to the existing telecommunication world and
their implementations a combination of both is needed. Specific the
IMS (IP Multimedia Subsytem) of 3GPP nees an implementation which is
backwardscompatible. Due to the fact that only one URN can be used
within the request line of a SIP Message a new approach is needed.
Therefore this documentdiscusses the requirement to address a
routingpossibility for a eCall.
2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [1].
3. Overview
RFC5031 [2] defines URN values for emergency calls. The values for
the SOS subtree are sos.ambulance, sos.animal-control, sos.fire,
sos.gas, sos.marine, sos.mountain , sos.physician, sos.poison and
sos.police draft-ietf-ecrit-ecall-01.txt [3] proposes two additional
URN for ecall. automatic and ecall.manual the sub-services 'sos' as
specified in Section 4.2 of RFC5031 [2].
Within the existing implementation in GSM networks for emergency call
as specified in 3GPP TS 22.101 [4] the following requirements and
code points are described:
---------------------------------------------------------------------
---
Jesske Expires April 30, 2015 [Page 2]
Internet-DrafeCall requirements for IMS backwardcompatible October 2014
It shall be possible to initiate emergency calls to different
emergency call centers, depending on the type of emergency. The
following types of emergency calls shall be possible:
o Police
o Ambulance
o Fire Brigade
o Marine Guard
o Mountain Rescue
o Manually Initiated eCall
o Automatically Initiated eCall
....
It shall be possible to tie any emergency call number to any single
emergency call type or to any combination of emergency call types.
--------------------------------------------------------------------
This means in practice that a emergency Call Center from police must
differentiate between automatic and manual eCalls. Same belongs to
the other types like fire brigade Marine Guard ect.
Requirement:
Req-1: It shall be possible to tie a manually initiated eCall with
different type of emergency type i.e. Police, Ambulance, Fire
Brigade, Marine Guard and Mountain Rescue.
Req-2:It shall be possible to tie a automatically initiated eCallC
with different type of emergency type i.e. Police, Ambulance, Fire
Brigade, Marine Guard and Mountain Rescue.
These requirements will not allow a second different URN Format as
described in draft-ietf-ecrit-ecall-01.txt [3] . This draft adds two
additional URN urn:service:sos.ecall.manual and
urn:service:sos.ecall.automatic Which allows to address the ecall
itself. But the requirement in 3GPP TS 22.101 [4] described will not
be satisfied. Therefor this document only describes the
requirements.
Jesske Expires April 30, 2015 [Page 3]
Internet-DrafeCall requirements for IMS backwardcompatible October 2014
Thus a mechanism is needed to tie any emergency call number to any
single emergency call type or to any combination of emergency call
types.
4. IANA Consideration
Currently no consideration required.
5. Security Considerations
This document does not raise security considerations beyond those
described in RFC5031 [2].
6. Contributors and Acknowledgements
The author would like to thank Dieter Jacobsohn, Maik Kirsch and
Thomas Dennert for clarifying the requirements on automatic and
manual eCall in the existing GSM world.
7. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031,
January 2008.
[3] Gellens, R. and H. Tschofenig, ""Next-Generation Pan-
European eCalll"", July 2014.
[4] 3GPP, "3rd Generation Partnership Project; Technical
Specification Group Services and System Aspects; Service
aspects; Service principles (Release 11)",", 3GPP TS
22.101 10.7.0, September 2012.
Author's Address
Roland Jesske
Deutsche Telekom
Heinrich-Hertz-Strasse 3-7
Darmstadt 64307
Germany
Phone: +4961515812766
Email: roland.jesske@web.de
Jesske Expires April 30, 2015 [Page 4]
