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
Frequently Asked Questions
ICS 35.240.60 is a classification code in the International Classification for Standards (ICS) system. It covers "IT applications in transport". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 1942 standards classified under ICS 35.240.60 (IT applications in transport). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
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.
This document specifies common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the “fundamentals and concepts” of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
- Standard53 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Technical specification732 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Technical specification518 pagesEnglish languagee-Library read for1 day
This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However, as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12), ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document.
This document specifies the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE, NR and their successors) 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 based on the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and
revise Conformance Test Procedures (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 112-eCall (Pan European eCall) tests provided in EN 16454 are
specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO’s, and PSAPs, required to ensure and demonstrate compliance to EN 17184.
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.
- Standard188 pagesEnglish languagee-Library read for1 day
In respect of pan European eCall (operating requirements defined in EN 16072), this document defines
the high level application protocols, procedures and processes required to provide the eCall service via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
NOTE 1 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 a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102.
This document makes reference to those provisions but does not duplicate them.
- Standard38 pagesEnglish languagee-Library read for1 day
This document specifies common fundamental concepts for long term archiving and retrieval of mechanical CAD information for elementary parts and assemblies. It details the “fundamentals and concepts” of EN 9300-003:2012 in the specific context of long-term archiving of CAD mechanical models.
Mechanical CAD information is divided into assembly structure and geometrical information, both including explicit and implicit geometrical representation, geometric dimensioning and tolerancing with form features.
The EN 9300-1XX series is organized as a sequence of parts, each building on the previous ones in a consistent way, each adding a level of complexity in the CAD data model. This includes the detailing of relationships between the essential information for the different types of CAD information covered by the EN 9300-1XX series.
As technology matures, additional parts will be released in order to support new requirements within the aerospace community.
1.2 In Scope
This document specifies:
- the fundamentals and concepts for long-term archiving and retrieval of 3D mechanical CAD information;
- the document structure of the EN 9300-1XX series, and the links between all these parts;
- the qualification methods for long-term preservation of archived mechanical CAD information; more specially, principles for the CAD validation properties and for verification of the quality of the CAD archived file;
- specifications for the preservation planning of archived CAD information;
- specific functions for administration and monitoring of CAD archived mechanical models;
- the definition of archive information packages for CAD data.
1.3 Out of scope
The following are out of scope for this part:
- long-term archiving of CAD 2D drawings;
- other CAD specialization disciplines, such as electrical harnesses, composite.
- Standard53 pagesEnglish languagee-Library read for1 day
Motorway chauffeur systems (MCS) perform Level 3 automated driving on limited access motorways with the presence of a fallback-ready user (FRU). This document describes a framework of MCS including system characteristics, system states and transition conditions and system functions. This document specifies requirements for the basic set of functionalities of a MCS, and test procedures to verify these requirements. The requirements include vehicle operation to perform the entire dynamic driving task (DDT) within the current lane of travel, to issue a request to intervene (RTI) before disengaging, and to extend operation and temporarily continue to perform the DDT after issuing an RTI. Requirements and test procedures for additional functionalities (such as lane changing) are provided in other parts of the ISO 23792 series. Means related to setting a destination and selecting a route to reach the destination are not within the scope of this document. This document applies to MCS installed in light vehicles[9].
- Standard38 pagesEnglish languagesale 15% off
This document specifies the requirements for discretionary lane change (DLC) for motorway chauffeur systems (MCS) that perform Level 3 automated driving on limited access motorways. It also specifies the test procedures to verify the requirements. DLC is an additional functionality that can be added to an MCS conforming to the general requirements specified in ISO/TS 23792-1. Means related to setting a destination and selecting a route to reach the destination are not in the scope of this document. This document applies to the system installed in light vehicles.
- Standard21 pagesEnglish languagesale 15% off
This document establishes a framework and specifies electronic fee collection (EFC) functions for the personalization process of on-board equipment (OBE) used for EFC.
The personalization process takes place within the domain of the entity that is responsible for the application in the OBE.
This document is applicable to the EFC interface, e.g. using dedicated short-range communication or integrated circuit(s) card, between the personalization equipment (PE) and OBE as shown in Figure 1.
This document does not cover the following:
whether the personalization functionality resides completely in the PE or whether this functionality instead resides in a central system, where the PE is more or less “transparent”;
the exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and are described in subsequent parts of the ISO 21719 series);
the test procedures for evaluation of an implementation for conformity to the requirements in this document;
setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party).
NOTE Some of the issues listed above are subject to separate documents prepared by ISO/TC 204, CEN/TC 278 and the European Telecommunications Standards Institute – Electromagnetic compatibility and Radio Spectrum Matters (ETSI ERM).
- Draft13 pagesEnglish languagee-Library read for1 day
This document establishes a framework and specifies electronic fee collection (EFC) functions for the personalization process of on-board equipment (OBE) used for EFC. The personalization process takes place within the domain of the entity that is responsible for the application in the OBE. This document is applicable to the EFC interface, e.g. using dedicated short-range communication or integrated circuit(s) card, between the personalization equipment (PE) and OBE as shown in Figure 1. This document does not cover the following: whether the personalization functionality resides completely in the PE or whether this functionality instead resides in a central system, where the PE is more or less “transparent”; the exact application command or message structures for the EFC personalization functionality (these are dependent on the communication media and are described in subsequent parts of the ISO 21719 series); the test procedures for evaluation of an implementation for conformity to the requirements in this document; setting-up of operating organizations (e.g. toll service provider, personalization agent, trusted third party). NOTE Some of the issues listed above are subject to separate documents prepared by ISO/TC 204, CEN/TC 278 and the European Telecommunications Standards Institute – Electromagnetic compatibility and Radio Spectrum Matters (ETSI ERM).
- Standard8 pagesEnglish languagesale 15% off
This document establishes the smart streetlighting management platform (SSMP) as a representative case study, based on the Korean implementation. This document provides practical, non-normative reference information to support other countries considering the adoption of similar systems. This document provides information on: the system components of SSMP, the roles and functions of each individual component; the classification, naming, descriptions, and operational procedures of traffic safety service use cases enabled by SSMP.
- Technical report25 pagesEnglish languagesale 15% off
In respect of pan European eCall (operating requirements defined in EN 16072), this document defines
the high level application protocols, procedures and processes required to provide the eCall service via
a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and
wireless access (such as LTE, NR and their successors).
This document assumes support of eCall using IMS over packet switched networks by an IVS and a
PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is
initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched
networks is not supported by an IVS or PSAP is out of scope of this document.
At some moment in time packet switched networks will be the only Public Land Mobile Networks
(PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12)
ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the
appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks
are available) are out of scope of this document.
NOTE 1 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 a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident.
NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102.
This document makes reference to those provisions but does not duplicate them.
- Standard38 pagesEnglish languagee-Library read for1 day
This document defines the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE/4G) as:
1) In-vehicle system (3.20) (IVS)/vehicle,
2) Mobile network Operator (MNO),
3) Public safety answering point (3.27) (PSAP),
and to provide conformance tests for actor groups 1) - 3).
NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants (3.36), 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 (3.32) standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider (3.29).
NOTE 3 These conformance tests are based an the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and revise Conformance Test Protocols (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 14 112-eCall (Pan European eCall) tests provided in EN 16454 are specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable.
This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO's, and PSAPS, required to ensure and demonstrate compliance to CEN/TS 17184.
NOTE 4 Because in the event of non-viability or non-existence of an IMS supporting network at any particular time/location, IMS-eCall systems revert to CS networked eCall systems eCall via GSM/UMTS, IVS and PSAPs need to support, and prove compliance to both IMS and CS switched networks.
The Scope covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.
- Standard188 pagesEnglish languagee-Library read for1 day
This document specifies system requirements and test methods for lane change decision aid systems (LCDAS). LCDAS are intended to warn the driver of the subject vehicle against potential collisions with vehicles either to the side or to the rear in the adjacent lanes of the subject vehicle and moving in the same direction as the subject vehicle for lane change manoeuvres. This document addresses LCDAS for use on forward-moving cars, vans and straight trucks. This document does not address LCDAS for use on motorcycles or articulated vehicles such as tractor/trailer combinations and articulated buses.
- Standard46 pagesEnglish languagesale 15% off
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Technical specification732 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 1.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Draft1257 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Technical specification518 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 3.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Draft272 pagesEnglish languagee-Library read for1 day
16614 (NeTEx) is composed of a series of standards:
- Part 1: Description of the public transport network topology exchange format.
- Part 2: Description of the scheduled timetables exchange format.
- Part 3: Description of the fare information exchange format.
- Part 4: Description of the passenger information European profile (EPIP).
- Part 5: Description of the alternative modes exchange format.
- Part 6: Description of the accessibility European profile (EPIAP).
The present update concerns Part 2.
All the parts will be updated together, except Part 6 currently under formal vote (a NWI is produced for each Part). This update is done in a similar timeframe as the Transmodel (EN12896) revision, to achieve the best possible consistency.
The updated version of TS 16614 is going to be published as NeTEx v2.
The global updates consist in the following main extensions/enhancements:
- Deck plan allowing for a digitalised representation of spaces and equipment on board vehicles (with considerations of accessibility features),
- Physical layout of compound vehicles (e.g. train composition),
- Multiple minor enhancements, adjustments, and fixes to consider all the feedback from the previous versions of NeTEx, especially in the context of the European Delegated Regulation EU 2017/1926
Consistency and coherences with Transmodel and SIRI and OJP have also been challenged and minor updates are to be integrated in this revision.
- Draft326 pagesEnglish languagee-Library read for1 day
This document specifies the sensor data fusion applicable to the use cases of indoor and outdoor seamless positioning solutions for a mobile user (multimodal transportation) in intelligent transport system (ITS) stations. This document provides technical requirements for data fusion between three domains: nomadic device [e.g. personal intelligent transport system station (P-ITS-S)], mobility [e.g. vehicle intelligent transport system station (V-ITS-S)], and infrastructure [e.g. roadside intelligent transport system station (R-ITS-S)]. The data exchange between these domains is based on a standardized message and data format and this document identifies use cases for each different case of communication between domains.
- Standard79 pagesEnglish languagesale 15% off
This document defines and establishes methodologies for developing a set of indicators to steer and measure the performance of sustainable mobility offers. This document applies to the digital governance part of the mobility system of a city engaged in sustainability. It aims at achieving sustainability goals of the local community. This document targets urban mobility and its connections with intercity and other long-distance transport solutions. It applies to mobility of people and goods. This document follows the principles set out in ISO 37101 and ISO 16481. This document is applicable to any city, municipality or local authority that undertakes to measure its performance in a comparable and verifiable manner, irrespective of size and location. It aims at helping mobility policy planners to measure the performance of the mobility systems.
- Standard30 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 recipients of the service.
NOTE 2 Third party eCall systems (TPS-eCall) are not within the scope of this document. 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 EN 17240. This deliverable therefore adapts and revises Conformance Test Procedures (CTPs) from EN 16454 and EN 17240 for hybrid circuit switched/packet switched network environments.
This document complements EN 16454 and EN 17240 and provides a suite of conformance tests for IVS equipment, MNOs and PSAPs, required to ensure and demonstrate compliance with EN 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.
- Standard152 pagesEnglish languagee-Library read for1 day
This document defines general information and use cases for providing road safety enhancement services to all types of road users with a nomadic device in urban localized areas by sharing status or intent messages between nomadic device users and conventional ITS stations. The road users in this document include all type of road users with nomadic device such as vulnerable road users (VRU) including pedestrians, bicyclists, kickboard users, as well as connected automated mobility users including conventional vehicles, automated or connected driving system equipped vehicles. In addition, this document considers a sensor-equipped roadside ITS station with AI-supported road user behaviour detection function to support overall road safety enhancement services by sharing status or intents information of all type of road users such as VRUs without a nomadic device and road vehicles without equipped ITS stations. This document also specifies general information, such as category of nomadic device supported road safety service, overall access technology in nomadic device, actors, and communication architecture to support use cases. This document also defines safety enhancement use cases to enhance overall road safety of all types of road users with nomadic device as well as road users without nomadic device with a connectivity of sensor-equipped roadside ITS station. The use cases are applicable to provide road safety enhancement service in a specific urban localized area such as an un-signalized intersection, T-intersection, roundabout, low speed zone, school zone, no turn on red zone, weaving area, etc.
- Technical report42 pagesEnglish languagesale 15% off
This document covers heavy rail rolling stock.
This document does not cover urban rail rolling stock.
NOTE 1 EN 17355 covers communication device requirements for urban rail rolling stock.
This document specifies:
- the functional requirements for a call for aid system and communication device system;
- the dynamic analysis of the call for aid system.
NOTE 2 "Dynamic analysis" is understood here as a sequence of actions.
NOTE 3 In a formation of vehicles where one complies with this document with one that does not, it is possible that the call for aid system is not fully functional.
NOTE 4 The call for aid system function is separate from the Passenger Alarm System (PAS) function, which is provided to deal with emergency situations. The PAS is described in EN 16334-1:2014+A1:2022.
NOTE 5 The communication device system can be different from the PAS, but it can share some or all parts of the PAS to achieve its functionalities.
NOTE 6 The PAS is regarded as a safety relevant system whereas the CFA system and communication device system are non-safety relevant aids to passengers.
- Standard21 pagesEnglish languagee-Library read for1 day
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 languagee-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 languagee-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 languagee-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.
- Standard152 pagesEnglish languagee-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 languagee-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 languagee-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 languagee-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 languagee-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 languagee-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 languagee-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 languagee-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 languagee-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 languagee-Library read for1 day
- Technical specification20 pagesEnglish languagee-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 languagee-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 languagee-Library read for1 day
- Technical specification20 pagesEnglish languagee-Library read for1 day