ecall days germany 2016 sept. 22-23, hamburg, …...– refarming frequency bands from 2g to 3g in...

Ralf Weber

eCall Technology Evolution in the EU and other Regions of the World

eCall Days Germany 2016 Sept. 22-23, Hamburg, Germany

2 Standards & Industry Organizations (QSIO)

Disclaimer

Not to be used, copied, reproduced in whole or in part, nor its contents revealed in any manner to others without the express written permission of Qualcomm.

QUALCOMM is a registered trademark of QUALCOMM Incorporated in the United States

and may be registered in other countries. Other product and brand names may be trademarks or registered trademarks of their respective owners.

This technical data may be subject to U.S. and international export, re-export or transfer

(“export”) laws. Diversion contrary to U.S. and international law is strictly prohibited.

QUALCOMM Incorporated 5775 Morehouse Drive

San Diego, CA 92121-1714

Copyright © 2016 QUALCOMM Incorporated. All rights reserved.


Outline

What happened so far … eCall Evolution in Europe IMS eCall Standardization Status IMS eCall Migration and Interworking eCall in other Regions Conclusions


eCall Evolution in Europe


What happened so far …

2005: EC tasked ETSI MSG to develop

eCall modem

2008: ETSI/3GPP

eCall modem

competition

2011: HeERO1 Start & MNO

Recommendation for

MS

2012: Qualcomm

Europe Field Trial

2013: HeERO2 Start &

ETSI NG eCall STF

& EU regulation for PSAPs

2015: EU IVS Type-Approval

Adoption & I_HeERO

Start


eCall Transmission Chain

Our main focus


eCall Transmission Chain (cont’d) eCall In-band Modem in MNO Environment

IVSData

modem

Speech Codec

MSD information

source

Microphone & Speakers

Radio Modem

Public-Safety Answering Point (PSAP)

PSAP Data

Modem

MSD Display

Microphone & Speakers

In-Vehicle System (IVS)

GPSReceiver

position data

PSTN/GSTN

Radio

Modem(BTS)

Speech Trans-coding (TRAU)

Mobile Switching

Center(MSC)

PLMN

IVS or PSAP initiates MSD transmission within the 112 call (‘push’ / ‘pull’)

- ‘push’ mode used for 1st MSD transmission Voice path is muted until MSD is correctly

received

Digital Voice Transmission

System

PCM (Signed 16bit, 8kHz)

PCM (G.711, A-Law,

8bit, 8kHz)


Network Environment Evolution

Speech

Data

IVS MNO FNO PSAP

CS-Domain

PS-Domain

Speech

Data

CS-Domain

PS-Domain

2G/3G network separating speech and data transmission over CS and PS domains

All NW components separate speech and data over CS and PS domains


MSD in

MSD out

Network Environment Evolution

Speech

Data

IVS MNO FNO PSAP

CS-Domain

PS-Domain

Speech

Data

CS-Domain

PS-Domain


All NW components separate speech and data over CS and PS domains

In-band modem eCall


Network Environment Evolution (cont’d)

Speech

Data

IVS MNO FNO PSAP

CS-Domain

PS-Domain

VoIP GW Speech

Data

VoIP GW

PS-Domain

FNO combines speech with data through Voice-over-IP gateways (VoIP GW)




Speech

Data

IVS MNO FNO PSAP

PS-Domain

Speech

Data

VoIP GW

PS-Domain

VoIP GW

2G/3G network combining speech and data transmission over PS domains

MNO and FNO combine speech with data through Voice-over-IP gateways (VoIP GW)



Speech

Data

IVS MNO FNO PSAP

PS-Domain

PS-Domain

VoIP GW

Speech

Data

VoIP GW

3.5G/4G networks can transport speech purely over PS domain through VoIP IVS devices require fallback to CS domain if networks do not support VoIP

End-to-end speech and data combination through Voice-over-IP gateways (VoIP GW)


MSD in

MSD out

eCall for Future Networks

Speech

Data

IVS MNO FNO PSAP

