This document covers services using LSADS-equipped vehicles only; in-vehicle control systems are outside the scope.

Examples of infrastructure facilities and road furniture include driving monitoring platforms, emergency response platforms, operation management platforms, user service platforms (e.g. for online reservations and online payments) and platforms for supporting automated driving systems.

• based on an identifier assigned to a vehicle (e.g. for recognition by national authorities),
• suitable to be used for:
  • electronic identification of local and foreign vehicles by national authorities;
  • vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life-cycle management);
  • adaptation of vehicle data, e.g. in case of international re-sales;
  • safety related purposes;
  • crime reduction;
  • commercial services, and
• adhering to privacy and data protection regulations.

It specifies the interfaces for a secure exchange of data between an electronic registration tag (ERT) and an ERI reader or ERI writer in or outside the vehicle using symmetric encryption techniques.

Symmetric encryption techniques are based on secret keys shared by a particular community of users, i.e. in closed user groups in which it is trusted that keys are not revealed to outsiders.

ISO/TS 24534-5:2008 specifies:

• the interface between an ERT and an onboard ERI reader or writer,
• the interface between the onboard ERI equipment and (road side) reading and writing equipment,
• security issues related to the communication with the ERT.

• electronic identification of local and foreign vehicles by national authorities,
• vehicle manufacturing, in-life-maintenance and end-of-life identification (vehicle life cycle management),
• adaptation of vehicle data, e.g. in case of international re-sales,
• safety related purposes,
• crime reduction, and
• commercial services.

It adheres to privacy and data protection regulations.

ISO TS 24534-4:2008 specifies the interfaces for a secure exchange of data between an ERT and an ERI reader or ERI writer in or outside the vehicle using asymmetric encryption techniques. It includes:

• the application layer interface between an ERT and a onboard ERI reader or writer,
• the application layer interface between the onboard ERI equipment and external ERI readers and writers, and
• security issues related to the communication with the ERT.

• electronic identification of local and foreign vehicles by national authorities,
• vehicle manufacturing, in-life-maintenance and end-of-life identification (vehicle life cycle management),
• adaptation of vehicle data, e.g. in case of international re-sales,
• safety-related purposes,
• crime reduction, and
• commercial services.

It adheres to privacy and data protection regulations.

ISO TS 24534-3:2008 defines the vehicle identification data. This data is called the ERI data and includes the vehicle identifier and possible additional vehicle related information (as typically included in a vehicle registration certificate).

• electronic identification of local and foreign vehicles by national authorities,
• vehicle manufacturing, in-life-maintenance and end-of-life identification (vehicle life cycle management),
• adaptation of vehicle data (e.g. for international resales),
• safety-related purposes,
• crime reduction, and
• commercial services.

It adheres to privacy and data protection regulations.

ISO TS 24534-2:2007 defines the operational requirements for the remaining parts of TS 24534 and the more limited, but relevant provisions of ISO TS 24535.

• electronic identification of local and foreign vehicles by national authorities,
• vehicle manufacturing, in-life maintenance and end-of-life identification (vehicle life cycle management),
• adaptation of vehicle data (e.g. for international resales),
• safety-related purposes,
• crime reduction, and
• commercial services.

It adheres to privacy and data protection regulations

ISO TS 24534-1:2007 provides an overview of the ERI system concept, in terms of the onboard vehicle components and the external off-vehicle components required for an operational system.

The Public Transport Information application is intended to cover all modes of public (i.e. collective) transport as well as inter-urban and intra-urban travel. The application itself is designed to allow the efficient and language-independent transmission of public transport information either directly to an end-user, be it the public or another service provider, such as broadcasters, service operators or other information disseminating points, or to centres for onward transmission.

TPEG applications contain the information required by a client TPEG decoder (i.e. both Location Referencing and event information), to present all the information intended for the end-user when it was originated by the service provider.

Location Referencing requires a service provider to give an impression or image, to the human end-user, of where an event has taken place. This cannot be done easily because the human end-user may or may not be familiar with the location. tpeg-loc has the added challenge of attempting to be as language independent as possible. This is achieved by the use of tpeg-loc tables (essentially word-oriented data object dictionaries).