1、PD ISO/TS 19091:2017Intelligent transport systems Cooperative ITS UsingV2I and I2V communicationsfor applications related tosignalized intersectionsBSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06PD ISO/TS 19091:2017 PUBLISHED DOCUMENTNational forewordThis Published
2、Document is the UK implementation of ISO/TS 19091:2017. The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purpo
3、rt to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2017. Published by BSI Standards Limited 2017ISBN 978 0 580 92102 5 ICS 03.220.20; 35.240.60 Compliance with a British Standard cannot confer immunity from l
4、egal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2017.Amendments/corrigenda issued since publicationDate Text affectedPD ISO/TS 19091:2017 ISO 2017Intelligent transport systems Cooperative ITS Using V2I and I2V commun
5、ications for applications related to signalized intersectionsSystmes intelligents de transport Cooprative ITS Utilisation de communications V2I et I2V pour des applications relatives aux intersections signalesTECHNICAL SPECIFICATIONISO/TS19091Reference numberISO/TS 19091:2017(E)First edition2017-03P
6、D ISO/TS 19091:2017ISO/TS 19091:2017(E)ii ISO 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2017, Published in SwitzerlandAll rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechani
7、cal, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, Switze
8、rlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgPD ISO/TS 19091:2017ISO/TS 19091:2017(E)Foreword viIntroduction vii1 Scope . 12 Normative references 13 Terms and definitions . 24 Abbreviated terms 95 General description (informative) 115.1 Overview . 115.2 Functional model .
9、 115.2.1 Description . 115.2.2 Architecture 135.2.3 Message interactions .155.2.4 Common operational assumptions . 155.3 Safety use cases . 165.3.1 Intent . 165.3.2 Additional assumptions 175.3.3 Architecture implications 175.4 Mobility/sustainability use cases 175.4.1 Intent . 175.4.2 Additional as
10、sumptions 185.4.3 Architecture implications 185.5 Priority/pre-emption use cases 185.5.1 Intent . 185.5.2 Additional assumptions 205.5.3 Architecture implications 205.5.4 Public transport signal priority application 215.5.5 Freight vehicle signal priority application225.5.6 Emergency (public safety)
11、 vehicle pre-emption application .236 Function description (informative) .246.1 Public safety vehicle 246.1.1 Broadcast public safety vehicle information 246.1.2 Broadcast emergency response indication 246.2 Signal pre-emption . 246.2.1 Signal pre-empt request (normal power) .256.2.2 Signal pre-empt
12、 request (high power) 256.2.3 Request signal pre-empt Message identifier .256.2.4 Request signal pre-empt Intersection identifier 256.2.5 Request signal pre-empt Approach lane .256.2.6 Request signal pre-empt Egress lane .266.2.7 Request signal pre-empt Vehicle class 266.2.8 Request signal pre-empt
13、Time of service .266.2.9 Request signal pre-empt Vehicle identity 266.2.10 Request signal pre-empt Vehicle location and speed.266.2.11 Request signal pre-empt Cancellation 266.2.12 Request signal pre-empt Transaction identifier 276.2.13 Request signal pre-empt Duration .276.3 Public transport and co
14、mmercial vehicle . 276.3.1 Broadcast priority requesting vehicle information 276.4 Signal priority requirements . 276.4.1 Signal priority request .276.4.2 Request signal priority Message identifier .276.4.3 Request signal priority Intersection identifier 28 ISO 2017 All rights reserved iiiContents P
15、agePD ISO/TS 19091:2017ISO/TS 19091:2017(E)6.4.4 Request signal priority Approach lane .286.4.5 Request signal priority Egress lane .286.4.6 Request signal priority Vehicle class 286.4.7 Request signal priority Time of service .286.4.8 Request signal priority Vehicle identity 286.4.9 Request signal
16、priority Vehicle location and speed .296.4.10 Request signal priority Service information .296.4.11 Request signal priority cancellation 296.4.12 Request signal priority Priority request level 296.4.13 Request signal priority Transaction identifier 296.4.14 Request signal priority Duration . 296.4.1
17、5 Request signal priority Transit schedule 296.5 Broadcast areas geometrics. 306.5.1 Broadcast roadway geometrics 306.5.2 Broadcast roadway geometrics Message identifier .306.5.3 Broadcast intersection Identifier 306.5.4 Broadcast intersection Reference point 306.5.5 Broadcast intersection Lane/appr
18、oach default width 306.5.6 Broadcast intersection Egress lanes/approach 306.5.7 Broadcast intersection Ingress lanes/approach 316.5.8 Broadcast intersection Lane/approach number316.5.9 Broadcast intersection Lane/approach centerline coordinates .316.5.10 Broadcast intersection Vehicle lane/approach
19、manoeuvres.316.5.11 Broadcast intersection Pedestrian crossing lane/approach manoeuvres .326.5.12 Broadcast intersection Special lane/approach manoeuvres .326.5.13 Broadcast intersection Version identifier 326.5.14 Broadcast intersection Crossings 326.5.15 Broadcast intersection Lane/approach width
20、.336.5.16 Broadcast intersection Node lane/approach width 336.5.17 Broadcast intersection Egress connection 336.5.18 Broadcast intersection Traffic control 336.5.19 Broadcast intersection Traffic control by lane/approach 336.5.20 Broadcast road conditions . 336.5.21 Broadcast intersection Signal gro
21、up 346.6 Broadcast GNSS augmentation details 346.6.1 Broadcast GNSS augmentations 346.6.2 Broadcast GNSS augmentation detail NMEA .346.6.3 Broadcast GNSS augmentation detail RTCM346.7 Signalized intersection requirements 346.7.1 Broadcast signal phase and timing information 346.7.2 Broadcast signal
22、phase and timing Message identifier 356.7.3 Broadcast signal phase and timing Intersection identifier .356.7.4 Broadcast signal phase and timing Intersection status .356.7.5 Broadcast signal phase and timing Timestamp 356.7.6 Broadcast manoeuvre Signal group 356.7.7 Broadcast manoeuvre Manoeuvre sta
23、te 356.7.8 Broadcast manoeuvre Vehicular state 356.7.9 Broadcast manoeuvre Pedestrian state .356.7.10 Broadcast manoeuvre Special state 366.7.11 Broadcast manoeuvre Time of change Minimum 366.7.12 Broadcast manoeuvre Time of change Maximum .366.7.13 Broadcast manoeuvre Succeeding signal indications
24、366.7.14 Broadcast manoeuvre Succeeding signal indication time of change 376.7.15 Broadcast manoeuvre pending manoeuvre start time 376.7.16 Broadcast manoeuvre Pedestrian detect 376.7.17 Broadcast manoeuvre Pedestrian call .376.7.18 Broadcast manoeuvre Optimal speed information 386.7.19 Broadcast ma
25、noeuvre Signal progression information .38iv ISO 2017 All rights reservedPD ISO/TS 19091:2017ISO/TS 19091:2017(E)6.7.20 Broadcast manoeuvre Egress lane queue 386.7.21 Broadcast manoeuvre Egress lane storage availability 386.7.22 Broadcast manoeuvre Wait indication .386.8 Broadcast cross traffic sens
26、or information . 386.9 Broadcast vulnerable road user sensor information 386.10 Broadcast dilemma zone violation warning .386.11 Broadcast signal preferential treatment status .386.11.1 Broadcast preferential treatment Signal status message .396.11.2 Broadcast preferential treatment Message identifi
27、er .396.11.3 Broadcast preferential treatment Intersection identifier 396.11.4 Broadcast preferential treatment Intersection status 396.11.5 Broadcast preferential treatment Prioritization request status 396.11.6 Broadcast preferential treatment Vehicle source396.11.7 Broadcast preferential treatmen
28、t Transaction identifier .406.12 Message identifier . 406.13 System performance requirements 406.13.1 Broadcast intersection Computed lane/approach .406.14 Transmission rates Signal preferential treatment .406.14.1 Maximum transmission rate Request signal preferential treatment .406.14.2 Maximum res
29、ponse time Request signal preferential treatment 406.14.3 Minimum transmission rate Signal status message 406.14.4 Minimum transmission period Signal status message .416.15 Transmission rate requirements Broadcast roadway geometrics information .416.15.1 Minimum transmission rate Broadcast roadway g
30、eometrics information .416.15.2 Maximum transmission rate Broadcast roadway geometrics information 416.15.3 Default transmission rate Broadcast roadway geometrics information .416.16 Transmission rate requirements GNSS augmentations detail broadcasts 416.16.1 Minimum transmission rate GNSS augmentat
31、ion details broadcasts .416.16.2 Default transmission rate GNSS augmentation details broadcasts 416.17 Transmission rate requirements Broadcast signal phase and timing information .416.17.1 Minimum transmission rate Broadcast signal phase and timing information 426.17.2 Maximum transmission rate Bro
32、adcast signal phase and timing information 426.17.3 Default transmission rate Broadcast signal phase and timing information .426.18 Transmission rate requirements Broadcast cross traffic sensor information .426.18.1 Minimum transmission rate Broadcast cross traffic sensor information 426.18.2 Maximu
33、m transmission rate Broadcast cross traffic sensor information 426.18.3 Default transmission rate Broadcast cross traffic sensor information .426.19 Transmission rate requirements Broadcast vulnerable road user sensor information 426.19.1 Transmission rate Broadcast vulnerable road user sensor infor
34、mation 426.19.2 Maximum transmission rate Broadcast vulnerable road user sensor information436.19.3 Default transmission rate Broadcast vulnerable road user sensor information437 Messages 438 Conformance 43Annex A (informative) Use cases44Annex B (informative) Use case to requirements traceability 1
35、02Annex C (informative) Requirements traceability matrix 119Annex D (normative) Extension procedures . 133Annex E (normative) Profile A for J2735. 134Annex F (normative) Profile B for J2735 . 138Annex G (normative) Profile C for J2735 . 162Bibliography . 211 ISO 2017 All rights reserved vPD ISO/TS 1
36、9091:2017ISO/TS 19091:2017(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body intereste
37、d in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Com
38、mission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO documents
39、should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible
40、for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www .iso .org/ patents).Any trade name used in this document is information given for
41、the convenience of users and does not constitute an endorsement.For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (T
42、BT) see the following URL: www .iso .org/ iso/ foreword .html.The committee responsible for this document is ISO/TC 204, Intelligent transport systems.vi ISO 2017 All rights reservedPD ISO/TS 19091:2017ISO/TS 19091:2017(E)IntroductionCooperative-ITS (C-ITS) is a promising and remarkable advancement
43、of intelligent transport systems (ITS). Numerous cooperative applications are specified that open up new possibilities to make traffic safer, more efficient, and smarter. Technologies are developed and improved to realize and support those new services and applications. To enable those applications,
44、 information needs to be reliably communicated between the stationary infrastructure and mobile vehicles.This document describes the use cases for several applications that address safety, mobility, and ecological sustainability. Each use case has information needs that communication between vehicle
45、s and the infrastructure facilitate. It then identifies the information needs for the applications and the requirements to satisfy them. In turn, it maps the requirements into data frames and data elements to fulfil the requirements within the specified message set.ISO 22951 has a relationship to th
46、is document. PRESTO addresses its user needs through the implementation of a specific system architecture similar to that described in NTCIP 1211. This architecture includes traffic signals, message signs, routing systems, human machine interfaces, and fixed detection locations. Many of PRESTOs data
47、 value details are “left undefined to allow for discretional definition by each country.” The PRESTO architecture detects priority requesting vehicles by installing specific detection equipment at these locations.This document uses a similar set of user needs to develop the message set between vehic
48、les and the roadside equipment they interface. This document does not address the system architecture other than data needed to fulfil the user needs that will be managed elsewhere in the architecture. It details data values and structures in order to define the interface between these two devices.
49、Routing information is supported in the architecture through other mechanisms and is not a need supported by the vehicle to roadside equipment information flows. The user needs also provide for priority by approach, a preconfigured strategy, and ingress/egress lane requests. This document is based on vehicles periodically broadcasting their location an
