This document specifies: —   requirements for the operational design domain, —   system requirements, —   minimum performance requirements, and —   performance test procedures for the safe operation of low-speed automated driving (LSAD) systems for operation on predefined routes. LSAD systems are designed to operate at Level 4 automation (see ISO/SAE PAS 22736), within specific operational design domains (ODD). This document applies to automated driving system-dedicated vehicles (ADS-DVs) and can also be utilized by dual-mode vehicles (see ISO/SAE PAS 22736). This document does not specify sensor technology present in vehicles driven by LSAD systems.

  • Standard
    43 pages
    English language
    sale 15% off
  • Draft
    43 pages
    English language
    sale 15% off

The ISO 15638 series (Parts 1 to 23) define the framework for online fleet management of regulated commercial freight vehicles utilizing data communication between in-vehicle systems and an application service provider via an on-board communication unit interfacing with road monitoring infrastructure and roadside sensors. This document defines an unregulated service architecture framework for freight vehicle safety information provision architecture. This statement does not preclude the regulated service where a jurisdiction requires such a function. The objective of this document is to provide a freight vehicle safety information provision service function/application for non-enforcement applications (and sometimes for regulated application services [RAS]). This is for the road transport safety management purposes of regulated commercial freight vehicle movements. This document intends to reinforce vehicle safety for non-enforcement and other purposes by providing safety advisory information provisions to the freight vehicle drivers/operators transporting heavy goods on freight vehicles. This document defines the framework for remote vehicle safety information provision for non-enforcement and the conceptual operation of other management purpose applications. This document is complementary to, and does not replace, any other documents in the ISO 15638 series. This document is beneficial to vehicle safety management purpose entities and it provides additional use cases for TARV service applications. This document is specifically oriented towards the realization of safer road transport of freight vehicles by providing safety advisory information to the vehicle from the service provider. It utilizes the ISO 15638 series basic architecture framework, as defined in ISO 15638-21. The service provider provides users with safety information such as recommended safety information for that vehicle and gives adequate safety advice messages, as necessary. The various V2X communication paths can be used according to the various use cases.

  • Standard
    26 pages
    English language
    sale 15% off
  • Draft
    26 pages
    English language
    sale 15% off

Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc. Field devices often need to exchange information with other external entities (managers). Field devices can be quite complex necessitating the standardization of many data concepts for exchange. As such, the ISO 20684Â series is divided into several individual parts. This part of the ISO 20684Â series identifies basic user needs for the management of virtually any field device and traces these needs to interoperable designs. This includes the ability to identify the device, its capabilities, and its status. NOTEÂ Â Â Â Â Â This document is similar to portions of NTCIP 1103Â v03 and NTCIP 1201Â v03. ISO 20684-1 provides additional details about how the ISO 20684Â series relates to the overall ITS architecture.

  • Technical specification
    40 pages
    English language
    sale 15% off
  • Draft
    39 pages
    English language
    sale 15% off

ISO 14819-1 describes the ALERT-C protocol concept and message structure used to achieve densely
coded messages to be carried in the RDS-TMC feature. This document specifies the ‘Events List’ to be
used in coding those messages.

  • Standard
    127 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the technical requirements to be met by contactless public transport (PT) devices in order to be able to interface together using the ISO/IEC 14443 (all parts) contactless communications protocol. This document applies to PT devices: —   PT readers which are contactless fare management system terminals acting as a PCD contactless reader based on ISO/IEC 14443 (all parts); —   PT objects which are contactless fare media acting as a PICC contactless object based on ISO/IEC 14443 (all parts). This document addresses interoperability of consumer-market NFC mobile devices, compliant to NFC Forum specifications, with above mentioned PT devices, aligns with ISO/IEC 14443 (all parts) and does not seek to limit compliance for PT readers with EMV Contactless Interface Specification.

  • Technical specification
    30 pages
    English language
    sale 15% off
  • Draft
    30 pages
    English language
    sale 15% off

This document lists all the test conditions to be performed on a PT reader or a PT object in order to ensure that all the requirements specified in ISO/IEC TS 24192-1 are met for the PT device under test. This document applies to PT devices only: —   PT readers which are contactless fare management system terminals acting as a PCD contactless reader based on ISO/IEC 14443 (all parts); —   PT objects which are contactless fare media acting as a PICC contactless object based on ISO/IEC 14443 (all parts). This document applies solely to the contactless communication layers described in ISO/IEC 14443 (all parts). Application-to-application exchanges executed once contactless communication has been established at RF level fall outside the scope of this document. However, a test application is used to make end-to-end transactions during tests on the RF communication layer. This document does not duplicate the contents of ISO/IEC 14443 (all parts) or ISO/IEC 10373‑6. It makes reference to the ISO/IEC 10373‑6 applicable test methods, specifies the test conditions to be used and describes the additional specific test conditions that can be run.

  • Technical specification
    23 pages
    English language
    sale 15% off
  • Draft
    23 pages
    English language
    sale 15% off

