This document describes a basic role model of smart city intelligent transport systems (ITS) service applications as a common platform for smart city instantiation, directly communicating via secure ITS interfaces. It provides a paradigm describing: a) a framework for the provision of a cooperative ITS service application; b) a description of the concept of operations, regulatory aspects and options, and the role models; c) a conceptual architecture between actors involved in the provision/receipt of ITS service applications; d) references for the key documents on which the architecture is based; e) a taxonomy of the organization of generic procedures.

  • Technical report
    36 pages
    English language
    sale 15% off
  • Draft
    36 pages
    English language
    sale 15% off

This document specifies a procedure for run-through train operations, identified as smart transportation. This concept provides direct, one-seat ride services in high quality corridors connecting cities and transportation hubs without forcing transfers. Improved operations planning, greater use of interchange or rental use arrangements are described so that these services can be implemented without constructing major infrastructure improvements in existing transportation corridors and right-of-way. This document also describes the application of run-through operation in bus services that are strictly licensed to bus carriers using public roads, ending the inconvenience of forcing passenger transfers between routes or service territories. NOTEÂ Â Â Â Â Â Smart transportation by run-through operation is applicable to other transportation modes besides rail and bus services, if applied in services operated in the same mode. Refer to ISOÂ 37154 for applicable transportation modes.

  • Standard
    13 pages
    English language
    sale 15% off
  • Draft
    13 pages
    English language
    sale 15% off

This document describes various use cases for the sharing of probe vehicle data as a common platform for smart city instantiation. When modernizing a city towards a smart city, it is necessary for information flows across various fields, such as transportation, healthcare, energy, water and other government services, to be effectively managed and shared. Despite efforts from many cities, integrating all databases related to all services has proven to be a cumbersome task. One challenge is the lack of a systematic way that can be modelled for data sharing. The ITS data sharing model for vehicle probe data can serve as the basis for instigating this type of work. To elaborate how vehicle probe data work can be applied to achieve this objective, this document: —   gathers use cases and examples of vehicle probe data sharing around the world, and —   provides use cases for data sharing that are appropriate for smart city ITS mobility solutions. By examining these use cases and current and planned data sharing practices around the world, this document demonstrates how this mechanism can help implement many smart city applications. This document also shows that by combining the vehicle probe data with roadside sensor data, and other important public and private data sources, the services can be operated more effectively. Data collection methods and data or information provisioning are beyond the scope this document. Specifically, this document does not describe items related to the vehicle probe data collection nor the vehicle probe data provision activities as specified by other existing standards such as ISO 19414.

  • Technical report
    22 pages
    English language
    sale 15% off
  • Draft
    22 pages
    English language
    sale 15% off

This document provides guidance on transportation and its related or additional services using quick response (QR) codes for identification and authentication in data transfer, in order to make their services both convenient and advantageous for customers and service agents while protecting them from cheating and illegal action in data transfer.

  • Standard
    10 pages
    English language
    sale 15% off
  • Draft
    10 pages
    English language
    sale 15% off

This document describes how to organize smart transportation to save energy consumed in operation, by modifying speed profiles of trains, buses, trucks and ferries, which is also able to offer passenger-friendly driving of transportation vehicles.

  • Standard
    10 pages
    English language
    sale 15% off
  • Draft
    10 pages
    English language
    sale 15% off

This document specifies a global transport data management (GTDM) framework composed of
— global transport basic data model,
— global transport access control data model,
— global transport function monitor data model, and
— sensor and control network data model
to support data exchange between applications.
This document defines standardized data classes in a Global Transport Data Format (GTDF), and the
means to manage them.
Application and role-based access control to resources in GTDF are specified in accordance with
IEEE 1609.2 certificates.
This document specifies GTDM as an ITS-S capability which is an optional feature (ITS-capabilities are
specified in ISO 24102-6).
The GT access control (GTAC) data model specifies access permissions to data and function control by
defining role-based mechanisms.
The GT function monitor (GTFM) data model specifies a configuration method to generate a flow logic
for monitoring purposes, e.g. observing data parameters with respect of a defined limit.

  • Technical specification
    124 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies: —   the Localized Message (LM) format: an NPDU of a networking & transport layer protocol that does not support routing of a packet through a network; —   the Service Advertisement Message (SAM): an APDU to be transported in an LM, for example; —   the Service Response Message (SRM): an APDU acknowledging a SAM that offered a service based on an ITS application class[2] to be transported in an LM, for example; —   related basic requirements for procedures. Specifications are partly done by normative references to IEEE 1609.3(TM)-2016. NOTE      These message format specifications and basic procedures need to be complemented by complete procedures and SAP specifications according to the context of usage, i.e. an ITS station specified in ISO 21217, or a WAVE device specified in IEEE 1609.0[13] or any other context.

  • Standard
    46 pages
    English language
    sale 15% off
  • Draft
    46 pages
    English language
    sale 15% off

