ISO/TS 13141:2010/Cor 1:2013
(Corrigendum)Electronic fee collection — Localisation augmentation communication for autonomous systems — Technical Corrigendum 1
- BACK
- 18-Mar-2013
- 18-Mar-2013
- 03.220.20
- 35.240.60
- ISO/TC 204
Electronic fee collection — Localisation augmentation communication for autonomous systems — Technical Corrigendum 1
Perception de télépéage — Communications d'augmentation de localisations pour systèmes autonomes — Rectificatif technique 1
General Information
Relations
Standards Content (Sample)
TECHNICAL SPECIFICATION ISO/TS 13141:2010
TECHNICAL CORRIGENDUM 1
Published 2013-04-01
INTERNATIONAL ORGANIZATION FOR STANDARDIZATION МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ ORGANISATION INTERNATIONALE DE NORMALISATION
Electronic fee collection — Localisation augmentation
communication for autonomous systems —
TECHNICAL CORRIGENDUM 1
Perception de télépéage — Communications d'augmentation de localisations pour systèmes autonomes —
RECTIFICATIF TECHNIQUE 1
Technical Corrigendum 1 to ISO/TS 13141:2010 was prepared by Technical Committee ISO/TC 204,
Intelligent transport systems, in collaboration with Technical Committee CEN/TC 278, Road transport and
traffic telematics.
Page 15, Annex A
ICS 03.220.20; 35.240.60 Ref. No. ISO/TS 13141:2010/Cor.1:2013(E)
© ISO 2013 – All rights reserved
Published in Switzerland
---------------------- Page: 1 ----------------------
ISO/TS 13141:2010/Cor.1:2013(E)
Replace
'Container::=CHOICE{
integer [0] INTEGER,
bitstring [1] BIT STRING,
octetstring [2] OCTET STRING (SIZE (0.127), .),
universalString [3] UniversalString,
beaconId [4] BeaconID,
t-apdu [5] T-APDUs,
dsrcApplicationEntityId [6] DSRCApplicationEntityID,
dsrc-Ase-Id [7] Dsrc-EID,
attrIdList [
...
This May Also Interest You
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 semantics 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.
- Standard49 pagesEnglish languagesale 15% off
- 31-Jul-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
Automated valet parking systems (AVPSs) perform level 4 automated driving of individual or multiple unoccupied vehicles within a prescribed area of a parking facility. This document specifies performance requirements for the operation functions, the environmental conditions within parking facilities where automated vehicle operation is performed, and the test procedures to verify the performance requirements. An AVPS is comprised of physically separated sub-systems distributed among vehicles, facility equipment and user domains. The functionalities of AVPSs are realized by cooperation of these sub-systems, which are, in many cases, provided by different organizations. This document defines the system architecture and the communication interfaces between the sub-systems at the logical level. An AVPS manages its system participants (i.e. AVPS-compliant vehicles and parking facilities) and provides interfaces to other facility users and involved persons (e.g. system operators, facility managers). This document contains requirements for the management functions such as checking compatibility between vehicles and parking facilities, performing remote assistance and recovery when automated driving cannot be performed, and executing operation stop commands in response to the actions of other facility users. AVPSs are intended for use by a service provider upon receiving authority over vehicles from individual service recipients. This document does not include parking automation technologies that are solely based on usage by an individual user. If the vehicle is put into driverless operation directly by the user, this is not considered to be part of the AVPS.
- Standard153 pagesEnglish languagesale 15% off
- 12-Jul-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
- Technical specification146 pagesEnglish languagesale 15% off
- Draft146 pagesEnglish languagesale 15% off
- Draft146 pagesEnglish languagesale 15% off
- 28-Jun-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
Motorway chauffeur systems (MCS) perform Level 3 automated driving on limited access motorways with the presence of a fallback-ready user (FRU). MCS can be implemented in various forms capable of responding to different driving scenarios. This document describes a framework of MCS including system characteristics, system states/transition conditions and system functions. MCS are equipped with a basic set of functionalities to perform in-lane operation and can also be equipped with additional functionalities such as lane changing. This document specifies requirements of the basic set of functionalities and test procedures to verify these requirements. The requirements include vehicle operation to perform the entire dynamic driving task (DDT) within the current lane of travel, to issue a request to intervene (RTI) before disengaging, and to extend operation and temporarily continue to perform the DDT after issuing an RTI. This document describes one specific form of system engagement. Other forms are possible. These other system engagement forms, especially those provided in combination with other driving automation system features, are not within the scope of this document. Requirements and test procedures for the additional functionalities are provided in other parts of the ISO 23792 series. Means related to setting a destination and selecting a route to reach the destination are not within the scope of this document. This document applies to MCS installed in light vehicles.
- Technical specification30 pagesEnglish languagesale 15% off
- Draft30 pagesEnglish languagesale 15% off
- Draft30 pagesEnglish languagesale 15% off
- 08-Jun-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
This document defines the charging performance metrics to be used during the evaluation or on-going monitoring of an electronic fee collection (EFC) system and the examination framework for the measurement of these metrics. 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. The following scheme types are within the scope of this document: a) discrete schemes; b) continuous schemes (autonomous type of systems). This document defines measurements only on standardized interfaces. This document defines metrics for the charging performance of EFC systems in terms of the level of errors associated with charging computation. This document describes a set of metrics with definitions, principles and formulations, which together make up a reference framework for the establishment of requirements for EFC systems and the subsequent examination of charging performance. This document defines metrics for the following information exchanges: — charge reports (including usage evidence); — toll declarations; — exception lists; — billing details and associated event data; — payment claims on the level of service user accounts; — end-to-end metrics which assess the overall performance of the charging process. These metrics 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 following aspects are outside the scope of this document. — Definition of specific numeric performance bounds, or average or worst-case error bounds in percentage or monetary units. — Specification of a common reference system which would be required for comparison of performance between systems. — Measurements on proprietary interfaces. NOTE It is not possible to define standardized metrics on such system properties. Neither is it possible to define metrics for parts of the charging processing chain which are considered to be the internal matter of an interoperability partner, such as: — equipment performance, e.g. for on-board equipment (OBE), roadside equipment (RSE) or data centres such as signal range, optical resolution or computing system availability; — position performance metrics: the quality of data generated by position sensors is considered as an internal aspect of the GNSS front end. It is masked by correction algorithms, filtering, inferring of data and the robustness of the charge object recognition algorithms. — The evaluation of the expected performance of a system based on modelling and measured data from a trial at another place.
- Technical specification118 pagesEnglish languagesale 15% off
- Draft120 pagesEnglish languagesale 15% off
- Draft120 pagesEnglish languagesale 15% off
- 08-Jun-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
This document defines the TPEG Speed information (SPI) application for reporting speed information for travellers. Speed limits are usually indicated to the driver through roadside signs. Drivers who are aware of the speed limit at all times are more likely to drive safely, which improves road safety. Most speed limit signs are static and remain unchanged for years and are thus available through navigation system map databases. However, there is an increasing number of variable message signs, temporary signing (e.g. for road works) and also changed speed limits which are not yet reflected in the map databases. With the TPEG-SPI application, speed limit information is offered in an accurate way so that different lanes and different vehicle types can be differentiated. TPEG-SPI also allows the drivers to be aware of the current allowed (maximum) speed, by delivering timely information about the current position and values of speed limits to the navigation or driver assistance systems. These data are seen as informational and are intended to be encoded in a compact way to minimize bandwidth consumption. TPEG2-SPI supports direct and indirect speed limits. Direct speed limits are used for signs showing a maximum speed at which a vehicle is allowed to travel. Such speed limit signs can be static or dynamic. Indirect speed limits refer to the speed of other road users. It is primarily the vehicle in front of the own vehicle that is used as a reference.
- Standard35 pagesEnglish languagesale 15% off
- Draft33 pagesEnglish languagesale 15% off
- 24-May-2023
- 03.220.01
- 03.220.20
- 35.240.60
- ISO/TC 204
This document defines an index to the complete set of TPEG Generation 2 toolkit components and applications. New applications are enumerated with an application identification (AID) as they are added to the TPEG applications family. NOTE 1 This document will be updated when new applications occur in order to indicate the latest status and the inter-working of the various TPEG specifications. This document will be revised as a new edition every time a new issue of any other specification is issued. NOTE 2 Preliminary AIDs are allocated and managed by TISA and are listed at Reference.
- Standard9 pagesEnglish languagesale 15% off
- 05-Mar-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
This document specifies basic control strategies, minimum functional requirements, basic driver interface elements, and test procedures for verifying the system requirements for collision evasive lateral manoeuvre systems (CELM). A CELM is a safety system aimed at supporting the driver’s vehicle operation by avoiding collisions with objects in the forward path of the vehicle. When a collision is predicted, the CELM controls lateral movement of the vehicle by generating yaw moment. The lateral control manoeuvres can be performed automatically by CELM or can be initiated by the driver and supported by CELM. Specific methods for object detection and other environmental perception technologies are not described in this document. This document applies to light vehicles and heavy trucks. Vehicles equipped with trailers are not within the scope of this document.
- Standard31 pagesEnglish languagesale 15% off
- 22-Feb-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
This document: — examines and analyses the safety environment for low-speed automated driving services (LSADS); — describes the safety role supplement to the functional model described in ISO/TS 5255-1; — describes the supplemental safety points for LSADS; — describes role for the functional model of service applications for LSADS. This document can contribute to the development of future automated driving system service safety requirement use cases, other than the one described in ISO/TS 5255-1. This document is applicable to services using LSADS-equipped vehicles only. In-vehicle control system is not in scope of this document.
- Technical report9 pagesEnglish languagesale 15% off
- Technical report9 pagesEnglish languagesale 15% off
- 09-Feb-2023
- 03.220.20
- 35.240.60
- ISO/TC 204
This document specifies the application interface in the context of electronic fee collection (EFC) systems using dedicated short-range communication (DSRC). The EFC application interface is the EFC application process interface to the DSRC application layer, as can be seen in Figure 1. This document comprises specifications of: — EFC attributes (i.e. EFC application information) that can also be used for other applications and/or interfaces; — the addressing procedures of EFC attributes and (hardware) components (e.g. integrated circuit(s) card); — EFC application functions, i.e. further qualification of actions by definitions of the concerned services, assignment of associated ActionType values, and content and meaning of action parameters; — the EFC transaction model, which defines the common elements and steps of any EFC transaction; — the behaviour of the interface so as to ensure interoperability on an EFC-DSRC application interface level. This is an interface standard, adhering to the open systems interconnection (OSI) philosophy (see ISO/IEC 7498-1), and it is as such not primarily concerned with the implementation choices to be realized at either side of the interface. This document provides security-specific functionality as place holders (data and functions) to enable the implementation of secure EFC transactions. Yet the specification of the security policy (including specific security algorithms and key management) remains at the discretion and under the control of the EFC operator, and hence is outside the scope of this document.
- Standard121 pagesEnglish languagesale 15% off
- Standard129 pagesFrench languagesale 15% off
- 20-Dec-2022
- 03.220.20
- 35.240.60
- ISO/TC 204
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.