The ALERT-C protocol is designed to provide mostly event-oriented road end-user information
messages.
This document specifies the messages which are presented to the user in accordance with a set of
general requirements. It defines the message structure and content and its presentation to the end-user.
The message management component of this document describes the message management functions
of RDS-TMC. The ALERT-C protocol distinguishes between user messages and system messages. User
messages are those potentially made known to the end-user, as defined in Clause 5. System messages
are of use only to the RDS-TMC terminal, for message management purposes.
RDS-TMC information comprises both ‘system information’ and ‘user messages’. System information
relates to the TMC service and details the parameters that the terminal needs to be able to find,
identify and decode the TMC information. System information is transmitted in type 3A groups and in
type 8A groups.
User messages contain the details of the traffic events; these may use one or more type 8A groups. Most
messages may be transmitted using a single type 8A group, however messages with more detail (e.g.
diversion advice) may use up to a total of five, type 8A groups.
The transmission component of this document conveys the messages over-air. The ALERT-C protocol,
used by RDS-TMC, has the fundamental approach of aiming to code most messages entirely within a
single RDS group.
The ALERT-C Event List, which contains all event descriptions, is described in ISO 14819‑2.

  • Standard
    66 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Field devices are a key component in intelligent transport systems (ITS). Field devices include traffic signals, message signs, weather stations, traffic sensors, roadside equipment for connected ITS (C-ITS) environments, etc. The ISO 20684 series defines data that can be used when field devices need to exchange information with other external entities (called “managers” in this document, even if they are other field devices). Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 20684 series is divided into several individual parts. This document (Part 1) introduces the ISO 20684 series and provides normative content that applies to all subsequent parts.

  • Standard
    20 pages
    English language
    sale 15% off
  • Draft
    20 pages
    English language
    sale 15% off

This document specifies location referencing rules to address the specific requirements of Traffic Message Channel (TMC) systems, which use abbreviated coding formats to provide traffic and travel information (TTI) messages over mobile bearers (e.g. GMS, DAB) or via exchange protocols like DATEX
II. In particular, the rules address the Radio Data System-Traffic Message Channel (RDS-TMC), a means
of providing digitally-coded TTI to travellers using a silent data channel on FM radio stations, based on the ALERT-C protocol.

  • Standard
    77 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Variable message signs (VMSs) are installed in areas where traffic managers identify a frequent need to convey information to the travelling public, such as upstream from interchanges to alert the public to downstream congestion in time for them to alter their routes. This allows traffic managers to improve the efficiency, safety, and quality of traveller journeys. In order to manage the operation of a VMS and the messages displayed, information exchange between the management systems and the VMS is needed. This document identifies basic user needs for the management of light-emitting diode (LED) matrix VMSs and traces these needs to interoperable designs. This includes the ability to identify the device, its capabilities, and its status. NOTEÂ 1Â Â This document is similar to portions of NTCIP 1203 v03, which defines how to manage VMSs using an older version of SNMP and is a normative reference in this document. NOTE 2Â Â ISO 20684-1 provides additional details about how this series of standards relates to the overall ITS architecture.

  • Technical specification
    27 pages
    English language
    sale 15% off
  • Draft
    27 pages
    English language
    sale 15% off

The ALERT-C protocol is designed to provide mostly event-oriented road end-user information messages. This document specifies the messages which are presented to the user in accordance with a set of general requirements. It defines the message structure and content and its presentation to the end-user. The message management component of this document describes the message management functions of RDS-TMC. The ALERT-C protocol distinguishes between user messages and system messages. User messages are those potentially made known to the end-user, as defined in Clause 5. System messages are of use only to the RDS-TMC terminal, for message management purposes. RDS-TMC information comprises both ?system information' and ?user messages'. System information relates to the TMC service and details the parameters that the terminal needs to be able to find, identify and decode the TMC information. System information is transmitted in type 3A groups and in type 8A groups. User messages contain the details of the traffic events; these may use one or more type 8A groups. Most messages may be transmitted using a single type 8A group, however messages with more detail (e.g. diversion advice) may use up to a total of five, type 8A groups. The transmission component of this document conveys the messages over-air. The ALERT-C protocol, used by RDS-TMC, has the fundamental approach of aiming to code most messages entirely within a single RDS group. The ALERT-C Event List, which contains all event descriptions, is described in ISO 14819‑2.

  • Standard
    54 pages
    English language
    sale 15% off
  • Standard
    57 pages
    French language
    sale 15% off
  • Draft
    54 pages
    English language
    sale 15% off