This document provides guidelines on security applicable in Intelligent Transport Systems (ITS) related
to communications and data access.
In particular, this document provides analyses and best practice content for secure ITS connectivity
using ISO/TS 21177.
This document analyses and identifies issues related to application security, access control, device
security and PKI for a secure ITS ecosystem.

  • Technical report
    135 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document serves as a guideline explaining the concept of hybrid communications and support
functionalities for Cooperative ITS services deployed in conformance with the ITS station architecture
and related Cooperative ITS standards.

  • Technical report
    39 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document
— describes standardization activities related to C-ITS on a global level by major standard development
organizations (SDOs);
— explains the various purposes of deliverables from SDOs and introduces a classification scheme of
such documents;
— describes methods on how C-ITS services are presented and performed;
— identifies an approach for C-ITS releases and exemplifies this approach;
— presents a list of standards (Bibliography) with special relevance for C-ITS.

  • Technical report
    33 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document gives guidelines for the development of multi-operator/multi-service interoperable
public surface (including subways) transport fare management systems (IFMSs) on a national and
international level.
This document is applicable to bodies in public transport and related services which agree that their
systems need to interoperate.
This document defines a conceptual framework which is independent of organizational and physical
implementation. Any reference within this document to organizational or physical implementation is
purely informative.
This document defines a reference functional architecture for IFMSs and establishes the requirements
that are relevant for ensuring interoperability between several actors in the context of the use of
electronic tickets.
The IFMS includes all the functions involved in the fare management process, such as:
— management of media,
— management of applications,
— management of products,
— security management, and
— certification, registration, and identification.
This document defines the following main elements:
— identification of the different sets of functions in relation to the overall IFMS and services and media
from non-transport systems which interact with fare management systems;
— a generic model of an IFMS describing the logical and functional architecture and the interfaces
within the system, with other IFMSs and with services and media from non-transport systems;
— use cases describing the interactions and data flows between the different sets of functions;
— security requirements.
In its annexes, this document provides a framework for mobility platforms that integrate fare
management and travel information for inter- and multimodal travel (see Annex A). It also elaborates
on specific subjects covered in document and offers some national examples with regard to IFMS
implementations (see Annex B, Annex C, Annex D and Annex E).
This document does not define:
— the technical aspects of the interface between the medium and the medium access device;
— the data exchanges between the medium and the medium access device;
NOTE The data exchanges between the medium and the medium access device are proposed by other
standardization committees.
— the financial aspects of fare management systems (e.g. customer payments, method of payment,
settlement, apportionment, reconciliation).

  • Standard
    92 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies a global transport data management (GTDM) framework composed of — global transport basic data model, — global transport access control data model, — global transport function monitor data model, and — sensor and control network data model to support data exchange between applications. This document defines standardized data classes in a Global Transport Data Format (GTDF), and the means to manage them. Application and role-based access control to resources in GTDF are specified in accordance with IEEE 1609.2 certificates. This document specifies GTDM as an ITS-S capability which is an optional feature (ITS-capabilities are specified in ISO 24102-6). The GT access control (GTAC) data model specifies access permissions to data and function control by defining role-based mechanisms. The GT function monitor (GTFM) data model specifies a configuration method to generate a flow logic for monitoring purposes, e.g. observing data parameters with respect of a defined limit.

  • Technical specification
    115 pages
    English language
    sale 15% off
  • Draft
    119 pages
    English language
    sale 15% off

This document provides guidelines on security applicable in Intelligent Transport Systems (ITS) related to communications and data access. In particular, this document provides analyses and best practice content for secure ITS connectivity using ISO/TS 21177. This document analyses and identifies issues related to application security, access control, device security and PKI for a secure ITS ecosystem.

  • Technical report
    125 pages
    English language
    sale 15% off
  • Draft
    125 pages
    English language
    sale 15% off