PS-Domain

PS-Domain

VoIP GW

Speech

Data

VoIP GW

Recommended by ETSI – Using IMS Emergency Services requires only small enhancements to support eCall – Provides end-to-end resource reservation and call prioritization

IMS eCall 3GPP

IETF

CEN ETSI S

cope


IMS eCall Standardization Status 3GPP (3rd Generation Partnership Project)

– Covers mobile communication aspects for IMS in Rel. 14 – Emergency call requirements for IMS – stable – IMS eCall requirements and migration from CS eCall – stable

IETF (Internet Engineering Task Force) – Covers internet protocol (IP) aspects – ‘additional-data’ draft (RFC 7852) - stable

• Transmit any registered data block with emergency call – ‘eCall’ draft - stable

• Focuses on next generation eCall specific needs for the EU • Carries data and metadata/control objects per ‘additional-data’ mechanism • Metadata/control (ack, retransmission, requests to vehicle, etc.)

ETSI (European Telecommunication Standards Institute) – TR 103 140 recommends to use 3GPP and IETF for eCall - done

CEN (Comité Européen de Normalisation) – EN 16072 (eCall requirements) needs an equivalent for IMS eCall – Started – EN 16062 (HLAP) needs reference to 3GPP IMS and IETF – Started – Future data objects for new categories – Now starting


IMS Network Availability Aspects Todays 2G/3G networks are mature and provide best coverage 4G network deployments increases but still lack coverage in certain regions

– IMS emergency call capability over VoIP is not yet commonly available – IVS can use CS fallback (CSFB) to transition to 2G/3G for making an in-band eCall

Mobile network operators (MNO) are continuously expanding their networks – Replacing infrastructure with newer standard revisions – Refarming frequency bands from 2G to 3G in order to benefit from higher capacity – Increasing 4G VoIP coverage

Availability of mobile emergency calls is determined by the coverage overlay of all available networks in the incident area

– IVS performs domain selection based on supported technologies

During the migration phase, there may be situations where e.g. – Only 4G networks are available but no IMS capable PSAP – A handover from 4G to 2G/3G happens after an IMS eCall was established due to lack

of 4G coverage (e.g. car drives out of 4G coverage)

3GPP provides interworking mechanisms to handle such cases (see next slides)


3GPP Domain Selection Any IVS that supports IMS eCall will also support CS eCall Hence IVSs supporting IMS eCall will need to perform domain selection A new IMS eCall flag (defined by 3GPP RAN2) will indicate to an IVS whether

IMS eCall is supported in any cell A PLMN can set the flag to indicate support if:

– The PLMN (or all PLMNs with LTE RAN sharing) supports IMS eCall AND – At least one PSAP associated with (or reachable from) the cell is IMS eCall capable

Domain selection for eCall is performed based on any IMS eCall flag and whether CS or PS domains are available

The PS domain (LTE) is chosen when available if the IMS eCall flag is set Otherwise an available CS domain will be chosen


3GPP 4G Architecture for IMS eCall with an IMS capable PSAP (IMS eCall flag = 1) The signaling path

rather than voice path is used to transfer the MSD from the IVS to the PSAP

Initial MSD can be transferred during call setup procedure and an updated MSD can be transferred during an eCall

UE eNB MME GMLC

E-SLP

E-SMLC

Location Servers

LRF

RDF

MGCF

IP Capable PSAP

Legacy CS PSAP

BGCF

IBCFE-CSCF

S-CSCF

P-CSCFPDN

GatewayServing Gateway

IMSEPS

IVS

MGW

Signaling Path

Voice Path

VoIP

EATF

1

2


3GPP 4G Architecture for IMS eCall with a legacy CS capable PSAP (IMS eCall flag = 0) The MSD cannot be

transferred using the signaling path

The MSD is transferred over the voice path using the same data modem as for CS eCall in Rel-13

The transcoding from VoIP to CS voice at the MGW can degrade in-band MSD transfer reliability and increase delay and is a solution of last resort

UE eNB MME GMLC

