03.220.20 - Road transport
ICS 03.220.20 Details
Road transport
Stra?enverkehr
Transport routier
Cestni transport
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 03.220.20 - Road transport
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document describes pre-crash classification systems that specify the conflict situations between road traffic actors that lead to real-world crashes. Classification systems are useful tools in defining and understanding the role and actions of traffic actors and therefore, can be applied to the development of vehicle active safety technology, vehicle-safety assessment and traffic-safety research in general. This document addresses pre-crash classification systems that are based on characteristics of conflict situations which can lead to a crash. This document does not address test scenarios that describe the operation domain of assisted or automated driving systems.
- Technical report27 pagesEnglish languagesale 15% off
The management of electronic transport regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network.
This document describes the operational concept (ConOps) for METR in a format that is consistent with ISO/IEC/IEEE 29148.
- Technical report94 pagesEnglish languagesale 10% offe-Library read for1 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. This document addresses the data in the application layer of the OSI (Open Systems Interconnection) reference model.
- Standard33 pagesEnglish languagesale 15% off
This document defines terms within the field of electronic fee collection (EFC).
This document defines:
— 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.
- Standard35 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines the end-to-end requirements for the entire management of electronic traffic regulations (METR) system of systems (SoS). This document introduces the reference architecture used by subsequent parts.
NOTE The operational concept for METR is provided in ISO/TR 24315-2.[9]
- Technical specification106 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the architecture and the logical data model of static map data for connected and automated driving system applications.
- Technical specification269 pagesEnglish languagesale 15% off
This document defines terms within the field of electronic fee collection (EFC).
This document defines:
— 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.
- Standard35 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines terms within the field of electronic fee collection (EFC). This document defines: — 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.
- Standard23 pagesEnglish languagesale 15% off
- Standard24 pagesFrench languagesale 15% off
The management of electronic transport regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network.
This document describes the operational concept (ConOps) for METR in a format that is consistent with ISO/IEC/IEEE 29148.
- Technical report94 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines the end-to-end requirements for the entire management of electronic traffic regulations (METR) system of systems (SoS). This document introduces the reference architecture used by subsequent parts.
NOTE The operational concept for METR is provided in ISO/TR 24315-2.[9]
- Technical specification106 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines the end-to-end requirements for the entire management of electronic traffic regulations (METR) system of systems (SoS). This document introduces the reference architecture used by subsequent parts. NOTE The operational concept for METR is provided in ISO/TR 24315-2.[ REF Reference_ref_13 \r \h 9 08D0C9EA79F9BACE118C8200AA004BA90B0200000008000000110000005200650066006500720065006E00630065005F007200650066005F00310033000000 ]
- Technical specification93 pagesEnglish languagesale 15% off
The management of electronic transport regulations (METR) provides trustworthy, authoritative, machine-interpretable, transport-related rules for using the road network. This document describes the operational concept (ConOps) for METR in a format that is consistent with ISO/IEC/IEEE 29148.
- Technical report80 pagesEnglish languagesale 15% off
This document:
— describes and specifies globally unique addresses and identifiers (ITS-S object identifiers) that are both internal and external to ITS stations and are used for ITS station management;
— describes how ITS-S object identifiers and related technical parameters are used for classification, registration and management of ITS applications and ITS application classes;
— describes how ITS-S object identifiers are used in the ITS communication protocol stack;
— introduces an organizational framework for registration and management of ITS-S objects;
— defines and specifies management procedures at a high functional level;
— specifies an ASN.1 module for the identifiers, addresses and registry records identified in this document; and
— specifies an ASN.1 module for a C-ITS data dictionary containing ASN.1 type definitions of general interest.
This document is based on the architecture of an ITS station specified in ISO 21217 as a bounded secured managed domain (BSMD).
- Standard57 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 13141.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment to support interoperability between different equipment supplied by different manufacturers.
ISO 13141 specifies requirements for the localization augmentation communication (LAC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard46 pagesEnglish languagesale 10% offe-Library read for1 day
This part 8 specifies the physical layer of an onboard data transmission bus between the different equipment for service operations and monitoring of the fleet. This applies to equipment installed on board vehicles that are operating as part of a public transport network, i.e. in operation under public service contracts. This equipment includes operation aid systems, automatic passenger information systems, fare collection systems, etc.
The use of IEEE 802.11 Wireless LAN communications is excluded from the scope of this Technical Specification; its use is not recommended for the service-based approach of CEN/TS 13149.
Equipment directly related to the safety-related functioning of the vehicle (propulsion management, brake systems, door opening systems, etc.) are excluded from the scope of this Technical Specification and are dealt with in other standardization bodies. Interfaces to such equipment or safety-critical networks can be provided through dedicated gateways.
This document covers the following:
— The link between equipment inside vehicles consisting of one carriage only, e.g. buses and trolleybuses, as well as a set of carriages, e.g. trams and trains;
— The Physical Layer for IP-communication networks onboard PT vehicles;
— The cables, connectors and other equipment including pin assignment and environmental requirements.
This document specifies wired communication networks onboard PT vehicles which are based on the Ethernet specification ISO/IEC/IEEE 8802-3-10 Base T, 100 Base Tx and 1000 Base T.
- Technical specification19 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical specification20 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 13141.
It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment to support interoperability between different equipment supplied by different manufacturers.
ISO 13141 specifies requirements for the localization augmentation communication (LAC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard46 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of on-board equipment (OBE) and roadside equipment (RSE) to ISO 13141. It provides a basis for conformance tests for dedicated short-range communication (DSRC) equipment to support interoperability between different equipment supplied by different manufacturers. ISO 13141 specifies requirements for the localization augmentation communication (LAC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard38 pagesEnglish languagesale 15% off
- Standard39 pagesFrench languagesale 15% off
This document:
— describes the functionality of a "local dynamic map" (LDM) in the context of the "bounded secured managed domain" (BSMD);
— specifies:
— general characteristics of LDM Data Objects (LDM-DOs) that can be stored in an LDM, i.e. information on real objects such as vehicles, road works sections, slow traffic sections, special weather condition sections, which are as a minimum requirement location-referenced and time-referenced;
— service access point functions providing interfaces in an ITS station (ITS-S) to access an LDM for:
— secure add, update and delete access for ITS-S application processes;
— secure read access (query) for ITS-S application processes;
— secure notifications (upon subscription) to ITS-S application processes;
— management access:
— secure registration, de-registration and revocation of ITS-S application processes at LDM;
— secure subscription and cancellation of subscriptions of ITS-S application processes;
— procedures in an LDM considering:
— means for maintaining the content and integrity of the data store;
— mechanisms supporting several LDMs in a single ITS station unit.
- Standard77 pagesEnglish languagesale 10% offe-Library read for1 day
This document:
— specifies communication service parameters presented by ITS station (ITS-S) application processes to the ITS-S management in support of automatic selection of ITS-S communication profiles in an ITS station unit (ITS-SU);
— specifies related procedures for the static and dynamic ITS-S communication profile selection processes at a high functional level;
— provides an illustration of objectives used to estimate an optimum ITS-S communication profile.
- Standard42 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies:
— the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;
— an exchange of information between the back-office system of the two roles of service provision and toll charging, e.g.:
— charging-related data (toll declarations, billing details, payment claims, payment announcements),
— administrative data (trust objects, EFC context data, etc.), and
— confirmation data;
— transfer mechanisms and supporting functions;
— information objects, data syntax and semantics.
This document is applicable for any vehicle-related toll service and any technology used for charging.
The data types and associated coding related to the data elements described in Clause 6 are specified in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).
This document does not specify, amongst others:
— any communication between TC or TSP with any other involved party;
— any communication between elements of the TC and the TSP that is not part of the back-office communication;
— interfaces for EFC systems for public transport;
— any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve several APDU exchanges;
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;
— definitions of service communication channels, protocols and service primitives to transfer the APDU.
- Standard307 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the test suite structure (TSS) and test purposes (TPs) for evaluation of on-board equipment (OBE) and roadside equipment (RSE) to EN 15509.
Normative Annex A presents the test purposes for the OBE.
Normative Annex B presents the test purposes for the RSE.
Normative Annex C provides the protocol conformance test report (PCTR) proforma for OBE.
Normative Annex D provides the PCTR proforma for RSE.
- Standard121 pagesEnglish languagesale 10% offe-Library read for1 day
This document:
— describes and specifies globally unique addresses and identifiers (ITS-S object identifiers) that are both internal and external to ITS stations and are used for ITS station management;
— describes how ITS-S object identifiers and related technical parameters are used for classification, registration and management of ITS applications and ITS application classes;
— describes how ITS-S object identifiers are used in the ITS communication protocol stack;
— introduces an organizational framework for registration and management of ITS-S objects;
— defines and specifies management procedures at a high functional level;
— specifies an ASN.1 module for the identifiers, addresses and registry records identified in this document; and
— specifies an ASN.1 module for a C-ITS data dictionary containing ASN.1 type definitions of general interest.
This document is based on the architecture of an ITS station specified in ISO 21217 as a bounded secured managed domain (BSMD).
- Standard57 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes remote support provided to LSADS operated at Level 4 automation on predefined routes by a remotely located human in order to facilitate safe trip continuation. "Remote support" refers to the provision of information, or temporary performance of the dynamic driving task (DDT), and remote monitoring required for these functions. This document is applicable to RS-LSADS in vehicles that provide passenger transport or logistics services on predefined routes. This document specifies: — the terms and definitions related to RS-LSADS and the system architecture of RS-LSADS; — functions of RS-LSADS, which are: remote monitoring, remote assistance and remote driving that is operated under very limited conditions, and conditions under which they need to be activated; — the performance requirements, system requirements and performance test procedures of RS-LSADS; — the data to be communicated between vehicles and the remote support facility (but not protocols or other aspects of communication system). This document is applicable to remote support of operational and tactical functions during continuous operations, but does not apply to strategic functions or to RS-LSADS daily startup or shutdown.
- Standard57 pagesEnglish languagesale 15% off
This document: — describes and specifies globally unique addresses and identifiers (ITS-S object identifiers) that are both internal and external to ITS stations and are used for ITS station management; — describes how ITS-S object identifiers and related technical parameters are used for classification, registration and management of ITS applications and ITS application classes; — describes how ITS-S object identifiers are used in the ITS communication protocol stack; — introduces an organizational framework for registration and management of ITS-S objects; — defines and specifies management procedures at a high functional level; — specifies an ASN.1 module for the identifiers, addresses and registry records identified in this document; and — specifies an ASN.1 module for a C-ITS data dictionary containing ASN.1 type definitions of general interest. This document is based on the architecture of an ITS station specified in ISO 21217 as a bounded secured managed domain (BSMD).
- Standard46 pagesEnglish languagesale 15% off
- Standard49 pagesFrench languagesale 15% off
- Standard49 pagesFrench 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 specifies requirements for the compliance check communication (CCC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard91 pagesEnglish languagesale 10% offe-Library read for1 day
The management of electronic transport regulations (METR) provides a means for METR users to obtain trustworthy, authoritative, machine-interpretable, publicly available and transport-related information for the use of the road network, in order to provide safer and more efficient, sustainable, comfortable, and equitable transport services.
The scope of METR includes both rules that are relatively static (e.g. static speed limits) as well as those that are dynamic (e.g. variable speed limits, signalized intersections). Where appropriate, METR incorporates existing documents (e.g. ISO/TS 19091 for signalized intersections).
This document defines terms specific to the ISO 24315 series on the management of electronic transport regulations.
- Technical specification35 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a unified logical data model based on available existing dynamic information standards. The data has precise relative location references to be linked with ISO/TS 22726-1 which specifies the architecture and the logical data model of static map data for connected and automated driving applications. Dynamic event data comes from external systems and has been defined and specified independently by existing standards. Therefore, the logical data model in this document is formed to synthesize contents referring to other standards.
- Technical specification119 pagesEnglish languagesale 10% offe-Library read for1 day
The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using ‘Public Land Mobile Networks’(PLMN), which supports the European pre-assigned emergency destination address (see normative references) and to provide a means of manually triggering the notification of an incident.
This document specifies the general operating requirements and intrinsic procedures for in-vehicle emergency call (eCall) services in order to transfer an emergency message from a vehicle to a Public Safety Answering Point (PSAP) in the event of a crash or emergency, via an eCall communication session and to establish a voice channel between the in-vehicle equipment and the PSAP.
Private third party in-vehicle emergency supporting services can also provide a similar eCall function by other means. The provision of such services are defined in EN 16102, and are outside the scope of this document.
The communications protocols and methods for the transmission of the MSD are not specified in this document.
This document specifies the operating requirements for an eCall service. An important part of the eCall service is a Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this document, but the form and data content of the MSD is not defined herein. A common European MSD is determined in EN 15722.
This document does not specify whether eCall is provided using embedded equipment or other means (for example in the case of aftermarket equipment).
- Standard30 pagesEnglish languagesale 10% offe-Library read for1 day
In respect of operating requirements specified in EN 16072, this document specifies adaptations to enable the provision of eCall for powered two-wheel vehicles.
As with the existing provisions for eCall for category M1/N1 vehicles, these are specified within the paradigm of being OEM-fit equipment supplied with new vehicles.
This document includes only the requirements for category L1 and L3 P2WV (vehicle based) with the exception of L1e-A (powered cycle), although other documents can subject other ‘L’ subcategories to use this document. Other documents can be prepared for other UNECE category ‘L’ variants.
The requirements herein relate only to the provision of pan-European eCall and does not provide requirements for third party service provision of eCall. Other than in the 112-eCall using IMS over packet switched networks paradigm, which involves a direct call from the vehicle to the most appropriate PSAP, third party service provision involves the support of an intermediary third-party service provider before the call is forwarded to the PSAP.
The provision of eCall for vehicles via the aftermarket (post sales and registration), and the operational requirements for any such aftermarket solution, will be the subject of other work.
- Standard19 pagesEnglish languagesale 10% offe-Library read for1 day
This document addresses the provision of tyre pressure monitoring (TPM) services. It specifies the form and content of the transmission data required to support TPM systems (TPMS) and the access methods for these data. This document provides specifications for common communications and data exchange aspects of the TPM application service that a jurisdiction regulator or operator can elect to require or support as an option, including: a) a high-level definition of the service that a service provider has to provide [the service definition describes common service elements (SEs), but does not specify the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined]; b) the means to realize the service; c) application data naming, content and quality that an in-vehicle system (IVS) has to deliver, including a number of TPM profiles or 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 provides specifications for the following application profiles: — Application profile A1: the cyclical initiation of TPM message by on-board equipment (TPM-C). — Application profile A2: the exceptional initiation of TPM message by on-board equipment (TPM-E). — Application profile A3: the provision of TPM data as the result of an off-board request (TPM-R). — Application profile A4: The provision of TPM data as the result of an off-board reading of tyre pressures of vehicles which can potentially be unequipped (TPM-O).
- Standard74 pagesEnglish languagesale 15% off
This document:
— describes the functionality of a "local dynamic map" (LDM) in the context of the "bounded secured managed domain" (BSMD);
— specifies:
— general characteristics of LDM Data Objects (LDM-DOs) that can be stored in an LDM, i.e. information on real objects such as vehicles, road works sections, slow traffic sections, special weather condition sections, which are as a minimum requirement location-referenced and time-referenced;
— service access point functions providing interfaces in an ITS station (ITS-S) to access an LDM for:
— secure add, update and delete access for ITS-S application processes;
— secure read access (query) for ITS-S application processes;
— secure notifications (upon subscription) to ITS-S application processes;
— management access:
— secure registration, de-registration and revocation of ITS-S application processes at LDM;
— secure subscription and cancellation of subscriptions of ITS-S application processes;
— procedures in an LDM considering:
— means for maintaining the content and integrity of the data store;
— mechanisms supporting several LDMs in a single ITS station unit.
- Standard77 pagesEnglish languagesale 10% offe-Library read for1 day
This document:
— specifies communication service parameters presented by ITS station (ITS-S) application processes to the ITS-S management in support of automatic selection of ITS-S communication profiles in an ITS station unit (ITS-SU);
— specifies related procedures for the static and dynamic ITS-S communication profile selection processes at a high functional level;
— provides an illustration of objectives used to estimate an optimum ITS-S communication profile.
- Standard42 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies:
— the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control;
— an exchange of information between the back-office system of the two roles of service provision and toll charging, e.g.:
— charging-related data (toll declarations, billing details, payment claims, payment announcements),
— administrative data (trust objects, EFC context data, etc.), and
— confirmation data;
— transfer mechanisms and supporting functions;
— information objects, data syntax and semantics.
This document is applicable for any vehicle-related toll service and any technology used for charging.
The data types and associated coding related to the data elements described in Clause 6 are specified in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1.
This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions).
This document does not specify, amongst others:
— any communication between TC or TSP with any other involved party;
— any communication between elements of the TC and the TSP that is not part of the back-office communication;
— interfaces for EFC systems for public transport;
— any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve several APDU exchanges;
— processes regarding payments and exchanges of fiscal, commercial or legal accounting documents;
— definitions of service communication channels, protocols and service primitives to transfer the APDU.
- Standard307 pagesEnglish languagesale 10% offe-Library read for1 day
This document: — specifies communication service parameters presented by ITS station (ITS-S) application processes to the ITS-S management in support of automatic selection of ITS-S communication profiles in an ITS station unit (ITS-SU); — specifies related procedures for the static and dynamic ITS-S communication profile selection processes at a high functional level; — provides an illustration of objectives used to estimate an optimum ITS-S communication profile.
- Standard33 pagesEnglish languagesale 15% off
- Standard34 pagesFrench languagesale 15% off
- Standard34 pagesFrench languagesale 15% off
The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using ‘Public Land Mobile Networks’(PLMN), which supports the European pre-assigned emergency destination address (see normative references) and to provide a means of manually triggering the notification of an incident.
This document specifies the general operating requirements and intrinsic procedures for in-vehicle emergency call (eCall) services in order to transfer an emergency message from a vehicle to a Public Safety Answering Point (PSAP) in the event of a crash or emergency, via an eCall communication session and to establish a voice channel between the in-vehicle equipment and the PSAP.
Private third party in-vehicle emergency supporting services can also provide a similar eCall function by other means. The provision of such services are defined in EN 16102, and are outside the scope of this document.
The communications protocols and methods for the transmission of the MSD are not specified in this document.
This document specifies the operating requirements for an eCall service. An important part of the eCall service is a Minimum Set of Data (MSD). The operating requirements for the MSD are determined in this document, but the form and data content of the MSD is not defined herein. A common European MSD is determined in EN 15722.
This document does not specify whether eCall is provided using embedded equipment or other means (for example in the case of aftermarket equipment).
- Standard30 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:
— ASN.1 (data) types within the field of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
- Standard65 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies: — the interfaces between electronic fee collection (EFC) back-office systems for vehicle-related transport services, e.g. road user charging, parking and access control; — an exchange of information between the back-office system of the two roles of service provision and toll charging, e.g.: — charging-related data (toll declarations, billing details, payment claims, payment announcements), — administrative data (trust objects, EFC context data, etc.), and — confirmation data; — transfer mechanisms and supporting functions; — information objects, data syntax and semantics. This document is applicable for any vehicle-related toll service and any technology used for charging. The data types and associated coding related to the data elements described in Clause 6 are specified in Annex A, using the abstract syntax notation one (ASN.1) according to ISO/IEC 8824-1. This document specifies basic protocol mechanisms over which implementations can specify and perform complex transfers (transactions). This document does not specify, amongst others: — any communication between TC or TSP with any other involved party; — any communication between elements of the TC and the TSP that is not part of the back-office communication; — interfaces for EFC systems for public transport; — any complex transfers (transactions), i.e. sequences of inter-related ADUs that can possibly involve several APDU exchanges; — processes regarding payments and exchanges of fiscal, commercial or legal accounting documents; — definitions of service communication channels, protocols and service primitives to transfer the APDU.
- Standard296 pagesEnglish languagesale 15% off
- Standard326 pagesFrench languagesale 15% off
- Standard326 pagesFrench languagesale 15% off
This document: — describes the functionality of a "local dynamic map" (LDM) in the context of the "bounded secured managed domain" (BSMD); — specifies: — general characteristics of LDM Data Objects (LDM-DOs) that can be stored in an LDM, i.e. information on real objects such as vehicles, road works sections, slow traffic sections, special weather condition sections, which are as a minimum requirement location-referenced and time-referenced; — service access point functions providing interfaces in an ITS station (ITS-S) to access an LDM for: — secure add, update and delete access for ITS-S application processes; — secure read access (query) for ITS-S application processes; — secure notifications (upon subscription) to ITS-S application processes; — management access: — secure registration, de-registration and revocation of ITS-S application processes at LDM; — secure subscription and cancellation of subscriptions of ITS-S application processes; — procedures in an LDM considering: — means for maintaining the content and integrity of the data store; — mechanisms supporting several LDMs in a single ITS station unit.
- Standard68 pagesEnglish languagesale 15% off
- Standard72 pagesFrench languagesale 15% off
- Standard72 pagesFrench languagesale 15% off
The management of electronic transport regulations (METR) provides a means for METR users to obtain trustworthy, authoritative, machine-interpretable, publicly available and transport-related information for the use of the road network, in order to provide safer and more efficient, sustainable, comfortable, and equitable transport services.
The scope of METR includes both rules that are relatively static (e.g. static speed limits) as well as those that are dynamic (e.g. variable speed limits, signalized intersections). Where appropriate, METR incorporates existing documents (e.g. ISO/TS 19091 for signalized intersections).
This document defines terms specific to the ISO 24315 series on the management of electronic transport regulations.
- Technical specification35 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 specifies requirements for the compliance check communication (CCC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard91 pagesEnglish languagesale 10% offe-Library read for1 day
The management of electronic transport regulations (METR) provides a means for METR users to obtain trustworthy, authoritative, machine-interpretable, publicly available and transport-related information for the use of the road network, in order to provide safer and more efficient, sustainable, comfortable, and equitable transport services. The scope of METR includes both rules that are relatively static (e.g. static speed limits) as well as those that are dynamic (e.g. variable speed limits, signalized intersections). Where appropriate, METR incorporates existing documents (e.g. ISO/TS 19091 for signalized intersections). This document defines terms specific to the ISO 24315 series on the management of electronic transport regulations.
- Technical specification21 pagesEnglish languagesale 15% off
This document specifies a unified logical data model based on available existing dynamic information standards. The data has precise relative location references to be linked with ISO/TS 22726-1 which specifies the architecture and the logical data model of static map data for connected and automated driving applications. Dynamic event data comes from external systems and has been defined and specified independently by existing standards. Therefore, the logical data model in this document is formed to synthesize contents referring to other standards.
- Technical specification119 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 specifies requirements for the compliance check communication (CCC) interface level, but not for the OBE or RSE internal functional behaviour. Consequently, tests regarding OBE and RSE functional behaviour remain outside the scope of this document.
- Standard83 pagesEnglish languagesale 15% off
- Standard83 pagesFrench languagesale 15% off
This document specifies a unified logical data model based on available existing dynamic information standards. The data has precise relative location references to be linked with ISO/TS 22726-1 which specifies the architecture and the logical data model of static map data for connected and automated driving applications. Dynamic event data comes from external systems and has been defined and specified independently by existing standards. Therefore, the logical data model in this document is formed to synthesize contents referring to other standards.
- Technical specification110 pagesEnglish languagesale 15% off
This document specifies the following elements for cooperative telematics applications for regulated commercial freight vehicles directly communicating via a secure vehicle interface: a) a framework for the provision of cooperative telematics application services for regulated commercial freight vehicles; b) a description of the concept of operation, regulatory aspects and options and the role models; c) a conceptual architecture using an on-board platform and wireless communications to a regulator or their agent; d) references for the key documents on which the architecture is based; e) the architecture of the facilities layer; f) a taxonomy of the organization of generic procedures. This document does not replace, but is complementary to ISO 15638-1. It provides an alternative communication architecture for achieving similar service provision by means of a standardized secure vehicle interface.
- Technical specification20 pagesEnglish languagesale 15% off
This document specifies the requirements for a secure interface for the provision of telematics applications for regulated commercial freight vehicles (TARV) application services data to jurisdictions and other relevant parties within the following scenarios: a) a secure credential management system (SCMS) already exists for ITS data management and access in the location of the service provision; b) an SCMS does not yet exist for ITS data management and access in the location of the service provision.
- Technical specification4 pagesEnglish languagesale 15% off
This document analyses the processes of image-based systems to be used for tolling purposes, with the aim to identify their specific characteristics, and where these characteristics can be observed. The study intends to answer the following questions: a) Which are the relevant characteristics of an image-based system used for electronic fee collection (EFC)? b) How can these characteristics be specified?
- Technical report20 pagesEnglish languagesale 15% off
This document establishes a method of using geographic location referencing (GLR) that can be used by relevant TPEG applications. The GLR type, defined in this document, is used for defining geographic location references (points, polylines and geographical areas). The GLR method is intended to be one of the methods that can be transported inside a TPEG-Location Referencing Container (TPEG-LRC) for those TPEG applications providing information for primarily geographical locations (e.g. weather). The GLR specification is deliberately kept basic and compact, so that it can also be employed advantageously in non-navigation devices, for simple TPEG services such as weather information, safety alerts, etc. As such, the GLR location referencing method is intended to be complementary to map-related location referencing methods, where the focus is on the referencing of anthropogenic artefacts such as roads and highways. For this reason, the scope of GLR is limited to geographic locations on the Earth’s surface.
- Standard29 pagesEnglish languagesale 15% off
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines:
— ASN.1 (data) types within the field of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
- Standard65 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of semantics are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824-1. This document defines: — ASN.1 (data) types within the field of EFC; — ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC. This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
- Standard55 pagesEnglish languagesale 15% off
- Standard60 pagesFrench languagesale 15% off