Study of eCall

The DG eCall recommends that the following essential requirements for transmitting both voice and data through the mobile networks shocould be adopted:

1. Pan-European solution:

O roaming capability

O belonging to GSM standards (ETSI, 3GPP) That must be available for long enough to support vehicle life cycle

O commonly implemented by all European Telcos & within preferably all GSM modules

2. Real Time Transport mechanic

3. Quasi simultaneous voice call and data transfer

4. Secure transport and routing Mechanic (E112)

5. Automatic acknowledgement

The DG eCall recommends that the architecture for eCall, as replicated strated in following figure, is adopted by all stakeholders when implementing eCall. The process is described below:

1) The eCall generator initiate the eCall by sensors triggered and/or manually, send the in-vehicle

Triggered eCall to a PSAP. The eCall consists of two elements: a pure voice (audio) telephone call

Based on 112 and the minimum set of data (MSD)

2) The eCall (Data + voice) carried through the mobile network, is recognized by the mobile network

Operator (MnO) as a 112 emergency call, and is first handled by the MnO. Based on the 112

Handling the MnO enrich the call with the CLI (caller Line Identification), and at the same time,

According to the USD and the E112 recommendation, add the best location available (based on

Best Effort principle11). After the 112 handling, the telecom operator delivers the 112-voice together

With the CLI, mobile location and the eCall MSD to the appropriate PSAP.

3) the PSAP transmits an acknowledgement to the eCall generator specifying that the MSD have been

Properly received.