E-SLP

E-SMLC

Location Servers

LRF

RDF

MGCF

IP Capable PSAP

Legacy CS PSAP

BGCF

IBCFE-CSCF

S-CSCF

P-CSCFPDN

GatewayServing Gateway

IMSEPS

IVS

MGW

Signaling Path

Voice Path

VoIP

CS Voice(e.g.PCM)

SIP

SIP

ISUP

SIP

EATF

1

2


Handover of an IMS eCall from LTE to CS with an IMS PSAP After handover (HO),

any updated MSD must be transferred in-band from the IVS to the PSAP

The PSAP will be aware of the handover and has to switch to in-band mode after the HO

PS Domain

CS Domain

UE eNB MME

SGW PDG P-CSCF E-CSCF

EATF

IBCF ES IP Network PSAP

GERAN/UTRAN

Target MSC

MSC Server MGCF

MGW

I-CSCF

+

Initial Signaling Path

Final Signaling Path

Initial Voice Path

Final Voice Path

ES Emergency Services

IVS

IMS eCall Flag = 0

IMS eCall Flag = 1

1

2

3

4


Handover of an eCall from LTE to CS with a legacy CS PSAP The MSD continues to

be transferred in-band between the IVS and PSAP

The PSAP is not aware that handover has occurred

CS Domain

PS Domain

CS Domain

UE eNB MME

SGW PDG P-CSCF E-CSCF

EATF

MGCF 2

Legacy ES

NetworkPSAP

GERAN/UTRAN

Target MSC

MSC Server MGCF 1

MGW 1

I-CSCF

MGW 2

+

Initial Signaling Path

Final Signaling Path

Initial Voice Path

Final Voice Path

ES Emergency Services

IVS

IMS eCall Flag = 0

IMS eCall Flag = 0

1

2

3

4


Example: IMS SIP Call Flow

1) IVS initiates eCall

2) PSAP acks MSD reception

3) IVS starts media streams

4) PSAP requests a new MSD

5) IVS acks MSD requests

6) IVS sends new MSD

7) PSAP acks MSD reception

8) PSAP hangs up

9) IVS stops media streams

10)IVS confirms call end


MSD Transfer and Interoperability With an IMS capable PSAP, the MSD is transferred along the signaling path

using SIP messages (SIP INVITE for initial MSD, SIP INFO for updated MSD) With a legacy CS capable PSAP, the MSD cannot be transferred along the

signaling path due to restrictions on the CS side The PSAP and IVS then need to fall back to transfer the MSD along the voice

path using the in-band modem used for CS eCall This is a solution of last resort as the in-band modem is not designed for voice

path transfer using LTE and with transcoding in an MGW, and performance can degrade

3GPP mandates support of CS eCall by any IVS that supports IMS eCall to enable a gradual transition from CS eCall to IMS eCall


Interworking Scenarios

IVS that supports IMS eCall has to also support in-band eCall (3GPP requirement) PSAP that supports IMS eCall should be also support (A) in-band eCall over VoIP

and (B) in-band CS eCall, so long as there exist CS only IVSs and CS only NWs This leads to the following basic scenarios:

a) CS only NW can connect to a legacy PSAP or an IMS PSAP with (B) b) PS only NW without full support for IMS eCall can connect to a legacy PSAP** or an IMS

PSAP with (A)** c) PS NW with full support for IMS eCall can connect to a legacy PSAP** or IMS PSAP

For cases indicated by **, MSD is transferred in-band over VoIP, which will reduce transfer reliability and increase delay. These cases can be avoided if prior to phase out of CS, NWs and PSAPs upgrade to IMS eCall support

IVS always uses CS eCall origination unless IMS eCall support is indicated by MNO

Available Network (NW)

PSAP Legacy Multi-mode

IVS

Legacy CS only CS In-band CS In-band

Multi-mode

CS only CS In-band CS In-band PS only VoIP In-band** VoIP In-band**

PS only + IMS VoIP In-band** IMS

Provided by 3GPP


