BS EN 16102 is applicable to intelligent transport systems of eCall for Operating requirements for third party support.
BS EN 16102 specifies the general operating requirements and intrinsic procedures for an in-vehicle eCall via the services of a Third-Party Service Provider (TPSP). BS EN 16102 also provides a definition of the service(s) provided to the PSAP and the method and form of service delivery.
Note 1: An important part of the TPS-eCall is the Minimum Set of Data (MSD). The operating requirements for the MSD are determined in BS EN 16102, but the form and data content of the MSD is not defined herein.
Note 2: 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.
BS EN 16102 on eCall operating requirements for third party support is useful for:
The objective of implementing a 'Third Party' emergency call is to provide emergency assistance and 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.
BS EN 16102 provides two ways for a vehicle to make an eCall: Using the emergency number 112 and the pan-European eCall, which transfers the voice call and data immediately to the PSAP, is one option. Another option is to use a 'third party services supported eCall,' or TPS-eCall, as defined by BS EN 16102.
Overall, BS EN 16102 can assist you in understanding the TPS-eCall's operating requirements for automating traffic accident notification.
EN 16102:2011