| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO/TS 15638-6:2013 |
Intelligent transport systems —- Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 6: Regulated applications |
ISO/TS 15638-6:2013 specifies the common roles and responsibilities of actors providing regulated application (4.47) systems which use TARV to provide regulated application services (4.48) for regulated commercial freight vehicles (4.49), and the interoperability of key operational steps and actions required to support all TARV regulated application service (4.48) systems.
ISO/TS 15638-6:2013 specifies the general conditions for data exchanges between an application service provider (4.7) and vehicle IVS (4.32), and from other ITS-stations (4.34) to the IVS of the regulated commercial freight vehicle (4.49), and specifies generic data concepts for identified services, but it does not define the detailed aspects of the application services (4.6) or their implementation, application specific aspects being defined in defined in ISO 15638-8 et sequential for each identified application service.
ISO/TS 15638-6:2013 addresses the general and common requirements for the provision of regulated application services (4.48) that require data in addition to, or instead of, basic vehicle data (4.16) and core application data (4.23) (application specific aspects being defined in defined in ISO 15638-8 et sequential for each identified application service).
ISO/TS 15638-6:2013 provides common aspects of specifications (4.55) for communications and data exchange aspects of identified application services (4.6) (as defined in defined in ISO 15638-8 et sequentia) that a regulator (4.50) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.53) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.6) is instantiated, not the acceptable value ranges of the data concepts defined)
b) means to realise the service
c) application data common to all parts as defined in defined in ISO 15638-8 et sequentia, naming content and quality that an IVS (4.32) has to deliver.
The definition of what comprises a ?regulated' service is regarded as an issue for national decision, and may vary from jurisdiction (4.38) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated commercial freight vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles [hereinafter referred to as ?regulated vehicles' (4.49)]. There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-7:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 7: Other applications |
ISO 15638-7:2013 provides business framework based on a (multiple) service provider oriented approach for the provision of additional unregulated services to regulated commercial freight vehicles using a common on-board telematics platform, including:
a) definition of the service that a 'Service Provider' has to provide, including a given service level (the service definition comprises service elements such as 'retrieve data from IVS', 'map data to a map with access conditions', etc.);
b) means to realise the service;
c) application data, naming content and quality that an IVS has to deliver;
d) development of (any) rules for the approval and auditing of service providers for non-regulated service provision.
ISO 15638-7:2013 defines the requirements for the scope and framework for all TARV commercial (unregulated) applications. These applications may then be simply instantiated as commercial applications conforming to the requirements of ISO 15638-7:2013, in which case no further standardization is required, so long as conformance can be demonstrated, and service offerings may vary from service provider to service provider. Where it is decided that there is benefit in standardized instantiation to a common format for a particular service, a separate standards deliverable will be required, but may be developed by the consensus of experts in that area of application by reference to ISO 15638-7:2013 in respect of the TARV technical aspects.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as 'regulated vehicles'). There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Published |
2013-06 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-8:2014 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated vehicles (TARV) — Part 8: Vehicle access management |
ISO 15638-8:2014 addresses the provision of "vehicle access management" (and monitoring) and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO 15638-8:2014 provides specifications for common communications and data exchange aspects of the application service vehicle access monitoring that a regulator may elect to require or support as an option, including
a) high level definition of the service that a service provider has to provide, (the service definition describes common service elements; but does not define the detail of how such an application service is instantiated, not the acceptable value ranges of the data concepts defined),
b) means to realize the service, and
c) application data, naming content, and quality that an IVS has to deliver.
|
Published |
2014-07 |
Edition : 1 |
Number of pages : 49 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17264:2009/Amd 1:2019 |
Intelligent transport systems — Automatic vehicle and equipment identification — Interfaces — Amendment 1 |
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 6460-1:2007/Amd 1:2015 |
Motorcycles — Measurement method for gaseous exhaust emissions and fuel consumption — Part 1: General test requirements — Amendment 1 |
|
Withdrawn |
2015-11 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
43.140
Motorcycles and mopeds
;
13.040.50
Transport exhaust emissions
|
| ISO/TS 15638-8:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 8: Vehicle access monitoring (VAM) |
ISO/TS 15638-8:2013 addresses the provision of ?Vehicle Access Management' (and monitoring) and specifies the form and content of such data required to support such systems, and access methods (4.3) to that data.
ISO/TS 15638-8:2013 provides specifications (4.50) for common communications and data exchange aspects of the application service (4.6) vehicle access monitoring that a regulator (4.43) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.48) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.6) is instantiated, not the acceptable value ranges of the data concepts defined)
b) means to realise the service
c) application data, naming content and quality that an IVS (4.29) has to deliver.
The definition of what comprises a ?regulated' service is regarded as an issue for national decision, and may vary from jurisdiction (4.33) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles [hereinafter referred to as 'regulated vehicles' (4.42)]. There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 50 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-9:2020 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 9: Remote digital tachograph monitoring |
This document addresses the provision of ?Remote Digital Tachograph Monitoring' and specifies the form and content of the transmission of such data required to support such systems, and access methods to that data.
This document provides specifications for common communications and data exchange aspects of the application service remote digital tachograph monitoring that a jurisdiction regulator can elect to require or support as an option, including:
a) High level definition of the service that a service provider provides. The service definition describes common service elements but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined.
b) Means to realize the service.
c) Application data naming, content and quality that an IVS delivers, including a number of profiles for data (noting that requirements and constraints of what can/cannot be transmitted over the air can vary between jurisdictions).
d) Support for a number of defined communication profiles to enable remote inspection.
This document is not applicable for analogue tachograph equipment/systems.
This document provides specifications for the following communication profiles:
— Communication Profile C1: Roadside inspection using a short-range wireless communication interrogator instigating a physical roadside inspection (master<>slave)
Profile C1a: via a hand aimed or temporary roadside mounted and aimed interrogator
Profile C1b: via a vehicle mounted and directed interrogator
Profile C1c: via a permanent or semi-permanent roadside or overhead gantry
— Communication Profile C2: Roadside inspection using a short-range wireless communication interrogator instigating a download of data to an application service provider via an ITS-station communication (master<>slave + peer<>peer)
Profile C2a: via a hand aimed or temporary roadside mounted and aimed interrogator
Profile C2b: via a vehicle mounted and directed interrogator
Profile C2c: via a permanent or semi-permanent roadside or overhead gantry
— Communication Profile C3: Remote inspection addressed via an ITS-station instigating a download of data to an application service provider via a wireless communications interface (as defined in ISO 15638‑2).
It is possible that subsequent versions of this document will support additional communication profiles.
NOTE 1 The definition of what comprises a ?regulated' service is regarded as an issue for national decision and can vary from jurisdiction to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardized sets of requirements descriptions for identified services to enable consistent and cost-efficient implementations where instantiated.
NOTE 2 The ISO 15638 series has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles'). However, there is nothing to prevent a jurisdiction from extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Published |
2020-08 |
Edition : 1 |
Number of pages : 97 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-9:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 9: Remote electronic tachograph monitoring (RTM) |
ISO/TS 15638-9:2013 addresses the provision of Remote Tachograph Monitoring and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO/TS 15638-9:2013 provides specifications for common communications and data exchange aspects of the application service remote tachograph monitoring that a regulator may elect to require or support as an option, including:
a) high level definition of the service that a service provider has to provide (the service definition describes common service elements; but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined);
b) means to realise the service;
c) application data, naming content and quality that an IVS has to deliver.
The definition of what comprises a regulate' service is regarded as an issue for national decision, and may vary from jurisdiction to jurisdiction. ISO/TS 15638-9:2013 does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardized sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
|
Withdrawn |
2013-07 |
Edition : 1 |
Number of pages : 47 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-10:2017 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 10: Emergency messaging system/eCall |
ISO 15638-10:2017 addresses the provision of ?Emergency messaging system/eCall' using the TARV framework, architecture and communications methodology (as defined in ISO 15638‑1 to 6) and specifies the form and content of such data required to support such systems, and access methods (3.1) to that data.
ISO 15638-10:2017 provides specifications (3.40) for common communications and data exchange aspects of the application service (3.3) ?Emergency Messaging System/eCall' that a regulator (3.28) may elect to require or support as an option, including:
a) High level definition of the service that a service provider (3.38) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (3.3) is instantiated, not the acceptable value ranges of the data concepts defined)
b) Means to realise the service
c) Application data, naming content and quality that an IVS (3.23) has to deliver.
The definition of what comprises a ?regulated' service is regarded as an issue for National decision, and may vary from jurisdiction (3.27) to jurisdiction. ISO 15638-10:2017 does not impose any requirements on nations in respect of which services for regulated commercial freight vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
The ISO 15638 suite of standards has been developed for use in the context of regulated commercial freight vehicles [hereinafter referred to as regulated vehicles (3.36)]. There is nothing however to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 45 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-10:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 10: Emergency messaging system/eCall (EMS) |
ISO/TS 15638-10:2013 addresses the provision of Emergency messaging system/eCall and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO/TS 15638-10:2013 provides specifications for common communications and data exchange aspects of the application service Emergency Messaging System/eCall that a regulator may elect to require or support as an option, including:
a) high level definition of the service that a service provider has to provide [the service definition describes common service elements, but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined];
b) means to realise the service;
c) application data, naming content and quality that an IVS has to deliver.
The definition of what comprises a regulated service is regarded as an issue for national decision, and may vary from jurisdiction to jurisdiction. This part of ISO 15638 does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardized sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
|
Withdrawn |
2013-07 |
Edition : 1 |
Number of pages : 53 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-11:2014 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated vehicles (TARV) — Part 11: Driver work records |
ISO 15638-11:2014 addresses the provision of Driver Work Records (DWR) and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO 15638-11:2014 provides specifications for common communications and data exchange aspects of the application service driver work records that a regulator can elect to require or support as an option, including
a) high-level definition of the service that a service provider has to provide, [The service definition describes common service elements; but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined.],
b) means to realize the service, and
c) application data, naming content, and quality that an IVS has to deliver.
|
Published |
2014-07 |
Edition : 1 |
Number of pages : 69 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-11:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 11: Driver work records (work and rest hours compliance) (DWR) |
ISO/TS 15638-11:2013 addresses the provision of ?Driver Work Records' and specifies the form and content of such data required to support such systems, and access methods (4.1) to that data.
ISO/TS 15638-11:2013 provides specifications (4.41) for common communications and data exchange aspects of the application service (4.3) driver work records that a regulator (4.37) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.39) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.3) is instantiated, not the acceptable value ranges of the data concepts defined)
b) means to realise the service
c) application data, naming content and quality that an IVS (4.22) has to deliver.
The definition of what comprises a 'regulated' service' is regarded as an issue for national decision, and may vary from jurisdiction (4.26) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable cnsistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles' (4.36). There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 59 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-12:2014 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated vehicles (TARV) — Part 12: Vehicle mass monitoring |
ISO 15638-12:2014 addresses the provision of vehicle mass monitoring (VMM) and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO 15638-12:2014 provides specifications for common communications and data exchange aspects of the application service VMM that a regulator can elect to require or support as an option, including the following
a) high level definition of the service that a service provider has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service is instantiated, not the acceptable value ranges of the data concepts defined),
b) means to realize the service, and
c) application data, naming content and quality that an IVS has to deliver.
|
Published |
2014-07 |
Edition : 1 |
Number of pages : 62 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-12:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 12: Vehicle mass monitoring (VMM) |
ISO/TS 15638-12:2013 addresses the provision of "Vehicle ?Mass' Monitoring" and specifies the form and content of such data required to support such systems, and access methods (4.4) to that data.
ISO/TS 15638-12:2013 provides specifications (4.46) for common communications and data exchange aspects of the application service (4.3) 'Vehicle ?Mass' Monitoring' that a regulator (4.42) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.44) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.3) is instantiated, not the acceptable value ranges of the data concepts defined)
b) means to realise the service
c) application data, naming content and quality that an IVS (4.26)) has to deliver.
The definition of what comprises a 'regulated' service is regarded as an issue for National decision, and may vary from jurisdiction (4.30) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated commercial freight vehicles (4.41) jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles' (4.41). There is nothing however to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-15:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 15: Vehicle location monitoring (VLM) |
ISO/TS 15638-15:2013 addresses the provision of ?Vehicle location monitoring' and specifies the form and content of such data required to support such systems, and access methods (4.2) to that data.
ISO/TS 15638-15:2013 provides specifications (4.43) for common communications and data exchange aspects of the application service (4.4) Vehicle location monitoring that a regulator (4.39) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.41) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.4) is instantiated, not the acceptable value ranges of the data concepts defined)
b) means to realise the service
c) application data, naming content and quality that an IVS (4.26) has to deliver.
The definition of what comprises a 'regulated' service is regarded as an issue for National decision, and may vary from jurisdiction (4.29) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles (4.38)'). There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 50 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-13:2015 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 13: "Mass" information for jurisdictional control and enforcement |
ISO/TS 15638-13:2015 addresses the provision of ?Mass (4.37) information for jurisdictional control and enforcement' and specifies the form and content of such data required to support such systems and access methods (4.3) to that data.
The Scope of this part of ISO 15638 is to provide specifications (4.50) for common communications and data exchange aspects of the application service (4.6) Mass (4.37) information for jurisdictional control and enforcement that a regulator (4.44) may elect to require or support as an option, including
a) high-level definition of the service that a service provider (4.48) has to provide (the service definition describes common service elements but does not define the detail of how such an application service (4.6) is instantiated, not the acceptable value ranges of the data concepts defined),
b) means to realize the service, and
c) application data, naming content and quality that an IVS (4.30) has to deliver.
For clarification, Mass in this context is defined as a mass of a given heavy vehicle as measured by equipment affixed to the regulated vehicle; these mass calculations are achieved by dynamic real-time measurement using equipment especially installed for this purpose to measure the ?mass' impact on the road surface; it is, by definition, a service that can only be available to regulated vehicles that are especially equipped" (4.37).
The definition of what comprises a ?regulated' service is regarded as an issue for National decision, and may vary from jurisdiction (4.34) to jurisdiction. This deliverable does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost-efficient implementations where instantiated.
ISO/TS 15638-13:2015 is not a substitute for general electronic fee collection system which, where applied normally need to accord to International EFC Standards in preference to this specification. The Scope of this part of ISO 15638 is limited to the imposition of control and enforcement measures for regulated commercial freight vehicles related to measurement of the Mass (4.37) on board the vehicle.
ISO/TS 15638-13:2015 has been developed for use in the context of regulated commercial freight vehicles [hereinafter, referred to as ?regulated vehicles' (4.43)]. There is nothing however to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Published |
2015-12 |
Edition : 1 |
Number of pages : 62 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-14:2014 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated vehicles (TARV) — Part 14: Vehicle access control |
ISO 15638-14:2014 addresses the provision of "vehicle access control" and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO 15638-14:2014 provides specifications for common communications and data exchange aspects of the application service vehicle access control that a regulator may elect to require or support as an option, including
a) high-level definition of the service that a service provider has to provide, [The service definition describes common service elements; but does not define the detail of how such an application service is instantiated, not the acceptable value ranges of the data concepts defined.],
b) means to realize the service, and
c) application data, naming content and quality that an IVS has to deliver.
|
Published |
2014-07 |
Edition : 1 |
Number of pages : 48 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-14:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 14: Vehicle access control (VAC) |
ISO/TS 15638-14:2013 addresses the provision of ?Vehicle access control' and specifies the form and content of such data required to support such systems, and access methods (4.3) to that data.
ISO/TS 15638-14:2013 provides specifications (4.49) for common communications and data exchange aspects of the application service (4.6) Vehicle access control that a regulator (4.43) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.47) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.6) is instantiated, not the acceptable value ranges of the data concepts defined)
b) means to realise the service
c) application data, naming content and quality that an IVS (4.30) has to deliver.
The definition of what comprises a 'regulated' service is regarded as an issue for national decision, and may vary from jurisdiction (4.34) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated commercial freight vehicles (4.42) jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (4.42). There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 50 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-15:2014 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated vehicles (TARV) — Part 15: Vehicle location monitoring |
ISO 15638-15:2014 addresses the provision of vehicle location monitoring and specifies the form and content of such data required to support such systems and access methods to that data.
ISO 15638-15:2014 provides specifications for common communications and data exchange aspects of the application service vehicle location monitoring that a regulator may elect to require or support as an option, including
a) high-level definition of the service that a service provider has to provide,
NOTE The service definition describes common service elements; but does not define the detail of how such an application service is instantiated, not the acceptable value ranges of the data concepts defined.
b) means to realize the service, and
c) application data, naming content, and quality that an IVS has to deliver.
|
Published |
2014-07 |
Edition : 1 |
Number of pages : 54 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-16:2014 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated vehicles (TARV) — Part 16: Vehicle speed monitoring |
ISO 15638-16:2014 addresses the provision of vehicle speed monitoring and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO 15638-16:2014 provides specifications for common communications and data exchange aspects of the application service vehicle speed monitoring that a regulator can elect to require or support as an option, including
a) high level definition of the service that a service provider has to provide (The service definition describes common service elements but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined),
b) means to realize the service, and
c) application data, naming content, and quality that an IVS has to deliver.
|
Published |
2014-07 |
Edition : 1 |
Number of pages : 53 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-16:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 16: Vehicle speed monitoring (VSM) |
ISO/TS 15638-16:2013 addresses the provision of ?Vehicle speed monitoring' and specifies the form and content of such data required to support such systems, and access methods (4.2) to that data.
ISO/TS 15638-16:2013 provides specifications (4.44) for common communications and data exchange aspects of the application service (4.4) Vehicle speed monitoring that a regulator (4.40) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.42) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.4) is instantiated, nor the acceptable value ranges of the data concepts defined)
b) means to realise the service
c) application data, naming content and quality that an IVS (4.25) has to deliver.
The definition of what comprises a 'regulated' service is regarded as an issue for National decision, and may vary from jurisdiction (4.29) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles' (4.39). There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 54 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-17:2014 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated vehicles (TARV) — Part 17: Consignment and location monitoring |
ISO 15638-17:2014 addresses the provision of consignment and location monitoring and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO 15638-17:2014 provides specifications for common communications and data exchange aspects of the application service consignment and location monitoring that a regulator can elect to require or support as an option, including
a) high level definition of the service that a service provider has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service is instantiated, not the acceptable value ranges of the data concepts defined),
b) means to realize the service, and
c) application data, naming content, and quality that an IVS has to deliver.
|
Published |
2014-07 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-17:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 17: Consignment and location monitoring (CLM) |
ISO/TS 15638-17:2013 addresses the provision of ?Consignment and location monitoring' and specifies the form and content of such data required to support such systems, and access methods (4.1) to that data.
ISO/TS 15638-17:2013 provides specifications (4.45) for common communications and data exchange aspects of the application service (4.3) Consignment and location monitoring that a regulator (4.41) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.43) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.3) is instantiated, not the acceptable value ranges of the data concepts defined);
b) means to realise the service;
c) application data, naming content and quality that an IVS (4.27) has to deliver.
The definition of what comprises a 'regulated' service is regarded as an issue for National decision, and may vary from jurisdiction (4.31) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles' (4.40). There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Withdrawn |
2013-08 |
Edition : 1 |
Number of pages : 47 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-18:2017 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 18: ADR (Dangerous Goods) |
ISO 15638-18:2017 addresses the provision of "ADR (dangerous goods)" and specifies the form and content of such data required to support such systems and access methods to that data.
The scope of this document is to provide specifications for common communications and data exchange aspects of the application service ADR (dangerous goods) that a regulator may elect to require or support as an option, including
a) high-level definition of the service that a service provider has to provide (the service definition describes common service elements, but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined),
b) means to realize the service, and
c) application data, naming content and quality that an IVS has to deliver.
The definition of what comprises a "regulated" service is regarded as an issue for national decision and may vary from jurisdiction to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardized sets of requirements descriptions for identified services to enable consistent and cost-efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as "regulated vehicles"). There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Published |
2017-06 |
Edition : 1 |
Number of pages : 55 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/DIS 15638-23 |
Intelligent transport systems — Framework for collaborative telematics applications for regulated commercial freight vehicles (TARV) — Part 23: Tyre pressure monitoring (TPM) |
|
Under development |
|
Edition : 1 |
Number of pages : 82 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17423:2018 |
Intelligent transport systems — Cooperative systems — Application requirements and objectives |
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.
|
Published |
2018-05 |
Edition : 1 |
Number of pages : 34 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-18:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 18: ADR (Dangerous Goods) transport monitoring (ADR) |
ISO/TS 15638-18:2013 addresses the provision of ADR (dangerous goods) and specifies the form and content of such data required to support such systems, and access methods to that data.
ISO/TS 15638-18:2013 provides specifications for common communications and data exchange aspects of the application service ADR (dangerous goods) that a regulator may elect to require or support as an option, including:
a) high level definition of the service that a service provider has to provide (the service definition describes common service elements, but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined);
b) means to realise the service;
c) application data, naming content and quality that an IVS has to deliver.
The definition of what comprises a regulated service is regarded as an issue for national decision, and may vary from jurisdiction to jurisdiction. ISO/TS 15638-18:2013 does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardized sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
|
Withdrawn |
2013-07 |
Edition : 1 |
Number of pages : 54 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 15638-19:2013 |
Intelligent transport systems — Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) — Part 19: Vehicle parking facilities (VPF) |
ISO/TS 15638-19:2013 addresses the provision of ?Vehicle Parking Facility' and specifies the form and content of such data required to support such systems, and access methods (4.2) to that data.
ISO/TS 15638-19:2013 provides specifications (4.44) for common communications and data exchange aspects of the application service (4.4) ?Vehicle Parking Facility' that a regulator (4.65) may elect to require or support as an option, including:
a) high level definition of the service that a service provider (4.42) has to provide (the service definition describes common service elements, but does not define the detail of how such an application service (4.4) is instantiated, not the acceptable value ranges of the data concepts defined);
b) means to realise the service
c) application data, naming content and quality that an IVS (4.26) has to deliver.
The definition of what comprises a ?regulated' service is regarded as an issue for national decision, and may vary from jurisdiction (4.30) to jurisdiction. This document does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardised sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
|
Published |
2013-07 |
Edition : 1 |
Number of pages : 58 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-20:2020 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 20: Weigh-in-motion monitoring |
This document addresses the provision of ?weigh-in-motion monitoring' and specifies the form and content of the transmission of such data required to support such systems, and access methods to that data.
This document provides specifications for both on-board weighing (WIM-O) systems and in-road "weigh-in-motion" (WIM-R) systems, and provides a profile where the vehicle weight measured is recorded on-board using equipment already installed for "Remote Tachograph Monitoring".
This document provides specifications for common communications and data exchange aspects of the application service weigh-in-motion monitoring (WIM-O and WIM-R) that a jurisdiction regulator can elect to require or support as an option, including:
a) High level definition of the service that a service provider has to provide (the service definition describes common service elements, but does not define the detail of how such an application service is instantiated, nor the acceptable value ranges of the data concepts defined);
b) Means to realize the service;
c) Application data naming, content and quality that an IVS has to deliver, including a number of profiles for data (noting that requirements and constraints of what can/cannot be transmitted over the air can vary between jurisdictions);
d) Support for a number of defined communication profiles to enable remote inspection.
The present version of this document provides specifications for the following application profiles:
— Application Profile A1: Vehicle weight measurement from "On-Board Weighing" systems (WIM-O);
— Application Profile A2: Vehicle weight measurement from in-road ?weigh-in-motion' systems where data is transferred to the IVS (WIM-R).
NOTE 1 Vehicle weight measurement from in-road ?weigh-in-motion' systems where data is linked to a specific vehicle by ANPR or other techniques and sent via landline or cellular communications to a processing centre is also a viable and alternate option, but as it does not include carrying data on-board the vehicle is not a TARV use case.
The present version of this document provides specifications for the following communication profiles:
— Communication Profile 1: Roadside inspection using a short range wireless communication interrogator instigating a physical roadside inspection (master-:-slave):
— Profile C1a: via a hand aimed or temporary roadside mounted and aimed interrogator;
— Profile C1b: via a vehicle mounted and directed interrogator;
— Profile C1c: via a permanent or semi-permanent roadside or overhead gantry.
— Communication Profile 2: Roadside inspection using a short range wireless communication interrogator instigating a download of data to an application service provider via an ITS-station communication (master-:-slave + peer-:-peer):
— Profile C2a: via a hand aimed or temporary roadside mounted and aimed interrogator;
— Profile C2b: via a vehicle mounted and directed interrogator;
— Profile C2c: via a permanent or semi-permanent roadside or overhead gantry.
— Communication Profile 3: Remote inspection addressed via an ITS-station instigating a download of data to an application service provider via a wireless communications interface (as defined in ISO 15638-2).
Subsequent versions of this document can support additional communication profiles.
NOTE 2 The ISO 15638 series of standards has been developed for use in the context of regulated commercial freight vehicles (hereinafter referred to as ?regulated vehicles'). There is nothing, however, to prevent a jurisdiction from extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
|
Published |
2020-07 |
Edition : 1 |
Number of pages : 106 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-21:2018 |
Intelligent transport systems — Framework for cooperative telematics applications for regulated commercial freight vehicles (TARV) — Part 21: Monitoring of regulated vehicles using roadside sensors and data collected from the vehicle for enforcement and other purposes |
The ISO 15638 series of standards defines the framework (3.21) for online fleet management of regulated commercial freight vehicles utilizing data communication between in-vehicle systems and an application service provider (3.39) via on-board communication unit interfacing with road monitoring infrastructure. This document defines an extension to the existing role model conceptual architecture (3.7) by adding roadside sensors (3.37) to the model for additional data collection path for enhancement of the system.
The objective of this document is to reinforce vehicle monitoring for enforcement and other management purposes of regulated commercial freight vehicle movements. The scope of this document is to
a) Reinforce vehicle monitoring for enforcement and other purposes,
b) Provide additional data security by using roadside sensor data links,
c) Detect/avoid tampering/incorrect setting of onboard sensor equipment,
d) Provide means of using roadside sensors to validate the accuracy of on-board equipment, and
e) Enable the combined use of data obtained from the regulated commercial freight vehicle and roadside/in-road sensors to monitor, manage and control the movement of regulated commercial freight vehicles.
In this extended role model architecture (3.7), roadside sensor (including buried in-road sensors) functionality is added to the existing TARV role model. In this extended role model, jurisdictions (3.28) and other entities can reinforce monitoring or other management purpose applications by using a combination of information from both in-vehicle systems and roadside/in-road sensors.
In this document, the framework (3.21) for this modified and improved reinforcement of vehicle monitoring for enforcement and other management purpose applications is defined.
This document is complementary to, and does not replace, any other parts of the ISO 15638 series of standards. This document is beneficial to jurisdiction enforcement and other vehicle monitoring management purpose entities and it provides a means for using roadside sensors to validate the accuracy of on-board equipment and provides additional use cases for TARV service applications.
|
Published |
2018-06 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-22:2019 |
Intelligent transport systems — Framework for collaborative telematics applications for regulated commercial freight vehicles (TARV) — Part 22: Freight vehicle stability monitoring |
The ISO 15638 series of standards (Parts 1 to 21) define the framework for online fleet management of regulated commercial freight vehicles utilizing data communication between in-vehicle systems and an application service provider via on-board communication unit interfacing with road monitoring infrastructure and roadside sensors. In this document, an unregulated service architecture frame work for freight vehicle stability monitoring architecture is defined. This statement does not preclude the regulated service where jurisdiction needs such a function.
The objective of this document is to provide a freight vehicle stability monitoring service function/application for non-enforcement applications [and sometimes for regulated application service (RAS)]. This is for road transport safety management purposes of regulated commercial freight vehicle movements. The scope of this document is to
a) Reinforce vehicle stability monitoring for non-enforcement and other purposes by providing safety advisory information provisions to the freight vehicle drivers/operators transporting heavy goods on the freight vehicles.
This document defines the framework for remote vehicle stability monitoring for non-enforcement and other management purpose applications conceptual operation.
This document is complementary to, and does not replace, any ISO 15638 series standards. This document is beneficial to vehicle monitoring management purpose entities and it provides additional use cases for TARV service applications.
This document is specialized towards the realization of safer road transport of freight vehicles by providing safety advisory information to the vehicle from the service provider and it utilizes ISO 15638 series of standards basic architecture framework defined in ISO 15638-21. The vehicle on-board sensor detected freight vehicle and/or freight container stability data and/or road side sensor data (vehicle stability status detection at roadside) are sent out to the service provider through ITS communication media. The service provider provides users with safety information such as recommended safe speed limit for that particular vehicle and gives speed limit advice messages as necessary. The various V2I communication paths can be used according to the various use cases.
|
Published |
2019-04 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15638-24:2021 |
Intelligent transport systems — Framework for collaborative telematics applications for regulated commercial freight vehicles (TARV) — Part 24: Safety information provisioning |
The ISO 15638 series (Parts 1 to 23) define the framework for online fleet management of regulated commercial freight vehicles utilizing data communication between in-vehicle systems and an application service provider via an on-board communication unit interfacing with road monitoring infrastructure and roadside sensors. This document defines an unregulated service architecture framework for freight vehicle safety information provision architecture. This statement does not preclude the regulated service where a jurisdiction requires such a function.
The objective of this document is to provide a freight vehicle safety information provision service function/application for non-enforcement applications (and sometimes for regulated application services [RAS]). This is for the road transport safety management purposes of regulated commercial freight vehicle movements.
This document intends to reinforce vehicle safety for non-enforcement and other purposes by providing safety advisory information provisions to the freight vehicle drivers/operators transporting heavy goods on freight vehicles.
This document defines the framework for remote vehicle safety information provision for non-enforcement and the conceptual operation of other management purpose applications.
This document is complementary to, and does not replace, any other documents in the ISO 15638 series. This document is beneficial to vehicle safety management purpose entities and it provides additional use cases for TARV service applications.
This document is specifically oriented towards the realization of safer road transport of freight vehicles by providing safety advisory information to the vehicle from the service provider. It utilizes the ISO 15638 series basic architecture framework, as defined in ISO 15638-21. The service provider provides users with safety information such as recommended safety information for that vehicle and gives adequate safety advice messages, as necessary. The various V2X communication paths can be used according to the various use cases.
|
Published |
2021-06 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/CD 15638-25 |
Intelligent transport systems — Framework for collaborative telematics applications for regulated commercial freight vehicles (TARV) — Part 25: Overhead clearance monitoring |
This work item is specialized for safe road transport of freight vehicles by utilizing the 15638 frameworks.
Vehicle sensor data and/or roadside sensor data are sent out to service provider. Service provider provides users the vehicle height clearance information for the vehicle.
Various data exchange paths are to be defined.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15784-1:2008 |
Intelligent transport systems (ITS) — Data exchange involving roadside modules communication — Part 1: General principles and documentation framework of application profiles |
ISO 15784-1:2008 provides principles and documentation rules of application profiles used to exchange data and messages between a traffic management centre and roadside modules used for traffic management.
The application profiles it specifies are used to exchange data and messages between a traffic management centre and roadside modules for traffic management and between roadside modules used for traffic management.
The scope of ISO 15784-1:2008 does not include the communication between roadside modules and on-board units, in-vehicle communication, in-cabinet communication and motion video transmission from a camera or recorded media.
|
Published |
2008-10 |
Edition : 1 |
Number of pages : 9 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15784-2:2015 |
Intelligent transport systems (ITS) — Data exchange involving roadside modules communication — Part 2: Centre to field device communications using SNMP |
ISO 15784-2:2015 specifies a mechanism to exchange data and messages in the following cases:
a) between a traffic management centre(s) and roadside modules for traffic management;
b) between roadside modules used for traffic management.
The scope of this part of ISO 15784-2:2015 does not include the communication between traffic management centre and in-vehicle units, between roadside modules and in-vehicle units, in-vehicle communication, in-cabinet communication, or motion video transmission from a camera or recorded media.
ISO 15784-2:2015 is complimentary to ISO 15784-3, but uses a different application layer for the information exchanges to configure, control, and monitor the field traffic control roadside modules. Where ISO 15784-3 is based on the DATEX standards, this part of ISO 15784 uses an alternative approach based on SNMP with an optional extension for more efficient transmission over low bandwidth media. Both of these standards conform to the application profile requirements set forth in ISO 15784-1.
|
Published |
2015-11 |
Edition : 1 |
Number of pages : 48 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 15784-2:2015/Amd 1:2020 |
Intelligent transport systems (ITS) — Data exchange involving roadside modules communication — Part 2: Centre to field device communications using SNMP — Amendment 1: Support for SHA2 encryption |
|
Published |
2020-02 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/CD 15784-2 |
Intelligent transport systems (ITS) — Data exchange involving roadside modules communication — Part 2: Centre to field device communications using SNMP |
ISO 15784-2:2015 specifies a mechanism to exchange data and messages in the following cases:
a) between a traffic management centre(s) and roadside modules for traffic management;
b) between roadside modules used for traffic management.
The scope of this part of ISO 15784-2:2015 does not include the communication between traffic management centre and in-vehicle units, between roadside modules and in-vehicle units, in-vehicle communication, in-cabinet communication, or motion video transmission from a camera or recorded media.
ISO 15784-2:2015 is complimentary to ISO 15784-3, but uses a different application layer for the information exchanges to configure, control, and monitor the field traffic control roadside modules. Where ISO 15784-3 is based on the DATEX standards, this part of ISO 15784 uses an alternative approach based on SNMP with an optional extension for more efficient transmission over low bandwidth media. Both of these standards conform to the application profile requirements set forth in ISO 15784-1.
|
Under development |
|
Edition : 2 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 16401-1:2018 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-2 — Part 1: Test suite structure and test purposes |
ISO/TR 16401-1:2018 covers the test purposes for Front End Communications API covering functionalities related to instance handling, session handling, communication service primitives (i.e. sending/receiving of ADUs) and visible state transitions. It covers EFC communication services described in ISO 17575‑2:2016, Clause 5 and PICS proforma in ISO 17575‑2:2016, B.2. Claims related to Front End storage capacity are out of scope of this document.
ISO/TR 16401-1:2018 covers the test purposes for Front End Application related to session establishment on Back End request and related to session re-establishment when session requested by Back End failed. There are no other claims with respect to Front End Application described in ISO 17575‑2.
The underlying communication technology requirements for layer 1 to 4 specified in ISO 17575‑2:2016, Clause 6 are out of scope of this document.
Similarly, Back End Communications API is out of scope of this document. According to ISO 17575‑2 it is expected that these Front End Communications API will be "reflected" in the BE; however, BE Communications API is out of scope of ISO 17575‑2.
Test purposes have been organized into the test suite groups, designated for the Front End Communications API and Front End Application, respectively.
Aside from the test purposes, this document also provides proforma conformance test reports templates for both the Front End and Back End test purposes.
ISO 17575‑2 contains more information regarding the requirements against which the conformance is evaluated in this document.
|
Published |
2018-01 |
Edition : 1 |
Number of pages : 152 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 16401-1:2012 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-2 — Part 1: Test suite structure and test purposes |
ISO/TS 16401-1:2011 specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of Front End Communications API and Front End application to ISO/TS 17575-2.
|
Withdrawn |
2012-03 |
Edition : 1 |
Number of pages : 154 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 16401-2:2018 |
Electronic fee collection — Evaluation of equipment for conformity to ISO 17575-2 — Part 2: Abstract test suite |
ISO/TR 16401-2:2018 contains the definition of test cases, reflecting the individual steps listed in specific test purposes defined in ISO/TR 16401-1. The test cases are written in Testing and Test Control Notation version 3 (TTCN-3).
|
Published |
2018-01 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 16401-2:2012 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-2 — Part 2: Abstract test suite |
ISO/TS 16401-2:2012 specifies the Abstract Test Suite (ATS) to evaluate the conformity of Front End Communications API and Front End Application to ISO/TS 17575-2.
|
Withdrawn |
2012-03 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 16403-1:2012 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-4 — Part 1: Test suite structure and test purposes |
ISO/TS 16403-1:2011 specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of Front End and Back End to ISO/TS 17575-4.
|
Withdrawn |
2012-03 |
Edition : 1 |
Number of pages : 48 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 16403-2:2012 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-4 — Part 2: Abstract test suite |
The objective of ISO/TS 16403-2 is to provide a basis for conformance tests for Front End and Back End in electronic fee collection, based on autonomous on-board equipment. This enables interoperability between different equipment supplied by different manufacturers.
|
Withdrawn |
2012-03 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 16407-1:2017 |
Electronic fee collection — Evaluation of equipment for conformity to ISO 17575-1 — Part 1: Test suite structure and test purposes |
The ISO 16407 series of standards specifies a suite of tests in order to assess the Front End and Back End behaviour compliancy towards the requirements listed in ISO 17575-1. ISO 16407-1:2017 contains the definition of such tests in the form of test purposes, listing the required initial conditions, references and individual steps in a structured textual manner.
|
Published |
2017-11 |
Edition : 1 |
Number of pages : 108 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 16407-1:2011 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-1 — Part 1: Test suite structure and test purposes |
ISO/TS 16407-1:2011 specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of Front End and Back End to ISO/TS 17575-1.
The objective of ISO/TS 16407-1:2011 is to provide a basis for conformance tests for the Front End and the Back End in electronic fee collection (EFC) based on autonomous on-board equipment (OBE) to enable interoperability between different equipment supplied by different manufacturers.
|
Withdrawn |
2011-10 |
Edition : 1 |
Number of pages : 101 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 4249-3:2004 |
Motorcycle tyres and rims (code-designated series) — Part 3: Rims |
ISO 4249-3:2004 specifies the rim dimensions for a selection of rims for motorcycle tyres. It sets only those rim contour dimensions necessary for tyre mounting, and for fitting the tyre to the rim.
|
Withdrawn |
2004-11 |
Edition : 5 |
Number of pages : 11 |
Technical Committee |
43.140
Motorcycles and mopeds
|
| ISO 16410-1:2017 |
Electronic fee collection — Evaluation of equipment for conformity to ISO 17575-3 — Part 1: Test suite structure and test purposes |
The ISO 16410 series provides a suite of tests in order to assess compliance of the Front End and Back End behaviours in relation to the requirements in ISO 17575‑3. ISO 16410-1:2017 contains the definition of such tests in the form of test purposes, listing the required initial conditions, references and individual steps in a structured textual manner. ISO 16410‑2 contains the identical tests written in testing and test control notation version 3 (TTCN v3).
The test purposes defined in ISO 16410-1:2017 reflect the structural and semantic requirements stated in ISO 17575‑3.
- Presence/absence of particular data elements (see ISO 17575‑3:2016, 8.5.5);
- Semantics related to various data elements, e.g.:
- Activation of context data and handling multiple contexts (see ISO 17575‑3:2016, 8.3);
- Handling the precedence and priority levels (see ISO 17575‑3:2016, 8.5.2 to 8.5.4);
- Uniqueness of relevant data elements (see ISO 17575‑3:2016, 8.5.2 to 8.5.4);
- Correct definition of the charge objects (see ISO 17575‑3:2016, 8.5.4);
- Fee calculation algorithm (see ISO 17575‑3:2016, 8.5.3.7);
- Security (see ISO 17575‑3:2016, 7.2).
With regard to the individual data sets and EFC attributes defined in ISO 17575‑3, the test purposes have been organized into the test suite groups, designated for the Front End and Back End respectively.
In addition to the test purposes, ISO 16410-1:2017 also provides proforma conformance test report templates for both the Front End and Back End test purposes and an informative statement on the usage of ISO 16410-1:2017 for the European electronic toll service (EETS).
For more information regarding the requirements against which the conformance is evaluated in ISO 16410-1:2017, refer to ISO 17575‑3.
Testing of the following behaviours and functionalities is outside the scope of ISO 16410-1:2017:
- dynamic behaviour, i.e. sequence of messages and triggering events that must be exchanged/happen to fulfil certain charging scenarios;
- profiles and business logic built on top of particular pricing schemas;
- behaviour invalid of Front End and Back End, BI test purposes are not applicable for any test purpose group (as ISO 17575‑3 does not specify behaviour invalid).
|
Published |
2017-11 |
Edition : 1 |
Number of pages : 163 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 16410-1:2011 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-3 — Part 1: Test suite structure and test purposes |
ISO/TS 16410-1:2011 specifies the test suite structure (TSS) and test purposes (TP) to evaluate the conformity of Front End and Back End to ISO/TS 17575-3.
The objective of ISO/TS 16410-1:2011 is to provide a basis for conformance tests for the Front End and the Back End in electronic fee collection (EFC) based on autonomous on-board equipment (OBE) to enable interoperability between different equipment supplied by different manufacturers.
|
Withdrawn |
2011-10 |
Edition : 1 |
Number of pages : 147 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 16410-2:2018 |
Electronic fee collection — Evaluation of equipment for conformity to ISO 17575-3 — Part 2: Abstract test suite |
The ISO 16410 series provides a suite of tests in order to assess the Front End (FE) and Back End (BE) behaviour's compliancy towards the requirements listed in ISO 17575‑3. This document contains the definition of such tests in the form of test cases, reflecting the required individual steps listed in specific test purposes defined in ISO 16410‑1. The test cases are written in Testing and Test Control Notation version 3 (TTCN v3).
|
Published |
2018-11 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 16410-2:2012 |
Electronic fee collection — Evaluation of equipment for conformity to ISO/TS 17575-3 — Part 2: Abstract test suite |
ISO/TS 16410-2:2011 specifies the Abstract Test Suite (ATS) to evaluate the conformity of Front End and Back End to ISO/TS 17575-3.
|
Withdrawn |
2012-03 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17262:2012 |
Intelligent transport systems — Automatic vehicle and equipment identification — Numbering and data structures |
ISO 17262:2012 defines generic numbering and data structures for unambiguous identification of equipment used for Intermodal goods transport. These data are known as "Intermodal Goods Transport Numbering and Data Structures".
It defines data independently of the data carrier. The modelling of data is based on Abstract Syntax Notation One (ASN.1) as defined in ISO/IEC 8824. It excludes any physical aspects such as interfaces, dimensions, etc. Data that form part of transmission or storage protocols (headers, frame markers and checksums) are excluded.
Data defined in ISO 17262:2012 require a system for control and distribution of number series independent of the different AVI/AEI systems. This is required in order to avoid ambiguity and to provide the necessary level of security where appropriate. For this reason the registration authority defined in ISO 14816 applies for ISO 17262:2012.
ISO 17262:2012 enables the use of optimised encoding schemes such as ASN.1 Packed Encoding Rules (PER).
|
Published |
2012-09 |
Edition : 1 |
Number of pages : 58 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17361:2007 |
Intelligent transport systems — Lane departure warning systems — Performance requirements and test procedures |
ISO 17361:2007 specifies the definition of the system, classification, functions, human-machine interface (HMI) and test methods for lane departure warning systems. These are in-vehicle systems that can warn the driver of a lane departure on highways and highway-like roads. The subject system, which may utilize optical, electromagnetic, GPS or other sensor technologies, issues a warning consistent with the visible lane markings. The issuance of warnings at roadway sections having temporary or irregular lane markings (such as roadwork zones) is not within the scope of ISO 17361:2007. ISO 17361:2007 applies to passenger cars, commercial vehicles and buses. The system will not take any automatic action to prevent possible lane departures. Responsibility for the safe operation of the vehicle remains with the driver.
|
Withdrawn |
2007-02 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 10423:2001 |
Petroleum and natural gas industries — Drilling and production equipment — Wellhead and christmas tree equipment |
|
Withdrawn |
2001-08 |
Edition : 2 |
Number of pages : 401 |
Technical Committee |
75.180.10
Exploratory, drilling and extraction equipment
|
| ISO/TS 17262:2003 |
Automatic vehicle and equipment identification — Intermodal goods transport — Numbering and data structures |
ISO/TS 17262:2003 defines generic numbering and data structures for unambiguous identification of equipment used for Intermodal goods transport. These data are known as Intermodal Goods Transport Numbering and Data Structures.
ISO/TS 17262:2003 defines data independently of the data carrier. The modelling of data is based on Abstract Syntax Notation One (ASN.1) as defined in ISO/IEC 8824. ISO/TS 17262:2003 excludes any physical aspects such as interfaces, dimensions etc. Data that form part of transmission or storage protocols (headers, frame markers and checksums) are excluded.
Data defined in ISO/TS 17262:2003 require a system for control and distribution of number series independent of the different AVI/AEI systems. This is required in order to avoid ambiguity and to provide the necessary level of security where appropriate. For this reason the registration authority defined in ENV ISO 14816 applies for ISO/TS 17262:2003.
ISO/TS 17262:2003 enables the use of optimised encoding schemes such as ASN.1 Basic Packed Encoding Rules (PER).
ISO/TS 17262:2003 provides interoperability, not only between simple AVI/AEI and more complex RTTT/TICS functions, but also with pre-existing Standards such as container (ISO 10374). Specifications for protecting against changes, classifying and qualifying security aspects of the data are out of scope of ISO/TS 17262:2003.
ISO/TS 17262:2003 relates to AVI/AEI units, but not to smaller containers and units being transported. For smaller units (pallet loads, trays, parcels etc.) please refer to ISO/IEC SC 31 standards, ISO 18000 series. The Numbering Structure defined in ISO/TS 17262:2003 is designed to enable combinations with the data definitions from ISO 18000 series. This combination will be covered in CEN ISO/TS 17264 (under preparation).
ISO/TS 17262:2003 provides the capability to carry application data, associated with the identification, to be carried as part of the AVI/AEI message. Within ISO/TS 17262:2003 this is provided as a "black box" facility. The definition of the structure and contents of such messages are outside the scope of ISO/TS 17262:2003 (examples will be shown in CEN ISO/TS 17264).
|
Withdrawn |
2003-06 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17262:2012/Amd 1:2019 |
Intelligent transport systems — Automatic vehicle and equipment identification — Numbering and data structures — Amendment 1 |
|
Published |
2019-02 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17262:2012/Cor 1:2013 |
Intelligent transport systems — Automatic vehicle and equipment identification — Numbering and data structures — Technical Corrigendum 1 |
|
Published |
2013-12 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17263:2012 |
Intelligent transport systems — Automatic vehicle and equipment identification — System parameters |
ISO 17263;2012 establishes an AEI system based on radio frequency technologies. This system is intended for general application in RTTT/TICS. It allows the transfer of the identification codes and further information about equipment and vehicles used in intermodal transport into such RTTT/TICS and information systems related to intermodal transport processes. Within the intermodal context of the RTTT/TICS Sector, AEI systems have the specific objective of achieving an unambiguous identification of an ITU or related equipment or vehicle or item used in intermodal transport, and to make that identification automatically. Vehicles will be considered and handled under Intermodal aspects as "Intermodal Equipment". Therefore, a differentiation between AEI and AVI systems for the purpose of this standard is not required.
|
Published |
2012-08 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17263:2003 |
Automatic vehicle and equipment identification — Intermodal goods transport — System parameters |
ISO/TS 17263:2003 establishes an AEI-System based on radio frequency technologies. This system is intended for general application in RTTT/TICS. It allows for the transfer of the identification codes and further information about equipment and vehicles used in intermodal transport into such RTTT/TICS and information systems related to Intermodal Transport processes. Within the intermodal context of the RTTT/TICS Sector, AEI systems have the specific objective of achieving an unambiguous identification of an ITU or related equipment or vehicle or item used in intermodal transport, and to make that identification automatically. Vehicles will be considered and handled under Intermodal aspects as "Intermodal Equipment". Therefore a differentiation between AEI and AVI systems under the purpose of ISO/TS 17263:2003 is not required.
ISO/TS 17263:2003 is specifically aimed at DSRC-type air interfaces. The requirement and test methods may not apply for Intermodal AEI systems using long range communications such as Cellular Networks or Satellite, or vicinity communication such as inductively coupled antennas. The interoperability across the air interface (reference point Delta) is outside the scope of ISO/TS 17263:2003.
The aim of ISO/TS 17263:2003 is to define, describe and specify the System Parameters related to an intermodal AEI system to provide an enabling Standard, which, whilst allowing the system specifier to determine the performance levels and operating conditions, provides a framework for interoperability. Therefore ISO/TS 17263:2003 specifies:
parameters and requirements of the identification system itself;performance criteria necessary to ensure consistent and reliable operation of AEI systems within international transport processing;requirements of the performance and the position of the electronic devices (tag) when installed on intermodal equipment;requirements for the installation of readers, and performance data related to these components.
|
Withdrawn |
2003-06 |
Edition : 1 |
Number of pages : 11 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17263:2012/Cor 1:2013 |
Intelligent transport systems — Automatic vehicle and equipment identification — System parameters — Technical Corrigendum 1 |
|
Published |
2013-12 |
Edition : 1 |
Number of pages : 1 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17264:2009 |
Intelligent transport systems — Automatic vehicle and equipment identification — Interfaces |
ISO 17624:2009 provides the specifications of:
common AVI/AEI transaction requirements, which define the common steps of any AVI/AEI transaction;
AVI/AEI application interface to standardized wireless protocols (referred to as the "Air Interface") supporting the AVI transaction requirements, so as to enable interoperability.
ISO 17624:2009 is an interface standard, adhering to the open systems interconnection (OSI) philosophy (ISO/IEC 7498‑1), and it is as such not concerned with the implementation choices to be realized at either side of the air interface between the "Fixed Equipment" and "OBE".
|
Published |
2009-11 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17361:2017 |
Intelligent transport systems — Lane departure warning systems — Performance requirements and test procedures |
ISO 17361:2017 specifies the definition of the system, classification, functions, human-machine interface (HMI) and test methods for lane departure warning systems. These are in-vehicle systems that can warn the driver of a lane departure on highways and highway-like roads. The subject system, which may utilize optical, electromagnetic, GPS or other sensor technologies, issues a warning consistent with the visible lane markings. The issuance of warnings at roadway sections having temporary or irregular lane markings (such as roadwork zones) is not within the scope of ISO 17361:2017. ISO 17361:2017 applies to passenger cars, commercial vehicles and buses. The system will not take any automatic action to prevent possible lane departures. Responsibility for the safe operation of the vehicle remains with the driver.
|
Published |
2017-06 |
Edition : 2 |
Number of pages : 12 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17361:2017/DAmd 1 |
Intelligent transport systems — Lane departure warning systems — Performance requirements and test procedures — Amendment 1 |
|
Under development |
|
Edition : 2 |
Number of pages : 1 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 17384:2008 |
Intelligent transport systems — Interactive centrally determined route guidance (CDRG) — Air interface message set, contents and format |
ISO/TR 17384:2008 describes the message contents and format of the air interface between the infrastructure and the in-vehicle unit in the Interactive CDRG system.
The air interface message set for route guidance information in the interactive CDRG system in this Technical Report is applicable to both vehicles equipped with an onboard map database and those which are not equipped (i.e., those equipped with simplified graphic output and/or text message display functions).
ISO/TR 17384:2008 covers media independent systems. In this Technical Report, messages required for both cellular phone-based CDRG and beacon-based CDRG are taken into account.
|
Published |
2008-04 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17387:2008 |
Intelligent transport systems — Lane change decision aid systems (LCDAS) — Performance requirements and test procedures |
ISO 17387:2008 specifies system requirements and test methods for Lane Change Decision Aid Systems (LCDAS). LCDAS are fundamentally intended to warn the driver of the subject vehicle against potential collisions with vehicles to the side and/or to the rear of the subject vehicle, and moving in the same direction as the subject vehicle during lane change manoeuvres. This standardization addresses LCDAS for use on forward moving cars, vans and straight trucks in highway situations.
|
Published |
2008-05 |
Edition : 1 |
Number of pages : 49 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17419:2018 |
Intelligent transport systems — Cooperative systems — Globally unique identification |
This document
— describes and specifies globally unique addresses and identifiers (ITS-S object identifiers) which are both internal and external to ITS stations and are used for ITS station management,
— describes how ITS-S object identifiers and related technical parameters are used for classification, registration and management of ITS applications and ITS application classes,
— describes how ITS-S object identifiers are used in the ITS communication protocol stack,
— introduces an organizational framework for registration and management of ITS-S objects,
— defines and specifies management procedures at a high functional level,
— is based on the architecture of an ITS station specified in ISO 21217:2014 as a Bounded Secured Managed Domain (BSMD),
— specifies an ASN.1 module for the identifiers, addresses, and registry records identified in this document, and
— specifies an ASN.1 module for a C-ITS Data Dictionary containing ASN.1 type definitions of general interest.
|
Published |
2018-05 |
Edition : 1 |
Number of pages : 46 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17419:2014 |
Intelligent transport systems — Cooperative systems — Classification and management of ITS applications in a global context |
ISO/TS 17419:2014 illustrates and specifies "Global Classification and Management of ITS Applications" (GCMA). It is based on the ITS station and communication architecture described in ISO 21217. It describes and specifies globally unique addresses and identifiers (ITS-S object identifiers) which are both internal and external to ITS stations and are used for ITS station management, describes how ITS-S object identifiers and related technical parameters are used for classification, registration and management of ITS applications and ITS application classes and how ITS-S object identifiers are used in the ITS communication protocol stack, introduces an organizational framework for registration and management of ITS-S objects, and defines and specifies management procedures at a high functional level.
|
Withdrawn |
2014-04 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17419:2018/CD Amd 1 |
Intelligent transport systems — Cooperative systems — Globally unique identification — Amendment 1: Intelligent transport systems - Cooperative systems — Globally unique identification |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17423:2014 |
Intelligent transport systems — Cooperative systems — ITS application requirements and objectives for selection of communication profiles |
ISO/TS 17423:2014 specifies communication service parameters presented by ITS-S 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) and related related procedures for the static and dynamic ITS-S communication profile selection processes at a high functional level, and provides an illustration of objectives used to estimate an optimum ITS-S communication profile.
|
Withdrawn |
2014-04 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17444-1:2012 |
Electronic fee collection — Charging performance — Part 1: Metrics |
ISO/TS 17444-1:2012 defines metrics for the charging performance of electronic fee collection (EFC) systems in terms of the level of errors associated with charging computation.
ISO/TS 17444-1:2012 is a toolbox standard of metrics. The detailed choice of metrics depends on the application and the respective context.
ISO/TS 17444-1:2012 describes a set of metrics with appropriate definitions, principles and formulations, which together make up a reference framework for the establishment of requirements for EFC systems and their later examination of the charging performance.
|
Withdrawn |
2012-10 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17444-1:2017 |
Electronic fee collection — Charging performance — Part 1: Metrics |
ISO/TS 17444-1:2017 defines metrics for the charging performance of electronic fee collection (EFC) systems in terms of the level of errors associated with charging computation.
ISO/TS 17444-1:2017 is a toolbox standard of metrics. The detailed choice of metrics depends on the application and the respective context.
ISO/TS 17444-1:2017 describes a set of metrics with appropriate definitions, principles and formulations, which together make up a reference framework for the establishment of requirements for EFC systems and their later examination of the charging performance.
The charging performance metrics defined in ISO/TS 17444-1:2017 are intended for use with any Charging Scheme, regardless of its technical underpinnings, system architecture, tariff structure, geographical coverage, or organizational model. They are defined to treat technical details that can be different among technologies and vendors or vary over time as a "black box".
They focus solely on the outcome of the charging process, i.e. the amount charged in relation to a pre-measured or theoretically correct amount, rather than intermediate variables from various components as sensors, such as positioning accuracy, signal range, or optical resolution. This approach ensures comparable results for each metric in all relevant situations.
The metrics are designed to cover the information exchanged on the Front End interface and the interoperability interfaces between Toll Service Providers, Toll Chargers and Road Users as well as on the End-to-End level.
|
Published |
2017-09 |
Edition : 2 |
Number of pages : 25 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17444-2:2013 |
Electronic fee collection — Charging performance — Part 2: Examination Framework |
ISO/TS 17444-2:2013 defines the Examination Framework for the measurement of Charging Performance Metrics defined in ISO/TS 17444-1 to be used during Evaluation and/or on-going Monitoring.
It specifies a method for the specification and documentation of a Specific Examination Framework which can be used by the responsible entity to evaluate charging performance for a particular information exchange interface or for overall charging performance within a Toll Scheme.
It provides a toolbox of Examination Tests for the roles of Toll Charger and Toll Service Provider for the following Scheme types:
DSRC Discrete;
Autonomous Discrete;
Autonomous Continuous.
The detailed choice of the set of examination tests to be used depends on the application and the respective context. Compliance with ISO/TS 17444-2:2013 is understood as using the definitions and prescriptions laid out in ISO/TS 17444-2:2013 whenever the respective system aspects are subjected to performance measurements, rather than using other definitions and examination methods than the ones specified in ISO/TS 17444-2:2013.
Out of scope of ISO/TS 17444-2:2013 are the following aspects:
ISO/TS 17444-2:2013 does not propose specific numeric performance bounds, or average or worst-case error bounds in percentage or monetary units. Those decisions are left to the Toll Charger (or to agreements between Toll Charger and Service Provider).This Technical Specification does not consider the evaluation of the expected performance of a system based on modelling and measured data from trial at another place.
ISO/TS 17444-2:2013 does not consider the specification of a common reference system which would be required for comparison of performance between systems.
ISO/TS 17444-2:2013 defines measurements only on standardised interfaces. Proprietary interfaces are excluded, because it is not possible to define standardised metrics on such system properties. These excluded interfaces are among others the link between Toll Charger RSE and central systems in DSRC systems, and the additional sensor input of GNSS modules (inertial sensors, CAN-bus for wheel ticks, etc.).
|
Withdrawn |
2013-11 |
Edition : 1 |
Number of pages : 93 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17444-2:2017 |
Electronic fee collection — Charging performance — Part 2: Examination framework |
ISO/TS 17444-2:2017 defines the Examination Framework for the measurement of charging performance metrics defined in ISO/TS 17444‑1 to be used during Evaluation and/or on-going Monitoring.
It specifies a method for the specification and documentation of a Specific Examination Framework which can be used by the responsible entity to evaluate charging performance for a particular information exchange interface or for overall charging performance within a Toll Scheme.
It provides a toolbox of Examination Tests for the roles of Toll Charger and Toll Service Provider for the following Scheme types:
a) DSRC Discrete;
b) Autonomous Discrete;
c) Autonomous Continuous.
The detailed choice of the set of examination tests to be used depends on the application and the respective context. Compliance with this specification is understood as using the definitions and prescriptions laid out in ISO/TS 17444-2:2017 whenever the respective system aspects are subjected to performance measurements, rather than using other definitions and examination methods than the ones specified in ISO/TS 17444-2:2017.
The following aspects are outside the scope of ISO/TS 17444-2:2017.
- ISO/TS 17444-2:2017 does not propose specific numeric performance bounds, or average or worst-case error bounds in percentage or monetary units. Those decisions are left to the Toll Charger (or to agreements between Toll Charger and Service Provider). ISO/TS 17444-2:2017 does not consider the evaluation of the expected performance of a system based on modelling and measured data from trial at another place.
- ISO/TS 17444-2:2017 does not consider the specification of a common reference system which would be required for comparison of performance between systems.
- ISO/TS 17444-2:2017 defines measurements only on standardized interfaces. Proprietary interfaces are excluded, because it is not possible to define standardized metrics on such system properties. These excluded interfaces are among others the link between Toll Charger RSE and central systems in DSRC systems, and the additional sensor input of GNSS modules (inertial sensors, CAN-bus for wheel ticks, etc.).
|
Published |
2017-09 |
Edition : 2 |
Number of pages : 93 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 4249-3:2010 |
Motorcycle tyres and rims (code-designated series) — Part 3: Rims |
ISO 4249-3:2010 specifies the rim dimensions for a selection of rims for motorcycle tyres. It stipulates only those rim contour dimensions necessary for tyre mounting, and for fitting the tyre to the rim.
|
Published |
2010-11 |
Edition : 6 |
Number of pages : 11 |
Technical Committee |
43.140
Motorcycles and mopeds
|
| ISO 17515-1:2015 |
Intelligent transport systems — Communications access for land mobiles (CALM) — Evolved universal terrestrial radio access network (E-UTRAN) — Part 1: General usage |
ISO 17515-1:2015 enables usage of the E-UTRAN cellular network technology as an ITS access technology in an ITS station by specifying details of the "Communication Adaptation Layer" (CAL) and the "Management Adaptation Entity" (MAE) of communication interfaces specified in ISO 21218, and session management by reference to ISO 25111.
Wherever practicable, this part of ISO 17515-1:2015 has been developed by reference to suitable extant standards, adopted by selection.
|
Published |
2015-09 |
Edition : 1 |
Number of pages : 10 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17515-2:2020 |
Intelligent transport systems — Evolved universal terrestrial radio access network (E-UTRAN) — Part 2: Device to device communications (D2D) |
This document provides specification on the ITS-Station (ITS-S) access layer for a communication interface (CI) named "ITS-LTE-D2D".
This specification is appropriate in the context of LTE-D2D communications that are being used for the dissemination of ITS information from an ITS-SU to other ITS-SUs, where these ITS-SUs can be either vehicle ITS-SUs, roadside ITS-SUs, or personal ITS-SUs, as specified in ISO 21217. It provides a combination of options from relevant ETSI/3GPP releases and ITS-station management standards in ISO 24102 to enable and achieve this objective.
ITS-LTE-D2D CIs are based on the evolved-universal terrestrial radio access network (E-UTRAN) device-to-device (LTE-D2D) technology standardized at 3GPP Release 13.
This document enables the use of the LTE-D2D technology as an ITS access technology in an ITS station by reference to respective specifications from 3GPP, and by specifying details of the Communication Adaptation Layer (CAL) and the Management Adaptation Entity (MAE) of CIs specified in ISO 21218.
|
Published |
2020-08 |
Edition : 1 |
Number of pages : 26 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17515-3:2019 |
Intelligent transport systems — Evolved-universal terrestrial radio access network — Part 3: LTE-V2X |
This document provides specifications related to the ITS-S access layer for a communication interface (CI) named "ITS-LTE-V2X".
ITS-LTE-V2X CIs are based on the evolved-universal terrestrial radio access (E-UTRA) vehicle-to- everything (LTE-V2X) technology standardized at 3GPP.
This document enables usage of the LTE-V2X technology as an ITS access technology in an ITS station by reference to respective specifications from 3GPP, and by specifying details of the "Communication Adaptation Layer" (CAL) and the "Management Adaptation Entity" (MAE) of communication interfaces specified in ISO 21218.
|
Published |
2019-08 |
Edition : 1 |
Number of pages : 27 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17573-1:2019 |
Electronic fee collection — System architecture for vehicle-related tolling — Part 1: Reference model |
This document defines the architecture of electronic fee collection (EFC) system environments, in which a customer with one contract may use a vehicle in a variety of toll domains with a different toll charger for each domain.
EFC systems conforming to this document can be used for various purposes including road (network) tolling, area tolling, collecting fees for the usage of bridges, tunnels, ferries, for access or for parking. From a technical point of view the considered toll systems may identify vehicles subject to tolling by means of electronic equipment on-board in a vehicle or by other means (e.g. automatic number plate recognition, ANPR).
From a process point of view the architectural description focuses on toll determination, toll charging, and the associated enforcement measures. The actual collection of the toll, i.e. collecting payments, is outside of the scope of this document.
The architecture in this document is defined with no more details than required for an overall overview, a common language, an identification of the need for and interactions among other standards, and the drafting of these standards.
This document as a whole provides:
— the enterprise view on the architecture, which is concerned with the purpose, scope and policies governing the activities of the specified system within the organization of which it is a part;
— the terms and definitions for common use in an EFC environment;
— a decomposition of the EFC systems environment into its main enterprise objects;
— the roles and responsibilities of the main actors. This document does not impose that all roles perform all indicated responsibilities. It should also be clear that the responsibilities of a role may be shared between two or more actors. Mandating the performance of certain responsibilities is the task of standards derived from this architecture;
— identification of the provided services by means of action diagrams that underline the needed standardised exchanges;
— identification of the interoperability interfaces for EFC systems, in specialised standards (specified or to be specified).
|
Published |
2019-07 |
Edition : 1 |
Number of pages : 48 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17573-2:2020 |
Electronic fee collection — System architecture for vehicle related tolling — Part 2: Vocabulary |
This document defines terms within the field of electronic fee collection (EFC).
This document defines:
— terms within the fields of electronic fee collection and road user charging;
— terms that are used in standards related to electronic fee collection;
— terms of a more general use that are used more specifically in standards related to electronic fee collection.
This document does not define:
— Terms related primarily to other fields that operate in conjunction with EFC, such as terms for intelligent transport systems (ITS), common payment systems, the financial sector, etc.
— Deprecated terms.
|
Published |
2020-07 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 39002:2020 |
Road traffic safety — Good practices for implementing commuting safety management |
This document provides guidelines for good practices that can be adopted by organizations for the implementation of commuting safety management. These practices are intended to reduce the number of fatalities and serious injuries, the severity of injuries, and further to minimize damage to property and economic loss due to road crashes.
This document is applicable to any organization to help it protect commuters including vulnerable road users (VRU) through the adoption of a proactive approach to manage commuting risks.
This document is also applicable to commercial transport organizations including fleet operators, as well as schools.
|
Published |
2020-04 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
03.220.20
Road transport
|
| ISO/FDIS 17573-3 |
Electronic fee collection — System architecture for vehicle-related tolling — Part 3: Data dictionary |
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of values are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824‑1. This document defines:
— ASN.1 (data) types within the fields of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
|
Under development |
|
Edition : 1 |
|
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17573-3:2021 |
Electronic fee collection — System architecture for vehicle-related tolling — Part 3: Data dictionary |
This document specifies the syntax and semantics of data objects in the field of electronic fee collection (EFC). The definitions of data types and assignment of values are provided in accordance with the abstract syntax notation one (ASN.1) technique, as specified in ISO/IEC 8824‑1. This document defines:
— ASN.1 (data) types within the fields of EFC;
— ASN.1 (data) types of a more general use that are used more specifically in standards related to EFC.
This document does not seek to define ASN.1 (data) types that are primarily related to other fields that operate in conjunction with EFC, such as cooperative intelligent transport systems (C-ITS), the financial sector, etc.
|
Published |
2021-08 |
Edition : 1 |
Number of pages : 44 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17573:2010 |
Electronic fee collection — Systems architecture for vehicle-related tolling |
ISO 17573:2010 defines the architecture of a toll system environment in which a customer with one contract can use a vehicle in a variety of toll domains and with a different Toll Charger for each domain.
Toll systems covered by ISO 17573:2010 can be used for various purposes including road (network) tolling, area tolling, collecting toll for bridges, tunnels, ferries, for access, and for parking. From a technical point of view the considered toll systems use electronic equipment on board a vehicle.
From a process point of view the architectural description focuses on toll determination, toll charging, and the associated enforcement measures. The actual collection of the toll, i.e. collecting payments, is not included.
The architecture in ISO 17573:2010 is defined with no more details than those required for an overall overview, a common language, an identification of the need for other standards, and the drafting of these standards.
|
Withdrawn |
2010-12 |
Edition : 1 |
Number of pages : 72 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17573:2003 |
Road Transport and Traffic Telematics — Electronic Fee Collection (EFC) — Systems architecture for vehicle related transport services |
ISO/TS 17573:2003 specifies a system architecture for electronic fee collection (EFC) systems concerning vehicle related transport services such as the use of toll roads, zone access, parking and route guidance.
ISO/TS 17573:2003 does not cover person related transport services such as public transport. However, some of the clauses in ISO/TS 17573:2003 may also be applicable for fare collection.
NOTE Fare collection architecture in public transport is covered by other Working Groups in CEN/TC278 and ISO/TC204, e.g. WG3 Public Transport in CEN/TC278.
ISO/TS 17573:2003 provides the overview of, and inter-relationship among, the set of standards for design, development, testing and operation of applications in the field of EFC.
ISO/TS 17573:2003 is also applicable to the ITS Fundamental Service called Electronic Financial Transactions which is the use of electronic, or "cashless" payment systems for transportation. Hence, ISO/TS 17573:2003 covers toll collection systems, parking fee collection systems, systems for road and congestion pricing and integrated payment systems for transport services.
|
Withdrawn |
2003-06 |
Edition : 1 |
Number of pages : 30 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17574:2004 |
Road transport and traffic telematics — Electronic fee collection (EFC) — Guidelines for EFC security protection profiles |
ISO/TS 17574:2004 gives guidelines for the preparation and evaluation of security requirements specifications, referred to as Protection Profiles (PP) in ISO/IEC 15408 and ISO/IEC TR 15446, for the production of PPs and security targets. A PP is a set of security requirements which meet specific needs for a category of products or systems. A typical example would be a PP for OBEs to be used in an EFC system. In this case the PP would be an implementation-independent set of security requirements for the OBEs meeting the operators' and users' needs.
|
Withdrawn |
2004-11 |
Edition : 1 |
Number of pages : 67 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TR 20545:2017 |
Intelligent transport systems — Vehicle/roadway warning and control systems — Report on standardisation for vehicle automated driving systems (RoVAS)/Beyond driver assistance systems |
ISO/TR 20545:2017 provides the results of consideration on potential areas and items of standardization for automated driving systems. In this document, automated driving systems are defined as systems that control longitudinal and lateral motions of the vehicle at the same time.
Potential standardization areas and items are widely extracted and marshalled in a systematic manner to distinguish potential standardization for various automated vehicle systems. When, what, and by whom the standardization activities are actually done are discussed separately.
|
Published |
2017-07 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17574:2009 |
Electronic fee collection - Guidelines for security protection profiles |
ISO/TS 17574:2009 provides a guideline for preparation and evaluation of security requirements specifications, referred to as Protection Profiles (PP) in the ISO/IEC 15408 series and in ISO/IEC TR 15446. By a Protection Profile (PP) is meant a set of security requirements for a category of products or systems that meet specific needs. A typical example would be a PP for On-Board Equipment (OBEs) to be used in an EFC system.
ISO/TS 17574:2009 should be read in conjunction with the underlying standards ISO/IEC 15408 and ISO/IEC TR 15446. Although a layman could read the first part of the document to have an overview on how to prepare a Protection Profile for EFC equipment, the annexes, in particular A.4 and A.5, require that the reader be familiar with ISO/IEC 15408. The document uses an OBE with an integrated circuit(s) card (ICC) as an example to describe both the structure of the PP as well as the proposed content.
|
Withdrawn |
2009-09 |
Edition : 2 |
Number of pages : 60 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17574:2017 |
Electronic fee collection — Guidelines for security protection profiles |
ISO/TS 17574:2017 provides guidelines for preparation and evaluation of security requirements specifications, referred to as Protection Profiles (PP) in ISO/IEC 15408 (all parts) and in ISO/IEC TR 15446.
By Protection Profile (PP), it means a set of security requirements for a category of products or systems that meet specific needs. A typical example would be a PP for On-Board Equipment (OBE) to be used in an EFC system. However, the guidelines in this document are superseded if a Protection Profile already exists for the subsystem in consideration.
|
Published |
2017-03 |
Edition : 3 |
Number of pages : 52 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17575-1:2016 |
Electronic fee collection — Application interface definition for autonomous systems — Part 1: Charging |
ISO 17575-1:2016 defines the format and semantics of the data exchange between a Front End (OBE plus optional proxy) and corresponding Back Ends in autonomous toll schemes. It defines the data elements that are used to generate charge reports containing information about the road usage of a vehicle for certain time intervals, sent from the Front End to the Back End. It also defines the data that can be used to re-configure the ongoing process of gathering charge relevant information in the Front End. The scope is shown in Figure 1.
The constitution of the charge report is dependent on configuration data that are assumed to be present in the Front End. The assembly of charge reports can be configured for each individual toll scheme according to local needs. Charge reports generated in accordance with this part of ISO 17575 are consistent with the requirements derived from the architectural concept defined in ISO 17573:2010.
The definitions in ISO 17575-1:2016 comprise
- reporting data, i.e. data for transferring road usage data from Front End to Back End, including a response from the Back End towards the Front End,
- data for supporting security mechanisms,
- contract data, i.e. data for identifying contractually essential entities,
- road usage data, i.e. data for reporting the amount of road usage,
- account data for managing a payment account,
- versioning data, and
- compliance checking data, i.e. data imported from ISO 12813:2015, which are required in compliance checking communication.
Annex A contains the data type specifications using ASN.1 notation.
The protocol implementation conformity statements (PICS) proforma are provided in Annex B.
Annex C provides a graphical presentation of the structure of the data elements described in Clause 7.
Annex D provides information on how this part of ISO 17575 can be used in EETS environment and how the requirements that are specified in the EU-Decision 2009/750 are addressed by this standard.
|
Published |
2016-01 |
Edition : 1 |
Number of pages : 38 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17575-1:2010 |
Electronic fee collection — Application interface definition for autonomous systems — Part 1: Charging |
ISO/TS 17575‑1:2010 defines the format and semantic of the data exchange between a Front End (OBE plus optional proxy) and corresponding Back Ends in autonomous toll regimes. ISO/TS 17575‑1:2010 deals with the definition of the data elements used to report charging details from the Front End to the CE and to receive data which can be used to re-configure the ongoing process of gathering charge relevant information in the Front End.
The data defined in ISO/TS 17575‑1:2010 is used to generate charge reports that contain information about the road usage of a vehicle for certain time intervals. The contents of these charge reports might vary between toll regimes. A toll regime comprises a set of rules for charging, including the charged network, the charging principles, the liable vehicles and a definition of the required contents of the charge report.
The data defined in ISO/TS 17575‑1:2010 are exchanged using an open definition of a communication stack as defined in ISO/TS 17575‑2.
The definitions in ISO/TS 17575‑1:2010 comprise:
reporting data, i.e. data for transferring road usage data from Front End to Back End, including a response from the Back End towards the Front End;
contract data, i.e. data for identifying contractually essential entities;
road usage data, i.e. data for reporting the amount of road usage;
account data for managing a payment account;
versioning data;
compliance checking data, i.e. data imported from ISO/TS 12813, which are required in Compliance Checking Communications.
|
Withdrawn |
2010-06 |
Edition : 1 |
Number of pages : 23 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17575-1:2010/Cor 1:2013 |
Electronic fee collection — Application interface definition for autonomous systems — Part 1: Charging — Technical Corrigendum 1 |
|
Withdrawn |
2013-04 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17575-2:2016 |
Electronic fee collection — Application interface definition for autonomous systems — Part 2: Communication and connection to the lower layers |
ISO 17575-2:2016 defines how to convey all or parts of the data element structure defined in other parts of ISO 17575 over any communication stack and media suitable for this application. It is applicable only to mobile communication links (although wired links, i.e. back office connections, can use the same methodology).
To establish a link to a sequence of service calls initializing the communication channel, addressing the reception of the message and forwarding the payload are required. The definition provided in this part of ISO 17575 includes the required communication medium independent services, represented by an abstract application programming interface (API).
The communication interface is implemented as an API in the programming environment of choice for the Front End (FE) system. The specification of the Back End (BE) API is outside the scope of this part of ISO 17575.
The definition of this API in concrete terms is outside of the scope of this part of ISO 17575. This part of ISO 17575 specifies an abstract API that defines the semantics of the concrete API as illustrated in Figure 3 and its protocol implementation conformance statement (PICS) proforma (see Annex B). An example of a concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs, the term "communications API" or just "API" can be used.
ISO 17575-2:2016 also provides a detailed specification for the structure of associated API statements, an example on how to implement it and its role in a complex toll cluster such as the EETS (see Annex A to Annex E).
Media selection policies, certificate handling and encryption mechanisms are outside of the scope of this part of ISO 17575.
|
Published |
2016-01 |
Edition : 1 |
Number of pages : 28 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17575-2:2010 |
Electronic fee collection — Application interface definition for autonomous systems — Part 2: Communication and connection to the lower layers |
ISO/TS 17575‑2:2010 defines how to convey all or parts of the data element structure defined in ISO/TS 17575‑1 over any communication stack and media suitable for this application. It is focussed on mobile communication links. However, wired links shall use the same methodology.
The communication interface shall be implemented as an API in the programming environment of choice for the Front End (FE) system. The definition of this API in concrete terms is outside of the scope of ISO/TS 17575‑2:2010. ISO/TS 17575‑2:2010 specifies an abstract API that defines the semantics of the concrete API. An example concrete API is presented in Annex C. Where no distinction is made between the abstract and concrete communications APIs the term "communications API" or just "API", can be used.
|
Withdrawn |
2010-06 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 17575-3:2016 |
Electronic fee collection — Application interface definition for autonomous systems — Part 3: Context data |
ISO 17575-3:2016 defines the content, semantics and format of the data exchange between a Front End (OBE plus optional proxy) and the corresponding Back End in autonomous toll systems. It defines the data elements used to specify and describe the toll context details. Context data are transmitted from the Back End to the Front End to configure it for the charging processes of the associated toll context.
In ISO 17575, context data is the description of the properties of a single instance of an electronic fee collection (EFC) context. This single instance of an EFC context operates according to one of the basic tolling principles such as
- road section charging,
- area charging (according to travelled distance or duration of time), and
- cordon charging.
EFC context data comprise a set of rules for charging, including the description of the charged network, the charging principles, the liable vehicles and a definition of the required contents of the charge report. This set of rules is defined individually for each EFC context according to local needs.
The following data and associated procedures are defined in this part of ISO 17575:
- data providing toll context overview information;
- data providing tariff information (including definitions of required tariff determinants such as vehicle parameters, time classe, etc.);
- data providing context layout information;
- data providing reporting rules information.
ISO 17575-3:2016 also provides the required definitions and data specifications to be applied when one single toll context is spilt inot more than one toll context partitions. This is applicable to cases where one EFC scheme and the rules applied cannot be described with a single set of context data.
Annex A provides the data type specification using ASN.1 notation.
The protocol implementation conformity statements (PICS) proforma are provided in Annex B.
Annex C provides a graphical presentation of the structure of the toll context data.
Annexes D, E and F contain further information and descriptions, which may support the understanding and the implementation of the rules specified in this part of ISO 17575.
Annex G provides information how this part of ISO 17575 can be used in a European Electronic Toll Service (EETS) environment, with reference to EU Decision 2009/750.
|
Published |
2016-01 |
Edition : 1 |
Number of pages : 118 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17575-3:2011 |
Electronic fee collection — Application interface definition for autonomous systems — Part 3: Context data |
ISO/TS 17575 defines the information exchange between the Front End and the Back End in Electronic Fee Collection (EFC) based on autonomous on-board equipment (OBE). ISO/TS 17575-3:2011 defines the data to be used for a description of individual charging systems in terms of charged geographical objects and charging and reporting rules. For every Toll Charger's system, attributes defined in ISO/TS 17575-3:2011 are used to transfer data to the Front End in order to instruct it which data to collect and report.
|
Withdrawn |
2011-04 |
Edition : 1 |
Number of pages : 91 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17575-3:2011/Cor 1:2013 |
Electronic fee collection — Application interface definition for autonomous systems — Part 3: Context data — Technical Corrigendum 1 |
|
Withdrawn |
2013-04 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 17575-4:2011 |
Electronic fee collection — Application interface definition for autonomous systems — Part 4: Roaming |
ISO/TS 17575 defines the information exchange between the Front End and the Back End in Electronic Fee Collection (EFC) based on autonomous on-board equipment (OBE). ISO/TS 17575-4:2011 defines the functional details and data elements required to operate more than one EFC regime in parallel. The domains of these EFC regimes may or may not overlap. The charge rules of different overlapping EFC regimes may be linked, i.e. they may include rules that an area pricing scheme shall not be charged if an overlapping toll road is used and already paid for.
|
Withdrawn |
2011-04 |
Edition : 1 |
Number of pages : 24 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 18750:2018 |
Intelligent transport systems — Co-operative ITS — Local dynamic map |
This document:
— describes the functionality of a "Local Dynamic Map" (LDM) in the context of the "Bounded Secured Managed Domain" (BSMD);
— specifies:
— general characteristics of LDM Data Objects (LDM-DOs) that may be stored in an LDM, i.e. information on real objects such as vehicles, road works sections, slow traffic sections, special weather condition sections, etc. which are as a minimum requirement location-referenced and time-referenced;
— service access point functions providing interfaces in an ITS station (ITS-S) to access an LDM for:
— secure add, update and delete access for ITS-S application processes;
— secure read access (query) for ITS-S application processes;
— secure notifications (upon subscription) to ITS-S application processes;
— management access:
— secure registration, de-registration and revocation of ITS-S application processes at LDM;
— secure subscription and cancellation of subscriptions of ITS-S application processes;
— procedures in an LDM considering:
— means to maintain the content and integrity of the data store;
— mechanisms supporting several LDMs in a single ITS station unit.
|
Published |
2018-05 |
Edition : 1 |
Number of pages : 70 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO/TS 18750:2015 |
Intelligent transport systems — Cooperative systems — Definition of a global concept for Local Dynamic Maps |
This Technical Specification
— describes the functionality of a “Local Dynamic Map” (LDM) in the context of the “Bounded Secured Managed Domain” (BSMD), and
— specifies
— general characteristics of LDM Data Objects (LDM-DOs) that may be stored in an LDM, i.e. information on real objects such as vehicles, road works sections, slow traffic sections, special weather condition sections, etc. which are as a minimum requirement location-referenced and time-referenced,
— service access point functions providing interfaces in an ITS station (ITS-S) to access an LDM for
— secure add, update, and delete access for ITS-S application processes,
— secure read access (query) for ITS-S application processes,
— secure notifications (upon subscription) to ITS-S application processes, and
— management access,
— secure registration, de-registration, and revocation of ITS-S application processes at LDM, and
— secure subscription and cancellation of subscriptions of ITS-S application processes,
— procedures in an LDM considering
— means to maintain the content and integrity of the data store, and
— mechanisms supporting several LDMs in a single ITS station unit.
|
Withdrawn |
2015-05 |
Edition : 1 |
Number of pages : 59 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 19079:2016 |
Intelligent transport systems — Communications access for land mobiles (CALM) — 6LoWPAN networking |
ISO 19079:2016 describes the networking protocol functionality related to 6LoWPAN networking between two or more ITS stations communicating over the global Internet communication network.
It is assumed that the reader is familiar with IETF specifications found in "Request for Comments" (RFCs) 4944, 6282 and 2460 for 6LoWPAN and IPv6 protocols respective blocks used within this document. This document does not define a new protocol, neither does it define new abstraction for exchange of messages at the 6LoWPAN layer nor does it define new data structures. It, however, illustrates how the IETF protocols are combined to allow seamless communication among both heterogeneous and homogeneous ITS stations using 6LoWPAN. The 6LoWPAN family of protocols defined in this document as the Internet of Things Management Service Entity (IoT MSE) is integrated within the ITS station reference architecture as a new protocol block of the ITS station Networking and Transport layer. The procedures defined to share information between the IoT MSE block of the ITS station networking and transport protocols and other components of the ITS station architecture will be defined in the ISO 24102 series. ISO 24102 series includes the specifications for ITS station management, which are standardized to be compliant with the ITS station reference architecture and related standards.
In addition to the requirements described within this document, a number of notes and examples are provided to illustrate the IoT MSE block and its configuration.
|
Published |
2016-10 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|
| ISO 19080:2016 |
Intelligent transport systems — Communications access for land mobiles (CALM) — CoAP facility |
ISO 19080:2016 describes the CoAP facilities between two or more ITS stations communicating over the global internet communication network.
It is assumed that the reader is familiar with IETF specifications found in request for comments (RFCs) of individual CoAP and 6LoWPAN protocol blocks used within this document. This document does not define a new protocol, a new exchange of messages at the CoAP layer, or new data structures. It defines how protocols standardized by IETF are combined so that ITS stations can communicate with one another using CoAP. Procedures defined to share information between the CoAP layer and other components of the ITS station architecture are defined in ISO 24102 series (Management). In addition to the requirements specified within this document, a number of notes and examples are provided to illustrate CoAP main facilities.
|
Published |
2016-10 |
Edition : 1 |
Number of pages : 18 |
Technical Committee |
03.220.20
Road transport
;
35.240.60
IT applications in transport
|