eCall‎ > ‎

Public-private interface


Go to:


Preparatory phase

Step 0: for any service that is implemented, it needs to be checked if:
  • a specific standard is being recommended 
  • any further specific recommendations are made to help ensure interoperability.
Assessment phase
  • Step 1: Prerequisites:
    • Agree service level agreement and/or standard ways of working with PSAPs - TPSP
    • Agree necessary language support - TPSP
    • Communicate language support to customers - TPSP
    • Evidence quality procedures - TPSP
    • Verify appropriate training - TPSP
    • Verify automatic call distribution (ACD) system – TPSP
    • Check link from MNO - TPSP
    • Deal with transmission failures - TPSP
    • Update GIS - TPSP
    • Protection of privacy – TPSP
  • Step 2TPS-eCall Responder:
    • Respond to a TPS-eCall transaction
    • Answer call in a timely manner 
    • Receive and route call 
    • Receive and check IVS dataset from vehicle
    • Talk with vehicle occupants and receive relevant information 
    • Call to vehicle if receiving data-only 
    • Call-back to vehicle if call drops
    • Trigger PSAP notification 
    • Make voice connection between vehicle and PSAP if required
    • Confirmation received from PSAP that call with vehicle can be ended
    • Call cleardown with vehicle
    • Call-back to vehicle 
  • Step 3TPS-eCall Notifier:
    • Emergency situation likely to require assistance
    • Establish contact with PSAP - TPS-N
    • Talk with PSAP operator and notify relevant information 
    • Make conference call voice connection between TPSP, vehicle and PSAP if required 
    • Make voice connection between vehicle and PSAP if required
    • PSAP informs that call can be ended 
    • Call cleardown to PSAP 
    • Call-back from PSAP.
Reporting phase

Step 4: Produce quality report

Subpages (1): Private eCall
Peter Van der Perre,
Dec 12, 2015, 11:47 AM