eCall Evolution in other Regions


eCall Status in Russia Following ERA-GLONASS regulation

ERA-GLONASS eCall regulation is based on GOST standards – Draft interstate standard from 2015 includes revised requirements – Since 2015 mandate for vehicle categories M1 and N1 – From 2017 onwards, mandate for all vehicle categories in Russia sold first time

eCall technology also employs in-band modem over CS networks – Fallback to SMS if MSD transmission is not possible via in-band – No evolution plans for PS networks yet

Other main differences to Pan-EU eCall – Requirement for GNSS compatibility with GLONASS and GPS – IVS must support 2G GSM and 3G UMTS technologies – Requirement for dual profile USIM support (Glonass-Union + commercial MNO) – Over-the-air vehicle management actions possible, e.g.

• Initiating test eCalls • Providing test analysis results back to PSAP server • Initiating SW updates

– Detailed GNSS and MSD transmission performance requirements – Detailed audio quality performance requirements based on ITU-T standards


eCall Status in China High interest in emergency call technology

Emergency Call started attracting public attention in China – As eCall mandatory in EU, eCall equipped vehicle get into China market. – More and more auto makers are cooperating with TSPs to provide emergency service

as part of telematics service package. Several standard bodies and organizations are jointly developing standards for

end-to-end emergency call service, from terminal/IVS, to call center to dispatch platform

– TIAA is responsible for answering point and dispatch platform and relevant interface. – CCSA is developing communication standards including in-band eCall and NG-eCall. – Terminal/IVS specification is pending.

No decision to establish national-wide PSAP yet, emergency call will be deployed in China as PPP (Public Private Partnership) mode

– Auto makers and TSPs to provide access service – 3rd party dispatch center (service proxy) will provide rescue service

Inter-border emergency call joint trial is being planned – Sino-Russia eCall trial is planned in May’17 as part of Sino-Russia Rally


eCall Status in China (cont’d) System architecture concept FAP (First Answering Point) pick up the call and

filter out the fault alert emergency call Service Proxy to organize and coordinate

rescue and service by multiple organizations and vendors

The interface between FAP and Service Proxy will be standardized

Multiple communication solutions will be adopted to differentiate among TSP

FAP (First Answering

Point) IVS

Service Proxy

Service 1 (Medical)

Service 2 (Car Rescue)

Service 3 (Traffic Police)

Service 4 (Insurance)

MSD

CS Call

Communication Part Rescue Part

PS + CS

eCall

NG-eCall (IMS)

10 sec

CS PS

TBox TSP Rescue Org.

1. Voice Call 1.1 Emergency data

2. three-party Call

3. Forward Emerg. data


eCall Status in Gulf Countries Timeline for eCall specifications

Gulf Countries Committee (GCC) decided to use Pan-EU eCall Emirates Standardization and Metrology Authority (ESMA) tasked GCC

Standardization Organization (GSO) to develop GCC standard

Final comments expected for the next GSO meeting in September ESMA already translated the GCC eCall Specifications into Arabic for submissions

to the UAE Prime Minister Cabinet – Make the eCall specifications mandatory in UAE – Confirm the 2018 date of the application to new cars being imported in UAE as still

pushed by UAE eCall National Committee Then same national actions to be replicated in other GCC countries

January 2016

•Notification to WTO of the GCC Specifications for eCall

April 2016

•End of the consultation period and comments from BMW, European Union and American Automotive Policy Council

May 2016

•Acknowledgement of comments

•Modifications of GCC specifications

July 2016

•GSO meeting for final validation of new GCC specifications postponed to September

September 2016

•Meeting planned on 25-27th of September for final validation

October 2016

•Submission of the Specifications to UAE Cabinet to make the GCC Specifications mandatory


Status of eCall in other Regions Turkey

- eCall based on Pan-EU eCall mandated for all vehicles starting 2018 USA & Canada

- Proprietary 3rd-Party services (TPS) available (e.g. OnStar, Ford etc) - No standard interfaces between IVS, TPSP and PSAP

