I_HeERO: Harmonised eCallEuropean Deploymentin FinlandMikko Tarkiainen, VTTRisto Öörni, VTT

8.2.2017

I_HeERO Consortium

Project leader: German State of Lower Saxony, under the authority of the GermanMinistry of Transport MVITechnical Implementation Officer: ERTICO – ITS EuropeProject operates in 11 EU Member States and includes 58 commercial partners

www.iheero.eu(www.iheero.com)

#I_HeERO #eCall

Duration 1 January 2015 – 31 December 2017Funding € 30.631.959 MEU Funding Total cost € 15.315.979,5 M

About I_HeERO

Deployment pilot project of EU-wide eCallI_HeERO (“I” for “Infrastructure”) aims at the preparation of thePSAP in Member States for the deployment of eCall based on 112 asreference implementations

Why I_HeERO

• Mandatory deployment of eCall based on 112 forMember State PSAP by 1 October 2017

• After 31 March 2018, eCall will be installed in all new types ofcars and light vans sold in the EU

Project Objectives andFinland Participation

• Prepare the PSAP infrastructure for eCall• Boost Member States investment in PSAP infrastructure and interoperability

of service• Prepare eCall for HGV (including Dangerous Goods) and

Long Distance Buses and Coaches• Prepare eCall for PTW (Powered Two Wheeled) vehicles• Define and perform PSAP Conformity Assessments• Look at management of data (incl. TPS-eCall connection)• Next generation 112• Provide Associated Partnership

I_HeERO Goals in Finland

• All 6 PSAPs have been upgraded at the same time with eCallfunctionalities and they are operated in similar way

• It has been proved that eCall (end-to-end) functions everywhere inFinland and we are ready to deploy eCall service 1 October 2017

• PSAP interoperability with ERA GLONASS in-vehicle devices is tested• Conformity assessment of PSAPs is done successfully• Recommendations are done for implementation of eCall for HGVs and

dangerous goods– National solutions are according to the latest standards and specifications and

Finland’s national specialties are taken into account.• eCall awareness in Finland has increased

Definitions

Definition Source

Conformance testing “The purpose of conformance testing is to determine towhat extent a single implementation of a particularstandard conforms to the individual requirements of thatstandard.”

Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON)Release 4;Interoperability test methods and approaches;Part 1: Generic approach to interoperabilitytesting (ETSI TS 102 237-1)

Interoperabilitytesting

“The purpose of interoperability testing is to prove thatend-to-end functionality between (at least) twocommunicating systems is as required by the standard(s)on which those systems are based.”

Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON)Release 4;Interoperability test methods and approaches;Part 1: Generic approach to interoperabilitytesting (ETSI TS 102 237-1)

End-to-end testing(e2e testing)

System testing: “Testing conducted on a complete,integrated system to evaluate the system’s compliancewith its specified requirements.”

IEEE Standard for System andSoftware Verification and Validation (IEEE Std1012™-2012)

Motivation for e2e testing of complete eCallservice chain• Conformance test specifications cover only PSAP (and IVS)

• Operation of eCall – e.g. MSD transmission – is also affected by mobile andfixed line networks between IVS and PSAP

• High expectations for the performance and reliability of the service – eCall isa safety-critical service

• e2e testing in the field allows verifying the functionality in realistic operatingconditions

eCall e2e tests in Finland

Approach• From individual components to system(s)• Verify that IVS, 2G and 3G networks (eCall flag) and PSAP conform to

standards. VTT’s eCall TestBed (PSAP simulator) as a reference.• Perform field tests with a number of calls allowing statistically conclusive

results with all mobile networks in various geographical locations

Objectives• e2e field tests cover the whole eCall service chain from IVS to PSAP• The aim is to verify that the systems satisfies the requirements for eCall

– Reliability– Performance– Functionality

Data collection

• Data collection at least on IVS and PSAP side are necessary to calculate KPIs– Tests will be done with production phase systems – data collection may be limited

• Possibilities to collect data from mobile and fixed line networks are being studied

eCall IVS- Initiated eCalls- Network registration and TS12

call setup- Operation of the in-band modem- MSDs transmitted (encoded MSD

and MSD content, if possible)- Quality of radio connection to

2G or 3G network

Mobile and fixed linenetworks (planned)- Data on call routing- Codec used during

the call

PSAP- Call setup and release- Operation of the in-band

modem- MSDs received (encoded

MSD and MSD content)

Key performance indicators for e2e tests

• The KPIs planned for end-to-end tests focus on verifying thecore functionalities of eCall:– the successfulness of the call setup– call routing to the most appropriate PSAP– MSD encoding, transmission and decoding– voice connection and call back

Key Performance Indicators (KPI) in FinlandKPI Definition Manual

test callsAutomated

test calls

KPI_001 Success rate of completed eCalls using 112Definition:KPI1 = (successful eCalls / all initiated eCalls) x100%

X X

KPI_002 Success rate of call-backsDefinition:KPI2 = (successful call backs / all ini ated call backs) x 100%

X

KPI_03 Success rate of correct MSDsDefinitionMSD success rate = successful MSDs / all initiated MSDs * 100 %Successful MSDs = initiated MSDs - failed MSDs

X X

KPI_004 Success rate of correct re-transmitted MSDsKPI4 = (successful retransmitted MSDs / all attempts to request new MSD) x 100%Successful MSDs = number of requested MSDs - failed MSDs

X X

KPI_005 Duration of voice channel blockingDefinition: KPI5 = ( ) ( )

X X

Definitions of KPIs:Final agreed KPIs, test specification and methodology,Deliverable D4.1 of HeERO2,http://www.heero-pilot.eu/

Classification of possible test call outcomesPotential failure modes related to data communication include:

– insufficient radio network coverage– network registration problems– failed call setup– unsuccessful MSD transmission– call disconnected without a cleardown request from PSAP– two-way voice channel not opened even though signalling related to call setup procedure

has been completed

Classification of successful and unsuccessful MSD transmissionsÖörni, R. and Korhonen, T. 2014. eCall minimum set of data transmission – results from a field test in Finland.IET Intelligent Transport Systems, Vol. 8, Issue 8, pp. 639-647

Schedule of the tests

End-to-end tests in the field can start only whenall MNOs in Finland have implemented the eCall flageCall reception and processing in PSAPs is ready to handle the test calls

The aim is to complete the e2e tests before1th October 2017

2016 20171 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9

1. Preparations for eCall tests2. Testing of eCall IVS types3. Laboratory tests of eCall discriminator4. Testing of eCall reception at PSAP5. Preparations for end-to-end tests6. Limited end-to-end tests7. National end-to-end tests

Questions?

For more information contactMikko Tarkiainen, VTT mikko.tarkiainen@vtt.fiRisto Öörni, VTT risto.öörni@vtt.fi

www.iheero.eu