Module 51 - CV271

CV271: Using the ISO TS 19091 Standard to Implement V2I Intersection Applications Introduction

HTML of the PowerPoint Presentation

(Note: This document has been converted from a PowerPoint presentation to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

Slide 1:

(Extended Text Description: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words "Standards ITS Training - Transit" in green and blue on the middle left side. The word "Welcome" in white is to the right of the logo. Under the logo box is the logo for the U.S. Department of Transportation, Office of the Assistant Secretary for Research and Technology.)

Slide 2:

(Extended Text Description: This slide, entitled "Welcome" has a photo of Ken Leonard, Director, ITS Joint Program Office, on the left hand side, with his email address, Ken.Leonard@dot.gov. A screen capture snapshot of the home webpage is found on the right hand side - for illustration only - from August 2014. Below this image is a link to the current website: www.its.dot.gov/pcb - this screen capture snapshot shows an example from the Office of the Assistant Secretary for Research and Development - Intelligent Transportation Systems Joint Program Office - ITS Professional Capacity Building Program/Advanced ITS Education. Below the main site banner, it shows the main navigation menu with the following items: About, ITS Training, Knowledge Exchange, Technology Transfer, ITS in Academics, and Media Library. Below the main navigation menu, the page shows various content of the website, including a graphic image of professionals seated in a room during a training program. A text overlay has the text Welcome to ITS Professional Capacity Building. Additional content on the page includes a box entitled What's New and a section labeled Free Training. Again, this image serves for illustration only. The current website link is: https://www.its.dot.gov/pcb.)

Slide 3:

CV271: Using the ISO TS 19091 Standard to Implement V2I Intersection Applications Introduction

(Extended Text Description: This slide contains the title "Module CV271: Using the ISO TS 19091 Standard to Implement V2I Intersection Applications Introduction" and also consists of a graphic of a connected vehicle environment. There are 3 intersections shown, 2 lanes in each direction for the middle intersection and also two T intersections, one north of the middle of the graphic and one located to the north east. There is also a train platform with a stopped train to the north of the middle intersection. The middle of the main intersection has white dashed lines (representing a wireless connection) drawn from the traffic signal to surrounding emergency and transit vehicles, and also to passenger vehicles and the nearby train. All of these vehicles have three yellow concentric circles around them, demonstrating wireless connectivity.)

Slide 4:

Instructor

Patrick Chan, P.E.

Senior Technical Staff

Consensus Systems Technologies (ConSysTec)

New York, NY, USA

Slide 5:

Learning Objectives

• Identify benefits of standardization for agencies, system developers, and suppliers
• Describe the scope of ISO TS 19091 Standard
• Describe the use cases addressed by ISO TS 19091 Standard
• Explain the relationship between ISO TS 19091 and SAE J2735
• Applying ISO TS 19091 Standard content to your project

Slide 6:

Learning Objective 1

• Identify benefits of standardization for agencies, system developers, and suppliers

Slide 7:

Benefits of Standardization for Agencies, System Developers, and Suppliers

Interoperability

• The ability of two or more systems or components to exchange information and use the information that has been exchanged
• Promotes competition and innovation
• Example: Wi-Fi with other internet standards

Slide 8:

Benefits of Standardization for Agencies, System Developers, and Suppliers

Overall Benefits of Standards

Benefit	Agency	System Developer	Supplier	Public
Facilitates regional integration
Decreases scope of the testing effort and makes testing easier
Expand market share
Reduces risk
Allows innovation
Safety, Mobility, Environmental Benefits
More consistent provision of services

Slide 9:

Slide 10:

Question

Which of the following is NOT a benefit of standardization?

Answer Choices

1. Supports interoperability
2. Reduces risk
3. Prohibits proprietary solutions
4. Helps with design and procurement

Slide 11:

Review of Answers

a) Supports interoperability
Incorrect. Standards support interoperability both within and between systems.

b) Reduces risk
Incorrect. Standards reduces risk by aiding testing.

c) Prohibits proprietary solutions
Correct! Standards allow proprietary extensions to allow for innovations.

d) Helps with design and procurement
Incorrect. Standards help with design and procurement by helping system developers to specify functions and communications.

Slide 12:

Learning Objectives

• Identify benefits of standardization for agencies, system developers, and suppliers
• Describe the scope of ISO TS 19091 Standard

Slide 13:

Learning Objective 2

• Describe the scope of ISO TS 19091 Standard

Slide 14:

What is a Connected Vehicle Environment, in Particular a V2I Environment?

Identify a Connected Vehicle Environment

• Vehicles broadcast their:
  • Current position
  • Current kinematics (speed, acceleration)
  • Sensor information
• Vehicles receive information that:
  • Can reduce the likelihood of incidents
  • Can improve mobility (e.g., reduce delays)
• Could also be a mobile device, such as a smartphone on a pedestrian or bicyclist

Slide 15:

What is a Connected Vehicle Environment, in Particular a V2I Environment?

V2I Scenario

• Vehicle Data:
  • Latitude, Longitude, Speed, Brake Status, Turn Signal Status, Vehicle Type
• Infrastructure Data:
  • Signal Phase and Timing
  • Time when vehicle will be allowed to travel through the intersection (Green)
  • Time when desired movement is no longer allowed (yellow)
  • Priority or preemption request granted

