Module 63 - CV265
CV265: Introduction to IEEE 1609 Family of Standards for Wireless Access in a Vehicular Environments (WAVE)
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:
Slide 3:
CV265
Introduction to IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE)
Slide 4:
Instructor
Raman K Patel, Ph.D., P.E.
President
RK Patel Associates, Inc.
Slide 5:
Learning Objectives
- Describe IEEE 1609 Family of Standards for Wireless Access in a Vehicular Environments (WAVE)
- Discuss Role of IEEE 1609.3 Networking Services
- Discuss Role of IEEE 1609.4 Multi-Channel Operations
- Discuss Role of IEEE 1609.2 Security Services and Identify WAVE Implementation Issues and Challenges
Slide 6:
Learning Objective 1
- Describe IEEE 1609 Family of Standards for Wireless Access in Vehicular Environments (WAVE)
Slide 7:
Connected Vehicle (CV) Environment
CV Environment Consists of:
- Vehicle to Everything (V2X)
- Vehicle to Vehicle (V2V)
- Vehicle to Infrastructure (V2I)
- Vehicle to Pedestrian (V2P)
CV Communications:
- Wireless
- Mixture of:
- Local short-range communications
- Remote communications, e.g. devices to Traffic Management Center (TMC)
- Safety/Mobility Applications
- Process messages/data and issue warnings/alerts to driver/users
Slide 8:
CV Environment is Unique
Dynamic Operational Characteristics
- Participants constantly changing
- Devices need to communicate under changing speeds-doppler shifts
- Safety applications require frequent communications (messages)
Slide 9:
WAVE (Wireless Access for Vehicular Environments)
WAVE is a Communication System
- Provides (ad-hoc) wireless connectivity for V2X to enable safety and mobility applications-higher layer entities
- Provides privacy (pseudonimity) and security (authentication and data integrity)
Slide 10:
Purpose and Mission of WAVE Standards
Mission
"The WAVE standards enable the development of interoperable low-latency, low overhead WAVE devices that can provide communications in support of transportation safety, efficiency, and sustainability, and that can enhance user comfort and convenience."
IEEE 1609.0 std.
Example
Latency is a measure of time delay experienced in a system; e.g. Forward Collision Warning application limits 0.1 sec latency, measured between end points.
IEEE
Institute of Electrical and Electronics Engineers
Source: USDOT
Slide 11:
Standardized Direct Communication Technologies that use WAVE
1. Dedicated Short Range Communication (DSRC) uses Published Standards:
- SAE J2945/1 V2V safety applications
- IEEE 1609 family (1609.3 Networking)
2. LTE-V2X Under Preparation
- LTE-V2X-Sidelink Mode 4 using the PC5 Interface (3GPP, Release 14,15)
- Uses SAE J3161/1 and IEEE 1609.3 revision (pending)
LTE - Long Term Evolution
3GPP - Third Generation Partnership Project
SAE - Society of Automotive Engineers
IEEE - Institute of Electrical and Electronics Engineers
Slide 12:
SAE Standards/Documents Published
Uses WAVE
- J2735: V2X Data Dictionary (technology-neutral revision nearly complete)
- J3061: Systems engineering enhancements to J2735 (information report)
Slide 13:
SAE Standards/Documents Published (cont.)
Uses WAVE
- J2945: Systems engineering guidance and common design elements
- J2945/1: V2V safety applications (DSRC-based BSM application - revision published April 2020)
- J2945/2: V2V safety awareness recommended practice (builds on 2945/1)
- J2945/3: Road Weather applications
- J2945/5: Security guidelines for connected vehicle applications
- J2945/9: Vulnerable road user recommended practice
Slide 14:
SAE Standards/Documents in Development
Uses WAVE
- J2945/1A: Vehicle-level test procedures for V2V safety communications (companion to J2945/1)
- J2945/4: Road safety applications (e.g. curve speed warning, work zone safety, reduced speed zones)
- J2945/6: Adaptive cruise control and platooning
- J2945/7: Positioning enhancements for V2X systems
- J2945/8: Cooperative perception system
- J2945/A: Next generation mapping (a more general, layered approach to maps for use by applications)
- J2945/B: Signalized intersection applications
- J2945/C: Probe data
- J2945/D: Road user to road user courteous communication
Slide 15:
SAE Standards/Documents in Development (cont.)
Uses WAVE
- J3161/1: On-Board System Requirements for LTE-V2X V2V Safety Communications
- Uses 3GPP PC5, Mode 4 for the physical interface
- J3161: C-V2X Deployment Profiles
- J3180: Cooperative perception system
- J3186: Maneuver sharing and coordinating
- J3216: Cooperative driving automation taxonomy and definitions (companion to SAE J3016)
- J3217: Electronic fee collection (V2X-based tolling)
- J3224: Sensor sharing for cooperative and automated driving
Slide 16:
WAVE'S Relationships to Other Protocol Models
WSMP - Wave Short Message Protocol
OSI - Open System Interconnect
ETSI - European Telecommunications Standards Institute
API - Application Programming Interface
LLC - Logical Link Control
Source: IEEE 1609.0 Std.
Slide 17:
IEEE 1609 Family of Standards (2016)
Standards Deployed in WAVE Protocol Stack-Devices
- 1609.0 Guide (Architecture)
- 1609.2 Security Services
- 1609.3 Networking Services
- 1609.4 Multi-channel Operation
- 1609.12 Identifier Allocations
- IEEE 802.11:MAC sublayer and PHY Layer
MAC-Media Access Control
PHY-Physical Layer
WSMP-WAVE Short Message Protocol
Slide 18:
WAVE is Customized Protocol Architecture
WSMP-WAVE Short Message Protocol
TCP-Transmission Control Protocol
IP-Internet Protocol
UDP-User Datagram Protocol
MAC-Media Access Control
Courtesy-Justin McNew
Slide 19:
Uses of Protocols
WSMP
- Customized for low latency needs of CV applications
- Compact, but ONLY supports broadcast of "single hop" short messages
- Common protocol for both Network and Transport layers
IPv6
- Adjusted for low latency needs
- Higher overheads, supports Unicast, larger messages (information transfer-private conversations or network communications)
- Deployed as UDP/IP or TCP/IP
Well-suited to message-based applications.
Slide 20:
DSRC 5.9 GHz Spectrum Assigned by FCC
Radio Channels Current Design
Slide 21:
WAVE Devices
Devices Transmit/Receive Messages (data) from other Devices in the Vicinity
Source: City of Dublin, OH
Slide 22:
WAVE Device Performs Two Roles
Provider issues a WSA (nominally on the CCH 178) to indicate available opportunity on SCHs.
User monitors CCH 178 for a WSA, makes determination to participate or not to participate.
WSA-WAVE Service Advertisement
Slide 23:
Slide 24:
Question
Which of the following is an incorrect statement related to WAVE System?
Answer Choices
- WAVE devices deploy IEEE 1609.3 standard.
- WSMP/IPv6, both protocols can be used at network layer.
- WAVE Service Advertising (WSA) indicates BSMs on SCH 172.
- V2X includes all forms of CV communication services.
Slide 25:
Review of Answers
a) WAVE devices deploy IEEE 1609.3 standard.
Statement is correct. IEEE 1609.3 standard provides networking capability.
b) WSMP/IPv6, both protocols can be used at network layer.
Statement is correct. Both protocols are deployable at network layer.
c) WAVE Service Advertising (WSA) indicates BSMs on SCH 172.
Incorrect. WSA is NOT used for safety channel SCH 172.
d) V2X includes all forms of CV communication services.
Statement is correct. V2X includes everything: V2V, V2I, V2P…
Slide 26:
Learning Objective 2
- Discuss Role of IEEE 1609.3 Networking Services
Slide 27:
IEEE 1609.3 Networking Services
Collection of Management and Data Services
Source: IEEE 1609.0
MIB-Management Information Base
Slide 28:
IEEE 1609.3 Networking Services
Both are separate and distinct networking protocols, and one does not depend on the other (e.g., IPv6 frames are not transported over WSMP, or vice versa).
Slide 29:
IEEE 1609.3 Networking Services
Data Services
Source: Ken Vaughn
Slide 30:
Provider Service Identifier (PSID)
Nearly 100 applications are registered with unique integer as PSID
https://standards.ieee.org/products-services/regauth/psid/public.html
Slide 31:
WAVE Communications Scenarios
Scenario 1: SCH 172 Communications
- Preconfigured WAVE devices-SCH operation; WSA is Not required
Example 1: V2V, BSMs are broadcasted 10X per sec.
Example 2: V2I, SPaT/MAP data can also be transmitted on 172
Slide 32:
WAVE Communications Scenarios
Scenario 2: CCH 178 Communications
- Nearby devices tuned to CCH 178 receive WSA at a time of transmission
- Provider device sends WSAs indicating where opportunity is available
- User device, listening for opportunity, may decide to participate or not to participate
Slide 33:
Example of WSM Transmission (V2X)
How it Works (V2X)-Information Broadcasts
Source: Courtesy Justin McNew
Slide 34:
Illustration of V2V Safety
Slide 35:
Example of Localization with RF Coverage
How it Works (V2I)-Localized Data Exchange
This approach can be used, for example, to support electronic fee collection.
Source: Courtesy Justin McNew
Slide 36:
Example of WSM Transmission (V2X)
How it Works (V2I)-Cloud Based
Example Applications: Probe Data Collection,
Road Weather Data Collection/Distribution, SCMS
Source: Courtesy Justin McNew
Slide 37:
Internet Connectivity with IPv6 Communication
Illustration of RSU Role as Gateway (V2I)
- Most Typically CCH 178 transmits WSA (with WRA)
- SCHs (except 172) provide IPv6 communication
Source: IEEE 1609.0 Std.
WRA-WAVE Routing Advertisement
TMC-Traffic Management Center
Slide 38:
Slide 39:
Question
Which of the following is NOT included in the IEEE 1609.3 standard?
Answer Choices
- WSA (WAVE Service Advertisement).
- PSID (Provider Service Identifier).
- WSMP (WAVE Short Message Protocol)/IPv6.
- BSM (Basic Safety Message).
Slide 40:
Review of Answers
a) WSA (Wave Service Advertisement).
Incorrect. WSA is included in 1609.3.
b) PSID (Provider Service Identifier).
Incorrect. PSID is included in 1609.3.
c) WSMP/IPv6.
Incorrect. Both protocols are included in 1609.3 standard.
d) BSM (Basic Safety Message).
Correct! BSM is NOT included in 1609.3; it is part of J2735/J2945.1 standards.
Slide 41:
Learning Objective 3
- Discuss Role of IEEE 1609.4 Multi-Channel Operations
Slide 42:
Role of IEEE 1609.4 Multi-Channel Operation
Management Plane Provides:
✓ Multi-channel Synchronization
✓ Channel Access
✓ MIB Maintenance
✓ Readdressing (MAC address)
Slide 43:
Role of IEEE 1609.4 Multi-Channel Operation
LLC: Logical Link Control
Slide 44:
Role of IEEE 1609.4 Multi-Channel Operation
Provides extension to 802.11 MAC sublayer to utilize more than one channel and coordination
Slide 45:
Role of IEEE 1609.4 Multi-Channel Operation
Supports Dual Radio Operation
- Dual radios can operate on multiple channels to ensure full benefits of safety and other information of interest
Slide 46:
Role of IEEE 802.11
Role of 802.11 is to Move Data between MAC/PHY Peers
- Describes specification for wireless connectivity using DSRC services
https://ieeexplore.ieee.org/document/6361248
Slide 47:
MAC/PHY Layers
- MAC Address
- IEEE assigned globally unique identifier-48 bits size, used in transferring data packets across data link
- IP Address
- Layer 3 address (128 bits in IPv6; 32 bits in IPv4), used in local network
- Both are subjected to change often in WAVE communication to provide anonymity
Slide 48:
What is Channel Coordination?
Channel Coordination Supports Data Exchange
Involving one or more switching devices with concurrent alternating operation on multiple channels
Slide 49:
Channel Coordination
Multi-Channel Operation at Lower Layers
- Includes when and how a device is allowed to access the PHY layer to transmit data (multi-channel operation)
- Access to specific radio channel(s) is provided by MLME as directed by WME
MLME-MAC sublayer Layer Management Entity
WME-WAVE Management Entity
Slide 50:
Channel Coordination
Access Options
Immediate access can be combined with continuous access to allow an extended time on channel (i.e. until the transection is done).
Slide 51:
Multi-Channel Synchronization with UTC
Coordinated Universal Time (UTC) Derived from GPS (GNSS) on the Device
GPS-Global Positioning System, also called GNSS-Global Navigation Satellite System
Slide 52:
Slide 53:
Question
Which of the following is an incorrect statement? Answer Choices
- IEEE 1609.4 supports channel switching capability.
- BSM messages are typically received on SCH 172.
- Channel switching operation occurs at Network layer.
- Dual radio ensures continuous listening of safety messages.
Slide 54:
Review of Answers
a) IEEE 1609.4 supports channel switching capability.
Correct Statement. 1609 provides channel switching capability.
b) BSM messages are typically received on SCH 172.
Correct statement. SCH 172 is typically reserved for BSMs.
c) Channel switching operation occurs at Network layer.
Incorrect statement, Channel switching occurs at PHY layer.
d) Dual radio ensures continuous listening of safety messages.
Correct statement. Radio 1 tuned to SCH 172 for safety messages, Radio 2 can switch to other SCHs.
Slide 55:
Learning Objective 4
- Discuss Role of IEEE 1609.2 Security Services and Identify WAVE Implementation Issues and Challenges
Slide 56:
WAVE Communication Security Challenges
Consider 2 vehicles, part of dynamic ad-hoc network
- Never encountered each other
- Must establish trust with each other
- Might only have seconds before a collision
- Need to maintain anonymity
- System needs capability to revoke credentials when needed, very large number of devices
Slide 57:
Role of 1609.2: Security Services
(Extended Text Description: This slide contains the figure from slide 18, but the WAVE stack is shown towards the right side. Security services provided by IEEE 1609.2 is shown with an arrow pointed to security plane. The bullet items include the following:
Features
- Signing/verification services (e.g. used for V2V broadcast messages)
- WSMP payloads (both broadcast and unicast) can be signed or signed and encrypted
- ISO 21177 is one option for encryption it uses TLS with 1609.2 certificates
- Security is NOT a layer, but a plane that spans the entire stack, uses 1609.2 services to establish trust
)
TLS-Transport Layer Security
ISO/TS 21177: https://www.iso.org/standard/70056.html
Slide 58:
Role of 1609.2: Security Services
Additional Features
- Ongoing amendments/revisions under 1609.2.1 will support SCMS implementation
- Support the Certificate Authority (CA)
SCMS-Security Credential Management System
Slide 59:
Communication Security Aspects
WAVE Security Services
- Certificate is distributed over WSMP
- CRL is distributed by the SCMS over IP interface
- Certificates are issued with limited lifespans/regularly renewed through an automated process; this allows the size of the CRL to be managed
- CRL is the outcome of Misbehavior Detection (MBD); revokes trust from these users
CRL-Certificate Revocation List
Slide 60:
Role of 1609.2: Security Services
Digital Certificate Defines Credentials Granted
- Transmit authorizations
- Receiver checks if the sender has the permissions to carry out the actions
Source: William Whyte
Certificate Authority (CA)
Slide 61:
Example: Certificate SSP in TSP V2I Application
SSP authorizes Transit/Emergency vehicles to make priority request; others may have various levels of permission (if any)
Slide 62:
Role of 1609.2: Security Services
Role of Application in Signing a Message
- Application (higher layer entity) requests security services to sign a message
- Cryptographically binds a certificate to each message
- Demonstrates it originated a given message and the message has not been altered
- Cryptographic binding is called "signing"
- Credential is issued by a Certificate Authority or CA
- Some messages are signed and unencrypted (for authentication purposes)
- Others are signed and encrypted (for authentication and data protection purposes)
Signing focuses on integrity, encryption is for confidentiality.
Slide 63:
Role of 1609.2: Security Services
Security Considerations for WSA
- All WSAs must be signed (PSID 0x87)
- Misbehavior reporting service can be advertised in a WSA
- WSA security header indicates weather or not the message is secured (a signed-SPDU) or it is encrypted.
WSA-WAVE Service Advertisement
SPDU- Secured Protocol Data Unit
Slide 64:
WAVE Implementation Challenges
Key Areas
- Evolving WAVE standards (2016)…
- Multiple communication support (e.g. DSRC, LTE-V2X)
- Dual Radio operation needs
- System integration issues (interoperability)
- Procurement issues, multiple vendor relationships
- SCMS implementation
- Intersection management (V2I, Traffic Controller)
- Other project-specific or MPO regional planning issues
MPO-Metropolitan Planning Organization
Slide 65:
Stakeholders-Specific Issues
(Extended Text Description: This slide shows relationship between Stakeholders and Issues. On the left the Stakeholders text is bracketed to the right with the bullet list of issues:
Stakeholders
Public Agencies
Vehicle Designers
OEM Manufacturers
ASD Vendors
Developers of Applications/Standards
Testing Engineers
Certification Groups
Academic Researchers
Vehicle/Fleet Owners
Issues
- Data Exchange Support:
- ITS Information
- WSA Broadcasts
- SPaT MAP BSM messages
- Standards/Interoperability Support
- IEEE 802.11 (2016)
- IEEE 1609.X (2016)
- SAE J2735
- USDOT v4.1a RSU specs.
- NTCIP 1202 v3, V2IHUB for controller interfaces
- Support for:
- WSMP v3
- IPv06 (optimized for low latency)
- Security: SCMS v2.0
)
Slide 66:
Protocol Implementation Conformance Statement (PICS)
(Extended Text Description: This slide contains a table labeled PICS Sample Portion (Full Table on page 118, IEEE 1609.3 with the following table data:
Item | Feature | Value | Reference | Status | Support |
---|---|---|---|---|---|
N1 | DATA PLANE | - | - | ||
N1.1. | LLC | 5.2 | M | YES | |
N1.1.1. | LLC extensions for WSMP | 7.5 | N1.3:M | YES | |
N1.2. | IPv6 | 5.3, 6.4 | O1 | YES | |
N1.2.1. | Use stateless configuration | 6.4 | O | ||
N1.2.2. | IP readdressing | 6.4.2 | M | ||
N1.2.3. | Send IP datagrams | 5.3 | O2 | ||
N1.2.4. | Receive IP datagrams | 5.3 | O2 | ||
N1.2.4.1. | Receive by link-local address | 6.4 | M | ||
N1.2.4.2. | Receive by global address | 6.4 | M | YES | |
N1.2.4.3. | Receive by host multicast addresses | 6.4 | O3 | ||
N1.2.4.4. | Receive by router multicast addresses | 6.4 | O3 | ||
N1.2.5. | UDP | 5.4 | O | ||
N1.2.6. | TCP | 5.4 | O | YES | |
N1.2.7. | Other IETF protocols | ()a | 5.4 | O | |
N1.3. | WSMP | 5.5 | O1 | ||
N1.3.1. | WSM reception | 5.5.3 | O4 | ||
N1.3.1.1. | Check WSMP Version number | ()b | 5.5.3, 8.3.2 | M | |
N1.3.1.2. | Check Subtype field | ()r | 5.5.3, 8.3.2 | M | YES |
N1.3.1.3. | Check TPID | ()s | 5.5.3, 8.3.2 | M | |
N1.3.1.4. | Wave Info Elem Extension field | 8.1.1 | M | ||
N1.3.1.5. | Deliver message based on Address Info (PSID) | 5.5.3 | M |
Additionally, the status cells on rows N1.1. and N1.1.3 are outlined in red, the Support cells of rows N1.1., N1.1.1., N1.2., N1.2.4.2., N1.2.6. and N1.3. through N1.3.1.5. are labeled with a green "YES". And above the Support column is the text "Illustration" pointing to the YES in row N1.1., and to the right of the table is a box with the text "My agency anticipates large data transfers, so I need both IPv6 and WSMP" pointing to the Support cells of the relevant table sections of IPv6 and WSMP.")
M-Mandatory, O-Optional
Slide 67:
Who Benefits from use of PICS
In General, CV Project Deployment Stakeholders Benefit from the Project Level PICS
Specifically,
- An implementer of WAVE devices may use the PICS to indicate which features are supported by an implementation.
- A vendor "unambiguously knows", upfront, what project needs are and no finger pointing….avoid disputes later.
- A tester may use the PICS as a checklist against which to verify conformance.
- A system integrator's "peace of mind" …at end of project interoperable devices will function as intended for safety/mobility applications in CV environment.
Slide 68:
Multivendor Relationships
System Integration Across Devices: "What are we procuring?"
Slide 69:
US CV Deployments (67 planned, 57 operational)
Slide 70:
WAVE Devices Implementation (CV Pilots)
Wyoming Pilot (WYDOT) | Complete | Target |
---|---|---|
WYDOT Maintenance Fleet Subsystem On-Board Unit (OBU) | 35 | 90 |
Integrated Commercial Truck Subsystem OBU | 0 | 25 |
Retrofit Vehicle Subsystem OBU | 17 | 255 |
WYDOT Highway Patrol | 0 | 35 |
Total Equipped Vehicles | 52 | ~405 |
Roadside Units (RSU) along 1-80 | 75 | 75 |
Tampa Pilot (THEA) | Complete | Target |
---|---|---|
Private Light-Duty Vehicles Equipped with On-Board Unit (OBU) | 727 | 1,080 |
HART Transit Bus Equipped with OBU | 7 | 10 |
TECO Line Street Car Equipped with OBU | 8 | 8 |
Total Equipped Vehicles | 742 | ~1,100 |
Roadside Units (RSU) at Downtown Intersections | 47 | 47 |
Devices use WAVE Standards (2016) v3
Source: USDOT 3/1/2020
Slide 71:
WAVE Devices Implementation: NYC Pilot Project
- Installed 1606 vehicles of a scheduled 3000, June 2020
- Installed 400 RSUs of a scheduled 450
- Verified Over-the-Air Firmware updates and applications parameters
Slide 72:
Lessons Learned from Deployments
Slide 73:
Lessons Learned from Deployments (cont.)
What have we tested?
✓ V2V/V2I Communications
✓ Interoperability, tested the reception of OTA (broadcasts) messages; BSMs, SPaT/MAP
Applications performance testing done separately by CV Pilots within their own test programs.
OTA-Over The Air
Slide 74:
Slide 75:
WAVE Devices Testing for Interoperability
Source: http://www.cflsmartroads.com/projects/CVAV_D5_Testing.html
Slide 76:
Testing Strategy: Test Equipment + Messages
Lab Setup included a total of 21 manufacturers and 3 types of devices
- 5 controller manufacturers
- 9 RSU manufacturers
- 7 OBU manufacturers
Field test validation at two locations, to test end-to-end communication (transmit/receive)
SPaT-Signal Phasing and Timing
TIM-Traveler Information Messages
EVP-Emergency vehicle Pre-emption
Slide 77:
WAVE Device and "Standards Conformance"
Conformance is defined as the adherence of an implementation to the requirements of one or more specific standard or technical specifications
-ISO/IEC 10641:1993
WAVE device is defined as a device that is conformant to the following standards:
- IEEE Std 1609.3
- IEEE Std 1609.4
- IEEE Std 1609.12
- IEEE Std 1609.2 (when sending secured WSAs or using 1609.2 certificates)
- IEEE Std 802.11, operating outside the context of a basic service set
Source: IEEE 1609.0 (2019) page 25
Slide 78:
WAVE Device and "Standards Conformance"
For IEEE Std 1609.3 conformance, a device implements at least the following features:
- LLC sublayer
- IPv6 or WSMP, or both
- Transmit or receive, or both
For IEEE Std 1609.4 conformance, a device implements at least the following features:
- OCBActivated communication (as specified in IEEE Std 802.11)
- Transmit or receive, or both EDCA and user priority when transmitting
EDCA-Enhanced Channel Distributed Access
OCBA-Outside the Context of a Basic Service
Source: IEEE 1609.0 (2019) page 25
Slide 79:
Example for Compliance Language for Dual Radios
(Extended Text Description: This slide contains the following text, with section 4.8.2.2 outlined in red:
4.8.2 DSRC
4.8.2.1 FCC Regulation 47 CFR Compliance: The RSU shall comply with Federal Communications Commission (FCC) Code of Federal Regulations title 47 Parts 0, 1, 2, 15, 90, and 95.
4.8.2.2 Each RSU shall include 2 radios capable of operating on all 7 channels of the DSRC spectrum and capable of having their output level modified for each channel and each message.
4.8.2.3 Nominally one channel will be 172 and shall monitor the BSM messages, and transmit the SPaT, MAP, and RTCM messages.
4.8.2.4 The second channel will be 178 and shall alternate or change between channels and modes for the support of IP communications and the messages necessary for the CVPD support of software and parameter updates and log downloads to the TMC.)
Source: City of New York, RSU Specification, 2017, page 81
https://www.cvp.nyc/proiect-status
Radio Transmission Commission for Maritime Services (RTCM)
Slide 80:
Slide 81:
Question
Which of the following is an Incorrect statement? Answer Choices
- WAVE supports both WSMP and IPv6 protocols.
- Compliant WAVE devices are typically interoperable.
- PICS should be included in a CV project specification.
- WSA broadcasts opportunity on any channel.
Slide 82:
Review of Answers
a) WAVE supports both WSMP and IPv6 protocols.
Incorrect. WAVE supports both protocols.
b) Compliant WAVE devices are typically interoperable.
Incorrect. They are tested for messages exchange for interoperability.
c) PICS should be included in the CV project specification.
Incorrect. PICS can be used as a checklist for conformance to WAVE standards.
d) WSA broadcasts opportunity on any channel.
Correct Answer! WSA is typically issued on CCH 178.
Slide 83:
CV Technical Resources
- Supplement provides references for the following:
- Current WAVE standards documents
- SAE Messages standards documents
- CV Pilots lessons learned
- Annex C, IEEE1609.0: Prof of Testing/Certification of WAVE devices
- RSU standard development effort (ITE) https://www.ite.org/technical-resources/standards/rsu-standardization/
- DSRC Roadside Unit (RSU) Specifications Document v4.1 www.cflsmartroads.com
Slide 84:
CV Training Modules Available
https://www.pcb.its.dot.gov/stds modules.aspx
- CV-T160 Connected Vehicles Certification Testing Introduction
- CV-261 (V2I) ITS standards for Project Managers
- CV-262 (V2V) ITS Standards for Project Managers
- CV-271: Using the ISO TS 19091 Standard to Implement V2I Intersection Applications Introduction
- CV-273: Introduction to SPaT/MAP Messages
- Transit 11: Transit and the Connected Vehicle Environment/Emerging Technologies, Applications, and Future Platforms
- Transit 24: Transit Signal Priority (TSP)
- CSE-201: Security Credential Management (SCMS)
- CSE-202: Introduction to Cybersecurity
Slide 85:
Learning Objectives
- Describe IEEE 1609 Family of Standards for Wireless Access in a Vehicular Environments (WAVE)
- Discuss Role of IEEE 1609.3 Networking Services
- Discuss Role of IEEE 1609.4 Multi-Channel Operations
- Discuss Role of IEEE 1609.2 Security Services and Identify WAVE Implementation Issues and Challenges
Slide 86:
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!