Verbal communication of location and crash data between TPSP and PSAP - IMS eCall over PS networks may employ also same IETF mechanisms for TPSP services - No eCall mandate planned

Korea - Looking into standardization of eCall for 4G systems and beyond - May reuse IMS eCall mechanisms from 3GPP and IETF - eCall mandate not yet decided

Japan - Proprietary TPS “HELPNET” started nationwide already in 2000 (privately owned) - MSD conveyed via PS data bearer prior to voice communication

Includes ‘travel trail’ data to estimate driving trajectory, speed change and phone # - “Dcall” extension includes passenger injury prediction algorithm used as severeness indicator - eCall mandate not yet decided

Australia - Showed interest in Pan-EU eCall - Further consultations planned during ITS World Congress 2016 in Melbourne


Conclusions


Conclusions eCall is targeted to save lives

PSAPs should retain in-band capability as long as some CS networks and IVSs exist – Ensures increased network coverage and thus the chance to setup an eCall – However, PSAPs should consider to make provisions now such that they can upgrade to IMS later

For non-eCall-only IVSs, a mid term solution is to use CS eCall on 2G/3G instead of packet-switched networks like LTE, even if the IVS is IMS capable

– i.e. employing 2G/3G CS fallback (CSFB) mechanism – CS eCall-only IVS shall not register on an LTE network

From a certain date, all IVSs should support both CS and IMS eCall – Even if PSAPs are upgraded to support IMS eCall then they should still continue to support CS eCall

for legacy devices and 4G coverage border scenarios – An IMS eCall broadcast flag is proposed to instruct dual-mode IVS to place an eCall over IMS when

this is supported end-to-end by the network and the PSAP IMS eCall introduction will happen only gradually over time, when MNOs upgrade their

networks with IMS emergency services based on economic considerations – It is not expected that IMS eCall will be mandated in the near future because it would mean a huge

investment for MNOs and PSAP operators IMS eCall paves the way for “Next Generation” eCall

– Allows the integration of new features and applications – Can further improve time and cost efficiency of rescue services for saving lives


Thank You ! Questions?

Contact: - Ralf Weber (rweber @ qualcomm.com)

mailto:[email protected]


Backup Slides


Selected Acronyms 3GPP = 3rd Generation Partnership Project

BGCF = Breakout Gateway Control Function

CS = Circuit Switched

CSCF = Call Session Control Function

EATF = Emergency Access Transfer Function

E-CSCF = Emergency-CSCF

eNB = evolved NodeB

EPS = Evolved Packet System

ES = Emergency Services

E-SLP = Evolved SUPL Location Platform

E-SMLC = Evolved Serving Mobile Location Centre

GERAN = GSM EDGE Radio Access Network

GMLC = Gateway Mobile Location Centre

GSM = Global System for Mobile communication

IBCF = Interconnection Border Control Function

I-CSCF = Interrogating-CSCF

IMS = Internet Multimedia Subsystem

ISDN = Integrated Services Digital Network

ISUP = ISDN User Part

IVS = In-Vehicle System

LRF = Location Retrieval Function

LTE = Long Term Evolution

MGCF = Media Gateway Control Function

MGW = Media Gateway

MME = Mobility Management Entity

MSC = Mobile Switching Centre

MSD = Minimum Set of Data

P-CSCF = Proxy-CSCF

PDN = Packet Data Network

PGW = PDN Gateway

PS = Packet Switched

PSAP = Public Safety Answering Point

PSTN = Public Switched Telephone Network

RDF = Resource Description Framework

S-CSCF = Serving-CSCF

SGW = Serving Gateway

SIP = Session Initiation Protocol

SUPL = Secure User Plane Location Protocol

UE = User Equipment (=IVS)

UMTS = Universal Mobile Telecommunications System

UTRAN = UMTS Terrestrial Radio Access Network

VoIP = Voice over IP

ecall days germany 2016 sept. 22-23, hamburg, …...– refarming frequency bands from 2g to 3g in...

Documents