(Extended Text Description: This graphic is the same as in Slide #3. It consists of a graphic of a connected vehicle environment. There are 3 intersections shown, 2 lanes in each direction for the middle intersection and also two T intersections, one north of the middle of the graphic and one located to the north east. There is also a train platform with a stopped train to the north of the middle intersection. The middle of the main intersection has white dashed lines (representing a wireless connection) drawn from the traffic signal to surrounding emergency and transit vehicles, and also to passenger vehicles and the nearby train. All of these vehicles have three yellow concentric circles around them, demonstrating wireless connectivity.)

Slide 16:

What is a Connected Vehicle Environment, in Particular a V2I Environment?

Typical Communications Requirements

(Extended Text Description: In the top left hand corner of the slide there are 2 clips arts, one of a transit vehicle and the other of a red sports car. At the bottom right hand corner of the slide is a clip art of a traffic signal. Located in the middle of slides is a clip art of a yellow lightning bolt between the vehicles and the traffic signal, to indicate communications between them. To the left is the text: How do we communicate? Wireless on the same frequency. What language are we using? Agree on the grammar and dictionary. How many people are talking in the room? Talk louder or softer or change rooms or channels. The text What language are we using is circled in red. To the right is the text: Required for Deployment: Different manufacturers How do we trust each other? Authentication.)

Slide 17:

The Scope and Purpose of ISO TS 19091 Standard

ISO TS 19091 Standard

• Intelligent transport systems -Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections
• Expected to be published in 2017
• Defines the dialogs, messages, data structures, and data elements to support exchanges between the roadside equipment and vehicles related to signalized applications
  • Procure, implement and test in a consistent manner

(Extended Text Description: This slide contains a 2-dimensional graphic showing a top-down view of a four-way intersection, with one lane on each approach into the intersection. There are four traffic signals and 4 pedestrian-crossing signals, one of each at each corner of the intersection. There are 3 vehicles traveling northbound, 1 of which is a transit vehicle, and 3 other vehicles, one traveling south, one east, and one westbound. All vehicles have three concentric yellow circles around them to depict each vehicle broadcasting information. At the southwest corner of the intersection there is DSRC roadside equipment that is connected to a traffic signal controller. The DSRC unit has three red concentric circles around it, representing transmitted data messages.)

Slide 18:

The Scope and Purpose of ISO TS 19091 Standard

Applications Supported

Priority/Preemption applications

ID	Use Cases
PR1	Localized Public Transport Signal Priority (TSP)
PR1-a	Localized TSP - Near Side Stop
PR2	TSP Along an Arterial
PR3	Localized Freight Signal Priority
PR3-a	Localized Freight Signal Priority with a Platoon
PR3-b	Arterial Freight Signal Priority for a Platoon
PR4	Emergency Vehicle Single or Multiple Vehicles
PR5	Emergency Vehicle Single or Multiple Vehicles - High Power PSOBE (Public Safety OBE)
PR6	Mixed Emergency Vehicle and other priority eligible

Slide 19:

The Scope and Purpose of ISO TS 19091 Standard

Applications Supported

Safety applications

ID	Use Cases
SA1	Dilemma Zone Protection
SA2	Red Light Violation Warning
SA3	Stop Sign Violation Warning
SA4	Turning Assistant - Oncoming Traffic
SA5	Turning Assistant -Vulnerable Road User Avoidance
SA6	Non-Signalized Crossing Traffic Warning
SA7	Crossing Vulnerable Road User Advisory (non-signalized)

(Extended Text Description: There is a three-dimensional graphic of a signalized intersection. A northbound vehicle is approaching the intersection in a left-turn only lane, and there is also a second southbound vehicle approaching the intersection in the opposite direction. Four white dotted lines are shown from a controller on the corner, one to a pedestrian sensor on the conflicting crosswalk for the vehicle intending to make the left turn, one to vehicle detectors on the northbound approach, one to vehicle detectors on the southbound approach, and one to the traffic signal for the intersection. The traffic signal is green for northbound traffic, but the traffic signal also shows a No Left Turn symbol for northbound traffic.)

Reference: ISO TS 19091 Table A.1

Slide 20:

The Scope and Purpose of ISO TS 19091 Standard

Applications Supported

Mobility/Sustainability applications

ID	Use Cases
MS1	Basic Local Traffic Signal Actuation
MS2	Platoon Detection for Coordinated Signals
MS3	Congested Intersection Adjustment
MS4	Traffic Signal Optimal Speed Advisory
MS5	Signalized Corridor Eco-Driving Speed Guidance
MS6	Idling Stop Support
MS7	Start Delay Prevention
MS9	Inductive Charging at Signals
MS10	Don't Block the Box

(Extended Text Description: There is a graphic of a speedometer for a vehicle, with the text "Recommend 45 mph" shown above the speedometer. The speedometer has a circular bar that is black to 45 mph to present the recommended speed of 45 mph, yellow from 45 mph to 55 mph to show the speed limit of 55 mph, and red from 55 mph to 80 mph.)

Slide 21:

Slide 22:

Question

Which of the following is NOT an application supported by ISO TS 19091?

Answer Choices

1. Localized Public Transport Signal Priority
2. Signalized Corridor Eco-Driving Speed Guidance
3. Red Light Violation Warning
4. Forward Collision Warning

Slide 23:

Review of Answers

a) Localized Public Transport Signal Priority
Incorrect. Public transport signal priority involves signalized intersections and is thus within the scope of the ISO TS 19091.

b) Signalized Corridor Eco-Driving Speed Guidance
Incorrect. Eco-driving uses traffic signal information to optimize vehicle trajectory and is thus within the scope of the ISO TS 19091.

c) Red Light Violation Warning
Incorrect. Red light violation warning involves signalized intersections and is thus within the scope of the ISO TS 19091.

d) Forward Collision Warning
Correct! Forward collision warning is a V2V application and thus not within the scope.

Slide 24:

Learning Objectives

• Identify benefits of standardization for agencies, system developers, and suppliers
• Describe the scope of ISO TS 19091 Standard
• Describe the use cases addressed by ISO TS 19091 Standard