This document serves as a guideline explaining the concept of hybrid communications and support functionalities for Cooperative ITS services deployed in conformance with the ITS station architecture and related Cooperative ITS standards.

  • Technical report
    30 pages
    English language
    sale 15% off
  • Draft
    28 pages
    English language
    sale 15% off

This document gives guidelines for the development of multi-operator/multi-service interoperable public surface (including subways) transport fare management systems (IFMSs) on a national and international level. This document is applicable to bodies in public transport and related services which agree that their systems need to interoperate. This document defines a conceptual framework which is independent of organizational and physical implementation. Any reference within this document to organizational or physical implementation is purely informative. This document defines a reference functional architecture for IFMSs and establishes the requirements that are relevant for ensuring interoperability between several actors in the context of the use of electronic tickets. The IFMS includes all the functions involved in the fare management process, such as: — management of media, — management of applications, — management of products, — security management, and — certification, registration, and identification. This document defines the following main elements: — identification of the different sets of functions in relation to the overall IFMS and services and media from non-transport systems which interact with fare management systems; — a generic model of an IFMS describing the logical and functional architecture and the interfaces within the system, with other IFMSs and with services and media from non-transport systems; — use cases describing the interactions and data flows between the different sets of functions; — security requirements. In its annexes, this document provides a framework for mobility platforms that integrate fare management and travel information for inter- and multimodal travel (see Annex A). It also elaborates on specific subjects covered in document and offers some national examples with regard to IFMS implementations (see Annex B, Annex C, Annex D and Annex E). This document does not define: — the technical aspects of the interface between the medium and the medium access device; — the data exchanges between the medium and the medium access device; NOTE The data exchanges between the medium and the medium access device are proposed by other standardization committees. — the financial aspects of fare management systems (e.g. customer payments, method of payment, settlement, apportionment, reconciliation).

  • Standard
    81 pages
    English language
    sale 15% off
  • Standard
    85 pages
    French language
    sale 15% off
  • Draft
    81 pages
    English language
    sale 15% off

This document — describes standardization activities related to C-ITS on a global level by major standard development organizations (SDOs); — explains the various purposes of deliverables from SDOs and introduces a classification scheme of such documents; — describes methods on how C-ITS services are presented and performed; — identifies an approach for C-ITS releases and exemplifies this approach; — presents a list of standards (Bibliography) with special relevance for C-ITS.

  • Technical report
    25 pages
    English language
    sale 15% off
  • Draft
    25 pages
    English language
    sale 15% off

This document describes the communications reference architecture of nodes called "ITS station units" designed for deployment in intelligent transport systems (ITS) communication networks. The ITS station reference architecture is described in an abstract manner. While this document describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. This document also describes the various communication modes for peer-to-peer communications over various networks between ITS communication nodes. These nodes can be ITS station units as described in this document or any other reachable nodes. This document specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain.

  • Standard
    55 pages
    English language
    sale 15% off
  • Draft
    55 pages
    English language
    sale 15% off

This document defines the use cases and general requirements for supporting emergency services via P-ITS-S. Any automotive-related service providers can refer to this document for developing eCall service systems into eCall non-supportive vehicles. The P-ITS-S acts as a monitoring and data transmitting device which gathers a vehicle's speed, impact and airbag deployment signal to assess the accident occurrence and type of accident. Once gathered data has been determined as an accident, accident related information is sent to an emergency service centre. Only notable events, such as an airbag-deployed event, rollover and stationary accident, are concerned by this document. In addition, the vehicle data gathering device requirement and implementation methodology for the emergency service are not applicable to this document.

  • Standard
    17 pages
    English language
    sale 15% off
  • Draft
    17 pages
    English language
    sale 15% off

This document gives guidelines for providing mobility information according to user preference on demand, utilizing a variety of existing applications on nomadic devices related to different means of transport. This document defines an integrated mobility information platform as a service methodology to be integrated with a variety of mobile apps with respect to different transport modes. This document defines the following urban mobility applications: — guidance documents to facilitate the practical implementation of identified standards in the transportation planning process, including related use cases; — provision of urban mobility information integrated with a variety of mobile apps on nomadic devices by multiple transport modes for collecting trip production and attraction data; — modal choice data based on time effectiveness, cost effectiveness, and eco-effectiveness in the trip distribution from origins to destinations.

  • Standard
    17 pages
    English language
    sale 15% off
  • Draft
    17 pages
    English language
    sale 15% off

This document specifies a generic position, velocity and time (PVT) service. It further specifies
the PVT service within the ITS station (ITS-S) facilities layer (ISO 21217) and its interface to other
functionalities in an ITS-S such as:
— ITS-S application processes (ITS-S-APs), defined in ISO 21217;
— the generic facilities service handler (FSH) functionality of the ITS station facilities layer, defined in
ISO/TS 17429.
This document specifies:
— a PVT service which, dependent on a specific implementation, uses a variety of positioning-related
sources such as global navigation satellite systems (GNSSs, e.g. GALILEO, GLONASS and GPS),
roadside infrastructure, cellular infrastructure, kinematic state sensors, vision sensors;
— a PVT service which merges data from the above-mentioned positioning-related sources and
provides the PVT output parameters (carrying the PVT information) including the associated
quality (e.g. accuracy);
— how the PVT service is integrated as an ITS-S capability of the ITS station facilities layer;
— the interface function calls and responses (Service Access Point – service primitives) between the
PVT ITS-S capability and other functionalities of the ITS station architecture;
— optionally, the PVT service as a capability of the ITS-S facilities layer; see ISO 24102-6;
— an ASN.1 module C-itsPvt, providing ASN.1 type and value definitions (in Annex A);
— an implementation conformance statement proforma (in Annex B), as a basis for assessment of
conformity to this document.
NOTE It is outside the scope of this document to define the associated conformance evaluation test
procedures.

  • Technical specification
    37 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides guidance on how to organize and implement smart transportation by digitally processed payment (d-payment) in order to provide a safe, convenient payment method for citizens and city visitors in transportation and its related or additional services. This will additionally benefit operators managing fee receipt in transportation services and money transfer or transactions between these business operators and banks or settlement organizations. Smart transportation by d-payment is not intended to eliminate cash payment from transportation services but is helpful in organizing inter-operator, city, regional and national common ticket networks and providing trading services independent of local currencies.

  • Standard
    8 pages
    English language
    sale 15% off
  • Draft
    8 pages
    English language
    sale 15% off

This document specifies a generic position, velocity and time (PVT) service. It further specifies the PVT service within the ITS station (ITS-S) facilities layer (ISO 21217) and its interface to other functionalities in an ITS-S such as: — ITS-S application processes (ITS-S-APs), defined in ISO 21217; — the generic facilities service handler (FSH) functionality of the ITS station facilities layer, defined in ISO/TS 17429. This document specifies: — a PVT service which, dependent on a specific implementation, uses a variety of positioning-related sources such as global navigation satellite systems (GNSSs, e.g. GALILEO, GLONASS and GPS), roadside infrastructure, cellular infrastructure, kinematic state sensors, vision sensors; — a PVT service which merges data from the above-mentioned positioning-related sources and provides the PVT output parameters (carrying the PVT information) including the associated quality (e.g. accuracy); — how the PVT service is integrated as an ITS-S capability of the ITS station facilities layer; — the interface function calls and responses (Service Access Point ? service primitives) between the PVT ITS-S capability and other functionalities of the ITS station architecture; — optionally, the PVT service as a capability of the ITS-S facilities layer; see ISO 24102-6; — an ASN.1 module C-itsPvt, providing ASN.1 type and value definitions (in Annex A); — an implementation conformance statement proforma (in Annex B), as a basis for assessment of conformity to this document. NOTE It is outside the scope of this document to define the associated conformance evaluation test procedures.

  • Technical specification
    28 pages
    English language
    sale 15% off
  • Draft
    28 pages
    English language
    sale 15% off

This document specifies the fast service announcement protocol (FSAP) for general purposes in ITS.
It references and supports all features of ISO/TS 16460, especially supporting the service response
message (SRM) and related features in addition to the service announcement message (SAM), which
enables only very basic features.
FSAP supports locally advertised ITS services uniquely identified by an ITS application identifier
(ITS-AID).
This document specifies message formats and related basic protocol procedures by reference to
ISO/TS 16460, and further related protocol requirements for operation of FSAP in the context of an ITS
station specified in ISO 21217.
This document illustrates its relations to service announcement protocols specified by ETSI TC ITS
and IEEE.

  • Standard
    64 pages
    English language
    sale 10% off
    e-Library read for
    1 day

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V6 (EN 12896 series) and SIRI (CEN/TS 15531-4/-5 and EN 15531-1/-2/-3) 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   Many NeTEx concepts are taken directly from Transmodel; the definitions and explanation of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptions in order to fit the NeTEx context.
Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger information systems and AVMS 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   Transport modes
All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional requirements that apply specifically to air transport.
1.3   Compatibility with existing standards and recommendations
Concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train composition and facilities; planned passing times; timetable versions and validity conditions.
In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (European Rail Agency) - TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperability, entered into force on 13 May 2011 as the Commission Regulation (EU) No 454/2011), based on UIC directives.
As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (The Netherlands) and NOPTIS (Nordic Public Transport Interface Standard).
The data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation.

  • Technical specification
    1078 pages
    English language
    sale 10% off
    e-Library read for
    1 day

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V5.1 (EN 12986), IFOPT (CEN/TS 28701) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3 ) and supports information exchange of relevance to public transport services for passenger information and AVMS systems.
NOTE   Many NeTEx concepts are taken directly from Transmodel and IFOPT; the definitions and explanation of these concepts are extracted directly from the respective standards and reused in NeTEx, sometimes with further adaptions in order to fit the NETEx context.
The data exchanges targeted by NeTEx are predominantly oriented towards passenger information and also for data exchange between transit scheduling systems and AVMS (Automated Vehicle Monitoring Systems). However it is not restricted to these purposes, and NeTEx can provide an effective solution to many other use cases for transport exchange.
1.2   Transport modes
Most public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tram-way, ferry, and their submodes. It is possible to describe airports and air journeys, but there has not been any specific consideration of any additional provisions that apply especially to air transport.
1.3   Compatibility with existing standards and recommendations
The concepts covered in NeTEx that relate in particular to long-distance train travel include; rail operators and related organizations; stations and related equipment; journey coupling and journey parts; train com-position and facilities; planned passing times; timetable versions and validity conditions.
In the case of long distance train the NeTEx takes into account the requirements formulated by the ERA (European Rail Agency) – TAP/TSI (Telematics Applications for Passenger/ Technical Specification for Interoperability, entered into force on 13 May 2011 as the Commission Regulation (EU) No 454/2011), based on UIC directives.
As regards the other exchange protocols, a formal compatibility is ensured with TransXChange (UK), VDV 452 (Germany), NEPTUNE (France), UIC Leaflet, BISON (Netherland) and NOPTIS (Nordic Public Transport Interface Standard).
The data exchange is possible either through dedicated web services, through data file exchanges, or using the SIRI exchange protocol as described in part 2 of the SIRI documentation.

  • Technical specification
    258 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the fast service announcement protocol (FSAP) for general purposes in ITS. It references and supports all features of ISO/TS 16460, especially supporting the service response message (SRM) and related features in addition to the service announcement message (SAM), which enables only very basic features. FSAP supports locally advertised ITS services uniquely identified by an ITS application identifier (ITS-AID). This document specifies message formats and related basic protocol procedures by reference to ISO/TS 16460, and further related protocol requirements for operation of FSAP in the context of an ITS station specified in ISO 21217. This document illustrates its relations to service announcement protocols specified by ETSI TC ITS and IEEE.

  • Standard
    55 pages
    English language
    sale 15% off
  • Standard
    55 pages
    English language
    sale 15% off
  • Standard
    59 pages
    French language
    sale 15% off

This document specifies a conformance test for a UVIP server and client system developer assessment of self-conformance of the supplier's UVIP server and client system. The conformance test cases follow the use cases definition of ISO 13185-1 and the requirements stated in ISO 13185-2 and ISO 13185-3. The purpose of this document is to provide information to the UVIP server and client system provider to build and test the UVIP server and client system against the conformance test cases.

  • Standard
    39 pages
    English language
    sale 15% off

This technical specification is a profile of CEN/TS 16614 series. It focuses on information relevant to feed passenger information services and excludes operational and fares information.
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information) based on Transmodel V6 (EN 12986) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3) and supports information exchange of relevance to public transport services for passenger information and AVMS systems.
As for most data exchange standards, defining subsets of data and dedicated rules for some specific use case is of great help for implementers and for the overall interoperability. This subset is usually called profile and this profile targets passenger information as only use case.

  • Technical specification
    177 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    177 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    177 pages
    English language
    sale 10% off
    e-Library read for
    1 day

1.1   General
NeTEx is dedicated to the exchange of scheduled data (network, timetable and fare information). It is based on Transmodel V5.1 (EN 12986), IFOPT (EN 28701) and SIRI (CEN/TS 15531-4/5 and EN 15531-1/2/3 ) 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 a refinement and an implementation of Transmodel and IFOPT; the definitions and explanations of these concepts are extracted directly from the respective standard and reused in NeTEx, sometimes with adaptations in order to fit the NeTEx context. Although the data exchanges targeted by NeTEx are predominantly oriented towards provisioning passenger information systems and AVMS 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   Fares scope
This Part3 of NeTEx, is specifically concerned with the exchange of fare structures and fare data, using data models that relate to the underlying network and timetable models defined in Part1 and Part2 and the Fare Collection data model defined in Transmodel V51. See the use cases below for the overall scope of Part3. In summary, it is concerned with data for the following purposes:
(i)   To describe the many various possible fare structures that arise in public transport (for example, flat fares, zonal fares, time dependent fares, distance-based fares, stage fares, pay as you go fares, season passes, etc., etc.).
(ii)   To describe the fare products that may be purchased having these fare structures and to describe the conditions that may attach to particular fares, for example if restricted to specific groups of users, or subject to temporal restrictions. These conditions may be complex.
(i)   To allow actual price data to be exchanged. Note however that NeTEx does not itself specify pricing algorithms or how fares should be calculated. This is the concern of Fare Management Systems. It may be used may be used to exchange various parameters required for pricing calculations that are needed to explain or justify a fare.
(iii)   To include the attributes and the text descriptions necessary to present fares and their conditions of sale and use to the public.
NeTEx should be regarded as being ‘upstream’ of retail systems and allows fare data to be managed and integrated with journey planning and network data in public facing information systems. It is complementary to and distinct from the ‘downstream’ ticketing and retail systems that sell fares and of the control systems that validate their use. See ‘Excluded Use Cases’ below for further information on the boundaries of NeTEx with Fare Management Systems.
1.3   Transport modes
All mass public transport modes are taken into account by NeTEx, including train, bus, coach, metro, tramway, ferry, and their submodes. It is possible to describe airports, air journeys, and air fares, but there has not been any specific consideration of any additional requirements that apply specifically to air transport.

  • Technical specification
    622 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Technical specification
    622 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document describes and lists the characteristics of the Precise Relative Location Referencing Method (PRLRM) which describes precise relative locations in the context of geographic databases and is used to locate transport-related objects in an encoder system as well as in the decoder side. This document does not define a physical format for implementing the PRLRM. However, the requirements for physical formats are defined. This document does not define details of the Precise Relative Location Referencing System (PRLRS), i.e. how the PRLRM is to be implemented in software, hardware or processes. This document specifies PRLRM, comprising: — conceptual data model for Location Referencing Methods (LFMs); — specification of location referencing for precise relative information; — use cases for Precise Relative Location References (informative Annex C); — use cases for elements of Precise Relative Location References (informative Annex D); — implementation of Precise Relative Location References (Japanese example) (informative Annex E). This document defines methods that enable exchange location information of the object to be referenced in the lane or the lane junction. This document does not specify the road (link) on which the object of reference exists.

  • Standard
    28 pages
    English language
    sale 15% off

This document defines an application interface between DSRC-based OBE (hereinafter referred to as "DSRC-OBE") and an external in-vehicle device (hereinafter referred to as "the external device") to make DSRC-OBE applicable for diversified external devices. NOTE For use in autonomous tolling and DSRC-based (CEN, UNI, ARIB, TTA and GB/T) electronic fee collection (EFC) systems. For use in urban and inter-urban toll schemes. The scope of this document covers the following items (as shown in Figure 4): — definitions of the application interface between DSRC-OBE and external devices, including global navigation satellite system (GNSS), cellular network (CN) and controller area network (CAN) device; — definitions of data groups and data elements. Figure 4 — Scope of this document The following items are out of the scope of this document: — definitions of hardware components in the external device such as GNSS module, CN module and mobile devices; — definitions of the physical interface between DSRC-OBE and the external device such as USB and Bluetooth; — definition of ITS services other than EFC; — definition of algorithms for authentication, encryption and key management.

  • Technical specification
    20 pages
    English language
    sale 15% off

This document provides guidance on reducing the energy consumed by transportation for passengers, delivery items, freight and postal item services in cities and city zones. This document does not designate specific procedures to save energy but suggests energy-saving options to be adopted in transportation systems normally organized in different locations, on different scales and for different purposes. NOTE Some typical energy-saving options are listed in 6.2.2.

  • Standard
    15 pages
    English language
    sale 15% off

This document specifies a procedure to arrange smart transportation for newly developing areas, including transportation services between the area and existing city centres. This document does not designate procedures for constructing smart transportation facilities.

  • Standard
    10 pages
    English language
    sale 15% off

An intelligent transport system (ITS) reference architecture is a tool that describes how an ITS delivers one or more ITS services. It includes a high-level description of the major elements and the interconnections among them that are needed for the service(s) to be provided to stakeholders. It provides the framework around which the interfaces, specifications, and detailed ITS designs can be standardized within ITS standards. By contrast, ITS standards are often focused on design details. While the development of these standards may be initiated by a single ITS user need, they are often (and properly) written in a generic format that allows for application in a broad array of contexts. However, this can present a challenge to the reader in understanding the original purpose of a standard and whether the standard is intended for other environments. This document defines documentation rules for standards that define interfaces between or among system elements of an ITS reference architecture. This includes: a) requirements for documenting aspects of the ITS reference architecture; b) terminology to be used when documenting or referencing aspects of the ITS reference architecture. In compiling this document, the authors have assumed that contemporary systems engineering practices are used. Such practices are not defined within this document.

  • Standard
    21 pages
    English language
    sale 15% off

This document specifies a service architecture that defines the framework and domain for classification of probe vehicle systems (PVS), which are systems that collect probe data from private vehicles and that process the probe data statistically towards useful information that finally can be provided to end users. This document focuses on services that can be developed using public sector probe data that are generated by vehicles. It specifies the following items related to PVS: — service framework of probe vehicle systems; — definition of service domain of PVS.

  • Standard
    11 pages
    English language
    sale 15% off

This document provides governance rules to be used for executing an organized process for business entities to connect to one another electronically for the conduct of electronic trade in a secure and open environment through a standardized framework for information exchange. This standardized framework includes processes and process tools to ease connections between trading partners, to provide full visibility, and to reduce the time goods spend in transit. The application of these rules and attendant standards and technology applications are expected to allow business entities to engage their legacy systems without the cost of upgrades.

  • Technical specification
    29 pages
    English language
    sale 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: - devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) 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 authentication and secure session establishment which are required to exchange information in a trusted and secure manner. These services are essential for many ITS applications and services including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2[5]), and roadside/infrastructure related services.

  • Technical specification
    97 pages
    English language
    sale 10% off
    e-Library read for
    1 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:
— devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) 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 authentication and secure session establishment which are required to exchange information in a trusted and secure manner.
These services are essential for many ITS applications and services including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2[5]), and roadside/infrastructure related services.

  • Technical specification
    97 pages
    English language
    sale 10% off
    e-Library read for
    1 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: — devices operated as bounded secured managed entities, i.e. "ITS Station Communication Units" (ITS-SCU) and "ITS station units" (ITS-SU) 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 authentication and secure session establishment which are required to exchange information in a trusted and secure manner. These services are essential for many ITS applications and services including time-critical safety applications, automated driving, remote management of ITS stations (ISO 24102-2[5]), and roadside/infrastructure related services.

  • Technical specification
    83 pages
    English language
    sale 15% off

This document establishes a method of conveying data for a wide range of applications that require the efficient transmission of point to multi-point data over potentially unreliable broadcast channels. It is also suitable for point-to-point and multicast applications and may easily be encapsulated in Internet Protocol. This document describes the basic capabilities of the generation 2 TPEG (TPEG2) for providing a multiplex of TPEG Services and applications. Together with the definitions of the general TPEG UML modelling rules and the particular physical TPEG representations for TPEG-binary streams (TISA: TPEG UML Conversion Rules) and tpegML files (TISA Specification: TPEG UML Conversion Rules), it replaces the former documents TPEG-INV and TPEG-SSF.

  • Standard
    42 pages
    English language
    sale 15% off

This document specifies the rules for converting TPEG application UML models to the tpegML format description. It contains the XML format definition of the abstract data types defined in ISO 21219-2. Rules for converting compound data types are also defined.

  • Standard
    40 pages
    English language
    sale 15% off

This document adds a basic toolkit definition to the ISO 21219 series specifying the Message Management Container (MMC) which is used by all TPEG applications to provide information about the handling of messages on the TPEG client side. The MMC holds administrative information allowing a decoder to handle the message appropriately. This information is not aimed at the end user. The MMC is a toolkit and not a stand-alone application but is included by TPEG applications.

  • Standard
    21 pages
    English language
    sale 15% off

TPEG applications are modelled in UML to provide an application description that is independent of a physical format representation. By separating semantics from application description, applications can easily be developed at a functional level. Different physical format representations can be generated following a well defined set of rules on how to convert UML classes to different physical formats. This document specifies the rules for converting UML models of TPEG application to the TPEG binary format. It contains the binary format definition of the abstract data types defined in ISO 21219-2. Rules for converting compound data types are also defined.

  • Standard
    19 pages
    English language
    sale 15% off

This document specifies the TPEG application Traffic Flow and Prediction (TFP). It has been specifically designed to provide information to a variety of receivers using different channels, including in the first instance digital broadcasting and Internet technologies. Traffic flow and prediction messages are intended for in-car applications and can also be presented directly to the user by textual, voice and graphical output devices. TFP is status oriented, i.e. the transmitted information continuously updates the receiver's knowledge for a dedicated road network. In particular the traffic states are delivered any time and for all road sections of the network, even when there are no abnormal traffic situations. Generally, TFP focuses on the following requirements: — provides dynamic navigation systems with up-to-date traffic state information; — ensures travel safety for the driver; — enables the calculation of alternative routes; — avoids delays (e.g. traffic jams); — lowers traffic load on over-saturated parts of the network; — keeps the driver informed about current and upcoming traffic; — compact and efficient coding of the traffic information.

  • Standard
    58 pages
    English language
    sale 15% off

This document specifies rules for the creation and extending of TPEG application UML models. The rules are intended to ensure that TPEG application UML models can be interpreted unambiguously for conversion to physical format representations. TPEG application UML models that are defined according to these rules can be used for automatic generation of TPEG standards and for automatic generation of TPEG application physical format descriptions. This document also specifies the preferred structure of TPEG application specifications. The TPEG abstract data types and the set of TPEG tables of common use are specified in the annexes.

  • Standard
    42 pages
    English language
    sale 15% off

This Technical Specification provides the Protocol Implementation Conformance Statement (PICS) pro forma for Conformance test specification for the Contextual Speed Information Service as defined in CEN ISO/TS 17426:2016 in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7.

  • Technical specification
    17 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides the Protocol Implementation Conformance Statement (PICS) pro forma for conformance test specification for the Contextual Speed Information Service as defined in ISO/TS 17426:2016 in accordance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7.

  • Technical specification
    17 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies a procedure to organize smart transportation that enables one-day trips by citizens between cities and in a large city zone, including its surrounding areas, and conveys a large number of people at a high frequency in a short time over distances of up to 1 000 km. Smart transportation aims to promote political and economic work and stimulate business activity by providing citizens with a manner of travel to complete a return trip from their home or place of work to destinations outside their cities on the same day. However, this document does not designate a procedure for constructing smart transportation facilities. NOTE "One-day trip" means travel from an origin to a destination and back to the origin on the same day. The purpose of such travel is out of the scope of this document.

  • Standard
    9 pages
    English language
    sale 15% off

This document defines a shareable geospatial database service framework and provides an overview of the ISO 19297 series of standards. This is intended to enhance user accessibility and interoperability of databases. It does not cover ITS applications or service specific issues.

  • Standard
    12 pages
    English language
    sale 15% off

This document provides the Protocol Implementation Conformance Statement (PICS) pro forma for conformance test specification for the Contextual Speed Information Service as defined in ISO/TS 17426:2016 in accordance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7.

  • Technical specification
    9 pages
    English language
    sale 15% off