Ecall Standards Update v2

download Ecall Standards Update v2

of 24

Embed Size (px)


Ecall Standards Update v2

Transcript of Ecall Standards Update v2

  • eCall standards update

    David Williams, Qualcomm

  • Contents

    Completed standardisation work in ETSI/3GPP

    Completed standardisation work in CEN

    Field trial results

    Future work in CEN

    Future work in ETSI/3GPP

  • Completed standardisation in 3GPP eCall standardisation in 3GPP Release 8 was completed in December 2009 (SA#46). Service requirements were done in SA1.

    ETSI TS 122 101 clause 10.7 and A.27

    Layer 3 protocol changes were done in CT1. ETSI TS 124 008 clause (eCall flag) and clause 4 (inactive substate) ETSI TS 127 007 clause 6.27 (CECALL command)

    USIM aspects were done in CT6 ETSI TS 131 102 clauses 4 and 5 (service number 89)

    In-band modem was done in SA4 ETSI TS 126 267 in band modem description ETSI TS 126 268 in band modem ANSI-C code ETSI TS 126 269 in band modem test specification ETSI TR 126 969 in band modem characterisation report

    UTRAN protocol testing was done in RAN5 ETSI TS 134 123 clause 13.3.1 Early implementation of eCall in Release 7 is certifiable.

    GERAN protocol testing was done in GERAN3 ETSI TS 151 010 clause 26.9.6

  • Completed standardisation in CEN EN15722 Minimum Set of Data

    Defines the 160 bytes that comprise the MSD

    EN16072 High Level Application protocol Defines the procedures and processes required to provide the eCall service

    using a TS12 emergency call over a mobile communications network.

    EN16072 Pan European Operating Requirements Defines the general operating requirements and intrinsic

    EN16102 Third Party Services Supported eCall Defines transfer of an emergency message and establishment of a voice call

    between a vehicle and a 'Third Party Service Provider' (TPSP)

    Defines the transfer of data from a TPSP to the most appropriate PSAP

    TR0278316 eCall end to end conformance testing Demonstrates conformance with EN16062 and EN16072

    Default to PE eCall in the event of TPS eCall failure

    Due to be published in late 2012. Resolution meeting will be in September.

  • Availability of ETSI and CEN standards

    CEN standards are purchased from a National Standards Organisation

    ETSI standards can be downloaded free of charge (registration is required)

  • eCall Drive Tests 48 Networks in 15 countries

    22 stationary locations

    12 mobility routes

    >16000 calls

    >25000 MSD transmissions

    February 2012

    International roaming calls to test PSAP in Nuremberg








    IVS Control

    via QXDM









    located in Nuremberg,


  • Conclusions of Drive Test Extensive drive tests carried out to investigate performance of eCall in-

    band modem Good overall performance, even in the presence of network echo

    cancellers Excellent success rate for the case of disabled NECs: >98% Only a small number of 3-4 problematic networks

    not necessary to use disabler tone everywhere

    Further performance optimization by parameter adaptations: >99% Detailed failure analysis required:

    implementation bugs at IVS and PSAP abnormal network behavior call setup and retention performance real modem transmission failures

    Half-Duplex unlikely to achieve overall performance improvement

  • Future work in ETSI/3G A New Work Item was agreed at ETSI MSG#29 (29 March) on

    Migration of eCall Transport Assessment of in-band modem solution in case of no use of Circuit Switched


    Study the adaptation of IMS emergency call and IMS Multimedia Emergency Service for supporting current and future service required by eCall

    Hybrid CS/IMS solution (scenarios for PSAPs and IVS implementations)

    Migration recommendations (how and when to migrate from CS to IMS only)

    Request for ETSI STF funding under the EC 2009-2013 ICT Standardisation Work Program

    Call for experts expected in Q3 (subject to funding approval)

    Technical Report scheduled for publication end of Q1/13

  • Future work in CEN

    Possible extension of MSD standard, e.g. Accelerometer, car doors open, seat belts

    Discussions on motorcycle eCall

    Discussions on personal eCall

    Amendment to HLAP using results obtained in HeERO, e.g. Mapping of AL-ACK bits

    Introduce the echo canceller tone procedure

    Change 2s timeout value to 5s to allow a 2.1kHz echo canceller tone to be sent

    Add PULL mode (beside PUSH) as option for the PSAP to start the transmission

    Possible work on eCall for LTE


  • List of ETSI and CEN Standards

    Title Number Latest Version (as of 1st April 2012)

    eCall requirements for data transmission 3GPP TS 22.101

    ETSI TS 122 101


    eCall Discriminator Table 10.5.135d 3GPP TS 24.008

    ETSI TS 124 008


    eCall Data Transfer; In-band modem solution;

    General Description

    3GPP TS 26.267

    ETSI TS 126 267


    eCall Data Transfer; In-band modem solution;

    ANSI-C Reference Code

    3GPP TS 26.268

    ETSI TS 126 268


    eCall Data Transfer; In-band modem solution;

    Conformance Testing

    3GPP TS 26.269

    ETSI TS 126 269


    eCall Data Transfer; in-band modem solution;

    Characterisation Report

    3GPP TS 26.969

    ETSI TS 126 969


    eCall minimum set of data CEN EN 15722

    Pan European eCall Operating Requirements CEN EN 16072

    High Level Application Protocols CEN EN 16062

    Data registry procedures ISO/EN 24978:2009

  • STF399 Deliverables

    ETSI TS 102 936 -1 eCall Network Access Device (NAD) conformance specification, Part 1: Protocol test specification Contains normative references to tests which are used to show compliance

    of an eCall terminal with eCall features in 3GPP specifications.

    ETSI TS 102 936-2 eCall Network Access Device (NAD) conformance

    specification, Part 2: Test Suites Contains the TTCN code.

    ETSI TR102 937 eCall communications equipment ; Conformance to R&TTE Directive, EC Regulations for eCall and EC Vehicle regulations. Describes how compliance with the R&TTE Directive is achieved. Describes the EU Commission intentions for deploying eCall (note the text is

    about 12 months old and superseded) Describes an analysis of UNECE (motor vehicle) regulations and their

    applicability to eCall

  • List of UTRAN eCall test cases

    Clause Title Test eCall using eCall capable MS with eCall only subscription on USIM Manually initiated eCall using eCall capable MS with eCall only subscription on USIM Manually initiated eCall using eCall capable MS with eCall capable USIM eCall after T3242 expires Automatically initiated eCall Reconfiguration Call using eCall capable MS with eCall only subscription on USIM

    A supplementary test on T3243 was added

  • List of GERAN eCall tests Clause Title

    26.9.6a.1.2 Test Call using eCall capable MS with eCall only subscription on USIM

    26.9.6a.1.3 Manually initiated eCall using eCall capable MS with eCall only subscription on USIM

    26.9.6a.1.4 Manually initiated eCall using eCall capable MS with eCall capable USIM

    26.9.6a.1.5 eCall after T3242 expires

    26.9.6a.1.6 Automatically initiated eCall

    26.9.6a.1.7 Reconfiguration Call using eCall capable MS with eCall only subscription on USIM

    It is intended to add a test on T3243

  • Contents/format of the MSD

    Block No.

    Name Description

    1 Format version MSD format version set to 1 to discriminate from later MSD formats

    2 Message Identifier

    incremented with every retransmission

    3 Control Automatic or manual activation, position trust indicator, vehicle class

    4 Vehicle ID VIN number according to ISO 3779

    5 Fuel type Gasoline, diesel, etc

    6 Time stamp Timestamp of incident event

    7 Vehicle Location

    Position latitude/longitude (ISO 6709)

    8 Vehicle direction 2degrees steps

    Mandatory parts

  • Contents/format of the MSD

    Block No.

    Name Description

    9 Recent Vehicle Location n-1

    Latitude/longitude Data

    10 Recent Vehicle Location n-2

    Latitude/longitude Data

    11 No. of passengers

    Minimum known number of fastened seatbelts omitted if no information is available

    12 Optional additional data

    e.g. passenger data

    Optional parts

  • HLAP, send MSD, lower layers

  • HLAP, send MSD, higher layers

  • TPS ecall system

  • eCall for HGV

    The following expansion of the MSD in EN 15722 is for HGVs: Truck type (suited for dangerous goods =true, standard goods = false) If truck type = true

    Dangerous goods present/not present (false, true) Coding protocol (1 byte) if coding protocol = 1

    Phone number of Truck Operator For 6 goods (the most dangerous first if a truck has more than 6

    goods, or zero-padded for trucks with less than 6) : UN number Quantities Package group

    if coding protocol = 2 IPv6 address information endpoint Password (8 characters)

  • HeERO Standardisation Task Force

    Discusses results of European HeERO eCall trials Analyses real-world performance of eCall system Develops proposals for standards changes Currently discussed change requests:

    Consistency of terminology between CEN and 3GPP standards Introduce option in CEN HLAP for PSAP to employ an NEC disabler tone

    according to ITU standards, if required Relaxed PUSH timeout value (2s 5s) Introduce new timer for PULL (START) messages, allow PULL mode as

    alternative to PUSH mode Specify exact number of HL-ACK messages to be transmitted by PSAP Clarification on HL-ACK message contents, bit mapping, and

    procedures Optimized setting of uplink synch tracking parameters as result of field


  • Stationary tests

    1. Single MSD transmission per call (PUSH mode = D1S)

    Repeated 20x with toggling disabler tone every other call

    New call started after CLEARDOWN or expired call duration timer (30s)

    2. Multiple MSD transmissions per call (PUSH-PULL-PULL mode = PPP)

    Repeated 100x with toggling disabler tone every other call

    New call started after CLEARDOWN by last PULL or expired call duration timer (80s)

    3. Half-Duplex emulation using fixed PCM TX data for PSAP and IVS per call (HD)

    Repeated 50x without disabler tone every 45s

    Mobility tests

    Drive routes cover different morphologies including urban and rural areas

    Test type per route and network:

    Single MSD transmissions per call

    Repeated 100-200 times with toggling disabler tone every other call

    New call started after CLEARDOWN or expired call duration timer (30s)

    Test Scenarios [Backup?]

  • UL sync

    MSD RV 0 MSD RV 1, ...

    Uplink: IVS Tx

    Downlink: IVS Rx

    5 x START 3 x NACK

    time [seconds]


    M le




    IVS initiation (up to 5 x SEND)

    3GPP Figure of Merit (FoM): > 1.4s, here 1.7s

    Overhead for

    IVS initiated signalling:

    0.8 2.0s, here 1.4s

    MSD Transmission Time:

    here 2.9s

    5 x HL-ACK

    Total time for acknowledgements:

    > 2.0s, here 2.7s




    received 1.2s

    Test Sample: eCall Signals and Timings

  • MSD Transmission Performance

    subtract approx. 1.2s for 3GPP Figure of Merit

    Mean: 4.0s, STD: 2.2s

    Transmission Success Rate:

    including non-modem related failures 95.57% overall 93.87% without T>20s

    excluding non-modem related failures 97.53% overall 95.88% without T>20s

    Includes stationary & mobility tests

    50% of calls used NEC disabler tone