1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there
2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2014 SAE International All rights reserved. No part of this p
3、ublication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-497
4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/J3067_201408 SURFACE VEHICLE INFORMATION REPORT J3067 AUG2014 Issued 2014-08 Cand
5、idate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary SAE J2735 Using Systems Engineering Methods RATIONALE The SAE DSRC Technical Committee (TC) has received this recommendation for a comprehensive revision of SAE J2735, including documentation of the Systems Engi
6、neering (SE) process that is the foundation for the suggested normative content found herein. The committee is publishing this recommendation in this non-normative information report (IR) in the interest of exposing the recommendation to a large number of stakeholders. This IR does not replace the S
7、AE J2735 standard. The TC is considering this recommendation along with other suggested revisions. Any revision of SAE J2735 will be produced by the DSRC TC using normal SAE procedures. The committee takes no position at this time with regard to the content of the recommendations. Some material in t
8、his recommendation might eventually be reflected in other technical reports produced by the DSRC TC, including SAE standard J2735, while other material might not. The recommendation is written in the form of a standard, and includes language that suggests normative requirements and options. In the c
9、ontext of this information report, however, these statements are intended purely for information to the reader about the recommendation, and not as normative statements from SAE. While some of the information in this document can aid in understanding or implementing a test deployment of DSRC, the co
10、mmittee recommends that the document not be used to form implementation requirements. The current published revisions in SAE J2735 remain normative and shall take precedence over any conflicting portions of this document. There is no conformance statement for this information report. The DSRC TC wel
11、comes comments about this recommendation, as well as suggestions related to all DSRC standards within the scope of this committee. This document was provided by USDOT FHWA to SAE as: SAE J2735 Systems Engineering Version, Candidate Standard for Consideration by SAE Version v01c April 15, 2013 Prepar
12、ed for the: U.S. Department of Transportation NOTICE This SAE Information Report is a compilation of engineering reference data and educational material from various sources deemed useful to the technical community. Normative language contained herein should not be considered as an SAE Recommended P
13、ractice or SAE Standard. SAE INTERNATIONAL J3067 Issued AUG2014 Page 2 of 639 This SAE Information Report is a compilation of engineering reference data and educational material from various sources deemed useful to the technical community. Normative language contained herein should not be considere
14、d as an SAE Recommended Practice or SAE Standard. DOCUMENT REVISION HISTORY Filename Version Date Author QC Review Comment J2735 SE Candidate v1.doc 1 12/15/12 Chan Eisenhart, Sumner, Baker Final Candidate Standard J2735 SE Candidate v1a.doc 1a 02/15/12 Chan Eisenhart, Baker Incorporates Noblis comm
15、ents J2735 SE Candidate v1b.doc 1b 04/01/13 Chan Eisenhart Incorporates additional Noblis comments J2735 SE Candidate v1b.doc 1c 04/15/13 Chan Incorporates additional Noblis comments dated 4/3/13 and 04/11/13 03/10/2013 DCK Document entered SAE process to become an IR after DSRC TC review SAE INTERN
16、ATIONAL J3067 Issued AUG2014 Page 3 of 639 This SAE Information Report is a compilation of engineering reference data and educational material from various sources deemed useful to the technical community. Normative language contained herein should not be considered as an SAE Recommended Practice or
17、 SAE Standard. TABLE OF CONTENTS 1. SECTION 1 - GENERAL INFORMATIVE 25 1.1 Scope . 25 1.2 References . 25 1.2.1 Normative References . 25 1.2.2 Related Publications 26 1.3 General Statements . 26 1.4 Terms . 27 1.5 Abbreviations 30 2. SECTION 2 - CONCEPT OF OPERATIONS NORMATIVE 32 2.1 Tutorial Infor
18、mative 33 2.2 Current Situation and Problem Statement Informative . 34 2.2.1 Background 34 2.2.2 Description of the Current Situation . 35 2.2.3 Stakeholders and Other Involved Personnel . 37 2.2.4 Objectives 37 2.3 Reference Physical Architecture 39 2.3.1 Typical Physical Architecture Informative 3
19、9 2.3.2 SAE J2735 SE Device Characteristics Normative . 40 2.3.2.1 On-Board Unit (OBU) 40 2.3.2.2 Roadside Unit (RSU) . 41 2.3.2.3 Public Safety On-Board Unit (PSOBU) . 41 2.3.2.4 Transit Vehicle On-Board Unit (TrVOBU) . 41 2.3.2.5 Commercial Motor Vehicle On-Board Unit (CVOBU) 41 2.4 Architectural
20、Needs 41 2.4.1 Fundamental Needs Driving Connected Vehicles Deployment . 41 2.4.2 Operational Environment . 41 2.5 Features . 41 2.5.1 Introduction to User Needs 42 2.5.2 V2V User Needs 43 2.5.2.1 Crash Prevention Safety . 43 2.5.2.1.1 Forward Collision Prevention 43 2.5.2.1.2 Intersection Movement
21、Assist . 44 2.5.2.1.3 Pre-crash Actions . 44 2.5.2.1.4 Control Loss Warning . 44 2.5.2.1.5 Lane Change Warning 44 2.5.2.1.6 Do Not Pass Warning . 44 2.5.2.1.7 Blind Spot Warning . 44 2.5.2.1.8 Facilitate Development and Testing . 44 2.5.2.2 Situational Awareness . 44 2.5.2.3 Emergency Vehicle Alert
22、. 45 2.5.2.4 Vehicle Emergency Response 45 2.5.2.5 Mayday Request 45 2.5.2.6 Transit Vehicle Crash Warning . 45 SAE INTERNATIONAL J3067 Issued AUG2014 Page 4 of 639 This SAE Information Report is a compilation of engineering reference data and educational material from various sources deemed useful
23、to the technical community. Normative language contained herein should not be considered as an SAE Recommended Practice or SAE Standard. 2.5.3 V2I User Needs . 45 2.5.3.1 Safety and Eco Driving Related User Needs 45 2.5.3.1.1 Data to Determine Stopline Violations at Unsignalized Intersections . 45 2
24、.5.3.1.2 Data to Determine Stopline Violations at Signalized Intersections and Grade Crossings 45 2.5.3.1.3 Signal Movement at Intersections: Eco-Driving 45 2.5.3.2 Infrastructure Restriction Warnings . 46 2.5.3.2.1 Warnings about Hazards in a Work Zone 46 2.5.3.2.2 Warnings about Upcoming Work Zone
25、 46 2.5.3.2.3 Restricted Lane Warnings 46 2.5.3.2.4 Roadway Hazards Information . 46 2.5.3.2.5 Pedestrian and Turning Vehicle Crash Warning 46 2.5.3.3 Mayday Forward 46 2.5.3.4 Mayday Request to Infrastructure . 47 2.5.3.5 Commercial Vehicle Operations User Needs . 47 2.5.3.5.1 Commercial Vehicle Cr
26、edentialing and Permitting . 47 2.5.3.5.2 Safety Inspection Data 47 2.5.3.5.3 Vehicle Clearance . 47 2.5.3.5.4 Receive Parking Space Availability and Service Information . 47 2.5.3.6 Data Capture and Management User Needs 47 2.5.3.6.1 Vehicle Data for Traffic Operations 47 2.5.3.6.2 Vehicle Data for
27、 Highway Maintenance and Design . 48 2.5.3.6.3 Vehicle Data for Environmental Monitoring 48 2.5.3.6.4 Vehicle Data to Determine Hazardous Road Conditions 48 2.5.3.6.5 Vehicle Data for Weather Forecasting 48 2.5.3.7 Traveler Related User Needs 49 2.5.3.7.1 Speed Advisories 49 2.5.3.7.2 Location-Based
28、 Traveler Information and Advisories . 49 2.5.3.7.3 Vehicle Restrictions 49 2.5.3.7.4 Curve Speed Warning 49 2.5.3.8 Emergency Response Needs . 49 2.5.3.8.1 Minimize Delay to Emergency Vehicles at Traffic Signals 49 2.5.3.9 Transit Operation Needs . 49 2.5.3.9.1 Transit Signal Priority 49 2.5.3.10 V
29、ehicle Manufacturers and Fleet Operators User Needs . 50 2.5.3.10.1 Ad Hoc Messages . 50 2.6 Security. 50 2.7 Operational Policies and Constraints . 50 2.8 Relationship to the National ITS Architecture Informative 51 2.8.1 Vehicle to Other Vehicle Interface . 51 2.8.2 Vehicle to Roadway Interface 52
30、 2.9 Operational Scenarios Informative . 53 2.9.1 System Environment Description with External Stakeholders . 54 2.9.2 Operational Scenario Categories . 54 2.9.2.1 Actor Definitions 54 2.9.2.2 Operational Scenario Category Definitions . 55 2.9.2.2.1 Vehicle-to-vehicle - General Conditions . 56 2.9.2
31、.2.2 Vehicle-to-vehicle - Vehicle Maneuver . 56 2.9.2.2.3 Vehicle-to-vehicle Mayday . 57 2.9.2.2.4 Infrastructure-to-vehicle - Situational Awareness: Infrastructure Conditions 57 SAE INTERNATIONAL J3067 Issued AUG2014 Page 5 of 639 This SAE Information Report is a compilation of engineering referenc
32、e data and educational material from various sources deemed useful to the technical community. Normative language contained herein should not be considered as an SAE Recommended Practice or SAE Standard. 2.9.2.2.5 Infrastructure-to-vehicle - Situational Awareness: Flow Conditions 57 2.9.2.2.6 Vehicl
33、e-to-infrastructure (V2I) - Data Collection . 58 2.9.2.2.7 Vehicle-to-infrastructure - E-Commerce . 58 2.9.2.2.8 Special Cases - Commercial Vehicle Operations . 58 2.9.2.2.9 Special Cases - Transit Operations 59 2.9.2.2.10 Special Cases - Emergency Vehicle Operations 59 2.9.2.2.11 Special Cases - Ve
34、hicle Manufacturers and Fleet Operators . 59 2.9.3 Specific Operational Scenarios 59 2.9.3.1 Introduction to Specific Operational Scenarios . 59 2.9.3.2 General Conditions 60 2.9.3.3 Vehicle Maneuver 61 2.9.3.4 Mayday 62 2.9.3.5 Emergency Alert 62 2.9.3.6 Situational Awareness (Field) 63 2.9.3.7 Dat
35、a Collection 64 2.9.3.8 E-Commerce . 64 2.9.3.9 Special Cases - Data Communications. 65 2.9.3.10 Transit Operations . 66 2.9.3.11 Commercial Vehicle Operations 66 2.9.3.12 SPaT Broadcast 67 3. SECTION 3 - FUNCTIONAL REQUIREMENTS NORMATIVE . 67 3.1 Tutorial Informative 68 3.2 Scope of the Interface I
36、nformative . 69 3.3 Protocol Requirements List (PRL) 70 3.3.1 Notation Informative . 70 3.3.1.1 Conformance Symbols 70 3.3.1.2 Conditional Status Notation . 71 3.3.1.3 Support Column Symbols 72 3.3.2 Instructions for Completing the PRL Informative . 72 3.3.2.1 Conformance Definition . 72 3.3.2.2 Ext
37、ensions . 73 3.3.3 Protocol Requirements List (PRL) Table . 74 3.3.3.1 User Need ID and User Needs Column 74 3.3.3.2 FR ID and Requirements Columns . 74 3.3.3.3 Additional Specifications Column 74 3.4 Architectural Requirements 195 3.4.1 OBU - Broadcast Information 195 3.4.2 RSU - Broadcast Informat
38、ion . 195 3.4.3 Connected Device Dialogs 195 3.4.4 Forwarded Requests . 195 3.5 Data Exchange and Operational Environment Requirements . 195 3.5.1 Vehicle Requirements 196 3.5.1.1 Broadcast Vehicle Information - Critical Information . 196 3.5.1.1.1 Broadcast Vehicle Information - Critical Informatio
39、n - Compact Form . 196 3.5.1.1.2 Broadcast Vehicle Information - Critical Information - Verbose 196 3.5.1.1.3 Broadcast Vehicle Information - Mandatory Requirements 196 3.5.1.1.4 Broadcast Vehicle Information - Optional Requirements 200 SAE INTERNATIONAL J3067 Issued AUG2014 Page 6 of 639 This SAE I
40、nformation Report is a compilation of engineering reference data and educational material from various sources deemed useful to the technical community. Normative language contained herein should not be considered as an SAE Recommended Practice or SAE Standard. 3.5.1.2 Device Information Request 208
41、 3.5.1.2.1 Request Vehicle Information - Message Identifier 209 3.5.1.2.2 Request Vehicle Information - Device Identifier . 209 3.5.1.2.3 Request Vehicle Information - Requested Item 209 3.5.1.3 Broadcast Intersection Infringement . 209 3.5.1.3.1 Broadcast Intersection Infringement - Message Identif
42、ier 209 3.5.1.3.2 Broadcast Intersection Infringement - Device Identifier 210 3.5.1.3.3 Broadcast Intersection Infringement - Vehicle Time . 210 3.5.1.3.4 Broadcast Intersection Infringement - Path History 210 3.5.1.3.5 Broadcast Intersection Infringement - Intersection Identifier 210 3.5.1.3.6 Broa
43、dcast Intersection Infringement - Lane Number 210 3.5.1.3.7 Broadcast Intersection Infringement - Intersection Violation 210 3.5.2 Public Safety Vehicle Requirements 210 3.5.2.1 Broadcast Emergency Response Indication . 210 3.5.2.2 Signal Preemption Requirements . 211 3.5.2.2.1 Transmit Preempt Requ
44、est . 211 3.5.2.2.2 Request Signal Preempt - Mandatory Requirements . 211 3.5.2.2.3 Request Signal Preempt - Optional Requirements . 211 3.5.3 Commercial Vehicle Requirements . 213 3.5.3.1 Commercial Credentials Information Requirements . 213 3.5.3.1.1 Commercial Vehicle Information Request 213 3.5.
45、3.1.2 Transmit Commercial Vehicle Information . 217 3.5.3.2 Commercial Vehicle Screening Information Requirements 221 3.5.3.2.1 Transmit Screening Activity Result . 221 3.5.3.2.2 Screening Activity Results Acknowledgement 225 3.5.3.2.3 Commercial Screening Information Request 225 3.5.3.2.4 Transmit
46、Previous Screening Activity Result 226 3.5.3.3 Commercial Vehicle Clearance Requirements . 226 3.5.3.3.1 Transmit Instructions 226 3.5.3.3.2 Transmit Instructions Acknowledgement 227 3.5.4 Transit Vehicle Requirements 228 3.5.4.1 Request Signal Priority Requirements 228 3.5.4.1.1 Transmit Priority R
47、equest . 228 3.5.4.1.2 Transmit Priority Request - Mandatory Requirements 228 3.5.4.1.3 Transmit Priority Request - Optional Requirements . 229 3.5.5 Probe Data Requirements . 230 3.5.5.1 Probe Data Request 230 3.5.5.2 Transmit Probe Data Message . 231 3.5.5.2.1 Transmit Probe Data Information - Man
48、datory Requirements 231 3.5.5.2.2 Transmit Probe Data Information - Optional Requirements . 232 3.5.5.3 Broadcast Probe Management Information 236 3.5.5.3.1 Broadcast Probe Management Information - Mandatory Requirements 236 3.5.5.3.2 Broadcast Probe Management Information - Optional Requirements 23
49、8 3.5.6 Broadcast Roadway Geometrics Requirements 239 3.5.6.1 Broadcast Roadway Geometrics . 239 3.5.6.1.1 Broadcast Roadway Geometrics - Message Identifier . 240 3.5.6.2 Broadcast Details of an Intersection Geometric 240 3.5.6.2.1 Broadcast Intersection - Mandatory Requirements 240 3.5.6.2.2 Broadcast Intersection - Optional Requirements 242 SAE INTERNATIONAL J3067 Issued AUG2014 Page 7 of 639 This SAE Informatio