Slide 25:

Learning Objective 3

• Describe the use cases addressed by ISO TS 19091 Standard

Slide 26:

The Contents of the Standard

ISO TS 19091

• Scope
• Normative References
• Terms and Definitions
• Symbols and Abbreviation Terms
• General Description
• Function Description
• Messages
• Conformance

(Extended Text Description: Author's relevant description: This slide contains a partial snapshot of the Table of Contents of ISO/DTS 19091:2016(E), from the Forward to Section 8.)

Slide 27:

The Contents of the Standard

ISO TS 19091

• Annex A - Use Cases
• Annex B - Use Case to Requirements Traceability
• Annex C - RTM
• Annex D - Extension procedures
• Annex E, F, G - J2735 Profiles

(Extended Text Description: Author's relevant description: This slide contains a partial snapshot of the Table of Contents of ISO/DTS 19091:2016(E), from Annex A to Annex G.)

Slide 28:

The Use Cases Described in the Standard

Use Case Types

The V2I applications covered in ISO TS 19091 are described by use cases

• Defines the operations between the actors
• Defines information needs for communication between vehicles and infrastructure
• Identifies information needs for the applications

Three types of use cases:

• PR: priority/preemption
• SA: safety
• MS: mobility/sustainability

Slide 29:

The Use Cases Described in the Standard

Use Case Examples

Table A.2 — PR1: Localized public transport signal priority (TSP)

Use Case Name	Basic TSP Scenario - Single Public Transport Vehicle at One Signalized Intersection
Category	Mobility
Infrastructure Role	Data Receiver, Traffic Signal Control, Data Transmitter
Short Description	This use case describes the basic priority control for connected Public Transport vehicles
Goal	Improved Public Transport efficiency and reliability
Constraints	Use of DSRC or other medium that will meet the performance requirements for this use case (the RSE and OBE include radio devices that operate in the medium used) Alternate: Wide area broadband communications is available for the public transport vehicle to indicate its TSP request via an alternate media than DSRC through Back-office Processing Center (BOPC) (Data flow #5 supports that situation)
Geographic Scope	Localized to a specific intersection
Actors	Public Transport Vehicle Equipped with On board Equipment (OBE) Road Side Equipment (RSE) & Traffic Signal Controller (TSC) Alternate: Traffic Management Central System (BOPC)

Slide 30:

The Use Cases Described in the Standard

Use Case

(Extended Text Description: This slide contains a 2-dimensional graphic showing a top-down view of a four-way intersection with one approach lane in each direction. There are four traffic signals, and 4 pedestrian-crossing signals, one of each at each corner of the intersection. There are 2 vehicles traveling northbound, 1 of which is a transit vehicle, and 3 other vehicles, one traveling south, one east, and one westbound. All vehicles have three concentric yellow circles around them to depict each vehicle broadcasting information. There are also 2 pedestrians, one crossing the east approach lanes and one crossing the west approach lanes. At the southwest corner of the intersection are three boxes entitled "DSRC Roadside Equipment", "Traffic Controller Equipment", and "Traffic Management Central System." There is a line with a "1" in a hexagon box between the northbound transit vehicle and the "DSRC Roadside Equipment" box to indicate Flow 1. There is a line with a "2" in a hexagon box between the "DSRC Roadside Equipment" box and the "Traffic Controller Equipment" box to indicate Flow 2. There is a line with a "3" in a hexagon box between the "DSRC Roadside Equipment" box and the "Traffic Management Central System" box to indicate Flow 3. There is a line with a "4" in a hexagon box between the "Traffic Controller Equipment" box and the "Traffic Management Central System" box to indicate Flow 4. There is a line with a "5" in a hexagon box between the "Traffic Management Central System" box and the northbound transit vehicle to indicate Flow 5.)

Slide 31:

The Use Cases Described in the Standard

Use Case Examples

Preconditions	The transportation agency(ies) have established a policy for priority control (called N-level priority) and the fleet management (Public Transport) system is prepared to provide priority service for vehicles on routes. The traffic signal controller is programmed with a variety of priority control schemes such as early green, green extension, phase rotation, phase skilling, etc.; the traffic signal controller has an intelligent algorithm for providing priority signal timing for priority requests.
Main flow	Vehicle to TSC - Direct The use case begins when an equipped Public Transport vehicle enters the radio range of an RSE (note that if another medium is used, the same assumption applies). The OBE (Public Transport vehicle) receives MAP and SPaT from the RSE. The OBE sends Basic Safety Messages [BSM] or Cooperative Awareness Message [CAM]. ... ...
Alternate flow(s)	[7] The Public Transport vehicle changes speed and the RSE updates priority timing based on travel time estimates. (insert between steps 12-13) The RSE updates the Public Transport vehicle served performance measures.
	Vehicle to Intersection - Indirect through BOPC OBE monitors its vehicle position using an on-board map and location algorithms. Hence, the vehicle determines which intersection(s) is approaching and the likely time of arrival. Precondition: the vehicle must have on-board map information

Slide 32:

The Use Cases Described in the Standard

Use Case

Post-conditions	The TSC initiates recovery operations to restore normal timing operation which might include appropriate coordination. Some recovery may include split time compensation to clear queues which might have formed on the phases that were adversely affected by the priority request.
Information Requirements	SPaT Current maneuver(s) permitted, remaining time for maneuver, yellow clearance time, red clearance time, next maneuver to be serviced, queue length or end of queue information, and pedestrian warning MAP Intersection Geometry (MAP base), permitted maneuvers, and changes to MAP other than base Etc.
Issues	This use case assumes that the scenarios needed for the Public Transport vehicle are pre-determined and loaded into TSC. It also presumes that the Public Transport vehicle knows which of the scenarios that the controller can support should be invoked to meet its specific needs although these might be included in the SSM. Note that this also assumes that the vehicle knows its route and hence knows what exit lane (or maneuver) to request. Etc...
Source docs/references	MMITSS, CEN, USDOT J2735TM SE Candidate

Slide 33:

The Types of Requirements Described in the Standard

Requirements

• The use cases describe the information flows between the actors
  • Defines what data is needed and why
• ISO 19091 lists requirements describing the details of that data
• Deployments that follow ISO 19091 would build to the same requirements - helps ensures interoperability

(Extended Text Description: There is a graphic with blue box entitled "Use Cases" on the left, a red box entitled "Requirements" on the right, and a black arrow pointing from the "Use Cases" to the "Requirements" box.)

Slide 34:

The Types of Requirements Described in the Standard

Requirement Types

• Two types of requirements in ISO TS 19091
  • Functional Requirements
  • Performance Requirements
    • Transmission Rates

(Extended Text Description: There is a graphic with blue box entitled "Use Cases" on the left, and two red box on the right, one on top of the other. The red box on top is entitled "Functional Requirements" and the box on the bottom is entitled "Performance Requirements." There are two black arrows from the "Use Cases", one pointing to each red box on the right.)

Slide 35:

The Types of Requirements Described in the Standard

Functional Requirement Types

Grouped by:

• Device
  • Public safety vehicle
  • Public transport and commercial vehicle
  • Signalized intersection
  • Cross Traffic Sensor
  • Vulnerable Road User Sensor Information

• Information
  • Signal Phase and Timing information
  • Signal preemption / priority
  • Signal preemption / priority Status
  • Roadway Geometrics
  • GNSS Augmentation Details

Slide 36:

Slide 37:

Question

Which of the following is NOT a category of use cases in ISO TS 19091?

Answer Choices

1. Safety
2. Electronic Payment
3. Mobility/Sustainability
4. Signal Priority/Preemption

Slide 38:

Review of Answers

a) Safety
Incorrect. Safety (SA) use cases are included in ISO TS 19091.

b) Electronic Payment
Correct! Electronic payment is not covered in ISO TS 19091, although it is a category of applications.

c) Mobility/Sustainability
Incorrect. Mobility/Sustainability (MS) is a category of uses cases in ISO TS 19091.

