Anvendelser av IT i transport og handel

This document defines requirements for short-range communication for the purposes of compliance checking in autonomous electronic fee collecting systems. Compliance checking communication (CCC) takes place between a road vehicle's on-board equipment (OBE) and an interrogator (roadside mounted equipment, mobile device or hand-held unit), and serves to establish whether the data that are delivered by the OBE correctly reflect the road usage of the corresponding vehicle according to the rules of the pertinent toll regime.

The operator of the compliance checking interrogator is assumed to be part of the toll charging role as defined in ISO 17573-1. The CCC permits identification of the OBE, vehicle and contract, and verification of whether the driver has fulfilled his obligations and the checking status and performance of the OBE. The CCC reads, but does not write, OBE data.

This document is applicable to OBE in an autonomous mode of operation; it is not applicable to compliance checking in dedicated short-range communication (DSRC)-based charging systems.

It defines data syntax and semantics, but not a communication sequence. All the attributes defined herein are required in any OBE claimed to be compliant with this document, even if some values are set to "not defined" in cases where certain functionality is not present in an OBE. The interrogator is free to choose which attributes are read in the data retrieval phase, as well as the sequence in which they are read. In order to achieve compatibility with existing systems, the communication makes use of the attributes defined in ISO 14906 wherever useful.

The CCC is suitable for a range of short-range communication media. Specific definitions are given for the CEN-DSRC as specified in EN 15509, as well as for the use of ISO CALM IR, the Italian DSRC as specified in ETSI ES 200 674-1, ARIB DSRC and WAVE DSRC as alternatives to the CEN-DSRC. The attributes and functions defined are for compliance checking by means of the DSRC communication services provided by DSRC application layer, with the CCC attributes and functions made available to the CCC applications at the roadside equipment (RSE) and OBE. The attributes and functions are defined on the level of application data units (ADU).

The definition of the CCC includes:

— the application interface between OBE and RSE (as depicted in Figure 2);

— use of the generic DSRC application layer as specified in ISO 15628 and EN 12834;

— CCC data type specifications given in Annex A;

— a protocol implementation conformance statement (PICS) proforma is given in Annex B;

— use of the CEN-DSRC stack as specified in EN 15509, or other equivalent DSRC stacks as described in Annex C, Annex D, Annex E and Annex F;

— security services for mutual authentication of the communication partners and for signing of data (see Annex H);

— an example CCC transaction is presented in Annex G;

— the informative Annex I highlights how to use this document for the European electronic toll service (as defined in Commission Decision 2009/750/EC).

Test specifications are not within the scope of this document.

This European Standard defines the key actors in the eCall chain of service provision as: 1) In-Vehicle System (IVS)/vehicle, 2) Mobile network Operator (MNO), 3) Public safety assistance point [provider](PSAP), in some circumstances may also involve: 4) Third Party Service Provider (TPSP), and to provide conformance tests for actor groups 1) - 4). NOTE Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service. This European Standard covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.

This Standard defines an additional data concept that may be transferred as an ‘optional additional data concept’ as defined in EN 15722 eCall MSD, that may be transferred from a goods carrying vehicle to a PSAP in the event of a crash or emergency via an eCall communication session. Two variants are provided, one (schema A) for use where information about the goods (ADR classified or not) is known in the eCall device; the second variant (schema B) is for use where such information is to be fetched from elsewhere. NOTE: This Standard is complementary and additional to EN 15722; and contains as little redundancy as possible. The communications media protocols and methods for the transmission of the eCall message are not specified in this Standard. Its contents are independent of the protocols and methods used. Other additional data concepts may also be transferred, and any such data concepts should be registered using a data registry as defined in EN ISO 24978. See www.esafetydata.com for an example.

This document addresses light vehicles^[1], e.g. passenger cars, pick-up trucks, light vans and sport utility vehicles (motorcycles excluded), equipped with partially automated parking systems (PAPS).

This document establishes minimum functionality requirements that the driver can expect and the manufacturer needs to take into account.

Possible system configuration includes the following two types:

— Type 1: System supervised by the conventional driver located in the driver's seat;

— Type 2: System supervised by the remote driver (present within or outside the vehicle) that is not necessarily located in the driver's seat. The vehicle remains in the line of sight of the remote driver.

For both types, minimum requirements and conditions of safety, system performance and function including HMI information content and description of system operating states are addressed.

The requirements include the driver who supervises the safety throughout the system manoeuvres.

System test requirements are also addressed including test criteria, method, and conditions.