UNLIMITED FREE ACCESS TO THE WORLD'S BEST IDEAS

close
Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

close
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

CEN - EN 16102

Intelligent transport systems - eCall - Operating requirements for third party support

active, Most Current
Organization: CEN
Publication Date: 1 December 2011
Status: active
Page Count: 58
ICS Code (IT applications in transport): 35.240.60
scope:

The objective of implementing a 'Third Party' emergency call is to provide emergency assistance and an automated notification of a traffic accident, using 'Third Party Services' packages where such services are supported between the vehicle and a Third Party Service Provider in countries where such notification of an emergency are supported by PSAPs.

The first objective of this TPS-eCall is to transfer an emergency message from a vehicle to a Third Party Service Provider (TPSP) in the event of a crash or an emergency, and to establish a voice channel between the in-vehicle equipment and the TPSP.

The second objective of this TPS-eCall is, in case of an emergency likely to require assistance from the emergency services, for the TPSP to transfer an emergency message including the data of the Minimum Set of Data (MSD) (as defined in EN 15722) from the TPSP to the most appropriate PSAP and to make best efforts to establish a direct voice contact between that PSAP and the occupants of the vehicle if required by the PSAP.

This European Standard specifies the general operating requirements and intrinsic procedures for an invehicle eCall via the services of a Third Party Service Provider (TPSP).

This European Standard also provides definition of the service(s) provided to the PSAP and the method and form of service delivery.

NOTE An important part of the TPS-eCall is the Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this European Standard, but the form and data content of the MSD is not defined herein. The common European MSD for eCall is determined in EN 15722. Additional data concepts may also be transferred, and it is recommended that any such data concepts be registered using a data registry as defined in EN ISO 24978 to ensure that they can be understood by the recipient.

Document History

EN 16102
December 1, 2011
Intelligent transport systems - eCall - Operating requirements for third party support
The objective of implementing a 'Third Party' emergency call is to provide emergency assistance and an automated notification of a traffic accident, using 'Third Party Services' packages where such...

References

Advertisement