| Network Working Group | R.J. Jesske |
| Internet-Draft | Deutsche Telekom |
| Intended status: Informational | July 15, 2013 |
| Expires: January 16, 2014 |
Uniform Resource Name (URN) extension for automatic and manual Emergency Services
draft-jesske-ecrit-ecall-urn-extension-01
This document describes and discusses a mechanism for extending sos URN's to fulfill the emergency call requirements of carriers.
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 January 16, 2014.
Copyright (c) 2013 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.
Uniform Resource Name (URN) for emergency and other Well-Known Services are well defined within RFC5031 [RFC5031]. 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. 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 document proposes to extend the existing URN's with an extension to reflect this.
This draft should be seen as proposal which could be incoperated into draft-rosen-ecrit-ecall-10 [draft-rosen-ecrit-ecall-10] after discussing this approach
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 [RFC2119].
RFC5031 [RFC5031] 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-rosen-ecrit-ecall-10 [draft-rosen-ecrit-ecall-10] proposes two additional URN for ecall. automatic and ecall.manual the sub-services 'sos' as specified in Section 4.2 of RFC5031 [RFC5031].
Within the existing implementation in GSM networks for emergency call as specified in 3GPP TS 22.101 [TS22101] the following requirements and code points are described:
--------------------------------------------------------------------- ---
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-rosen-ecrit-ecall-10 [draft-rosen-ecrit-ecall-10]. 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 [TS22101] described will not be satisfied. Therefor this document proposes an other format of the URN
IANA is requested to register the URNs described below under the sub-services 'sos' registry defined in Section 4.2 of RFC5031[RFC5031]
An additional sublabel for sos and the 5 base values of police, ambulance, fire, mountain are defined.
.ecall
This sublevel indicated that an ecall has been triggered.
.automatic
This sublevel indicates that an eCall had been triggered automatically. This could be a sensor-controlled measuring of heat or pressure in case of car accidents or fire situations.
.manual
This sublevel indicates that an eCall had been triggered based on the manual interaction of a person.
Service Reference Description
-----------------------------------------------------------------------------------
sos.ecall RFC xxxx Emergency services, automatic eCall
sos.ecall.automatic RFC xxxx Emergency services, automatic eCall
sos.ecall.manual RFC xxxx Emergency services, manual eCall
sos.police.ecall.automatic RFC xxxx Police, law enforcement, automatic eCall
sos.police.ecall.manual RFC xxxx Police, law enforcement, manual eCall
sos.ambulance.ecall.automatic RFC xxxx Ambulance service, automatic eCall
sos.ambulance.ecall.manual RFC xxxx Ambulance service, manual eCall
sos.fire.ecall.automatic RFC xxxx Fire service, automatic eCall
sos.fire.ecall.manual RFC xxxx Fire service, manual eCall
sos.marine.ecall.automatic RFC xxxx Maritime search and rescue, automatic eCall
sos.marine.ecall.manual RFC xxxx Maritime search and rescue, manual eCall
sos.mountain.ecall.automatic RFC xxxx Mountain rescue, automatic eCall
sos.mountain.ecall.manual RFC xxxx Mountain rescue, manual eCall
This document does not raise security considerations beyond those described in RFC5031 [RFC5031].
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.
| [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] | Rosen, B., Tschofenig, H. and R. Gellens, ""Internet Protocol-based In-Vehicle Emergency Call"", July 2013. |
| [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. |