MSG(13)034xxx
Pseudo CHANGE REQUEST124 229 / Version / 11.9.0 / CR / P-CR / rev / -
CR Title: / eCall over IMS
Source: / STF 456
Work Item Ref: / Migration of eCall transport / Date: / 06/02/2014
Category: / B / Release: / Rel-11
Use one of the following categories:
F (correction)
A (corresponds to a correction in an earlier release)
B (addition of feature)
C (functional modification of feature)
D (editorial modification)
Reason for change: / ETSI STF456, partly funded by the European Commission, is investigating migration of eCall transport over PS domain/EPS.
The Release-8 eCall covers CS only, and therefore excludes PS/IMS emergency services.
ETSI MSG TC agreed the TR103140 that studies the Migration of eCall transport. Proposed and recommended solutions are included in this TR. The solution considers eCall over IMS in line with the IMS emergency call/services.
Summary of change: / Based on the requirements in TS 22.101, The voice session for IMS eCall follows the normal IMS emergency services procedures. The IMS eCall UE shall include an eCall flag (eCall-manual or eCall-automatic) and the Minimum Set of Data (MSD) in the emergency session request. The eCall flag is used for filtering and routing the eCall session to the appropriate PSAP (that supports eCall).
The eCall flag is reflected in the eCall URNs ("urn:service:sos.ecall.automatic" and "urn:service:sos.ecall.manual") that are introduced in draft-gellens-ecrit-ecall-01 and a related draft-ietf-ecrit-additional-data-15. 3GPP needs to consider the IETF drafts in the dependency list and ensure IANA registration for the URNs.
The MSD is sent by the UE to the PSAP. The UE shall insert the MSD, with the content type application/emergencyCallData.eCall.MSD+xml, in the INVITE request message body, as described in draft-gellens-ecrit-ecall-01.
The XML definition is based on CEN EN 15722 (eCall minimum set of data Road transport and traffic telematics - eSafety - eCall minimum set of data). 3GPP needs to consider the MIME Content-type Registration for 'application/ emergencyCall.eCall.MSD+xml'. Also IETF drafts in the dependency need to be checked.
The UE should receive acknowledgement from the PSAP confirming its reception of the MSD, also the UE may receive a request from the PSAP to resend the MSD or provide a new MSD. The eCall shall only be termination by the PSAP. SIPINFO method / RFC 6086 is foreseen to serve the purpose of this additional UE –PSAP communication. 3GPP needs to define the SIP-INFO package for eCall.
Privacy and data protection of the voice component and the MSD follows the same requirement on MNO for other telecommunications services.
As described in 3GPP TS 22.101, the eCall only UE, determined by information configured in the USIM, has limitation in the services it may receive based on the information configured in the USIM. The eCall only UE can initiate eCall emergency services and received call-back from the PSAP. The eCall only UE may perform test and reconfiguration services (non-emergency services). The reconfiguration of eCall only UE removes these restrictions.
The test URN needs to be registered with IANA, in alignment with RFC 6881 that may take the form of URN "urn:service:test.sos.ecall".
Note: it is preferred to keep the eCall session running for example one hour to allow the PSAP operator to communicate with the vheicle occupans and to request data (MSD) if required. This is to prevent the need to perfrom call-back that might fail for different reasons.
The changes are summerised as:
1-adding refrence to Next-Generation Pan-European eCall; draft-gellens-ecrit-ecall-01.
2-providing reference to eCall, eCall only mode, MSD definitions
3-adding in several places the eCall URNs reference defined in draft-gellens-ecrit-ecall-01. This is to complete the other service URNs with a top level service type “SOS”.
4-clarifying that the INVITE message shall carry MSD as defined in draft-gellens-ecrit-ecall-01.
5- for the mapping between type of emergency service and emergency URN in TableB.2.2.6.1 and TableL.2.2.6.1, the manually initiated eCall and automatically initiated eCall are added.
Note: There are still several points that need to be taken into consideration and included in the updated revision when discussing this CR, as indicated in the summery of the eCall feature above.
Note: Refer to ETSI MSG TR103140 for detiled analysis of different solution options and the conclusion on the selected solution.
Clauses affected: / 2, 3.1, 5.1.6.8.1, 5.1.6.8.3, 5.4.3.2, 5.7.1.14, 5.10.3.2, 5.11.2, 5.11.3, B.2.2.6, L.2.2.6.
Other deliverables
affected:
Other comments:
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
· References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific.
· For a specific reference, subsequent revisions do not apply.
· For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPPTR21.905: "Vocabulary for 3GPP Specifications".
[1A] 3GPPTS22.101: "Service aspects; Service principles".
[1B] 3GPPTS22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[2] 3GPPTS23.002: "Network architecture".
[3] 3GPPTS23.003: "Numbering, addressing and identification".
[4] 3GPPTS23.060: "General Packet Radio Service (GPRS); Service description; Stage2".
[4A] 3GPPTS23.107: "Quality of Service (QoS) concept and architecture".
[4B] 3GPPTS23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[4C] 3GPPTS23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[4D] 3GPPTS23.140 Release 6: "Multimedia Messaging Service (MMS); Functional description; Stage 2".
[5] 3GPPTS23.218: "IP Multimedia (IM) Session Handling; IM call model".
[6] 3GPPTS23.221: "Architectural requirements".
[7] 3GPPTS23.228: "IP multimedia subsystem; Stage2".
[7A] 3GPPTS23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking; System description".
[7B] 3GPPTS23.401: "GPRS enhancements for E-UTRAN access".
[7C] 3GPPTS23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage2".
[7D] 3GPPTS23.380: "IMS Restoration Procedures".
[7E] 3GPPTS23.402: "Architecture enhancements for non-3GPP accesses".
[7F] 3GPPTS23.334: "IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW) interface".
[8] 3GPPTS24.008: "Mobile radio interface layer3 specification; Core Network protocols; Stage3".
[8A] 3GPPTS24.141: "Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage3".
[8B] 3GPPTS24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage3".
[8C] 3GPPTS24.234: "3GPP System to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage3".
[8D] Void.
[8E] 3GPPTS24.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services, stage3, Release7".
[8F] 3GPPTS24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage3".
[8G] 3GPPTS24.167: "3GPP IMS Management Object (MO); Stage3".
[8H] 3GPPTS24.173: "IMS Multimedia telephony communication service and supplementary services; Stage3".
[8I] 3GPPTS24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[8J] 3GPPTS24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage3".
[8K] 3GPPTS24.323: "3GPP IMS service level tracing management object (MO)".
[8L] 3GPPTS24.341: "Support of SMS over IP networks; Stage3".
[8M] 3GPPTS24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage3".
[8N] 3GPPTS24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem".
[8O] 3GPPTS24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage3".
[8P] 3GPPTS24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[8Q] 3GPPTS24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification".
[8R] 3GPPTS24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification".
[8S] 3GPPTS24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem".
[8T] 3GPPTS24.305: "Selective Disabling of 3GPP User Equipment Capabilities (SDoUE) Management Object (MO)".
[8U] 3GPPTS24.302: "Access to the Evolved Packet Core (EPC) via non-3GPP access networks; Stage3".
[8V] 3GPPTS24.303: "Mobility management based on Dual-Stack Mobile IPv6".
[8W] 3GPPTS24.390: "Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS".
[8X] 3GPPTS24.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage3".
[9] 3GPPTS25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
[9A] 3GPPTS25.331: "Radio Resource Control (RRC); Protocol Specification".
[9B] 3GPPTS26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[10] Void.
[10A] 3GPPTS27.060: "Mobile Station (MS) supporting Packet Switched Services".
[11] 3GPPTS29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services and Packet Data Networks (PDN)".
[11A] 3GPPTS29.162: "Interworking between the IM CN subsystem and IP networks".
[11B] 3GPPTS29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks".
[11C] 3GPPTS29.161: "Interworking between the Public Land Mobile Network (PLMN) supporting Packet Based Services with Wireless Local Access and Packet Data Networks (PDN)"
[11D] 3GPPTS29.079: "Optimal Media Routeing within the IP Multimedia Subsystem".
[12] 3GPPTS29.207 Release6: "Policy control over Go interface".
[13] Void.
[13A] 3GPPTS29.209 Release6: "Policy control over Gq interface".
[13B] 3GPPTS29.212: "Policy and Charging Control (PCC); Reference points".
[13C] 3GPPTS29.213: "Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping".
[13D] 3GPPTS29.214: "Policy and Charging Control over Rx reference point".
[14] 3GPPTS29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".
[15] 3GPPTS29.229: "Cx and Dx Interfaces based on the Diameter protocol, Protocol details".
[15A] 3GPPTS29.311: "Service Level Interworking for Messaging Services".
[15B] 3GPP TS 31.103: "Characteristics of the IP multimedia services identity module (ISIM) application".
[15C] 3GPPTS31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[15D] 3GPPTS31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)".
[16] 3GPPTS32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[17] 3GPPTS32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[17A] 3GPPTS32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
[18] 3GPPTS33.102: "3G Security; Security architecture".
[19] 3GPPTS33.203: "Access security for IP based services".
[19A] 3GPPTS33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[19B] 3GPPTS36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[19C] 3GPPTS33.328: "IP Multimedia Subsystem (IMS) media plane security".
[20] 3GPPTS44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol".
[20A] RFC2401 (November1998): "Security Architecture for the Internet Protocol".
[20B] RFC1594 (March1994): "FYI on Questions and Answers to Commonly asked "New Internet User" Questions".
[20C] Void.
[20D] Void.
[20E] RFC2462 (November1998): "IPv6 Stateless Address Autoconfiguration".
[20F] RFC2132 (March1997): "DHCP Options and BOOTP Vendor Extensions".
[20G] RFC 2234 (November 1997): "Augmented BNF for Syntax Specification: ABNF".
[21] RFC2617 (June1999): "HTTP Authentication: Basic and Digest Access Authentication".
[22] RFC3966 (December2004): "The tel URI for Telephone Numbers".
[23] RFC4733 (December2006): "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals".
[24] RFC6116 (March2011): "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)".
[25] RFC6086 (October2009): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[25A] RFC3041 (January2001): "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".
[26] RFC3261 (June2002): "SIP: Session Initiation Protocol".
[27] RFC3262 (June2002): "Reliability of provisional responses in Session Initiation Protocol (SIP)".
[27A] RFC3263 (June2002): "Session Initiation Protocol (SIP): Locating SIP Servers".
[27B] RFC3264 (June2002): "An Offer/Answer Model with Session Description Protocol (SDP)".
[28] RFC3265 (June2002): "Session Initiation Protocol (SIP) Specific Event Notification".
[28A] Void.
[29] RFC3311 (September2002): "The Session Initiation Protocol (SIP) UPDATE method".
[30] RFC3312 (October2002): "Integration of resource management and Session Initiation Protocol (SIP)".
[31] RFC3313 (January2003): "Private Session Initiation Protocol (SIP) Extensions for Media Authorization".
[32] RFC3320 (March2002): "Signaling Compression (SigComp)".
[33] RFC3323 (November2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[34] RFC3325 (November2002): "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks".
[34A] RFC3326 (December2002): "The Reason Header Field for the Session Initiation Protocol (SIP)".
[35] RFC3327 (December2002): "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts".
[35A] RFC3361 (August2002): "Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) Servers".
[36] RFC3515 (April2003): "The Session Initiation Protocol (SIP) REFER method".
[37] RFC3420 (November2002): "Internet Media Type message/sipfrag".
[37A] RFC 3605 (October 2003): "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)".
[38] RFC3608 (October2003): "Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration".
[39] RFC4566 (June2006): "SDP: Session Description Protocol".
[40] RFC3315 (July2003): "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
[40A] RFC 2131 (March1997): "Dynamic host configuration protocol".
[41] RFC3319 (July2003): "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers".
[42] RFC3485 (February2003): "The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) static dictionary for Signaling Compression (SigComp)".
[43] RFC3680(March2004): "A Session Initiation Protocol (SIP) Event Package for Registrations".
[44] Void.
[45] Void.
[46] Void.
[47] Void.
[48] RFC3329 (January2003): "Security Mechanism Agreement for the Session Initiation Protocol (SIP)".
[49] RFC3310 (September2002): "Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA)".
[50] RFC3428 (December2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[51] Void.
[52] draft-drage-sipping-rfc3455bis-06 (November2012): "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.
[53] RFC3388 (December2002): "Grouping of Media Lines in Session Description Protocol".
[54] RFC3524 (April2003): "Mapping of Media Streams to Resource Reservation Flows".
[55] RFC3486 (February2003): "Compressing the Session Initiation Protocol (SIP)".
[55A] RFC3551 (July2003): "RTP Profile for Audio and Video Conferences with Minimal Control".
[56] RFC3556 (July2003): "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth".