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
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.60 - IT applications in transport
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
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
- Corrigendum3 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 describes the key actors in the eCall chain of service provision in hybrid circuit switched/packet switched network
environments as:
1) In-Vehicle System (IVS)/vehicle,
2) Mobile Network Operator (MNO),
3) Public Safety Answering Point (PSAP),
and to provide conformance tests for actor groups 1) – 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants, although they are the recipient of the service.
NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this deliverable. This is because the core TPS-eCall
standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider.
NOTE 3 These conformance tests are partly based on the appropriate conformance tests from EN 16454 and CEN/prEN 17240.
This deliverable therefore adapts and revises Conformance Test Protocols (CTP) from EN 16454 and CEN/prEN 17240 for hybrid circuit switched/packet switched network environments.
This document complements EN 16454 and CEN/prEN 17240 and provides a suite of conformance tests for IVS equipment, MNOs and PSAPs, required to ensure and demonstrate compliance with CEN/prEN 17905.
The scope covers conformance testing of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
- Draft113 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.
- Standard35 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a publication sub-model within the DATEX II model that supports the publication of electronic traffic regulations and controlled zones.
This publication is intended to support the exchange of informational content from road traffic authorities issuing traffic regulation orders and organizations implementing these orders to other organizations providing ITS services or onward information exchange.
- Technical specification169 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 specifies a publication sub-model within the DATEX II model that supports the publication of electronic traffic regulations and controlled zones.
This publication is intended to support the exchange of informational content from road traffic authorities issuing traffic regulation orders and organizations implementing these orders to other organizations providing ITS services or onward information exchange.
- Technical specification169 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 defines detailed use cases, requirements and message specifications for supporting central ITS station based indoor positioning to provide indoor navigation functionality between a personal/vehicle (P/V) ITS station and the central ITS station. This document is only applicable to the core flow for the central ITS station based indoor positioning. The following issues which are adjunctive but essential for commercial navigation services are beyond the scope of this document: — authorized and authenticated access of users and services, including security; — payment; — preparation of indoor data which are necessary for indoor navigation; — low-level communication protocols required to transfer and share data from and to a roadside ITS station or a central ITS station; — other issues dependent on implementation of an instance of indoor navigation.
- Standard21 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 aims at achieving sustainability goals of the local community. It applies to the digital governance part of the mobility system of a city engaged in sustainability. This document applies to the digital governance part of the mobility system of a city committed to sustainability. It aims at achieving sustainability goals of the local community. It targets urban mobility and its connections with intercity and other long-distance transport solutions. It applies to the mobility of people and goods. An urban mobility system is a system of transport systems which: — contributes to the dimensioning and governance of mobility as a whole; — contributes to transport solutions: orchestrated, on demand, shared or not; — provides mobility services.
- Standard31 pagesEnglish languagesale 15% off
This document describes the physical and functional views defined in ISO/TS 14812 on integrated mobility, based on the role and responsibilities models in the mobility-as-a-service (MaaS) and mobility on demand (MOD) ecosystems as described in ISO/TR 4447 and ISO/TR 7878. This document focuses on mobility service concepts where the included transport services are publicly available.
- Technical report18 pagesEnglish languagesale 15% off
The main objective of this WI is to define a SIRI Passenger Real-Time Information European profile:
• To identify a minimum subset of SIRI with codification rules and constraints for a European level plug and play exchange of real-time passenger information data between organisations at a European level
• To reflect already existing NeTEx profiles defined at national level (Norway, France, Sweden, etc.).
• To maintain a relevant real-time information dataset, as small and simple as possible, to ensure interoperability is maximised while at the same time enabling exchange of supplementary national real-time data that will not interfere with the core international dataset
• To complement the EPIP (NeTEx European Passenger Information Profile) with real-time passenger information
• To establish quality assessment procedures for implementing validation and quality assessment tools - including compliance checking rules - necessary to fulfil the requirement of the Commission
This profile will complement the NeTEx Passenger information profile and NeTEx Accessibility profile (under drafting) in order to get a set of consistent European profiles fulfilling the requirements of the Priority Action "A" of the ITS Directive.
- Technical specification208 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
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 environments, etc. The ISO 26048 series defines data that can be used to manage field devices, including device configuration, control and monitoring. Field devices can be quite complex, necessitating the standardization of many data concepts for exchange. As such, the ISO 26048 series is divided into several individual parts. This document (ISO/TS 26048-1) introduces the ISO 26048 series, provides content that is normatively referenced in subsequent parts, and defines data that is applicable to the management of a wide range of field devices. The scope of the ISO 26048 series does not define the logic used by the management station, the underlying protocols used to exchange the defined data elements, or internal design of the field device. However, the ISO 26048 series does define functional requirements on the interface and assumes an interface based on an SNMPv3 environment as specified by ISO 15784-2. NOTE Many of the concepts defined in this document were derived from NTCIP 1103[ REF Reference_ref_11 \r \h 1 08D0C9EA79F9BACE118C8200AA004BA90B0200000008000000110000005200650066006500720065006E00630065005F007200650066005F00310031000000 ] and NTCIP 1201[ REF Reference_ref_12 \r \h 2 08D0C9EA79F9BACE118C8200AA004BA90B0200000008000000110000005200650066006500720065006E00630065005F007200650066005F00310032000000 ], however, the design has been updated to better address security concerns. It is expected that future versions of NTCIP will migrate to the design defined in this document.
- Technical specification95 pagesEnglish languagesale 15% off
This document specifies the constructional and performance requirements and methods of tests for light emitting diode destination board systems (LEDDBSs) for use in all categories of buses and coaches (including mini/midi buses).
- Standard19 pagesEnglish languagesale 15% off
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 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:
— 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:
— 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.
- Standard42 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 defines terms relating to intelligent transport systems (ITS).
- Technical specification87 pagesEnglish languagesale 15% off
This document specifies a transport protocol and network layer services tailored to meet the requirements of LIN‑based vehicle network systems on local interconnect networks. The protocol specifies an unconfirmed communication. The LIN protocol supports the standardized service primitive interface as specified in ISO 14229-2. This document provides the transport protocol and network layer services to support different application layer implementations such as: — normal communication messages, and — diagnostic communication messages. The transport layer defines transportation of data that is contained in one or more frames. The transport layer messages are transported by diagnostic frames. A standardized API is specified for the transport layer. Use of the transport layer is targeting systems where diagnostics are performed on the backbone bus (e.g. CAN) and where the system builder wants to use the same diagnostic capabilities on the LIN sub-bus clusters. The messages are in fact identical to ones in ISO 15765-2 and the PDUs carrying the messages are very similar. The goals of the transport layer are: — to have low load on commander node, — to provide full (or a subset thereof) diagnostics directly on the responder nodes, and — to target clusters built with powerful LIN nodes (not the mainstream low cost).
- Standard75 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 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
- Standard33 pagesEnglish languagesale 15% off
This document defines the common terms, abbreviations and references used throughout the EN 9300 series of standard parts.
- Standard41 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).
- Standard46 pagesEnglish languagesale 15% off
- Standard49 pagesFrench languagesale 15% off
- Standard49 pagesFrench languagesale 15% off
This document specifies test methods to evaluate the behaviour of a vehicle equipped with an acceleration control pedal error (ACPE) system according to ISO/PAS 19486. Those forward and reverse accidents occur during a straight-line acceleration when the vehicle under test (VUT) accelerates due to driver misapplication of accelerator pedal instead of intended brake pedal. This document is limited to ACPE systems of light vehicles only classified in UN-ECE (TRANS/WP.29/1045) Vehicle: “Category 1-1 vehicle” and does not apply to such devices installed in vehicles of other categories, such as heavy vehicles or motorcycles. This document focuses on an important part of the vehicle behaviour during these collision scenarios, which is the capacity to avoid or mitigate the collision especially to the other vehicle.
- Technical specification13 pagesEnglish languagesale 15% off
This document defines the common terms, abbreviations and references used throughout the EN 9300 series of standard parts.
- Standard41 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
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 scope of this document is the definition of the functional interface between TDC and DMIs.
[Figure 1]
The DMIs are those defined and considered in CLC/TR 50542 1:2025.
The TDC is defined in CLC/TR 50542 1:2025.
NOTE 1 The conversion of physical signals into numerical representation is out of scope.
NOTE 2 The term DMI is used in this clause as synonym for display.
- Technical report12 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
In accordance with the ERTMS/ETCS specifications (mainly Subset 026 and ERA_ERTMS_015560 document), UIC 612 leaflet, EN 50126 (series), EN 16186 (series) and EN 61375 (series) requirements, this Technical Report describes the Train Display System (TDS) in the driver’s cab which comprises the Train Display Controller (TDC) and the following six interfaces:
- Interface with Command Control Display (CCD),
- Interface with Train Radio Display (TRD),
- Interface with Electronic Timetable Display (ETD),
- Interface with Technical and Diagnostic Display (TDD),
- Interface with ETCS Onboard systems and the interfaced STMs, which is excluded from the scope of this document,
- Interface with Other Onboard Systems.
[Figure 1]
NOTE Dotted lines are not described by this document.
The scope of this document is to define the functional architecture around the (TDC).
This document excludes the following items:
- Communication protocols (e.g. EN 61375 series);
- Ergonomic aspects;
- Interface with ETCS Onboard systems and the interfaced STMs;
- Train functions;
- GSM-R EIRENE functions;
- Use of the displays as terminals for maintenance purpose.
- Technical report19 pagesEnglish languagesale 10% offe-Library read for1 day
The proposed Part 13 will specify a DATEX II platform-independent model for expression of intelligent transport system device status and fault data. It will follow the EN 16157-1 methodology and reuse common concepts from EN 16157-2 and EN 16157-7.
It will define a UML model with a corresponding data dictionary and XML Schema.
The model will define a device publication which identifies static data, a device status publication, and a device faults publication.
Devices in scope are any that participate in intelligent transport systems.
This specification may be used in system-to-system exchanges about device status and faults, for example a traffic management system that performs operational control of devices may provide information about the status and faults of those devices to a separate technology status and fault management system.
- Technical specification67 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
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 describes the common description of the driving behaviour information set (DBIS) data structure and data exchange procedures for sharing among distributed ITS stations by nomadic devices.
- Technical report16 pagesEnglish languagesale 15% off
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