03.220.01 - Transport in general
ICS 03.220.01 Details
Transport in general
Verkehr im allgemeinen
Transport en général
Transport na splošno
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 03.220.01 - Transport in general
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
- Corrigendum3 pagesEnglish languagesale 10% offe-Library read for1 day
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 establishes a basic role model, as a common platform for smart city instantiation, of smart city automated mobility services. It provides a paradigm describing: a) a framework architecture for the provision of an automated mobility service; b) a description of the concept of operations, and the role models; c) a conceptual architecture between actors involved in the provision/receipt of automated mobility service applications; d) references for the key documents on which the architecture is based; e) a taxonomy of the organization of generic procedures. In-vehicle control system is not in the scope of this document. The scope of this document is limited to automated mobility services using physical and digital infrastructure.
- Standard10 pagesEnglish languagesale 15% off
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 defines terms relating to intelligent transport systems (ITS).
- Technical specification87 pagesEnglish languagesale 15% off
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 specifies the data transfer models between roadside equipment (RSE) and integrated circuit cards (ICCs) and the interface descriptions between the RSE and on-board equipment (OBE) for on-board accounts using an ICC. It also provides examples of interface definitions and transactions deployed in several countries. This document covers: — data transfer models between the RSE and ICC which correspond to the categorized operational requirements and the data transfer mechanism for each model; — the interface definition between the RSE and OBE based on each data transfer model; — the interface definition for each model; — the functional configuration; — RSE command definitions for ICC access; — the data format and data element definitions of RSE commands; — a transaction example for each model (Annex B).
- Standard29 pagesEnglish languagesale 15% off
This document establishes a method of using geographic location referencing (GLR) that can be used by relevant TPEG applications. The GLR type, defined in this document, is used for defining geographic location references (points, polylines and geographical areas). The GLR method is intended to be one of the methods that can be transported inside a TPEG-Location Referencing Container (TPEG-LRC) for those TPEG applications providing information for primarily geographical locations (e.g. weather). The GLR specification is deliberately kept basic and compact, so that it can also be employed advantageously in non-navigation devices, for simple TPEG services such as weather information, safety alerts, etc. As such, the GLR location referencing method is intended to be complementary to map-related location referencing methods, where the focus is on the referencing of anthropogenic artefacts such as roads and highways. For this reason, the scope of GLR is limited to geographic locations on the Earth’s surface.
- Standard29 pagesEnglish languagesale 15% off
This document describes the “public transport information service” (PTS) application, which is intended to cover all modes of public (i.e. collective) transport, both for inter-urban and intra-urban travel. The PTS application is designed to allow the efficient and language-independent delivery of public transport information directly from a service provider to end-users. The PTS application design is based on three main use cases. — Provision of alert information: an alert is a warning that indicates an emergency situation. This case is specifically relevant for broadcast/push mode, for major deviations or disruptions which are relevant for a large number of travellers. A dedicated alert request is also defined and can be used if a backchannel is available. — Timetable information, both scheduled and real time: this information is in some cases relevant for broadcast, e.g. in case of large events for the transport modalities to/from the event site. A dedicated timetable request is also defined and can be used if a backchannel is available. — Individual requests for trip information (backchannel is required). The PTS application focuses on providing core information regarding public transport in order to ensure the compactness of the TPEG application. Specific information as provided in typical public transport apps (e.g. fare information) is not in the scope of this document.
- Technical specification73 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.
- Standard37 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the "electromobility information" (EMI) TPEG application. The EMI application has been specifically designed to support information about charging infrastructure for electric vehicles (not just cars), the location of e-charging points and their suitability for the respective vehicle (e.g. connector type, charging modality). As electric vehicles will occupy a “charging space” for longer a time than other vehicles, information on availability/waiting time and reservation options are accounted for, as they are highly relevant for enabling a user of an electric vehicle to optimally plan their route/trip. The standardized delivery, via TPEG technology, of electromobility information has the following benefits to an end user of this TPEG service: a) identification of suitable charging units for vehicles, thus preventing unnecessary travel to find a fitting unit (also has environmental benefits); b) verification of the real-time availability of charging units; c) possibility of planning ahead and reserving a spot in a charging park, thus optimizing trip planning; d) possibility of selecting a financially attractive charging point in a charging park where the operator has billing agreements with the user’s electromobility provider. In addition to these end-user benefits, electromobility providers and charging park operators also benefit from a standardized TPEG format as it facilitates harmonization of the electromobility information with the data formats used for the exchange of information between management systems of electromobility providers and charge park operators and related specifications (e.g. Open Charge Alliance,[1] eMobility ICT Interoperability Innovation (eMI3),[2] etc.). The EMI application, as an add-on service component next to traffic information, for example, is laid out to support large numbers of charge parks with only modest bandwidth requirements.
- Standard65 pagesEnglish languagesale 15% off
This document describes use cases related to seamless positioning systems for multimodal transportation in ITS stations. The use cases define the effectiveness of the seamless positioning concept model based on the P-ITS-S to conclude basic PVT service results using available sensors when mobility is moving indoor and outdoor in a network on/off situation. Use cases are provided for each stage in different environments, e.g. indoor, outdoor, tunnel and out-of-network area when travelling starts or ends. Within the use cases, the nomadic device implements a personal ITS station (P-ITS-S) to achieve compatibility with other ITS stations as referenced in this document. The main purpose of this document is to describe the overall concept model, which specifies: — the concept model and actors for each domain; — the relationship of actors under the material domain; — the message sequence diagrams for each domain; and — the data transmission list for each actor to provide a seamless indoor and outdoor positioning system through sensor data fusion. In addition, this document provides: — basic principles used in its drafting; and — a gap analysis, consisting of a formal study of: — the status of seamless positioning technology and implementations, — how seamless positioning technology intends to evolve, and — how to close the gap between current and future technology and implementations. — This document compares desired and actual outcomes and pinpoints opportunities for improvement.
- Technical report40 pagesEnglish languagesale 15% off
This document specifies the functional requirements of nomadic devices for lane-level positioning and integrity monitoring with the network-based precise positioning infrastructure for land transportation (NETPPI-LT), a lane-level positioning system based on global navigation satellite systems (GNSS) described in ISO/TR 22086-1. This document identifies the GNNS threats to monitor and the errors to remove or mitigate to achieve lane-level accuracy and integrity. It also specifies the data sets to be contained in messages between the nomadic device and the control station providing GNSS correction and integrity information. This specification enables the nomadic device to support lane-level positioning and integrity monitoring. Enabling techniques and methods, which can be different for each provider or vendor, are not addressed in this document.
- Standard14 pagesEnglish languagesale 15% off
This document provides a framework and information on the total amount of energy appropriate for the deployment of smart city mobility and energy efficiency technologies. These technologies can increase operational energy efficiency and unlock enhanced transportation waste-free energy applications, as well as measuring energy consumption. The standard framework for energy-based green intelligent transport systems (G-ITS) builds on the best practices for energy efficient transport and management systems, as well as applications of intelligent transport systems (ITS), and aims to accommodate the specific needs of energy-based green ITS in smart cities. G-ITS use data platforms to measure energy for transport and to forecast demand. A smart city provides G-ITS services to improve energy efficiency by using nomadic devices and by monitoring energy supply and demand. This document describes the change in the traffic paradigm from the perspective of energy efficiency. It outlines: — general information for energy-based G-ITS as a service using nomadic and mobile devices; — use cases for energy-based G-ITS services using nomadic and mobile devices; — use cases for energy-based mobility services, for example electric vehicles (EV), transportation infrastructure and other mobility services using nomadic devices.
- Technical report12 pagesEnglish languagesale 15% off
This document is a profile of the CEN/TS 16614 series. It focuses on information relevant to feed the necessary accessibility passenger information services and excludes operational and fares information. It is based directly on EPIP (CEN/TS 16614-4).
This European Passenger Information Accessibility Profile (EPIAP) for NeTEx is for exchanging passenger information; it describes how to extend EPIP (the European Passenger Information Profile) with additional information (including a minimal set) to feed the necessary accessibility passenger information services in a European wide and multimodal context. EPIAP especially formulates a mandatory minimal implementation that needs to be filled in by everybody to deliver the necessary information for an assessment of the accessibility of site(s), vehicles and on vehicle-site interaction for impaired persons. The minimal level allows an assessment and contains the information to produce PRM TSI if necessary. It will also cover what the current legislation usually warrants. It then describes how additional information must be provided if an organisation decides to provide it (e.g. the information of the full DELFI+ standard in Germany).
EPIP does not reflect part 5 (New Modes) yet. However, EPIAP takes it into account. EPIP will have to be adapted accordingly.
For EPIAP to be of use, the EC needs to declare the minimal level of EPIAP as mandatory.
- Technical specification209 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines requirements and specifications of indoor positioning references, which can be referenced for positioning in indoor space, for supporting indoor navigation functionality of a personal/vehicle (P/V) ITS station. NOTE Specific structure and contents of indoor positioning references depend on types of indoor positioning technologies. This document defines: a) the composition of an indoor map for indoor navigation of P/V ITS stations; b) the schema and encoding format of the indoor map for indoor navigation at the P/V ITS stations. This document focuses on the specification and format of the indoor map. 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.
- Standard29 pagesEnglish languagesale 15% off
This document defines requirements and specifications for indoor positioning references, which can be referenced for positioning in indoor space, for supporting indoor navigation functionality of a personal/vehicle (P/V) ITS station. This document defines: a) the composition of indoor positioning references for use in obtaining indoor positions for indoor navigation of P/V-ITS-stations; b) the schema and encoding format of indoor positioning references for P/V-ITS-stations. This document focuses on indoor positioning references. 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.
- Standard18 pagesEnglish languagesale 15% off
This document provides an overview of the ground-based automated mobility systems deployment paradigm. The paradigm covers such kerbsides and pathways as are suitable for co-temporal, collaborative use by various types and combinations of automated and non-automated, wheeled, or ambulatory, motorized and non-motorized, mobility-related vehicles and devices as well as for various levels of automated or remote operation of such vehicles. This includes vehicles and devices that move people as well as goods within proximate distances of human bystanders. Note Aerial (flying) drones are not part of the scope.
- Technical report24 pagesEnglish languagesale 15% off
This document provides a description of the primary services that have been internationally defined to promote consistency among implementations. Implementations can provide any of these services in combination with any other services that are appropriate. This document organizes ITS services by defining service groups, which are placed into one of several service domains. Each service group contains one or more individual services, each of which is described. This document is intended for use by at least two groups of people involved in the ITS sector: a) those who are looking for ideas about the services that ITS implementations can provide, and b) those who are developing International Standards. For the first group, this document provides service descriptions that can act as the catalyst for more detailed descriptions. The level of detail can differ from one ITS implementation to another, depending on whether or not a national ITS architecture is involved, and whether or not this architecture is based directly on services, or on groups of functions. The service descriptions in this document are pitched at a high-level as too much detail can be prescriptive and reduces flexibility. For standards developers, this document is applicable to Technical Committees who are developing International Standards for the ITS sector. This document is designed to provide information and explanations of services that can form the basis and reason for developing standards. Due to its nature, this document is largely advisory and informative with minimal requirements. It is designed to assist the integration of services into a cohesive reference architecture, thereby promoting interoperability and the use of common data definitions. Specifically, services defined within the service groups can be the basis for defining “use cases”, “user needs” or "user service requirements” depending on the methodology being used to develop the resultant ITS architecture functionality. They can also assist with defining applicable data within data dictionaries, and applicable communications and data exchange standards.
- Standard121 pagesEnglish languagesale 15% off
This document establishes the method of signalling the specific location referencing used by all TPEG2 applications that require detailed location information to be delivered to client devices. This document describes the TPEG2-Location Referencing Container (TPEG2-LRC) and shows how it is used to signal which specific location referencing method is in use for a particular TPEG message. It is able to handle location referencing methods that are external to the ISO 21219 series and the internal location referencing methods defined as parts of this series.
- Standard14 pagesEnglish languagesale 15% off
This document contains specifications for a set of ITS station security services required to ensure the authenticity of the source and integrity of information exchanged between trusted entities, i.e.:
— between devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) as specified in ISO 21217; and
— between ITS-SUs (composed of one or several ITS-SCUs) and external trusted entities such as sensor and control networks.
These services include the authentication and secure session establishment which are required to exchange information in a trusted and secure manner.
These services are essential for many intelligent transport system (ITS) applications and services, including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2), and roadside/infrastructure-related services.
- Standard113 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes a basic role and functional model for mobility services using low Earth orbit (LEO) satellite systems for ITS services. This document provides: a) a role and functional model using a LEO satellite system for mobility services; b) a description of the concept of operations (CONOPS), and the relevant role models; c) a conceptual architecture between actors involved; d) references for the key documents on which the architecture is based; e) a mobility service use case summary. In-vehicle control systems are not within the scope of this document. This document scope is limited to mobility services using physical and digital infrastructure. NOTE Physical infrastructure facilities include for example, battery charging facilities, dynamic charging facilities for battery electric vehicles, physical infrastructure markings, physical traffic regulation signs, mobility monitoring facilities, emergency response service support facilities, traffic operation control centre facilities, fee collection service facilities (e.g. road usage fee), battery electric vehicle charging facilities, online reservation and online mobility usage fee payment facilities, and other infrastructure platform facilities that support ITS mobility services.
- Technical report17 pagesEnglish languagesale 15% off
This document contains specifications for a set of ITS station security services required to ensure the authenticity of the source and integrity of information exchanged between trusted entities, i.e.:
— between devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) as specified in ISO 21217; and
— between ITS-SUs (composed of one or several ITS-SCUs) and external trusted entities such as sensor and control networks.
These services include the authentication and secure session establishment which are required to exchange information in a trusted and secure manner.
These services are essential for many intelligent transport system (ITS) applications and services, including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2), and roadside/infrastructure-related services.
- Standard113 pagesEnglish languagesale 10% offe-Library read for1 day
This document contains specifications for a set of ITS station security services required to ensure the authenticity of the source and integrity of information exchanged between trusted entities, i.e.: — between devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) as specified in ISO 21217; and — between ITS-SUs (composed of one or several ITS-SCUs) and external trusted entities such as sensor and control networks. These services include the authentication and secure session establishment which are required to exchange information in a trusted and secure manner. These services are essential for many intelligent transport system (ITS) applications and services, including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2), and roadside/infrastructure-related services.
- Standard99 pagesEnglish languagesale 15% off
- Standard104 pagesFrench languagesale 15% off
This document describes a basic role model of communications as a common platform for ITS services including cooperative service in smart city areas: a) a framework for the provision of a communication service; b) a description of the concept of operations and the role models; c) a conceptual architecture between actors involved in the provision/receipt of communication; d) references for the key documents on which the architecture is based; e) a taxonomy of the organization of generic procedures, with a focus on the basic role and functional model of service for the introduction of communications including infrastructure facilities to support mobility in urban and rural areas. In-vehicle control system is not within the scope of this document. The scope of this document is limited to the communications using physical and digital infrastructure.
- Technical report8 pagesEnglish languagesale 15% off
This document compiles use cases for the implementation of sustainable mobility services. The collected data will be analysed to identify issues for international standardization. This document focuses on use cases that aim to implement sustainable transport services. The use cases considered are at the city scale or metropolitan scale, aligned with the scope of smart cities and communities. The use cases encompass land transport, water transport, and air transport for both passengers and freight. Ideas related to connection and integration, including demand-side, supply-side, and policy framework aspects, are included.
- Technical report26 pagesEnglish languagesale 15% off
This document specifies the infection prevention and control (IPC) measures for cross-border workers. It is applicable only in the circumstance of novel infectious disease outbreak while valid vaccine or drug for treatment are not available. It can be used for the purpose of maintaining economic activities when a country that workers need to enter blocks its border due to a pandemic or epidemic (Annex A). This document provides information on the key aspects and details of the process requirements, procedures for selecting service providers, such as travel management company, and procedures for cross-border workers amidst a pandemic, encompassing the complete set of stages from ‘pre-departure’, ‘border crossing’, ‘quarantine and commute’, to ‘return’, and is addressed to all stakeholders involved in travel, whether from the public or private sector. NOTE Stakeholders are comprised of but not limited to health authority, healthcare organization and screening stations, accommodation services, transportation services, travel agencies, and private companies including their contractors and providers.
- Technical specification23 pagesEnglish languagesale 15% off
This document specifies a procedure to arrange smart transportation for newly developing areas, including transportation services between the developing area and existing city centres. This document does not designate procedures for constructing smart transportation facilities.
- Standard10 pagesEnglish languagesale 15% off
This document provides a review of mobility integration standardization efforts supporting all travellers using active and light transport modes and identifies gaps where additional standardization is potentially required. The gap analysis is focused on cooperative intelligent transportation systems (C-ITS) for all users, including people with disabilities, as they plan, manage and carry out their “complete trip”, including all connections and transfers, from end-to-end. The term “light mode conveyances" covers C-ITS for light power and active modes such as micromobililty vehicles (e.g. e-scooters), power or power-assisted vehicles (e.g. e-bikes, power wheelchairs), and full powered vehicles (e.g. motorcycles, mopeds). This document identifies areas where standardization is potentially required to resolve problems and challenges, or to create opportunities, particularly with respect to enhancing safety and the provision of end-to-end multimodal journeys and support.
- Technical report25 pagesEnglish languagesale 15% off
This document describes a basic role and functional model of the intelligent transport systems (ITS) data aggregation role, which is a basic role of ISO/TR 4445. It provides a paradigm describing: a) a framework for the provision of ITS data aggregation for cooperative ITS service application; b) a description of the concept of a role and functional model for such roles; c) a conceptual architecture between actors involved in the provision/receipt of ITS data aggregation; d) references for the key documents on which the architecture is based; e) a taxonomy of the organization of generic procedures.
- Technical report11 pagesEnglish languagesale 15% off
This document defines the TPEG Weather (WEA) application for reporting weather information for travellers. It provides general weather-related information to all travellers and is not limited to a specific mode of transportation. This application does not provide specific weather-related safety warnings to drivers; these are provided as safety related messages as part of the TPEG2-TEC application (ISO 21219-15). The WEA application provides weather-related forecasts and status information over multiple time periods and for multiple, possibly linked, geographical areas. NOTE The presentation of the information is dependent on the specific human-machine interface (HMI) of the receiving device. Therefore, this document does not define any prerequisites for the HMI of the device. This document contains examples to help explain how some typical weather reports can be signalled (see Annex C) and suggested translations between WEA table codes and WMO SYNOP weather observation codes (see Annex D).
- Standard61 pagesEnglish languagesale 15% off
This document defines the TPEG Speed information (SPI) application for reporting speed information for travellers. Speed limits are usually indicated to the driver through roadside signs. Drivers who are aware of the speed limit at all times are more likely to drive safely, which improves road safety. Most speed limit signs are static and remain unchanged for years and are thus available through navigation system map databases. However, there is an increasing number of variable message signs, temporary signing (e.g. for road works) and also changed speed limits which are not yet reflected in the map databases. With the TPEG-SPI application, speed limit information is offered in an accurate way so that different lanes and different vehicle types can be differentiated. TPEG-SPI also allows the drivers to be aware of the current allowed (maximum) speed, by delivering timely information about the current position and values of speed limits to the navigation or driver assistance systems. These data are seen as informational and are intended to be encoded in a compact way to minimize bandwidth consumption. TPEG2-SPI supports direct and indirect speed limits. Direct speed limits are used for signs showing a maximum speed at which a vehicle is allowed to travel. Such speed limit signs can be static or dynamic. Indirect speed limits refer to the speed of other road users. It is primarily the vehicle in front of the own vehicle that is used as a reference.
- Standard35 pagesEnglish languagesale 15% off
This document specifies the method for delivering service and network information within a TPEG service. The TPEG-SNI application is designed to allow the efficient, language-independent delivery of information about the availability of the same service on another bearer channel, or similar service data from another service provider, directly from service provider to end-users. A number of tables of information are described in this document which provide comprehensive options for describing services, their timing, content, geographical coverage, etc. In all TPEG streams, it is mandatory to deliver the so-called guide to the service table (GST). Additionally, it is possible to signal linkage of content between different bearers and services.
- Standard60 pagesEnglish languagesale 15% off
This document specifies the "traffic event compact" (TEC) TPEG application. The TEC application has been specifically designed to support information about traffic events (e.g. road works, traffic jams). A specific form of traffic event is local hazard warnings which, being safety-related messages, are sent with high priority to warn a driver of unexpected dangerous situations (e.g. black-ice, accident beyond curves, obstacles on road, etc.). Generally, the TEC application is designed to allow receivers to: — ensure travel safety for the driver; — enable the calculation of alternative routes; — avoid delays (e.g. traffic jams); — warn the driver of obstructions on route; and — provide the driver with information on infrastructural problems (e.g. closed petrol stations, non-functioning emergency telephones).
- Standard80 pagesEnglish languagesale 15% off
This document specifies the TPEG parking information (PKI) application which has been designed to deliver parking information to a variety of receivers using a number of different channels, particularly digital broadcasting and internet technologies. Parking information can be presented to the user in many different ways, including text, voice or graphics. Today, traffic congestion has become a serious problem in urban areas. Some traffic congestion is attributed to drivers searching for parking spaces. Timely provision of parking information can help to ease traffic congestion. Furthermore, parking information is valuable for visitors, particularly when it can be used to signal where a temporary parking facility is established for a special event.
- Standard51 pagesEnglish languagesale 15% off
This document specifies the TPEG fuel price information and availability (FPI) application. The FPI application has been specifically designed to support information from fuel stations, such as their location, fuel types offered and fuel pricing and availability information. The standardized delivery, via TPEG technology, of fuel price information has the following benefits for end users of a TPEG service: a) cost savings to the driver through improved ease of access to price information; b) potentially significant cost savings for fleet operators through improved ease of access to price information; c) environmental benefits from drivers not having to drive around to find the cheapest fuel prices; d) safety improvements for highways authorities, as drivers are less likely to run out of fuel if they are well-informed of local availability and prices; e) as availability of new fuels becomes more common, and more vehicles begin to use them (e.g. biofuels, hydrogen, etc.), drivers will be better informed about availability of fuelling stations. The TPEG FPI application (as an add-on service component next to traffic information, for example) is laid out to support large numbers of fuel stations and fuel prices with only modest bandwidth requirements The application described in this document (TPEG2-FPI) is not appropriate for cases where the objective is to inform electric vehicles of the location of charging stations and the availability of charging points. In such cases, the TPEG application TPEG2-EMI (electro mobility information) is chosen. This is because while TPEG2-FPI (the application described in this document) contains rudimentary support for electric charging stations, a TISA investigation revealed that a simple extension/differentiation of TPEG2-FPI is insufficient for addressing the evolving market needs of the electric vehicle market. Hence, a separate TPEG application has been created to serve the information needs of electric vehicles and their operators: TPEG2-EMI, specified in ISO/TS 21219-25.
- Standard64 pagesEnglish languagesale 15% off
This document defines the TPEG conditional access information (CAI) application. It allows the protection of the content of a TPEG service from unauthorized access. It further supports the management of subscriber information (e.g. control words and entitlement control message, ECM) on client devices in order to setup, prolong or revoke a subscription on a given client device. The CAI application defines: — the logical channel for the transmission of the additional CAI, and — how the CAI is linked and synchronized to the scrambled content. This document is related to conditional access applied on the service component level. It can be integrated into different conditional access systems. NOTE The basic concept behind the CAI application is to transport CAI in separate TPEG service components of a dedicated application type and to define a service and network information (SNI) table that contains the link between scrambled content and related CAI.
- Standard7 pagesEnglish languagesale 15% off
This document establishes a common methodology for the quantification and reporting of greenhouse gas (GHG) emissions arising from the operation of transport chains of passengers and freight.
- Standard133 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines terms, characterization and the relationship of concepts, defined using model-driven architecture methods, for parking and parking-related activities (both on-street and off-street) covering common data supporting business to business exchanges and end user services.
- Technical specification247 pagesEnglish languagesale 15% off
This document establishes a common methodology for the quantification and reporting of greenhouse gas (GHG) emissions arising from the operation of transport chains of passengers and freight.
- Standard133 pagesEnglish languagesale 10% offe-Library read for1 day
This document contains specifications for a set of ITS station security services required to ensure the authenticity of the source and integrity of information exchanged between trusted entities, i.e.: — between devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) as specified in ISO 21217; and — between ITS-SUs (composed of one or several ITS-SCUs) and external trusted entities such as sensor and control networks. These services include the authentication and secure session establishment which are required to exchange information in a trusted and secure manner. These services are essential for many intelligent transport system (ITS) applications and services including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2), and roadside/infrastructure-related services.
- Standard100 pagesEnglish languagesale 15% off
This document provides: — a framework for transportation services using 5G communication by providing meshes; — a description on expanding the service coverage of 5G backbone networks for transportation and mobility by applying meshes created in transportation facilities, vehicles and service dispatches; — a service framework using infrastructure, vehicles and mobility service providers; — a description on the effective transportation service for sustainable cities and communities.
- Standard7 pagesEnglish languagesale 15% off
This document describes the enterprise view (see ISO/TS 14812:2022, 3.1.4.3) of integrated mobility based on the role and responsibility models in the mobility as a service (MaaS) and mobility on demand (MOD) ecosystems as described in ISO/TR 4447. Other ISO documents (e.g. ISO 24014-1, ISO 17573-1 and ISO/TR 21724-1) have been reviewed in order to enhance and merge the MaaS and MOD role models. The enterprise view addresses the relationships between organizations and users, and the roles those entities play in the delivery and consumption of mobility services. Relationships between entities are dependent on the roles those entities take in the delivery of user services. Enterprise objects interact to exchange information, manage and operate systems beyond the scope of one organization. The enterprise view focuses on the relationships between those enterprise objects, but also defines how enterprise objects interact with physical objects, which appear in the enterprise view as "resources". This document focuses on mobility service concepts where the included transport services are publicly available. Examples of such transport services are listed in Clause 3.
- Technical report19 pagesEnglish languagesale 15% off
This document defines a platform-specific model (PSM) for data exchange, which specifically uses ASN.1 and TCP/UDP (transmission control protocol/user datagram protocol) datagrams which were defined as “DATEX-ASN” in the first edition of this document for AP-DATEX (application profile-data exchange) and other Internet protocol (IP) networks. A PSM is an actual implementation of a platform-independent model (PIM) for exchange. This document specifies the message rules and procedures for communication between different systems for ITS using TCP/UDP datagrams. This document deals mainly with the communication interfaces. It has been designed to meet the unique requirements of intelligent transport systems (ITS). However, it has also been designed in a generic fashion and thus can be used for other data exchanges as well.
- Standard83 pagesEnglish languagesale 15% off
This document, based on ISO/TS 19468, specifies a platform-specific method for implementing data exchange among centres based on simple object access protocol (SOAP), supporting the EN 16157 series (DATEX II) for Push/Pull data delivery and service request/feedback collaborative intelligent transport system (ITS) services.
This document defines the message rules and procedures for communication between transport information and control systems using XML (Profile B).
This document clarifies how to package end-application messages and relevant data.
The payload data definition used in specific end-applications and the exact structure of the content payload delivered in the messages are beyond the scope of this document.
Rules and procedures for exchanging data-packets in lower communication layers are also out of the scope of this document. These functionalities can be implemented using generic protocols defined in the industry standards. However, this document does define how to use these protocols.
- Technical specification25 pagesEnglish languagesale 10% offe-Library read for1 day
This document, based on ISO/TS 19468, specifies a platform-specific method for implementing data exchange among centres based on simple object access protocol (SOAP), supporting the EN 16157 series (DATEX II) for Push/Pull data delivery and service request/feedback collaborative intelligent transport system (ITS) services. This document defines the message rules and procedures for communication between transport information and control systems using XML (Profile B). This document clarifies how to package end-application messages and relevant data. The payload data definition used in specific end-applications and the exact structure of the content payload delivered in the messages are beyond the scope of this document. Rules and procedures for exchanging data-packets in lower communication layers are also out of the scope of this document. These functionalities can be implemented using generic protocols defined in the industry standards. However, this document does define how to use these protocols.
- Technical specification17 pagesEnglish languagesale 15% off
This document is used in conjunction with and is supplementary to EN 16247-1, Energy audits - Part 1: General requirements. It provides additional requirements to EN 16247-1 and is applied simultaneously.
The procedures described here apply to the different modes of transport (road, rail, marine and aviation), as well as the different ranges (local- to long-distance) and what is transported (i.e. goods and people).
This document specifies the requirements, methodology and deliverables specific to energy audits in the transport sector, every situation in which a displacement is made, no matter who the operator is (a public or private company or whether the operator is exclusively dedicated to transport or not), is also addressed in this document.
This document advises on both the optimization of energy within each mode of transport, as well as selecting the best mode of transport in each situation; the conclusions drawn by the energy audit can influence decisions on infrastructure and investment e.g. in teleconferencing or web meetings.
Energy audits of buildings and processes associated with transport can be conducted respectively with the EN 16247-2 Buildings and EN 16247-3 Processes, e.g. pipelines, depots and escalators/travelators. This part of the standard does not include the infrastructure which supplies energy e.g. the electricity generation of energy for railways.
- Standard24 pagesEnglish languagesale 10% offe-Library read for1 day
1.1 General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel European reference model for PT data. The most recent version of NeTEx v1.1 is based on the most recent version of Transmodel, V6.0 (EN 12986 1/2/3/4/5/6), which now incorporates the prior IFOPT (EN 28701). NeTEx also relates to SIRI (CEN 15531-1/2/3/4) and supports the exchange of information of relevance for passenger information about public transport services and also for running Automated Vehicle Monitoring Systems (AVMS).
NOTE NeTEx is an implementation of a subset of Transmodel (including IFOPT); the definitions and explanations of its concepts are extracted directly from Transmodel and reused in NeTEx, sometimes with adaptations in order to fit the NeTEx context. Although the data exchanges targeted by NeTEx Parts 1 to 5 are predominantly oriented towards provisioning passenger information systems, AVMS and fare systems with data from transit scheduling systems, it is not restricted to this purpose and NeTEx can also provide an effective solution to many other use cases for transport data exchange.
1.2 Alternative Modes Scope
This Part 5 of NeTEx is specifically concerned with the exchange of reference data to support “new” alternative modes for mobility services, adding certain new concepts to the NeTEx schema (indicated as NeTEx v1.2.2), but also to a high degree making use of existing schema elements defined in NeTEx Parts 1, 2 and 3.
The high-level design for alternative modes support is derived from a conceptual model for alternative modes CEN PT1711 (CEN/TS 17413:2020) prepared by CEN working group TC278 WG17. This CEN Technical Specification describes a conceptual model for alternative modes as an extension to Transmodel V6.0 and based on a detailed set of use cases taken from CEN PT1711 and given in Appendix A.
The NeTEx format is concerned with a subset of the use cases for reference data (real-time use cases are covered by dynamic protocols such as SIRI and DATEX II). Overall, it is concerned with data for the following purposes:
- to be able to integrate legs made on alternative modes with conventional mode legs in seamless trip plans;
- to describe the coverage areas of alternative mode mobility services so that trip planning engines and others can make passengers aware of the possibility of using them, and provide appropriate links to invoke the dynamic services;
- to be able to find the locations of access points for alternative mode services, such as parking points, pooling stations, etc. including their relation to access points for conventional modes;
- to be able to indicate the costs of the mobility services for specific trip legs. Where operators offer a bundle of modes services (for example free cycle use with metro use) to be able to include the “fare product” for alternative mode legs in the sales offer;
- to be able to indicate how to book, purchase and pay for mobility services, and how to access them.
NeTEx is primarily concerned with the exchange of reference data to allow the integration of new modes with other data; it does not describe dynamic services. The PT1711 specification indicates the nature of some of these services such as trip planning.
1.3 Transport modes
All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, air, and their submodes. Such modes are provided by transport operators, who may operate one or more modes.
NeTEx part 5 widens the concept of an operator to include providers of other forms of transport, and introduces the separate concept of a “mode of operation” to classify the way services are provided: conventional, flexible, pooling, sharing, etc.
...
- Technical specification511 pagesEnglish languagesale 10% offe-Library read for1 day
- Technical specification511 pagesEnglish languagesale 10% offe-Library read for1 day
The ISO 17572 series specifies location referencing methods (LRMs) that describe locations in the context of geographic databases and that are intended for use in locating transport-related phenomena both in an encoder system and from the decoder side. This document defines what is meant by such objects and describes the reference in detail, including whether or not components of the reference are mandatory or optional, and their characteristics. The ISO 17572 series specifies three different LRMs: — pre-coded LRM (pre-coded profile); — dynamic LRM (dynamic profile); — precise relative LRM (precise relative profile). The ISO 17572 series does not define a physical format for implementing the LRM. However, the requirements for physical formats are defined. The ISO 17572 series does not define details of the location referencing system (LRS), i.e. how the LRMs are to be implemented in software, hardware or processes. This document specifies the following general LRM-related subjects: — requirements of an LRM; — conceptual data model for LRMs; — inventory LRMs (see Annex A). This document also provides: — examples of conceptual model use (see Annex B); — a comparison of definitions with ISO/TC 211 (see Annex C).
- Standard21 pagesEnglish languagesale 15% off
This document specifies requirements and recommendations for the planning, design, development and provision of user communications related to passenger transport so that these communications can be accessed, understood and used by the widest range of users, including persons with disabilities and older persons.
These requirements and recommendations enable an organization to extend its range of users by identifying diverse characteristics, capabilities, and preferences.
The requirements specified in this standard are applicable to but not limited to passenger transport service providers including air-, bus, rail-, and waterborne passenger transport services.
- Standard59 pagesEnglish languagesale 10% offe-Library read for1 day