d) Signal Priority/Preemption
Incorrect. Signal Priority and Preemption (PR) is a category of use cases in ISO TS 19091.

Slide 39:

Learning Objectives

• Identify benefits of standardization for agencies, system developers, and suppliers
• Describe the scope of ISO TS 19091 Standard
• Describe the use cases addressed by ISO TS 19091 Standard
• Explain the relationship between ISO TS 19091 and SAE J2735

Slide 40:

Learning Objective 4

• Explain the relationship between ISO TS 19091 and SAE J2735™

Slide 41:

The Relationship of This Standard with SAE J2735^TM

(Extended Text Description: This slide has a graphic with the three levels of information. The top level is entitled "Data" and contains four blue bubbles with the word "Word" inside. The middle level is entitled Message and contains one blue bubble with the word "Sentence" inside. The bottom level is entitled "Protocol" and has a clipart with a pencil writing on a notepad. There is a black arrow pointing from the bullet point "Specifies data frames and data elements" to the top level entitled "Data", and a blue arrow pointing from the bullet point "Specifies the message set for DSRC" to the middle level entitled "Message." To the left are the following bullet points:

ISO TS 19091 and SAE J2735

• SAE J2735, Dedicated Short Range Communications (DSRC) Message Set Dictionary, is a data dictionary
  • Specifies the message set for DSRC
  • Specifies data frames and data elements
• Analogy: English language

)

Slide 42:

The Relationship of This Standard with SAE J2735^TM

(Extended Text Description: This slide has a graphic with the three levels of information. The top level is entitled "Data" and contains four blue bubbles with the word "Word" inside. The middle level is entitled Message and contains one blue bubble with the word "Sentence" inside. The bottom level is entitled "Grammar" and has a clipart with a pencil writing on a notepad. There is a black arrow pointing from the bullet point "Adds the rules for the use of these messages, data structures and data elements" to the bottom level entitled "Grammar." To the left are the following bullet points:

ISO TS 19091 and SAE J2735

• Analogy: English grammar
• ISO TS 19091 is the grammar
  • References SAE J2735 for the messages, data structures and data elements for V2I applications
  • Adds the rules for the use of these messages, data structures and data elements

)

Slide 43:

The Relationship of This Standard with SAE J2735^TM

ISO TS 19091 and SAE J2735

ISO TS 19091

• Works together with SAE J2735 to define the design to fulfill the functional requirements in ISO TS 19091
• Provides a matrix that defines the SAE J2735 design to fulfill each functional requirement in ISO TS 19091
  • The design may be in the form of a message, data frame or data element

(Extended Text Description: There is a graphic with blue box entitled "Use Cases" on the left, a red box entitled "Functional Requirements" in the middle, and a green box entitled "SAE J2735" on the right. There is a black arrow pointing from "Use Cases" to the "Functional Requirements" box. There is a black arrow pointing from the "SAE J2735" to the "Functional Requirements" box, with a note "fulfills requirements" to indicate that SAE J2735 is used to fulfill the Functional Requirements.)

Slide 44:

The Relationship of This Standard with SAE J2735^TM

ISO TS 19091 and SAE J2735

Example:

• Requirement 6.7.1 Broadcast signal phase and timing information
  • An RSE shall broadcast a message with signal phase and timing information. Signal phase and timing information may be used to provide connected devices with the current status of a signalized intersection. Together with the intersection geometric information, connected vehicles can determine what maneuvers are currently permitted by lane/approach, and when their permitted maneuver may end.
  • ISO TS 19091 defines the SAE J2735 Signal Phase and Timing Message (SPaT) to fulfill this requirement

Slide 45:

The Relationship of This Standard with SAE J2735^TM

ISO TS 19091 and SAE J2735

Other SAE J2735 Messages used to fulfill requirements in ISO TS 19091:

• Basic Safety Message (BSM (P1))
• Signal Request Message (SRM)
• MAP Data Message (MAP). Describes the geometry of the roadway intersection
• NMEA Message (NMEA). Provides differential GPS corrections.
• RTCM Message (RTCM). Provides differential GPS corrections.
• Signal Status Message (SSM)

Slide 46:

The Relationship of This Standard with SAE J2735^TM

ISO TS 19091 and SAE J2735

Example:

• Requirement 6.7.2 Broadcast signal phase and timing - message identifier
  • An RSE shall include a message identifier as part of the signal phase and timing message broadcast. A change in the message identifier indicates a change in the message content. This requirement allows a connected device to ignore (not process) messages from an RSE when the content has not changed.
  • ISO TS 19091 defines the SAE J2735 data element MsgCount within the (SAE J2735) SPaT message to fulfill this requirement

Slide 47:

The Relationship of This Standard with SAE J2735^TM

ISO TS 19091 and SAE J2735

• SAE J2735 allows DE_MsgCount to be incremented every time a message is broadcasted OR when the contents of the message changes
  • ISO TS 19091 standardizes the use of DE_MsgCount for SPAT and MAP messages so it is only incremented when the contents change
• Decreases risk of misinterpretations, which may compromise safety

Slide 48:

Slide 49:

Question

How does ISO TS 19091 use SAE J2735 to specify message contents?

Answer Choices

1. Fulfill requirements based on ISO 19091 use cases
2. Fulfill requirements found in the SAE J2735 standard
3. Directly satisfy the user needs derived from the ISO 19091 use cases
4. Directly satisfy the user needs in the SAE J2735 standard

Slide 50:

Review of Answers

a) Fulfill requirements based on ISO 19091 use cases
Correct! SAE J2735 defines the message contents to fulfill requirements derived from the use cases in ISO 19091.

b) Fulfill requirements found in the SAE J2735 standard
Incorrect. SAE J2735 is used to fulfill requirements in ISO 19091. SAE J2735 does not contain requirements.

c) Directly satisfy the user needs derived from the ISO 19091 use cases
Incorrect. There are no user needs in ISO 19091 and SAE J2735 is used to fulfill requirements, not satisfy user needs.

d) Directly satisfy the user needs in the SAE J2735 standard
Incorrect. SAE J2735 defines a message set and does not identify user needs.

Slide 51:

Learning Objectives

• Identify benefits of standardization for agencies, system developers, and suppliers
• Describe the scope of ISO TS 19091 Standard
• Describe the use cases addressed by ISO TS 19091 Standard
• Explain the relationship between ISO TS 19091 and SAE J2735
• Applying ISO TS 19091 Standard content to your project

Slide 52:

Learning Objective 5

• Applying ISO TS 19091 Standard content to your project

Slide 53:

Use Case to Requirements Matrix

Provides traceability from use cases to requirements.