ISO 14819-1 describes the ALERT-C protocol concept and message structure used to achieve densely coded messages to be carried in the RDS-TMC feature. This document specifies the `Events List' to be used in coding those messages.

  • Standard
    119 pages
    English language
    sale 15% off
  • Standard
    135 pages
    French language
    sale 15% off
  • Draft
    120 pages
    English language
    sale 15% off

This document specifies location referencing rules to address the specific requirements of Traffic Message Channel (TMC) systems, which use abbreviated coding formats to provide traffic and travel information (TTI) messages over mobile bearers (e.g. GMS, DAB) or via exchange protocols like DATEX II. In particular, the rules address the Radio Data System-Traffic Message Channel (RDS-TMC), a means of providing digitally-coded TTI to travellers using a silent data channel on FM radio stations, based on the ALERT-C protocol.

  • Standard
    69 pages
    English language
    sale 15% off
  • Standard
    77 pages
    French language
    sale 15% off
  • Draft
    69 pages
    English language
    sale 15% off

This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the
conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and
RSE to support interoperability between different equipment supplied by different manufacturers.
ISO 12813 defines requirements on the compliance check communication (CCC) interface level, but
not for the RSE or OBE internal functional behaviour. Consequently, tests regarding OBE and/or RSE
functional behaviour remain outside the scope of this document.

  • Standard
    78 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the conceptual and logical data model in addition to the physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. This document includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents are to be represented, and how relevant information about the database itself can be specified (metadata). This document further defines map data used in automated driving systems, Cooperative-ITS, and Multi-modal transport. The focus of this document is firstly on emerging ITS applications and services, such as Cooperative-ITS and automated driving systems, and it emphasizes road, lane and relevant information on road and lane. However, ITS applications and services also require other information in addition to road and road-related information, which are provided as external databases to connect with GDF and to complement each other. Highly defined public transport databases, for instance, are indispensable in multi-modal transport applications and services in particular. Thus, this document focuses secondly on an expansion of the specification to connect with externally existing databases. It is particularly designed to connect a Transmodel (EN 12896-1 and EN 12896-2) conformant public transport database. Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems. The conceptual data model specified here has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this model with other geographic database standards.

  • Standard
    589 pages
    English language
    sale 15% off
  • Draft
    589 pages
    English language
    sale 15% off

This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluating the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 12813. It provides a basis for conformance tests for dedicated short-range communication (DSRC) OBE and RSE to support interoperability between different equipment supplied by different manufacturers. ISO 12813 defines requirements on the compliance check communication (CCC) interface level, but not for the RSE or OBE internal functional behaviour. Consequently, tests regarding OBE and/or RSE functional behaviour remain outside the scope of this document.

  • Standard
    70 pages
    English language
    sale 15% off
  • Standard
    72 pages
    French language
    sale 15% off
  • Draft
    70 pages
    English language
    sale 15% off
  • Draft
    72 pages
    French language
    sale 15% off

This document shall be considered as a complementary standard to EN 16803-2 that is intended to assessment of the performances of a GBPT placed in real-life or simulated road environments. This document is instead specifically targeting security attacks such as interferences, jamming, meaconing or spoofing. This document cannot be applied independently from EN 16803-2 that describes in details the general methodology of the assessment procedure.
This document provides normative information necessary to replay in the lab standardized scenarios specifically dedicated to security tests applied to GNSS.
Depending on the case (jamming or spoofing), these scenarios are composed of data sets combining either real life recorded SIS and jamming signals or simulated SIS and spoofing signals. The reason for that will be explained in Clause 6.
Although a high-level categorization of GNSS attacks is given in Annex A, a comprehensive and detailed categorization of possible GNSS attacks is out of the scope of this document.
It is not the aim of this EN to standardize the record procedure neither to define the specific requirements for the generation of the attack scenarios. The record procedure itself and its quality framework for accredited GNSS-specialized laboratories (Lab-A), with the detailed definition of standardized attack scenarios, will be totally and precisely described in EN 16803-4 (under preparation). The list of attack scenarios will have to be regularly updated considering the evolution of GNSS technologies, emerging threats, and countermeasures.

  • Standard
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day

EN 16803-1 addresses the final stage of the performance management approach, i.e. the assessment of the whole Road ITS system performance equipped with a given Positioning System, using the Sensitivity analysis method.
EN 16803-1 addresses the identification and the definition the positioning performance features and metrics required for Positioning System assessment.
This document gives definitions of the various items to be considered when specifying an Operational scenario and provides a method to compare finely two environments with respect to their effects on GNSS positioning performance.
This document gives definition of the most important terms used all along the document and describes the architecture of a Road ITS system based on GNSS as it is intended in this standard.
This document does not address:
-   the performance metrics to be used to define the Road ITS system performance requirements, highly depending on the use case and the will of the owner of the system;
-   the performance requirements of the various kinds of Road ITS systems;
-   the tests that are necessary to assess Positioning System performances (Record and Replay tests for this purpose will be addressed by prEN 16803-2 and prEN 16803-3.

  • Standard
    57 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Like the other ENs of the whole series, this EN deals with the use of GNSS-based positioning terminals (GBPT) in road Intelligent Transport Systems (ITS). GNSS-based positioning means that the system providing position data, more precisely Position, Velocity and Time (PVT) data, comprises at least a GNSS receiver and, potentially, for performance improvement, other additional sensor data or sources of information that can be hybridized with GNSS data.
This new EN proposes testing procedures, based on the replay of data recorded during field tests, to assess the basic performances of any GBPT for a given use case described by an operational scenario. These tests address the basic performance features Availability, Continuity, Accuracy and Integrity of the PVT information, but also the Time-To-First-Fix (TTFF) performance feature, as they are described in EN 16803-1, considering that there is no particular security attack affecting the SIS during the operation. This EN does not cover the assessment tests of the timing performances other than TTFF, which do not need field data and can preferably be executed in the lab with current instruments.
"Record and Replay" (R&R) tests consist in replaying in a laboratory environment GNSS SIS data, and potentially additional sensor data, recorded in specific operational conditions thanks to a specific test vehicle. The dataset comprising GNSS SIS data and potential sensor data resulting from these field tests, together with the corresponding metadata description file, is called a "test scenario". A dataset is composed of several data files.
This EN 16803-3 addresses the "Replay" part of the test scenario data set. It does not address the "Record" part, although it describes as informative information the whole R&R process. This "Record" part will be covered by EN 16803-4 under preparation.
Although the EN 16803 series concerns the GNSS-based positioning terminals and not only the GNSS receivers, the present release of this EN addresses only the replay process of GNSS only terminals. The reason is that the process of replaying in the lab additional sensor data, especially when these sensors are capturing the vehicle’s motion, is generally very complex and not mature enough to be standardized today. It would need open standardized interfaces in the GBPT as well as standardized sensor error models and is not ready to be standardized. But, the procedure described in the present EN has been designed to be extended to GBPT hybridizing GNSS and vehicle sensors in the future.
This EN 16803-3 does not address R&R tests when specific radio frequency signals simulating security attacks are added to the SIS. This case is specifically the topic of EN 16803-3.
Once standardized assessment tests procedures have been established, it is possible to set minimum performance requirements for various intelligent transport applications but it makes sense to separate the assessment tests issue from minimum performance requirements, because the same test procedure may be applicable to many applications, but the minimum performance requirements typically vary from one application to another. So, this EN does not set minimum performance requirements for any application.

  • Standard
    87 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the standard data concepts that comprise the "Minimum Set of Data" (MSD) to be transferred from a vehicle to a 'Public Safety Answering Point' (PSAP) in the event of a crash or emergency via an 'eCall' communication transaction.
Optional additional data concepts may also be transferred.
The communications media protocols and methods for the transmission of the eCall message are not specified in this document.

  • Standard
    39 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document 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 vehicle to a PSAP in the event of a crash or emergency via an eCall communication session.
The purpose of this document is simply to enable the existing MSD to house multiple OADs. This is achieved by providing a short optional additional data concept, which facilitates the inclusion of multiple additional datasets within the currently defined MSD of 140 bytes (Every OAD still requires its own specification).
This document can be seen as an addendum to EN 15722; it contains as little redundancy as possible.
NOTE 1   The communications media protocols and methods for the transmission of the eCall message are not specified in this document.
NOTE 2   Additional data concepts can also be transferred, and it is advised to register any such data concepts using a data registry as defined in EN ISO 24978. See www.esafetydata.com for an example.

  • Standard
    13 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document addresses the provision of ?Remote Digital Tachograph Monitoring' and specifies the form and content of the transmission of such data required to support such systems, and access methods to that data. This document provides specifications for common communications and data exchange aspects of the application service remote digital tachograph monitoring that a jurisdiction regulator can elect to require or support as an option, including: a) High level definition of the service that a service provider provides. The service definition describes common service elements but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined. b) Means to realize the service. c) Application data naming, content and quality that an IVS delivers, including a number of profiles for data (noting that requirements and constraints of what can/cannot be transmitted over the air can vary between jurisdictions). d) Support for a number of defined communication profiles to enable remote inspection. This document is not applicable for analogue tachograph equipment/systems. This document provides specifications for the following communication profiles: — Communication Profile C1: Roadside inspection using a short-range wireless communication interrogator instigating a physical roadside inspection (masterslave) Profile C1a: via a hand aimed or temporary roadside mounted and aimed interrogator Profile C1b: via a vehicle mounted and directed interrogator Profile C1c: via a permanent or semi-permanent roadside or overhead gantry — Communication Profile C2: Roadside inspection using a short-range wireless communication interrogator instigating a download of data to an application service provider via an ITS-station communication (masterslave + peerpeer) Profile C2a: via a hand aimed or temporary roadside mounted and aimed interrogator Profile C2b: via a vehicle mounted and directed interrogator Profile C2c: via a permanent or semi-permanent roadside or overhead gantry — Communication Profile C3: Remote inspection addressed via an ITS-station instigating a download of data to an application service provider via a wireless communications interface (as defined in ISO 15638‑2). It is possible that subsequent versions of this document will support additional communication profiles. NOTE 1 The definition of what comprises a ?regulated' service is regarded as an issue for national decision and can vary from jurisdiction to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardized sets of requirements descriptions for identified services to enable consistent and cost-efficient implementations where instantiated. NOTE 2 The ISO 15638 series has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles'). However, there is nothing to prevent a jurisdiction from extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.

  • Standard
    97 pages
    English language
    sale 15% off
  • Draft
    98 pages
    English language
    sale 15% off

The objective is to analyse the security issues that can occur at the GNSS SIS level. In order to do so, a full taxonomy of the GNSS SIS attacks are proposed and GNSS SIS attack security model are elaborated and classified. Security metrics for the validation of the GBPT robustness performances are defined.
The proposed methodology for this technical report consists in three distinct steps that are described hereunder:
I. The first step consists in providing a full taxonomy of the possible GNSS Signal in Space attacks (voluntary or not) to be considered and identify their impact at GBPT level;
II. The second step consists in regrouping narrow sets of previouslyidentified GNSS SIS attacks into security attack models. For each security attack model, an assessment of the dangerousness based on beforehand identified key parameters and methodology will be provided;
III. The third step consists in providing definition of performance objectives, security control, security metrics, and a specific procedure for a robustness evaluation of a GBPT against the identified security attack models at step II.
The results will benefit to the EN16803-3 "Assessment of security performances of GNSS based positioning terminals"

  • Technical report
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    60 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines an information security framework for all organizational and technical entities of an EFC scheme and for the related interfaces, based on the system architecture defined in ISO 17573-1. The security framework describes a set of security requirements and associated security measures. Annex D contains a list of potential threats to EFC systems and a possible relation to the defined security requirements. These threats can be used for a threat analysis to identify the relevant security requirements for an EFC system. The relevant security measures to secure EFC systems can then be derived from the identified security requirements.

  • Standard
    129 pages
    English language
    sale 15% off
  • Standard
    144 pages
    French language
    sale 15% off
  • Draft
    129 pages
    English language
    sale 15% off

This document provides specification on the ITS-Station (ITS-S) access layer for a communication interface (CI) named "ITS-LTE-D2D". This specification is appropriate in the context of LTE-D2D communications that are being used for the dissemination of ITS information from an ITS-SU to other ITS-SUs, where these ITS-SUs can be either vehicle ITS-SUs, roadside ITS-SUs, or personal ITS-SUs, as specified in ISO 21217. It provides a combination of options from relevant ETSI/3GPP releases and ITS-station management standards in ISO 24102 to enable and achieve this objective. ITS-LTE-D2D CIs are based on the evolved-universal terrestrial radio access network (E-UTRAN) device-to-device (LTE-D2D) technology standardized at 3GPP Release 13. This document enables the use of the LTE-D2D technology as an ITS access technology in an ITS station by reference to respective specifications from 3GPP, and by specifying details of the Communication Adaptation Layer (CAL) and the Management Adaptation Entity (MAE) of CIs specified in ISO 21218.

  • Standard
    26 pages
    English language
    sale 15% off

This document describes the characteristics of a Common Transport Service Account System (CTSA). It presents the common transport service account framework and associated use cases. The objective of the CTSA role model is to cover relevant transport services, the payment methods, the account types where the user of the service is charged for the service and that requires a more overall role and responsibilities model. The model also defines external stakeholders that impact and border the model, that is, the general financial (banking) system. The framework assumes an account-based system where charges for services are calculated and charged in the account system. The main idea behind the CTSA framework is to provide a transport service user with the benefit of seamless acquisition of access rights to multiple transport services by multiple service / operator managers through a common transport account. This framework assumes a technology-agnostic front end with respect to the payment media and reading equipment. The focus of this framework is the back-office / account management system as a vehicle to integrate multiple transport services and managers. A new set of terms are introduced in this document to distinguish the convergence of a common approach for payment for transportation services from more traditional models using "smart cards" or electronic tickets. The model describes a move towards common or linked mobility accounts for all traveller payment needs, whether for parking, tolls, public transport and other disruptive mode options (e.g., bikeshare, carshare, microtransit, micromobility), inclusive of commercial payment and benefit models.

  • Technical report
    32 pages
    English language
    sale 15% off
  • Draft
    32 pages
    English language
    sale 15% off

This document addresses the provision of ?weigh-in-motion monitoring' and specifies the form and content of the transmission of such data required to support such systems, and access methods to that data. This document provides specifications for both on-board weighing (WIM-O) systems and in-road "weigh-in-motion" (WIM-R) systems, and provides a profile where the vehicle weight measured is recorded on-board using equipment already installed for "Remote Tachograph Monitoring". This document provides specifications for common communications and data exchange aspects of the application service weigh-in-motion monitoring (WIM-O and WIM-R) that a jurisdiction regulator can elect to require or support as an option, including: a) High level definition of the service that a service provider has to provide (the service definition describes common service elements, but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined); b) Means to realize the service; c) Application data naming, content and quality that an IVS has to deliver, including a number of profiles for data (noting that requirements and constraints of what can/cannot be transmitted over the air can vary between jurisdictions); d) Support for a number of defined communication profiles to enable remote inspection. The present version of this document provides specifications for the following application profiles: — Application Profile A1: Vehicle weight measurement from "On-Board Weighing" systems (WIM-O); — Application Profile A2: Vehicle weight measurement from in-road ?weigh-in-motion' systems where data is transferred to the IVS (WIM-R). NOTE 1 Vehicle weight measurement from in-road ?weigh-in-motion' systems where data is linked to a specific vehicle by ANPR or other techniques and sent via landline or cellular communications to a processing centre is also a viable and alternate option, but as it does not include carrying data on-board the vehicle is not a TARV use case. The present version of this document provides specifications for the following communication profiles: — Communication Profile 1: Roadside inspection using a short range wireless communication interrogator instigating a physical roadside inspection (master-:-slave): — Profile C1a: via a hand aimed or temporary roadside mounted and aimed interrogator; — Profile C1b: via a vehicle mounted and directed interrogator; — Profile C1c: via a permanent or semi-permanent roadside or overhead gantry. — Communication Profile 2: Roadside inspection using a short range wireless communication interrogator instigating a download of data to an application service provider via an ITS-station communication (master-:-slave + peer-:-peer): — Profile C2a: via a hand aimed or temporary roadside mounted and aimed interrogator; — Profile C2b: via a vehicle mounted and directed interrogator; — Profile C2c: via a permanent or semi-permanent roadside or overhead gantry. — Communication Profile 3: Remote inspection addressed via an ITS-station instigating a download of data to an application service provider via a wireless communications interface (as defined in ISO 15638-2). Subsequent versions of this document can support additional communication profiles. NOTE 2 The ISO 15638 series of standards has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles'). There is nothing, however, to prevent a jurisdiction from extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.

  • Standard
    106 pages
    English language
    sale 15% off
  • Draft
    106 pages
    English language
    sale 15% off

This document defines terms within the field of electronic fee collection (EFC). This document defines: — terms within the fields of electronic fee collection and road user charging; — terms that are used in standards related to electronic fee collection; — terms of a more general use that are used more specifically in standards related to electronic fee collection. This document does not define: — Terms related primarily to other fields that operate in conjunction with EFC, such as terms for intelligent transport systems (ITS), common payment systems, the financial sector, etc. — Deprecated terms.

  • Technical specification
    24 pages
    English language
    sale 15% off
  • Technical specification
    24 pages
    French language
    sale 15% off
  • Draft
    24 pages
    English language
    sale 15% off

The CEN 13149 series of products concerns on-board data communication systems on public transport vehicles. This series provides for data services that enable open and managed sharing of relevant information.
This document, being Part 9 of the series, specifies a time publication, enabling all on-vehicle services to share a common understanding of current time, based on a suitable agreed master network clock. It covers:
-   the functional scope, i.e. which data the service provides, why, when and how often.
-   the transport protocol, i.e. how the data are transmitted.
-   the service publication, i.e. how the service can be found by other modules or applications
-   the structure of the data, i.e. how the data are structured and how the data elements are named.
This document implements the service framework described in FprCEN/TS 13149-7.

  • Technical specification
    9 pages
    English language
    sale 10% off
    e-Library read for
    1 day

a) A TM interface standard to enable exchange network performance data (e.g. traffic conditions, travel times) and planned and unplanned events/incidents (e.g. roadworks, road/bridge/tunnel closures, bad weather, road surface conditions) which are not currently covered by DATEX II.
b) A TM interface standard to enable the provision of appropriate and relevant traffic information (e.g. congestion and travel times) to users, across a variety of platforms.

  • Technical specification
    44 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The CEN 13149 series of products concerns on-board data communication systems on public transport vehicles. This series provides for data services that enable open and managed sharing of relevant information.
This document, being Part 11 of the series, specifies a publication service for data provided by the vehicle platform, enabling all on-vehicle services to share a common understanding of the operational activity of the vehicle, based on inputs taken from chassis systems such as the J1939 CAN bus. It covers:
-   the functional scope, i.e. which data the service provides, why, when and how often.
-   the transport protocol, i.e. how the data are transmitted.
-   the service publication, i.e. how the service can be found by other modules or applications
-   the structure of the data, i.e. how the data are structured and how the data elements are named.
This document implements the service framework described in FprCEN/TS 13149-7.

  • Technical specification
    14 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The CEN 13149 series of products concerns on-board data communication systems on public transport vehicles. This series provides for data services that enable open and managed sharing of relevant information.
This document, being Part 10 of the series, specifies a location publication, enabling all on-vehicle services to share a common understanding of the location and orientation of the vehicle, based on inputs taken from global navigational satellite systems (GNSS) such as GPS and Galileo. It covers:
-   the functional scope, i.e. which data the service provides, why, when and how often;
-   the transport protocol, i.e. how the data are transmitted;
-   the service publication, i.e. how the service can be found by other modules or applications;
-   the structure of the data, i.e. how the data are structured and how the data elements are named.
This document implements the service framework described in FprCEN/TS 13149-7.

  • Technical specification
    13 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    10 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    7 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document contains the basic control strategy, minimum functionality requirements, basic driver interface elements, minimum requirements for reaction to failure, and performance test procedures for PALS. PALS perform part or all of lane change tasks under the driver's initiation and supervision. PALS are intended to function on roads with visible lane markings, where non-motorized vehicles and pedestrians are prohibited (e.g. access controlled highway), and to perform a lane change into a lane with traffic moving in the same direction. Support on sections of roadway with temporary or irregular lane markings (such as roadwork zones) is not within the scope of this document. This document does not describe functionalities based on combinations with longitudinal control systems such as those standardized in ISO 22839 (FVCMS) or ISO 15622 (ACC). The driver always assumes responsibility for this system and the driver's decisions and operations take priority at all times. Use of PALS is intended for light-duty and heavy-duty vehicles (heavy trucks and buses). This document does not address any functional or performance requirements for detection sensors, nor any communication links for co-operative solutions.

  • Standard
    13 pages
    English language
    sale 15% off

This document provides guidelines for good practices that can be adopted by organizations for the implementation of commuting safety management. These practices are intended to reduce the number of fatalities and serious injuries, the severity of injuries, and further to minimize damage to property and economic loss due to road crashes. This document is applicable to any organization to help it protect commuters including vulnerable road users (VRU) through the adoption of a proactive approach to manage commuting risks. This document is also applicable to commercial transport organizations including fleet operators, as well as schools.

  • Standard
    28 pages
    English language
    sale 15% off
  • Standard
    30 pages
    French language
    sale 15% off
  • Amendment
    10 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    7 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document constitutes the main deliverable from WP1.1 of the GP-START project. It is devoted to a thorough review of the metrics defined in EN 16803-1 and proposes a performance classification for GNSS-based positioning terminals within designed for road applications. It will serve as one of the inputs to the elaboration of prEN 16803-2:2019 and prEN 16803-3:2019.
This document should serve as a starting point for discussion within CEN/CENELEC/JTC 5/WG1 on a consolidated set of performance metrics and associated classification logic. The proposals and conclusions appearing in this document are therefore only preliminary.

  • Technical report
    41 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    42 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the conceptual and logical data model and physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. It includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents shall be represented, and of how relevant information about the database itself may be specified (metadata). The focus of this document is on ITS applications and services and it emphasizes road and road-related information. ITS applications and services, however, also require information in addition to road and road-related information. EXAMPLE 1 ITS applications and services need information about addressing systems in order to specify locations and/or destinations. Consequently, information about the administrative and postal subdivisions of an area is essential. EXAMPLE 2 Map display is an important component of ITS applications and services. For proper map display, the inclusion of contextual information such as land and water cover is essential. EXAMPLE 3 Point-of-Interest (POI) or service information is a key feature of traveller information. It adds value to end-user ITS applications and services. Typical ITS applications and services targeted by this document are in-vehicle or portable navigation systems, traffic management centres, or services linked with road management systems, including public transport systems. The Conceptual Data Model has a broader focus than ITS applications and services. It is application independent, allowing for future harmonization of this document with other geographic database standards.

  • Standard
    1046 pages
    English language
    sale 15% off
  • Standard
    4 pages
    English language
    sale 15% off
  • Standard
    4 pages
    French language
    sale 15% off

This document specifies the general rules for an on-board data communication system between the different systems that may be used within public transport vehicles, based on the Internet Protocol (IPv4, [3] and IPv6, [4]). This includes operational support systems, passenger information systems, fare collection systems, etc.
This document describes:
-   the requirements for an on board IP network;
-   the overview architecture and components for an IP based on-board network;
-   the modular structure of the network architecture;
-   the Service Oriented Architecture (SOA) approach, and approach to defining services.
Systems directly related to the safe operation of the vehicle (including propulsion management, brake systems, door opening systems) are excluded from the scope of this document and are dealt with in other standardization bodies. However, the architecture described in this document may be used for support services such as safety information messages. Interfaces to safety-critical systems should be provided through dedicated gateways with appropriate security provisions; for the purposes of this document, these are regarded as simply external information sources.
This document is designed primarily for vehicles with a fixed primary structure, where networks can be installed on a permanent basis and the system configuration task consists largely of the integration, adjustment or removal of the functional end systems that produce and/or consume data. Public transport vehicles consisting of units linked temporarily for operational purposes (specifically, trains in which individual engines, cars or consists are routinely connected and disconnected) require additional mechanisms to enable the communications network itself to reconfigure. Such mechanisms are provided through other standards, notably the IEC 61375 series [5].

  • Technical specification
    26 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document constitutes the main deliverable from WP1.1 of the GP-START project. It is devoted to a thorough review of the metrics defined in EN 16803-1 and proposes a performance classification for GNSS-based positioning terminals within designed for road applications. It will serve as one of the inputs to the elaboration of prEN 16803-2:2019 and prEN 16803-3:2019.
This document should serve as a starting point for discussion within CEN/CENELEC/JTC 5/WG1 on a consolidated set of performance metrics and associated classification logic. The proposals and conclusions appearing in this document are therefore only preliminary.

  • Technical report
    41 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical report
    42 pages
    English language
    sale 10% off
    e-Library read for
    1 day

Security requirements address both hardware and software aspects. This document addresses the security requirements for: — the transfer of TARV data from an IVS to an application service provider across a wireless communications interface; — the receipt of instructions from an application service provider to a TARV IVS; — the communications aspects of handling of software updates for the IVS over wireless communications. This document defines the requirements for telematics applications for regulated commercial vehicles for: a) threat, vulnerability and risk analysis; b) security services and architecture; c) identity management; d) security architecture and management; e) identity-trust and privacy management; f) security-access control; g) security-confidentiality services. This document provides: — general specifications for the security of TARV; — specifications for the security of TARV transactions and data within an ITS-station "bounded secure managed domain" (BSMD); — specifications for the security of TARV transactions and data transacted with a predetermined address outside of a BSMD. IVS security requirements are dealt with by the prime service provider and application service provider (See ISO 15638-1). Application service provision security is dealt with by the application service provider (and could be the subject of a separate TARV standards deliverable).

  • Technical specification
    16 pages
    English language
    sale 15% off

This document is written in the frame of WP1.3 of GP-START project. It discusses several models to provide synthetic data for PVT tracks and the ways to analyse and compare the tracks to ensure these are similar to the reality.

  • Technical report
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document is written in the frame of WP1.3 of GP-START project. It discusses several models to provide synthetic data for PVT tracks and the ways to analyse and compare the tracks to ensure these are similar to the reality.

  • Technical report
    59 pages
    English language
    sale 10% off
    e-Library read for
    1 day

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).

  • Standard
    62 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the requirements for the secure application module (SAM) used in the secure monitoring compliance checking concept. It specifies two different configurations of a SAM:
-   trusted recorder, for use inside an OBE;
-   verification SAM, for use in other EFC system entities.
This document describes
-   terms and definitions used to describe the two Secure Application Module configurations;
-   operation of the two Secure Application Modules in the secure monitoring compliance checking concept;
-   functional requirements for the two Secure Application Modules configurations, including a classification of different security levels;
-   the interface, by means of transactions, messages and data elements, between an OBE or Front End and the trusted recorder;
—   requirements on basic security primitives and key management procedures to support Secure Monitoring using a trusted recorder.
This document is consistent with the EFC architecture as defined in FprEN ISO 17573-1 and the derived suite of standards and Technical Specifications, especially FprCEN/TS 16702-1 and CEN ISO/TS 19299.
The following is outside the scope of this document:
-   The life cycle of a Secure Application Module and the way in which this is managed;
-   The interface commands needed to get a Secure Application Module in an operational state;
-   The interface definition of the verification SAM;
-   Definition of a hardware platform for the implementation of a Secure Application Module.

  • Technical specification
    54 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies data elements and data frames for messages a) exchanged between roadside modules and: 1) signal controllers, 2) traffic management centres, and/or 3) other roadside modules. b) exchanged between traffic management centres and signal controllers. NOTE Roadside modules can generate data based on inputs from vehicle detectors and/or probe data transmitted by vehicles. This document does not address how the roadside module generates the data; it only addresses communication after receiving and processing raw data from one or more sources. EXAMPLE A roadside module can calculate vehicle volume, average speed, and queue length by utilizing data from vehicle detectors and probe information. The data structure follows the framework specified in ISO 14817-1, and the data elements and data frames are described by description name, object identifier, definition, and data type following ISO 14817-1. The specifications of this document complement those from ISO/TS 19091 and other standards. The roadside modules can be constructed in any manner using any architecture including the ITS station as described in ISO 21217, or other hardware and software constructs.

  • Technical specification
    21 pages
    English language
    sale 15% off

This document defines the requirements for the secure application module (SAM) used in the secure monitoring compliance checking concept. It specifies two different configurations of a SAM:
-   trusted recorder, for use inside an OBE;
-   verification SAM, for use in other EFC system entities.
This document describes
-   terms and definitions used to describe the two Secure Application Module configurations;
-   operation of the two Secure Application Modules in the secure monitoring compliance checking concept;
-   functional requirements for the two Secure Application Modules configurations, including a classification of different security levels;
-   the interface, by means of transactions, messages and data elements, between an OBE or front end and the trusted recorder;
-   requirements on basic security primitives and key management procedures to support Secure Monitoring using a trusted recorder.
This document is consistent with the EFC architecture as defined in EN ISO 17573-1 and the derived suite of standards and Technical Specifications, especially CEN/TS 16702-1 and CEN ISO/TS 19299.
The following is outside the scope of this document:
-   The life cycle of a Secure Application Module and the way in which this is managed;
-   The interface commands needed to get a Secure Application Module in an operational state;
-   The interface definition of the verification SAM;
-   Definition of a hardware platform for the implementation of a Secure Application Module.

  • Technical specification
    54 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies transactions and data for Compliance Checking - Secure Monitoring. The Scope of this document consists of:
—-   the concept and involved processes for Secure Monitoring;
-   the definition of transactions and data;
-   the use of the OBE compliance checking transaction as specified in EN ISO 12813, for the purpose of Compliance Checking - Secure Monitoring;
-   the use of back end transactions as specified in EN ISO 12855, for the purpose of Compliance Checking – Secure Monitoring. This includes definitions for the use of optional elements and reserved attributes;
-   a specification of technical and organizational security measures involved in Secure Monitoring, on top of measures provided for in the EFC Security Framework;
-   the interrelations between different options in the OBE, TSP and TC domain and their high level impacts.
NOTE   Outside the Scope of this document is: The information exchange between OBE and TR, choices related to compliance checking policies e.g. which options are used, whether undetected/unexpected observations are applied, whether fixed, transportable or mobile compliance checking are deployed, locations and intensity of checking of itinerary freezing and checking of toll declaration, details of procedures and criteria for assessing the validity or plausibility of Itinerary Records.

  • Technical specification
    87 pages
    English language
    sale 10% off
    e-Library read for
    1 day