35.240.60 - IT applications in transport
ICS 35.240.60 Details
IT applications in transport
IT-Anwendungen in Verkehr, Handel, Verwaltung
Application des TI dans le transport
Uporabniške rešitve IT v prometu
General Information
Unchanged with respect to the current edition CLC/TS 50459-2:2015.
Scope of the revision:
- to update general principles for the presentation of ERTMS/ETCS/GSM-R information correlated with ERA_ERTMS_015560 v3.4.0:2016,
- to update ergonomic arrangements with EN 16186-1:2014, EN 16186-2:2017, EN 16186-3:2016
- to harmonize layout with existing and on supplier side well-established solutions and enhancement of touch-layout
- to update in accordance to the Results of the outcome of the Rascop DMI ad’hoc group
- Technical specification99 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard43 pagesEnglish languagesale 15% off
- Draft43 pagesEnglish languagesale 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.
- Standard26 pagesEnglish languagesale 15% off
- Draft26 pagesEnglish languagesale 15% off
Unchanged with respect to the current edition CLC/TS 50459-1:2015.
Scope of the revision:
- to update general principles for the presentation of ERTMS/ETCS/GSM-R information correlated with ERA_ERTMS_015560 v3.4.0:2016,
- to update ergonomic arrangements with EN 16186-1:2014, EN 16186-2:2017, EN 16186-3:2016
- to update in accordance to the Results of the outcome of the Rascop DMI ad’hoc group
- Technical specification22 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical specification22 pagesEnglish languagesale 10% offe-Library read for1 day
Unchanged with respect to the current edition CLC/TS 50459-3:2016.
Scope of the revision:
- to update general principles for the presentation of ERTMS/ETCS/GSM-R information correlated with ERA_ERTMS_015560 v3.4.0:2016,
- to update ergonomic arrangements with EN 16186-1:2014, EN 16186-2:2017, EN 16186-3:2016
- to revise pictures and layouts
- to update in accordance to the Results of the outcome of the Rascop DMI ad’hoc group
- Technical specification59 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides technical specifications to facilitate an efficient exchange of electronic information between ships and shore, for coastal transit or port calls. It specifies requirements for the safety, security and efficiency enhancement of information, related mainly to the relationships between the ship and the port and coastal state authorities. This document provides the definition of core data elements for use in electronic port clearance (EPC) messages. It does not define any structuring of messages nor provides any guidance on what information is required for a particular purpose; it is a general data dictionary for safety, security or operation-related maritime information. Details about message formats and applications are defined in ISO 28005-1. The data elements in this document is a superset of the data elements and the data model defined in the IMO Reference Data Model as specified in the IMO Compendium on Facilitation and Electronic Business. It also contains data elements from other IMO instruments as described in 4.1. The specifications in this document is compatible with the definitions in the IMO Reference Data Model and the mapping between ISO 28005 and the data element list in the IMO Reference Data Model is defined in Annex B.
- Standard123 pagesEnglish languagesale 15% off
- Draft122 pagesEnglish languagesale 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 specification40 pagesEnglish languagesale 15% off
- Draft39 pagesEnglish languagesale 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.
- Standard127 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard66 pagesEnglish languagesale 10% offe-Library read for1 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 specification30 pagesEnglish languagesale 15% off
- Draft30 pagesEnglish languagesale 15% off
This document describes tests which verify on-board unit (OBU) conformance of functions and data
structures implementations, as defined in the implementation conformance statement (ICS) based on
ISO 14906 for EFC applications.
This document defines tests for assessing OBU conformance in terms of :
— basic dedicated short-range communication (DSRC) L7 functionality,
— EFC application functions,
— EFC attributes (i.e. EFC application information),
— the addressing procedures of EFC attributes and (hardware) components,
— the EFC transaction model, which defines the common elements and steps of any EFC transaction, and
— the behaviour of the interface so as to support interoperability on an EFC-DSRC application
interface level.
After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing a
complete EFC transaction (C.3). Although this document defines examples of test cases for DSRC
and EFC functionality (see Annex C), it does not intend to specify a complete test suite for a certain
implementation. To compose a test suite for a specific EFC implementation, the test cases can be
modified and new test cases can be defined and added in order for the conformance test suite to be
complete. It can be useful to consider the following when defining a complete test suite:
— small range: “exhaustive testing” of critical interoperability/compatibility features,
— large range: testing of boundaries and random values, and
— composite types: testing of individual items in sequence or parallel.
This document does not define tests which assess:
— performance,
— robustness, and
— reliability of an implementation.
NOTE 1 ISO 14907-1 defines test procedures that are aimed at assessing performance, robustness and
reliability of EFC equipment and systems.
NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and
related devices that can be relevant for OBUs which support such cards.
Annex D provides an informative overview of Japanese on-board equipment (OBE) conformance tests
which are based on the ISO 14907 series, in order to illustrate how these can be applied in practice.
- Standard85 pagesEnglish languagesale 10% offe-Library read for1 day
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 specification23 pagesEnglish languagesale 15% off
- Draft23 pagesEnglish languagesale 15% off
This document specifies a global transport data management (GTDM) framework composed of
— global transport basic data model,
— global transport access control data model,
— global transport function monitor data model, and
— sensor and control network data model
to support data exchange between applications.
This document defines standardized data classes in a Global Transport Data Format (GTDF), and the
means to manage them.
Application and role-based access control to resources in GTDF are specified in accordance with
IEEE 1609.2 certificates.
This document specifies GTDM as an ITS-S capability which is an optional feature (ITS-capabilities are
specified in ISO 24102-6).
The GT access control (GTAC) data model specifies access permissions to data and function control by
defining role-based mechanisms.
The GT function monitor (GTFM) data model specifies a configuration method to generate a flow logic
for monitoring purposes, e.g. observing data parameters with respect of a defined limit.
- Technical specification124 pagesEnglish languagesale 10% offe-Library read for1 day
This standard specifies functional requirements for non-UGTMS signalling and control systems in the field of urban rail systems which are along off-street alignment and which operate to “line of sight” or automatic block signalling with intermittent train control.
The standard is restricted to Functional Requirements to which allow users to define more specific requirements based on the given frame of the system requirements at top level. This standard is not applicable to command and control systems for urban rail using continuous data transmission and continuous supervision of train movements by train protection profile already covered by IEC 62290 (UGTMS).
- Standard29 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard20 pagesEnglish languagesale 15% off
- Draft20 pagesEnglish languagesale 15% off
This document specifies: —   the Localized Message (LM) format: an NPDU of a networking & transport layer protocol that does not support routing of a packet through a network; —   the Service Advertisement Message (SAM): an APDU to be transported in an LM, for example; —   the Service Response Message (SRM): an APDU acknowledging a SAM that offered a service based on an ITS application class[2] to be transported in an LM, for example; —   related basic requirements for procedures. Specifications are partly done by normative references to IEEE 1609.3(TM)-2016. NOTE      These message format specifications and basic procedures need to be complemented by complete procedures and SAP specifications according to the context of usage, i.e. an ITS station specified in ISO 21217, or a WAVE device specified in IEEE 1609.0[13] or any other context.
- Standard46 pagesEnglish languagesale 15% off
- Draft46 pagesEnglish languagesale 15% off
This document serves as a guideline explaining the concept of hybrid communications and support
functionalities for Cooperative ITS services deployed in conformance with the ITS station architecture
and related Cooperative ITS standards.
- Technical report39 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides guidelines on security applicable in Intelligent Transport Systems (ITS) related
to communications and data access.
In particular, this document provides analyses and best practice content for secure ITS connectivity
using ISO/TS 21177.
This document analyses and identifies issues related to application security, access control, device
security and PKI for a secure ITS ecosystem.
- Technical report135 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a methodology to define ITS-S communication profiles (ITS-SCPs) based on standardized communication protocols to interconnect trusted devices. These profiles enable secure information exchange between such trusted devices, including secure low-latency information exchange, in different configurations. The present document also normatively specifies some ITS-SCPs based on the methodology, yet without the intent of covering all possible cases, in order to exemplify the methodology.
Configurations of trusted devices for which this document defines ITS-SCPs include:
a) ITS station communication units (ITS-SCU) of the same ITS station unit (ITS-SU), i.e. station-internal communications;
b) an ITS-SU and an external entity such as a sensor and control network (SCN), or a service in the Internet;
c) ITS-SUs.
Other ITS-SCPs can be specified at a later stage.
The specifications given in this document can also be applied to unsecured communications and can be applied to groupcast communications as well.
- Technical specification36 pagesEnglish languagesale 10% offe-Library read for1 day
This European Standard (EN 16157 series) specifies and defines component facets supporting the exchange and shared use of data and information in the field of traffic and travel.
The component facets include the framework and context for exchanges, the modelling approach, data content, data structure and relationships.
This European Standard is applicable to:
- Traffic and travel information which is of relevance to road networks (non-urban and urban),
- Public transport information that is of direct relevance to the use of a road network (e.g. road link via train or ferry service),
- Traffic and travel information in the case of Cooperative intelligent transport systems (C-ITS).
This European Standard establishes specifications for data exchange between any two instances of the following actors:
- Traffic Information Centres (TICs),
- Traffic Control Centres (TCCs),
- Service Providers (SPs),
Use of this European Standard may be applicable for use by other actors.
This European Standard series covers, at least, the following types of informational content:
- Road traffic event information – planned and unplanned occurrences both on the road network and in the surrounding environment,
- Operator initiated actions,
- Road traffic measurement data, status data, and travel time data,
- Travel information relevant to road users, including weather and environmental information,
- Road traffic management information and instructions relating to use of the road network.
This part of the CEN/TS 16157 series specifies the informational structures, relationships, roles, attributes and associated data types required for publishing variable message sign information within the Datex II framework. This is specified in two publications, a DATEX II VMS Table Publication sub-model and a VMS Publication sub-model, which are part of the DATEX II platform independent model, but this part excludes those elements that relate to:
- location information which are specified in EN 16157-2,
- common information elements, which are specified in EN 16157-7,
- situation information which are specified in EN 16157-3.
The VMS Table Publication supports the occasional exchange of tables containing generally static reference information about deployed VMS which enable subsequent efficient references to be made to pre-defined static information relating to those VMS. The VMS Publication supports the exchange of the graphic and textual content of one or several VMS plus any status information on device configuration that aid the comprehension of the informational content. This content is potentially subject to rapid change.
These publications are not intended to support the control or configuration of VMS equipment. Each is part of the DATEX II platform independent model.
- Standard99 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard77 pagesEnglish languagesale 10% offe-Library read for1 day
This document
— describes standardization activities related to C-ITS on a global level by major standard development
organizations (SDOs);
— explains the various purposes of deliverables from SDOs and introduces a classification scheme of
such documents;
— describes methods on how C-ITS services are presented and performed;
— identifies an approach for C-ITS releases and exemplifies this approach;
— presents a list of standards (Bibliography) with special relevance for C-ITS.
- Technical report33 pagesEnglish languagesale 10% offe-Library read for1 day
This document gives guidelines for the development of multi-operator/multi-service interoperable
public surface (including subways) transport fare management systems (IFMSs) on a national and
international level.
This document is applicable to bodies in public transport and related services which agree that their
systems need to interoperate.
This document defines a conceptual framework which is independent of organizational and physical
implementation. Any reference within this document to organizational or physical implementation is
purely informative.
This document defines a reference functional architecture for IFMSs and establishes the requirements
that are relevant for ensuring interoperability between several actors in the context of the use of
electronic tickets.
The IFMS includes all the functions involved in the fare management process, such as:
— management of media,
— management of applications,
— management of products,
— security management, and
— certification, registration, and identification.
This document defines the following main elements:
— identification of the different sets of functions in relation to the overall IFMS and services and media
from non-transport systems which interact with fare management systems;
— a generic model of an IFMS describing the logical and functional architecture and the interfaces
within the system, with other IFMSs and with services and media from non-transport systems;
— use cases describing the interactions and data flows between the different sets of functions;
— security requirements.
In its annexes, this document provides a framework for mobility platforms that integrate fare
management and travel information for inter- and multimodal travel (see Annex A). It also elaborates
on specific subjects covered in document and offers some national examples with regard to IFMS
implementations (see Annex B, Annex C, Annex D and Annex E).
This document does not define:
— the technical aspects of the interface between the medium and the medium access device;
— the data exchanges between the medium and the medium access device;
NOTE The data exchanges between the medium and the medium access device are proposed by other
standardization committees.
— the financial aspects of fare management systems (e.g. customer payments, method of payment,
settlement, apportionment, reconciliation).
- Standard92 pagesEnglish languagesale 10% offe-Library read for1 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 specification27 pagesEnglish languagesale 15% off
- Draft27 pagesEnglish languagesale 15% off
This document provides formal procedures and two, alternative, methods (users are advised to choose whichever of the two suits their individual requirements) for determining the priority of on-board messages presented to drivers of road vehicles by transport information and control systems (TICS) and other systems. It is applicable to the whole range of TICS in-vehicle messages, including traveller information, navigation, travel and traffic advisories, "yellow pages" information, warnings, systems status, emergency calling system information, and electronic toll/fee collection, as well as to messages from non-TICS sources such as telephone, warnings and telltales. Although applicable to systems that allow the free generation of messages, it neither provides guidance on how to use the messages deriving from its procedures nor is it applicable to mandatory or legally required messages.
- Technical specification31 pagesEnglish languagesale 15% off
- Draft31 pagesEnglish languagesale 15% off
This document describes tests which verify on-board unit (OBU) conformance of functions and data structures implementations, as defined in the implementation conformance statement (ICS) based on ISO 14906 for EFC applications. This document defines tests for assessing OBU conformance in terms of : — basic dedicated short-range communication (DSRC) L7 functionality, — EFC application functions, — EFC attributes (i.e. EFC application information), — the addressing procedures of EFC attributes and (hardware) components, — the EFC transaction model, which defines the common elements and steps of any EFC transaction, and — the behaviour of the interface so as to support interoperability on an EFC-DSRC application interface level. After the tests of isolated data items and functions (C.2 to C.4), an example is given for testing a complete EFC transaction (C.3). Although this document defines examples of test cases for DSRC and EFC functionality (see Annex C), it does not intend to specify a complete test suite for a certain implementation. To compose a test suite for a specific EFC implementation, the test cases can be modified and new test cases can be defined and added in order for the conformance test suite to be complete. It can be useful to consider the following when defining a complete test suite: — small range: "exhaustive testing" of critical interoperability/compatibility features, — large range: testing of boundaries and random values, and — composite types: testing of individual items in sequence or parallel. This document does not define tests which assess: — performance, — robustness, and — reliability of an implementation. NOTE 1 ISO 14907‑1 defines test procedures that are aimed at assessing performance, robustness and reliability of EFC equipment and systems. NOTE 2 The ISO/IEC 10373 series defines test methods for proximity, vicinity, integrated circuit(s) cards and related devices that can be relevant for OBUs which support such cards. Annex D provides an informative overview of Japanese on-board equipment (OBE) conformance tests which are based on the ISO 14907 series, in order to illustrate how these can be applied in practice.
- Standard77 pagesEnglish languagesale 15% off
- Standard76 pagesFrench languagesale 15% off
- Draft78 pagesEnglish languagesale 15% off
- Draft75 pagesFrench languagesale 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.
- Standard54 pagesEnglish languagesale 15% off
- Standard57 pagesFrench languagesale 15% off
- Draft54 pagesEnglish languagesale 15% off
This document specifies a global transport data management (GTDM) framework composed of — global transport basic data model, — global transport access control data model, — global transport function monitor data model, and — sensor and control network data model to support data exchange between applications. This document defines standardized data classes in a Global Transport Data Format (GTDF), and the means to manage them. Application and role-based access control to resources in GTDF are specified in accordance with IEEE 1609.2 certificates. This document specifies GTDM as an ITS-S capability which is an optional feature (ITS-capabilities are specified in ISO 24102-6). The GT access control (GTAC) data model specifies access permissions to data and function control by defining role-based mechanisms. The GT function monitor (GTFM) data model specifies a configuration method to generate a flow logic for monitoring purposes, e.g. observing data parameters with respect of a defined limit.
- Technical specification115 pagesEnglish languagesale 15% off
- Draft119 pagesEnglish languagesale 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.
- Standard119 pagesEnglish languagesale 15% off
- Standard135 pagesFrench languagesale 15% off
- Draft120 pagesEnglish languagesale 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.
- Standard69 pagesEnglish languagesale 15% off
- Standard77 pagesFrench languagesale 15% off
- Draft69 pagesEnglish languagesale 15% off
This document provides guidelines on security applicable in Intelligent Transport Systems (ITS) related to communications and data access. In particular, this document provides analyses and best practice content for secure ITS connectivity using ISO/TS 21177. This document analyses and identifies issues related to application security, access control, device security and PKI for a secure ITS ecosystem.
- Technical report125 pagesEnglish languagesale 15% off
- Draft125 pagesEnglish languagesale 15% off
This document serves as a guideline explaining the concept of hybrid communications and support functionalities for Cooperative ITS services deployed in conformance with the ITS station architecture and related Cooperative ITS standards.
- Technical report30 pagesEnglish languagesale 15% off
- Draft28 pagesEnglish languagesale 15% off
This document gives guidelines for the development of multi-operator/multi-service interoperable public surface (including subways) transport fare management systems (IFMSs) on a national and international level. This document is applicable to bodies in public transport and related services which agree that their systems need to interoperate. This document defines a conceptual framework which is independent of organizational and physical implementation. Any reference within this document to organizational or physical implementation is purely informative. This document defines a reference functional architecture for IFMSs and establishes the requirements that are relevant for ensuring interoperability between several actors in the context of the use of electronic tickets. The IFMS includes all the functions involved in the fare management process, such as: — management of media, — management of applications, — management of products, — security management, and — certification, registration, and identification. This document defines the following main elements: — identification of the different sets of functions in relation to the overall IFMS and services and media from non-transport systems which interact with fare management systems; — a generic model of an IFMS describing the logical and functional architecture and the interfaces within the system, with other IFMSs and with services and media from non-transport systems; — use cases describing the interactions and data flows between the different sets of functions; — security requirements. In its annexes, this document provides a framework for mobility platforms that integrate fare management and travel information for inter- and multimodal travel (see Annex A). It also elaborates on specific subjects covered in document and offers some national examples with regard to IFMS implementations (see Annex B, Annex C, Annex D and Annex E). This document does not define: — the technical aspects of the interface between the medium and the medium access device; — the data exchanges between the medium and the medium access device; NOTE The data exchanges between the medium and the medium access device are proposed by other standardization committees. — the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).
- Standard81 pagesEnglish languagesale 15% off
- Standard85 pagesFrench languagesale 15% off
- Draft81 pagesEnglish languagesale 15% off
The RFID tag location, tag data content and functional requirements have been developed for application on the main line railway networks. Other networks (such as metro) may apply this standard but are outside of its scope.
This document contains:
- a description of the RFID tag installation location;
- a description of the RFID tag data content;
- a description of the functional requirements in relation to the RFID tag track side reading performance.
- Standard37 pagesEnglish languagesale 10% offe-Library read for1 day
This document — describes standardization activities related to C-ITS on a global level by major standard development organizations (SDOs); — explains the various purposes of deliverables from SDOs and introduces a classification scheme of such documents; — describes methods on how C-ITS services are presented and performed; — identifies an approach for C-ITS releases and exemplifies this approach; — presents a list of standards (Bibliography) with special relevance for C-ITS.
- Technical report25 pagesEnglish languagesale 15% off
- Draft25 pagesEnglish languagesale 15% off
This document describes the communications reference architecture of nodes called "ITS station units" designed for deployment in intelligent transport systems (ITS) communication networks. The ITS station reference architecture is described in an abstract manner. While this document describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. This document also describes the various communication modes for peer-to-peer communications over various networks between ITS communication nodes. These nodes can be ITS station units as described in this document or any other reachable nodes. This document specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain.
- Standard55 pagesEnglish languagesale 15% off
- Draft55 pagesEnglish languagesale 15% off
This document defines the use cases and general requirements for supporting emergency services via P-ITS-S. Any automotive-related service providers can refer to this document for developing eCall service systems into eCall non-supportive vehicles. The P-ITS-S acts as a monitoring and data transmitting device which gathers a vehicle's speed, impact and airbag deployment signal to assess the accident occurrence and type of accident. Once gathered data has been determined as an accident, accident related information is sent to an emergency service centre. Only notable events, such as an airbag-deployed event, rollover and stationary accident, are concerned by this document. In addition, the vehicle data gathering device requirement and implementation methodology for the emergency service are not applicable to this document.
- Standard17 pagesEnglish languagesale 15% off
- Draft17 pagesEnglish languagesale 15% off
This document specifies the in-vehicle information (IVI) data structures that are required by different
intelligent transport system (ITS) services for exchanging information between ITS Stations (ITS-S).
A general, extensible data structure is specified, which is split into structures called containers to
accommodate current-day information. Transmitted information includes IVI such as contextual
speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, locationbased
services, re-routing. The information in the containers is organized in sub-structures called data
frames and data elements, which are described in terms of its content and its syntax.
The data structures are specified as communications agnostic. This document does not provide the
communication protocols. This document provides scenarios for usage of the data structure, e.g. in case
of real time, short-range communications.
- Technical specification58 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides an EETS gap analysis with the aim to identify the need for new or updated standards to provide an enhanced support of the recast of the EU EETS legislation [29], [31], [32].
- Technical report36 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard78 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard589 pagesEnglish languagesale 15% off
- Draft589 pagesEnglish languagesale 15% off
This document gives guidelines for providing mobility information according to user preference on demand, utilizing a variety of existing applications on nomadic devices related to different means of transport. This document defines an integrated mobility information platform as a service methodology to be integrated with a variety of mobile apps with respect to different transport modes. This document defines the following urban mobility applications: — guidance documents to facilitate the practical implementation of identified standards in the transportation planning process, including related use cases; — provision of urban mobility information integrated with a variety of mobile apps on nomadic devices by multiple transport modes for collecting trip production and attraction data; — modal choice data based on time effectiveness, cost effectiveness, and eco-effectiveness in the trip distribution from origins to destinations.
- Standard17 pagesEnglish languagesale 15% off
- Draft17 pagesEnglish languagesale 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.
- Standard70 pagesEnglish languagesale 15% off
- Standard72 pagesFrench languagesale 15% off
- Draft70 pagesEnglish languagesale 15% off
- Draft72 pagesFrench languagesale 15% off
This document specifies a generic position, velocity and time (PVT) service. It further specifies
the PVT service within the ITS station (ITS-S) facilities layer (ISO 21217) and its interface to other
functionalities in an ITS-S such as:
— ITS-S application processes (ITS-S-APs), defined in ISO 21217;
— the generic facilities service handler (FSH) functionality of the ITS station facilities layer, defined in
ISO/TS 17429.
This document specifies:
— a PVT service which, dependent on a specific implementation, uses a variety of positioning-related
sources such as global navigation satellite systems (GNSSs, e.g. GALILEO, GLONASS and GPS),
roadside infrastructure, cellular infrastructure, kinematic state sensors, vision sensors;
— a PVT service which merges data from the above-mentioned positioning-related sources and
provides the PVT output parameters (carrying the PVT information) including the associated
quality (e.g. accuracy);
— how the PVT service is integrated as an ITS-S capability of the ITS station facilities layer;
— the interface function calls and responses (Service Access Point – service primitives) between the
PVT ITS-S capability and other functionalities of the ITS station architecture;
— optionally, the PVT service as a capability of the ITS-S facilities layer; see ISO 24102-6;
— an ASN.1 module C-itsPvt, providing ASN.1 type and value definitions (in Annex A);
— an implementation conformance statement proforma (in Annex B), as a basis for assessment of
conformity to this document.
NOTE It is outside the scope of this document to define the associated conformance evaluation test
procedures.
- Technical specification37 pagesEnglish languagesale 10% offe-Library read for1 day
The present document provides the specification of the Position and Time (PoTi) services. It includes functional and
operational requirements for the position and time data to support ITS Applications. In addition, it includes the
definition of syntax and semantics of messages exchanged between ITS Stations (ITS-Ss) to augment the position and
time accuracy. Finally, it specifies the facilities layer protocol in support of such message exchanges.
- Standard42 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard42 pagesEnglish languagesale 15% off
- Standard42 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard42 pagesEnglish languagesale 15% off
- Standard42 pagesEnglish languagesale 15% off
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.
- Standard57 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard87 pagesEnglish languagesale 10% offe-Library read for1 day
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.
- Standard58 pagesEnglish languagesale 10% offe-Library read for1 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.
- Standard144 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the in-vehicle information (IVI) data structures that are required by different intelligent transport system (ITS) services for exchanging information between ITS Stations (ITS-S). A general, extensible data structure is specified, which is split into structures called containers to accommodate current-day information. Transmitted information includes IVI such as contextual speed, road works warnings, vehicle restrictions, lane restrictions, road hazard warnings, location-based services, re-routing. The information in the containers is organized in sub-structures called data frames and data elements, which are described in terms of its content and its syntax. The data structures are specified as communications agnostic. This document does not provide the communication protocols. This document provides scenarios for usage of the data structure, e.g. in case of real time, short-range communications.
- Technical specification48 pagesEnglish languagesale 15% off
- Draft48 pagesEnglish languagesale 15% off