• Organized by use case operational type (PR, SA, MS), then by specific use case
• Indicates for each use case whether a requirement is:
  • Mandatory (M or M.#)
  • Optional (O or O.#)
  • Conditional (C)
  • Not Applicable (N/A)
  • Excluded or Prohibited (X)
  • Regional selection (REG:)
  • Internal RSE <-> TSC (Traffic Signal Controller) use only with 'x' replaced by the status symbols listed above

Slide 54:

Use Case to Requirements Matrix

SA2: Red Light Violation Warning

Table B.5 — Safety related use case to requirements

(Extended Text Description: This slide contains a table, entitled "Table B.5 - Safety related use case to requirements", with the column headings "Requirements" and "Safety related use cases." Under "Requirements" are two columns with the heading "ID" and "Title", respectively. Under "Safety related use cases to requirements" are three columns with the heading "SA2", "SA3", and "SA4." There are several rows in the table, each row with a (section) number under "ID", the title of the requirement under "Title", and either the letter "M", "X", "O", or "REG:M" under "SA2", "SA3", and "SA4." In column "SA2," all rows with an "M" in this column have a red circle around the "M," all rows with an "X" in the column have a green circle around the "X," and all rows with an "O" in the column are circled in blue. The complete table contents are below:

Requirements		Safety related use cases
ID	Title	SA2	SA3	SA4
65.1	Broadcast Area Geometries	M	M	M
65.2	Broadcast Roadway Geometries - Message Identifier	M	M	M
65.3	Broadcast Intersection - Identifier	M	M	M
65.4	Broadcast Intersection - Reference Point	M	M	M
65.5	Broadcast Intersection - Lane/Approach Default Width	M	M	M
65.6	Broadcast Intersection - Egress Lanes	X	X	REG:M
65.7	Broadcast Intersection - Approach Lanes	M	M	M
6.5.B	Broadcast Intersection - Lane/Approach Number	M	M	M
6.5.9	Broadcast Intersection - Lane/Approach Centerline Coordinates	M	M	M
65.10	Broadcast Intersection - Vehicle Lane/Approach Maneuvers	M	M	M
65.11	Broadcast Intersection - Pedestrian Lane/Approach Maneuvers	X	X	0
65.12	Broadcast Intersection - Special Lane/Approach Maneuvers	X	X	0
65.13	Broadcast Intersection - Version Identifier	0	X	0
65.14	Broadcast Intersection - Crossings	X	X	0
65.15	Broadcast Intersection - Lane/Approach Width	0	0	0
65.16	Broadcast Intersection - Node Lane/Approach Width	0	0	0

)

Reference: ISO TS 19091 Table B.5

Slide 55:

Requirements Traceability Matrix

Provides traceability between requirements and design:

• Dialogs
• Messages
• Data Frames
• Data Elements

• Used to determine the design of the communications for the system
• Used by a tester to determine what requirements need to be verified, and help design the test cases

Slide 56:

Requirements Traceability Matrix

• Dialogs
  • For ISO TS 19091, the dialogs consists of broadcast messages (See Section 5.1.3)
    • A device broadcasts the message content to all entities within range
  • The sequence that messages are broadcasted can be found in the use cases
  • Dialogs mostly handled by the DSRC communications stack, but may be other wireless communications technologies (3G, 4G, LTE, etc.)
• Message sets, data frames and data elements are defined in SAE J2735.

Slide 57:

Requirements Traceability Matrix

(Extended Text Description: This slide contains a table with 1 header row, 6 rows of data and 7 columns. The column headings are "Rqmt ID", "Requirement Title", "Msg", "Parent Identifier", "Parent type", "Identifier", and "Identifier type." Rows 4, 5, and 6 have red circles around the information. The complete table contents are below:

Rqmt ID	Requirement Title	Msg	Parent Identifier	Parent type	Identifier	Identifier type
6.5.1	Broadcast area geometries	MAP	N/A	N/A	Message Types	MapData
6.5.2	Broadcast roadway geometries - message identifier	MAP	MSG_MapData	MapData	msglssue Revision	MsgCount
6.5.3	Broadcast intersection -identifier	MAP	intersections	Intersection Geometry	id	Intersection ReferenceID
6.5.4	Broadcast intersection -reference point	MAP	refPoint	Position3D	lat	Latitude
6.5.4	Broadcast intersection -reference point	MAP	refPoint	Position3D	long	Longitude
6.5.4	Broadcast intersection -reference point	MAP	refPoint	Position3D	elevation	Elevation

)

Reference: ISO TS 19091 Table C.1

Slide 58:

Requirements Traceability Matrix

Using the RTM

RTM uses the same key defined in the Use Case Requirements Matrix

• Mandatory (M or M.#)
• Optional (O or O.#)
• Conditional (C)
• Not Applicable (N/A)
• Excluded or Prohibited (X)

(Extended Text Description: This slide contains a table with 2 header rows, 3 data rows, and 7 columns. There are 3 headings, "Requirement", "Design", and "Project Implementation." Below "Requirement" are two columns, "ID" and "Title." Below "Design" is one column "Identifier Type." Below "Project Implementation" are three columns, "Conformance", "Support / Project Rqmt", and "Additional Rqmt." Under the "Support / Project Rqmt" column, the word "Yes" is circled in red in the first two rows, and the word "No" is circled in red in the third row. The complete table contents are below:

Requirement		Design	Project Implementation
ID	Title	Identifier Type	Conformance	Support / Project Rqmt	Additional rqmt
6.5.4	Broadcast intersection - reference point	Latitude	M	Yes
6.5.4	Broadcast intersection - reference point	Longitude	M	Yes
6.5.4	Broadcast intersection - reference point	Elevation	O	Yes / No

)

Reference: ISO TS 19091 Table C.1

Slide 59:

Requirements Traceability Matrix

Using the RTM

(Extended Text Description: This slide contains a table with 1 header row, 4 rows of data and 6 columns. The column headings are "Rqmt ID", "Requirement Title", "Identifier", "Conformance", "Support / Project Rqmt", and "Additional Reqt." Under the "Support / Project Rqmt" the word "Yes" is circled in red in the first, second, and fourth rows, and the word "No" is circled in red in the third row. Under the "Additional Reqt" column, the words "1 Hz" in the first and fourth rows are in red to indicate the words was entered by a project specification writer. Also under the "Additional Reqt" column, the words "10 Hz" in the second row are in red to indicate the words was entered by a project specification writer. The complete table contents are below:

Rqmt ID	Requirement Title	Identifier	Conformance	Support / Project Rqmt	Additional Reqt
6.15.1	Minimum transmission rate - broadcast roadway geometrics	N/A	O	Yes / No	Rate of Hz 1 Hz
6.15.2	Maximum transmission rate - broadcast roadway geometrics	N/A	O	Yes / No	Rate of Hz 10 Hz
6.15.3	Default transmission rate - broadcast roadway geometrics	N/A	O	Yes / No	Rate of Hz
6.16.1	Minimum transmission rate -GNSS augmentation details broadcasts	N/A	O	Yes / No	Rate of Hz 1 Hz

)

Reference: ISO TS 19091 Table C.1

Slide 60:

Application of Annexes E, F, & G

Regional Extensions

Annexes E, F, G describe different profiles for J2735 for use in 3 different international regions

• Annex E : North America
• Annex F: Japan
• Annex G: Europe

• Regional specific requirements appear in the Use Case to Requirements Matrix
• Annex D describes the extension mechanisms for SAE J2735

Slide 61:

Application of Annexes E, F, & G

Annex E

Use cases, requirements, and traceability matrices for North America

• No additional requirements defined for the MAP, SRM or SSM messages
• SPAT message - Defines two additional optional data frames and data elements
  • Provide an indication that a pedestrian or bicycle call has been requested for a movement through the intersection
  • Provide support for the current signal state of a special lane (e.g., tracked) at the intersection

Slide 62:

Conformance Statement

An implementation is conformant with ISO TS 19091 when:

• The implementation's data content shall fulfill the mandatory and selected optional requirements as identified in the requirements traceability matrix (Annex C) or as defined in the selected annexes

AND

Slide 63:

Conformance Statement

• The implementation's message structure fulfills the requirements of the selected annex

AND

• To conform to a requirement in this technical specification, a system or device interface shall implement all data elements traced from that requirement (and in the order specified in the technical specification). To be consistent with a requirement, a system or device interface shall be able to fulfill the requirement using only messages, data frames, and data elements that (the) conforming system or device interface is required to support

Slide 64:

Example

Transit Signal Priority

• First, go to Annex A and examine the Use Case Table
  • Complete list of use cases covered in ISO TS 19091
  • Select appropriate use cases for deployment
• For our example, assume a transit signal priority application

(Extended Text Description: This slide has a photograph of an intersection, with four traffic signal heads and a transit vehicle. The bus was captured while moving and shows a motion blur following it, which makes the bus look like it was traveling at a high velocity.)

Reference: ISO TS 19091 Table A.1

Slide 65:

Example

Transit Signal Priority

Table A.1 — Table of identified use cases

(Extended Text Description: This slide shows a table of identified use cases for transit signal priority with an "ID" column and a "Title" column. The first row reads across "PR1" in the ID column and "A.2-PR1: Localized public transport signal priority (TSP)" in the Title column. This whole row has a dark red box around it. The complete table contents are below:

ID	Title
PR1	A.2 — PR1: Localized public transport signal priority [TSP]
PRl-a	A.3 — PRl-a: Localized public transport signal priority - near side stop
PR2	A.4 — PR2: Public transport signal priority along an arterial [group of intersections)
PR3	A.5 — PR3: Localized freight signal priority
PR3-a	A.6 — PR3-a: Localized freight signal priority with a platoon
PR3-b	A.7 — PR3-b: Arterial freight signal priority for a platoon
PR4	A.8 — PR4: Emergency vehicle single or multiple vehicles [normal power PSOBE]
PR5	A.9 — PR5: Emergency vehicle single or multiple vehicles [high power PSOBE]
PR6	A. 10 — PR6: Mixed emergency vehicle and other priority eligible vehicles

)

Reference: ISO TS 19091 Table A.1

Slide 66:

Example

Transit Signal Priority

Table A.2 — PR1: Localized public transport signal priority (TSP)

(Extended Text Description: This slide contains a snapshot of the PR1: Localized public transport signal priority (TSP) use case from ISO TS 19091. The use case has two columns, the first column indicating the type of information, and the second column containing the specifics of the use case. The types of information are, starting from the first row, "Use Case Name", "Category", "Infrastructure Role", "Short Description", "Goal", "Constraints", "Geographic Scope", and "Actors. Constraints and Actors are circled in red. The complete table contents are below:

Use Case Name	Basic TSP Scenario - Single Public Transport Vehicle at One Signalized Intersection
Category	Mobility-
Infrastructure Role	Data Receiver, Traffic Signal Control, Data Transmitter
Short Description	This use case describes the basic priority control for connected Public Transport vehicles
Goal	Improved Public Transport efficiency and reliability
Constraints	Use of DSRC or other medium that will meet the performance requirements for this use case (the RSE and OBE include radio devices that operate in the medium used) Alternate: Wide area broadband communications is available for the public transport vehicle to indicate its TSP request via an alternate media than DSRC through Back-office Processing Center (BOPC). (Data flow #5 supports that situation)
Geographic Scope	Localized to a specific intersection
Actors	Public Transport Vehicle Equipped with On-board Equipment [OBE] Road Side Equipment (RSE) & Traffic Signal Controller (TSC) Alternate: Traffic Management Central System (BOPC).

)

Slide 67:

Example

Use Case to Requirements Matrix

PR1: Localized Public Transport Signal Priority (TSP)

(Extended Text Description: This slide is a fragment from the use case to requirements matrix. Under column "PR1" are five rows with a single letter in each row. There is a red circle around each letter. The complete table contents are below:

Requirements		Use Cases
ID	Title	PR1	PR1-a
6.1.1	Broadcast public safety vehicle information	M	M
6.1.2	Broadcast emergency response indication	X	X
6.2.1	Transmit pre-empt request	O	O
6.2.2	Request signal pre-empt - message identifier	O	O
6.2.4	Request signal pre-empt - intersection identifier	O	O

)

Slide 68:

Example

Requirements Traceability Matrix

(Extended Text Description: CHECK WITH SLIDE 69This slide contains a Requirements Traceability Matrix, with 2 header rows, 3 data rows, and 7 columns. There are 3 headings, "Requirement", "Design", and "Project Implementation." Below "Requirement" are two columns, "ID" and "Title." Below "Design" is one column "Identifier Type." Below "Project Implementation" are three columns, "Conformance", "Support / Project Rqmt", and "Additional Rqmt." Under the "Identifier Type" column, the word "BasicSafetyMessage" in the first row is circled in red as part of the slide animation. Under the "Conformance" column, the word "M.4(1)" in the first and second row is circled in red as part of the slide animation. Under the "Support / Project Rqmt" column, the word "Yes" is circled in red in the first row, and the word "No" is circled in red in the second to fourth rows. The complete table contents are below:

Requirement		Design
ID	Title	Msg	Parent identifier	Parent type	Identifier	Identifier type
6.1.1	Broadcast public safety vehicle information (Safe1)	BSM (P1)	N/A	N/A	MessageTypes	BasicSafety Message
6.1.1	Broadcast public safety vehicle information (Safe2)	CAM	N/A	N/A	CAM	CoopAwareness
6.1.2	Broadcast emergency response indication	BSM (P2)	supplemental	Supplemen talVehicleExtensions	classDetails	VehicleClassification

)

Slide 69:

Example

Requirements Traceability Matrix

(Extended Text Description: This slide contains a Requirements Traceability Matrix, with 2 header rows, 3 data rows, and 7 columns. There are 3 headings, "Requirement", "Design", and "Project Implementation." Below "Requirement" are two columns, "ID" and "Title." Below "Design" is one column "Identifier Type." Below "Project Implementation" are three columns, "Conformance", "Support / Project Rqmt", and "Additional Rqmt." Under the "Identifier Type" column, the word "BasicSafetyMessage" in the first row is circled in red as part of the slide animation. Under the "Conformance" column, the word "M.4(1)" in the first and second row is circled in red as part of the slide animation. Under the "Support / Project Rqmt" column, the word "Yes" is circled in red in the first row, and the word "No" is circled in red in the second to fourth rows. The complete table contents are below:

Requirement		Design	Project Implementation
ID	Title	Identifier Type	Conformance	Support / Project Rqmt	Additional Reqt
6.1.1	Broadcast public safety vehicle information (Safe1)	BasicSafetyMessage	M.4(1)	Yes / No
6.1.1	Broadcast public safety vehicle information (Safe2)	CoopAwareness	M.4(1)	Yes / No
6.1.2	Broadcast emergency response indication <Safe1>	VehicleClassification	M	Yes / No
6.1.2	Broadcast emergency response indication	LightbarlnUse	M	Yes / No

)

Slide 70:

Example

Requirements Traceability Matrix

(Extended Text Description: This slide contains a Requirements Traceability Matrix, with 2 header rows, 3 data rows, and 7 columns. There are 3 headings, "Requirement", "Design", and "Project Implementation." Below "Requirement" are two columns, "ID" and "Title." Below "Design" is one column "Identifier Type." Below "Project Implementation" are three columns, "Conformance", "Support / Project Rqmt", and "Additional Rqmt." Under the "Support / Project Rqmt" column, the word "Yes" is circled in red in the first to third rows, and the word "No" is circled in red in the fourth to fifth rows. The complete table contents are below:

Requirement		Design	Project Implementation
ID	Title	Identifier Type	Conformance	Support / Project Rqmt	Additional Reqt
6.2.5	Request signal preempt - approach lane	lntersectionAccessPoint	M	Yes
6.2.6	Request signal preempt - egress lane	lntersectionAccessPoint	O	Yes / No
6.2.7	Request signal preempt - vehicle class	BasicVehicleRole	O	Yes / No
6.2.7	Request signal preempt - vehicle class	RequestSubRole	O	Yes / No
6.2.7	Request signal preempt - vehicle class	RequestlmportanceLevel	O	Yes / No

)

Reference: ISO TS 19091 Table C.1

Slide 71:

Example

Requirements Traceability Matrix

Assuming DSRC

(Extended Text Description: This slide contains a table, the complete contents are below. The field values in Additional Reqt column are highlighted in red:

Rqmt ID	Requirement Title	Message	Conformance	Support / Project Rqmt	Additional Reqt
6.14.1	Maximum transmission rate - request signal preferential treatment	SRM	O	Yes / No	Rate of 1 Hz
6.14.2	Maximum response time - request signal preferential treatment	SSM	O	Yes / No	100 ms
6.14.3	Minimum transmission rate - signal status message	SSM	O	Yes / No	Rate of 1 Hz
6.14.4	Minimum transmission period - signal status message	SSM	O	Yes / No	Period of 10 s

)

Reference: ISO TS 19091 Table C.1

Slide 72:

Slide 73:

Question

Which matrices allow a system designer to select system requirements based on use cases?

Answer Choices

1. Needs to Requirements Traceability Matrix
2. Requirements Traceability Matrix
3. Use Case to Requirements Traceability
4. Test Case to Requirements Traceability Matrix

Slide 74:

Review of Answers

a) Needs to Requirements Traceability Matrix
Incorrect. There is no NRTM included in ISO TS 19091.

b) Requirements Traceability Matrix
Incorrect. The RTM traces requirements to design.

c) Use Case to Requirements Traceability
Correct! The Use Case to Requirements Traceability traces requirements to use cases and allows a system designer to select requirements for a deployment.

d) Test Case to Requirements Traceability Matrix
Incorrect. There is no TCRTM in ISO TS 19091.

Slide 75:

Module Summary

• Identify benefits of standardization for agencies, system developers, and suppliers
• Describe the scope of ISO TS 19091 Standard
• Describe the use cases addressed by ISO TS 19091 Standard
• Explain the relationship between ISO TS 19091 and SAE J2735
• Applying ISO TS 19091 Standard content to your project

Slide 76:

We Have Now Completed the CV Curriculum

Module I261:
Vehicle-to-Infrastructure (V2I) ITS Standards for Project Managers

Module I262:
Vehicle-to-Vehicle (V2V) ITS Standards for Project Managers

Module CV271:
Using the ISO TS 19091 Standard to Implement V2I Intersection Applications Introduction

Slide 77:

Next Course Module

Module CV-T160: Connected Vehicles Certification Testing Introduction

Concepts taught in next module (Learning Objectives):

1. Identify key elements of ATC 5201 standard equipment for testing documentation
2. Describe within the context of a systems engineering lifecycle the role of a test plan and the testing to be undertaken
3. Describe the application of good testing documentation for transportation controller equipment based on the ATC 5201 v06 standard
4. Describe the testing of ATC using a sample testing documentation

Slide 78:

Thank you for completing this module.

Feedback

Please use the Feedback link below to provide us with your thoughts and comments about the value of the training.

Thank you!