Module 62 - CV273
CV273: Introduction to SPaT / MAP Messages
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:
Slide 2:
Welcome
Ken Leonard, Director
ITS Joint Program Office
Ken.Leonard@dot.gov
ITS PCB Home
Slide 3:
Module CV273:
Introduction to SPaT / MAP Messages
Source: US Department of Transportation
Slide 4:
Instructor
Patrick Chan, P.E.
Senior Technical Staff
Consensus Systems Technologies
Flushing, NY, U.S.A.
Co-Author:
Anu J. (AJ) Lahiri
Technical Staff
Consensus Systems Technologies
Slide 5:
Learning Objectives
- Describe the scope of the SAE J2735 Standard
- Describe the SPaT Message
- Describe the MAP Message
- Implementation Considerations
Slide 6:
Learning Objective 1
Describe the scope of SAE J2735 Standard
Slide 7:
What is a Connected Vehicle Environment, in Particular V2I Environment Transportation Challenges
Source: US Department of Transportation, 2019 Urban Mobility Report, TTI
Slide 8:
What is a Connected Vehicle Environment, in Particular a V2I Environment
The CV Environment
Source: US Department of Transportation
CV environment consists of:
- Connected vehicles
- Connected individuals
- Connected infrastructure
CV Communications
- Wireless
-
Mixture of
- Short-range communications
- Remote communications
Slide 9:
What is a Connected Vehicle Environment, in Particular a V2I Environment
Source: US Department of Transportation
Slide 10:
What is a Connected Vehicle Environment, in particular a V2I Environment
Source: US Department of Transportation
Slide 11:
What is the Need for SPaT and MAP Information?
- Signal Phase and Timing (SPaT) data and MAP data
Slide 12:
What is the Need for SPaT and MAP Information?
-
Signal Phase and Timing (SPaT) data are used by applications to generate:
- Pedestrian warnings: allowed pedestrian movements
- Driver warnings: potential red light violations, potential pedestrian conflicts, allowed vehicle movements
- Driver advisories: suggested travel speeds (for mobility and environmental purposes)
Source: US Department of Transportation
Slide 13:
What is the Need for SPaT and MAP Information?
-
MAP data can be used by applications to provide benefits at intersections or roadway segments
- Driver warnings: sharp curves, allowable movements
- Driver advisories: location of lanes
- Pedestrian advisories: location of crosswalks
- Required to link SPaT data (currently allowable movements) with lanes
Slide 14:
What is the Need for SPaT and MAP Information?
- Applications:
- Red Light Violation Warning (RLVW): warnings to travelers for impending red light violations
- Pedestrian in Signalized Crosswalk Warning: warnings to transit operators when pedestrians are in the intended path of the bus
- Mobile Accessible Pedestrian Signal System (PED-SIG): automated calls from a visually impaired pedestrian and cues to safely navigate the crosswalk
- Eco-Approach and Departure at Signalized Intersections: recommend speed trajectories as vehicles approach and depart the intersection
Source: US Department of Transportation
Slide 15:
What is the Scope and Purpose of SAE J2735?
-
A data dictionary for the CV environment.
- Defines messages and data elements
- Includes vehicle kinematic information, position correction information, traveler information
Source: SAE International
Slide 16:
What is the Scope and Purpose of SAE J2735?
-
Signal Phase and Timing (SPaT)
-
Provides signal phase and timing data from one or more traffic signal controllers
- Provides dynamic data
- General controller status
- What movements (by lane) are currently allowed and when will the movement state is likely to end
- Tied to the MAP data message
Source: Applied Information
Slide 17:
What is the Scope and Purpose of SAE J2735?
-
MAP Data Message
-
Provides static roadway geometric information
- Lane widths, path, location
- Lane types - vehicle lanes, crosswalks, barriers
- Lane attributes - allowable movements, safe landing zones for the visually impaired
- Indicates what part of the SPaT message applies to the traveler's intended movement
Slide 18:
What is the Scope and Purpose of SAE J2735?
-
Signal Request / Signal Status Message (SRM/SSM)
- Provides signal priority/preemption request and status messages
- Uses approach and desired egress lane, and estimated times
- Must be configured to work reliably and with security protections
Source: US Department of Transportation
Slide 19:
What is the Scope and Purpose of SAE J2735?
-
Basic Safety Message
- Broadcasted by vehicles about their kinematics and sensor information
-
Traveler Information Message
- General traveler information broadcasted from the infrastructure to travelers
-
NMEA Corrections and RTCM Corrections
- Contains data used to calibrate GNSS (e.g., GPS) for vehicles and mobile devices to increase the absolute and relative location accuracy.
Slide 20:
Slide 21:
Question
Which of the following user needs for a signalized intersection is NOT addressed with SPaT data?
Answer Choices
- Receive currently allowed vehicle movements
- Receive lane location descriptions
- Receive suggested vehicle speeds
- Receive estimated times when signal indications will change
Slide 22:
Review of Answers
a) Receive currently allowed vehicle movements
Incorrect.
This information is supported by SPaT data
b) Receive lane location descriptions
Correct! Lane location descriptions are provided by MAP message data
c) Receive suggested vehicle speeds
Incorrect. This information is supported by SPaT data
d) Receive estimated times when signal indications will change
Incorrect. This information is supported by SPaT data
Slide 23:
Learning Objective
Describe the SPaT Message
Slide 24:
What is the Structure of the SPaT Message?
-
Previously described WHY SPaT data is needed
- Support in-vehicle and individual applications
- Next several slides describes WHAT data is provided in SAE J2735_201603
Slide 25:
What is the Structure of the SPaT Message?
Slide 26:
What is the Structure of the SPaT Message?
- messageId. DE_DSRCmsgID = 19
- timeStamp. Number of elapsed minutes in the year
- name. Name of the group of intersections for testing purposes
- intersections. Data for each intersection
- regional. Regional extensions
Slide 27:
What is the Structure of the SPaT Message?
-
Each SPaT message can provide signal phase and timing and dynamic information for multiple intersections.
- Useful in dense urban areas.
Slide 28:
What are the Mandatory Elements of the SPaT Message?
- region. Identifier of the responsible agency
- id. Regionally unique intersection identifier
Slide 29:
What are the Mandatory Elements of the SPaT Message?
-
revision is message counter. Increments:
- Every time message is transmitted, OR
- When the message content changes
- status is the general status of the controller, e.g., adaptive, priority, preempt, flash, no valid SPaT data
Slide 30:
What are the Mandatory Elements of the SPaT Message?
-
Status. Example potential implementation issues:
-
Definition of providing signal priority.
- When request is received?
- When modifications are made to the timing?
-
Definition of preempt mode.
- When the preempt request is received?
- Does it include the preempt exit phases?
-
Definition of recent MAP update.
- Within the last week? Last month?
- Some status values may be defined in other standards, e.g., NTCIP 1202 v03
Slide 31:
What are the Mandatory Elements of the SPaT Message?
- states provide information for each movement at the intersection
- signalGroup is an identifier tying the SPaT data to a specific lane-to-lane movement in the MAP message
Slide 32:
What are the Mandatory Elements of the SPaT Message?
- eventState. Unavailable, dark (signal indication is dark), stop then proceed (e.g., flashing red, red turn on red), stop and remain, permissive movement, protected movement, permissive clearance, protected clearance, proceed with caution (e.g., flashing yellow)
Slide 33:
What are the Mandatory Elements of the SPaT Message?
Slide 34:
What are the Mandatory Elements of the SPaT Message?
-
Summary
- messageId
-
Intersection (optional)
- id (of the intersection)
- revision (counter)
- status (of the controller)
-
state
- signalGroup (identifier of the movement)
- eventState (signal state of the movement)
Slide 35:
What are the Optional Elements of the SPaT Message?
-
Enabled (revocable) lanes
- List of revocable lanes that are active
- Must be defined as a revocable lane in the MAP message
Slide 36:
What are the Optional Elements of the SPaT Message?
Lane 201, 203, 211, 205 are revocable lanes
- Revocable lanes may be mutually exclusive
- Lanes 201 and 211 are reversible lanes
- Lane 203 is an active lane and Lane 205 is a parking lane
Slide 37:
What are the Optional Elements of the SPaT Message?
-
timing. Measured in tenths of a second in the current or next hour.
- Time OF change, not time TO change.
- NOT valid if in preempt mode
-
minEndTime. Earliest time the eventState may change (mandatory)
- How to interpret for actuated signals if the minEndTime has already passed?
- startTime. Ambiguous, could be past or future
Slide 38:
What are the Optional Elements of the SPaT Message?
-
timing. (continued)
- maxEndTime. Latest time the eventState may change
- likelyTime. Most likely time the eventState will change
- confidence. Statistical probability of the likelyTime
- nextTime. When the current eventState will likely occur again
Slide 39:
What are the Optional Elements of the SPaT Message?
(Extended Text Description: Author's relevant description for this figure: This slide entitled "What are the optional elements of the SPaT message?" fully consists of a chart that shows the values for the states data frame for the SPaT message for specific timepoints along the x-axis within a full signal cycle. At the top are two color bars (red, green, yellow) showing the signal indication for main street green and the cross street as time progresses through the cycle length. Below is text indicating timestamps at which data was recorded. Data was recorded at:
- 10:59:58:0 (all-red)
- 11:00:00:0 (two seconds later, beginning of main street green)
- 11:00:06:0 (six seconds later)
- 11:00:12:0 (six seconds later, end of minimum green for main street green)
- 11:00:24:0 (12 seconds later, end of maximum green for main street green)
- 11:00:25:5 (1.5 seconds later, halfway through the yellow clearance interval)
- 11:00:27:0 (1.5 seconds later, beginning of the red clearance interval)
- 11:00:29:0 (two seconds later, beginning of cross street green)
- 11:00:36:0 (seven seconds later, end of minimum green for cross street green)
- 11:00:45:0 (nine seconds later, end of maximum green for cross street green)
- 11:00:48:0 (three seconds later, end of yellow clearance interval)
Below the time points is a chart with data values for each timestamp. The first row contains the timeStamp (in tenths of a second within the current hour) as it would appear in the SPaT message. Below this row is data values for each signal group - signalGroup 2 for main street and signalGroup 4 for the cross street. The following data is recorded:
- startTime (in tenths of a second within the current hour)
- minEndTime (in tenths of a second within the current or next hour)
- maxEndTime (in tenths of a second within the current or next hour)
- likelyEndTime (in tenths of a second within the current or next hour)
- nextTime (in tenths of a second within the current or next hour)
- eventState (an integer)
)
Slide 40:
What are the Optional Elements of the SPaT Message?
-
Advisory speeds for a movement
- The advisory speed and distance from the stop bar the advisory speed is good for
- Specify the vehicle class the advisory is valid for
Slide 41:
What are the Optional Elements of the SPaT Message?
-
Information for a specific lane movements
- Current queue length for this movement
- Distance from the stop bar within which vehicles can expect to clear the intersection
- If a vehicle should stop at the stop bar
- If a conflicting pedestrian or bicycle in the path is detected
- Requires a MAP message
Slide 42:
What are the Optional Elements of the SPaT Message?
-
Optional elements are optional as defined by the SAE J2735 standard
- Mandatory are minimum elements based on the experience of the standards committee
-
Optional elements should be broadcasted IF:
- Required by a regulation or regulatory agency
-
Required by another standard or specification
- E.g., the Connected Signalized Intersection project
Slide 43:
What are the Optional Elements of the SPaT Message?
-
Optional elements should be broadcasted if needed to support a desired application
- To support a basic Red Light Violation application, the mandatory elements are sufficient
- To support the Eco-Approach and Departure at Signalized Intersections application, the advisory speeds for an approach towards the intersection is needed
- To support phase time remaining in an in-vehicle application, the timing information is needed
Slide 44:
Slide 45:
Question
Signal timing information for how many intersections can be included in a single SPaT message?
Answer Choices
- Only one signalized intersection
- Only one signalized and one non-signalized intersection
- Up to two signalized intersections along an arterial
- Up to 32 signalized intersections
Slide 46:
Review of Answers
a) Only one signalized intersection
Incorrect.
b) One signalized and one non-signalized intersection
Incorrect.
c) Up to two signalized intersections along an arterial
Incorrect.
d) Up to 32 signalized intersections
Correct! A SPaT message can provide signal timing information for up to 32 signalized intersections
Slide 47:
Learning Objective 3
Describe the MAP message
Slide 48:
What is the Structure of the MAP Message?
-
MAP messages provide static geographic road information
- descriptions of lanes and lane types
-
Each MAP message can provide roadway geometric information for:
- Up to 32 intersections, and
- Up to 32 road segments
Slide 49:
What is the Structure of the MAP Message?
- messageId. DE_DSRCmsgID = 18
- timestamp. Number of elapsed minutes in the year
- msgIssueRevision. Message counter indicating contents changed
- layerType. Type of map information, e.g., general, curve, intersection, roadway segment
- layerId. Layer identifier
Slide 50:
What is the Structure of the MAP Message?
- intersections. MAP data for intersections
- roadSegments. MAP data for road segments
- dataParameters. Metadata about the MAP contents
- restrictionList. List of potential user class restrictions
Slide 51:
What are the Mandatory Elements of a MAP Message?
- id. Identifier of the responsible agency (optional) + regionally unique identifier for the intersection
- revision. Message counter to indicate if the road geometry for the intersection has changed
- refpoint. Geographic reference (anchor) point for this intersection. Latitude-Longitude. Elevation is optional.
- laneSet. Data describing a lane
Slide 52:
What are the Mandatory Elements of a MAP Message?
- laneId. A lane identifier unique within the intersection
- laneAttributes. A data frame containing data about the lane characteristics
Slide 53:
What are the Mandatory Elements of a MAP Message?
- directionalUse. Direction of travel in the lane
- sharewith. Indicates the presence of another user type that has equal rights to use the lane
-
laneType. Defines the type of lane. Valid values include vehicle lane, crosswalk, bicycle lane, sidewalk, (physical) barrier, striped lane, tracked vehicle and parking lane.
- Also used to indicate if it is revocable lane. Used by the SPaT message
Slide 54:
What are the Mandatory Elements of a MAP Message?
-
nodeList. Sequence of signed offset node points representing the centerline of the lane. CHOICE of:
- nodes. A sequence of 2 to 63 node points defining the centerline of the lane
- computed. A lane that has similar (lane) attributes as another lane
Slide 55:
What are the Mandatory Elements of a MAP Message?
-
delta. Each node is an X-Y offset from the previous node, in units of 1 centimeter.
- Each node could also be a latitude-longitude geographic coordinate but not generally used
- The first node point is the offset from the reference point and typically at the stopline.
- With lane width represents the lane as a polygon
Slide 56:
What are the Mandatory Elements of a MAP Message?
Source: New York City Connected Vehicle Pilot
Slide 57:
What are the Mandatory Elements of a MAP Message?
- referencedLaneId. Identifier of the lane that this computed lane is based on.
- offsetXaxis / offsetYaxis. Offset of the first node of the computed lane from the referenced lane along the x-axis / y-axis
Slide 58:
What are the Mandatory Elements of a MAP Message?
Source: New York City Connected Vehicle Pilot
Slide 59:
What are the Mandatory Elements of a MAP Message?
-
Summary
- messageId
- msgIssueRevision (of the message)
- id (of each intersection)
- refPoint (of each intersection)
- revision (counter for each intersection)
-
For each lane:
- laneId
- laneAttributes
- nodes (sequence of node offsets)
Slide 60:
What are the Optional Elements of a MAP Message?
-
speedLimits. Regulatory information for a lane or set of lanes
- type. Type of regulatory speed limit.
- speed. Velocity of the object (in 0.02 m/s)
- Metadata about the map contents
- User class restrictions for lane/movement restrictions (e.g., transit only, emissions compliant, height compliant, pedestrians only)
Slide 61:
What are the Optional Elements of a MAP Message?
-
maneuvers. Allowed maneuvers for the lane
- connectingLane. Lane identifier that a maneuver connects to
- remoteIntersection. Identifier of another intersection that describes the connecting lane
- signalGroup. Identifier of the movement. Used to tie to the SPaT message.
- userClass. Identifies the lane/movement restrictions
Slide 62:
What are the Optional Elements of a MAP Message?
-
Node information. Presents the attributes at a node that describes the path of a lane.
- localNode. Defines up to 8 attributes for this node point. E.g., fire hydrant, traffic island for crosswalks
- disabled / enabled. Defines up to 8 attributes for a segment. E.g., transit stop, parking zone, bike lane on left, rumble strip present
- dWidth. Linear taper in the lane width from the previous node
- dElevation. Linear taper in the lane elevation from the previous node
Slide 63:
What are the Optional Elements of a MAP Message?
-
Computed Lane
- rotateXY. Rotation of the initial node point
- scaleXaxis / scaleYaxis. Defines expansion or contraction of the computed lane along the X-axis / Y-axis
Slide 64:
What are the Optional Elements of a MAP Message?
- Optional elements are optional as defined by the standard
- Optional elements may be required by a regulation, another standard or a specification
-
Optional elements should be broadcasted if needed to support an application
- Maneuver information, e.g., SignalGroupID data, is needed to support the SPaT message if broadcast
- Location of safety zones (e.g., traffic islands) for pedestrian safety applications may be needed.
Slide 65:
Slide 66:
Question
Which of the following attributes for a lane is included in a MAP message?
Answer Choices
- The centerline locations of a lane
- The permitted direction of travel of the lane
- The permitted vehicle types that may use the lane
- All of the above
Slide 67:
Review of Answers
a) The centerline locations of a lane
True. Nodes are used to define the centerline of a lane.
b) The permitted direction of travel of the lane
True. The permitted direction of travel of the lane may be provided in a MAP message.
c) The permitted vehicle types that may use the lane
True. Vehicle class restrictions may be included in a MAP message.
d) All of the above
Correct! All of the above are true.
Slide 68:
Learning Objective 4
Implementation Considerations
Slide 69:
ISO TS 19091
-
Previously described WHY SPaT and MAP data is needed
- Support safety, mobility and environmental applications
- Previously describes WHAT data is provided by the SPaT and MAP messages
-
Next slides describe WHEN, WHERE, and HOW the data is provided to support interoperability
- Standards help answer some questions
- May depend on the application
Slide 70:
ISO TS 19091
-
ISO TS 19091 - Intelligent transport systems - Cooperative ITS - Using V2I and I2V communications for applications related to signalized intersections
-
Defines dialogs and HOW to exchange messages, data structures, and data elements between roadside units and travelers to support signalized intersection applications
- Procure, implement and test in a consistent manner
- Used in Europe
- May be used as guidance in North America
Slide 71:
ISO TS 19091
-
The V2I applications addressed 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 for the applications
-
Use case types
- Priority/Preemption applications
- Safety applications
- Mobility/Sustainability applications
Slide 72:
ISO TS 19091
- Lists requirements describing the details of that data
-
Deployments that conform to ISO 19091 would build to the same requirements - helps ensure interoperability
- Functional Requirements
- Performance Requirements (WHEN)
Slide 73:
ISO TS 19091
-
Defines what specific SAE J2735 messages, data frames or data elements are used to fulfill each functional requirement in ISO TS 19091.
- SPaT
- MAP
- Basic Safety Messages
- NMEA/RTCM
- SRM/SSM
- See Module CV271 - Using the ISO TS 19091 Standard to Implement V2I Intersection Applications Introduction
Slide 74:
SAE J2945/x Family of Standards
-
SAE J2945/x Family of Standards identify the information and performance requirements for applications using SAE J2735 messages
- How often a message is sent (minimum, typical, maximum)
- Minimum quality requirements
- Each document identifies the minimum requirements or recommended practices for specific applications.
Slide 75:
SAE J2945/x Family of Standards
-
SAE J2945_2017012 - Dedicated Short Range Communications (DSRC) Systems Engineering Process Guidance for SAE J2945/x Documents and Common Design Concepts
- Also known as J2945/0, defines common requirements for connected vehicle applications
- Includes systems engineering content (Concept of Operations, requirements, message exchanges, and message content) for the family of standards
Slide 76:
SAE J2945/x Family of Standards
-
SAE J2945/A - MAP/SPaT Deployment - Intersection Operations
- Previously SAE J2945/10, contains recommended best practices on using the MAP and SPaT message content to meet operational needs.
- Currently on hold
-
SAE J2945/B - Recommended Practices for Signal Preemption Message Development
- Previously SAE J2945/11, provides reference implementations on how to provide priority and preemption at signalized intersections.
- Currently under development.
Slide 77:
NTCIP 1202 v03
-
NTCIP 1202 v03 - Object Definitions for Actuated Signal Controllers
- Standardizes the communications interface between an actuated signal controller and a center
- Published May 2019 as an update to NTCIP 1202 v02 (published 2005)
- Adds systems engineering content and accommodates new user needs
Slide 78:
NTCIP 1202 v03
Slide 79:
NTCIP 1202 v03
-
Connected Vehicle user needs addressed by the standard
- Focus is the interface between the Roadside Unit and the controller
- Provides SPaT data to the Roadside Unit
- Provides a check that the SPaT data matches the MAP data
- Supports the entire SPaT and MAP data messages except regional extensions and start time
Slide 80:
NTCIP 1202 v03
-
Implementation Issues:
-
Does the controller push or pull data with the RSU?
- If push, should the controller push on change (when a value changes) or periodically (e.g., ten times per second)?
-
If pull, how often should the RSU request the SPaT data from the controller?
- The controller should still push periodically.
Slide 81:
NTCIP 1202 v03
-
Implementation Issues:
- Clock differential
- For additional information about NTCIP 1202 v03, see A315 modules
Slide 82:
How to Specify SPaT Messages
-
Determine what optional data elements to include in your specification
- Use ISO TS 19091 as a guideline (by use case)
-
If using NTCIP 1202 v03, complete the PRL.
- Requires some of the optional data elements in SAE J2735 to be mandatory.
-
Connected Signalized Intersections project
- Develop a standard or specification to define key capabilities to support interoperability
- Started November 2019
Slide 83:
How to Specify SPaT Messages
-
For both SPaT and MAP messages, consider the communications media
-
Dedicated Short Range Communications (DSRC)
- Would use IEEE standards, which imposes a limit of approximately 1500 bytes
- Consider latency
- Where? Range of approximate 300 meters
-
Cellular Vehicle to Anything (C-V2X)
- Release 16 expected 2020.
Slide 84:
How to Specify SPaT Messages
-
For both SPaT and MAP messages, consider security:
- Signed to indicate it's an authentic message from the source it claims to be
- Could be signed at the Roadside Unit or a center
- For additional information about security, see other PCB modules
Slide 85:
How to Specify MAP Messages
-
MAP messages must be included with SPaT messages
- Contains indexes (SignalGroupIDs) connecting SPaT movements to ingress and egress lanes
- The MAP message indicates "where the lane" is.
-
Level of Detail: Varies depending on the applications supported
- Level of resolution needed may vary
- Geographical extent needed may vary
- What information is needed (report all lanes?)
- Communications limitations (message size)
Slide 86:
How to Specify MAP Messages
- Typically only 1 to maybe 3 intersections per MAP message
-
SAE J2945/0 contains recommendations:
- Transmission rates - once every one or two seconds
- DSRC channels
- Transmission power levels
Slide 87:
How to Specify MAP Messages
-
Implementation Issues
- Must be based on WGS84 coordinate system
- Intersection ID numbering
-
Need to define consistently
- E.g., How crosswalks are represented varies around the world.
-
Creation of a Guidance Document for MAP Preparation project
- Develop a guidance document on how to create MAP messages
- Expected start date March 2020
Slide 88:
How to Specify MAP Messages
-
Tools for Developing MAP messages
- USDOT J2735 MAP Tool
- Can automate map data validation and visualize data to reduce errors
Slide 89:
Additional References
- See Student Supplement
-
ITS Professional Capacity Building Program
-
National Operations Center of Excellence
-
USDOT Connected Vehicle Pilots
Slide 90:
Slide 91:
Case Study: City of Anaheim
-
Deployed OBUs and RSUs from 3 different vendors
- OBUs and RSUs from the same vendor worked
-
A side-by--side comparison of applications on the different OBUs showed different results
- Times to change may be different
- Applications did not always work
- Some applications were expecting optional data elements and did not properly display if the optional data elements were not provided
Slide 92:
Case Study: City of Anaheim
-
Lessons Learned
-
MAP configuration affected the application on the OBU
- Some applications were expecting optional data elements and did not properly display if the optional data elements were not provided
- Applications were not properly handling unexpected or non-conforming data packets
- Specify which optional elements are mandatory
- Test applications to handle unexpected or non-conforming data packets
Slide 93:
Slide 94:
Question
When broadcasting SPaT and MAP messages, which of the following issues must be considered?
Answer Choices
- Only one intersection is contained in each SPaT and MAP message
- All MAP messages must be accompanied by a SPaT message
- Other standards may limit the number of bytes in a message
- SPaT and MAP messages must use the same broadcast rate
Slide 95:
Review of Answers
a) Only one intersection is contained in each SPaT and MAP message
Incorrect. Each SPaT and MAP message may describe up to 32 intersections
b) All MAP messages must be accompanied by a SPaT message
Incorrect. However, SPaT messages should be accompanied by a MAP message
c) Other standards may limit the number of bytes in a message
Correct! Other standards may impose message size limitations
d) SPaT and MAP messages must use the same broadcast rate
Incorrect. For example, SPaT messages are dynamic and may need to be broadcasted more frequently
Slide 96:
Module Summary
- Describe the scope of the SAE J2735 Standard
- Describe the SPaT Message
- Describe the MAP Message
- Implementation Considerations
Slide 97:
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!
↑ Return to top