The messages — what actually goes over the air.
V2X interoperability lives or dies at this layer. Two devices from two vendors on two continents can share a radio and still be mutually useless if they do not agree on the message. There are two families — SAE J2735 in North America and the ETSI ITS message set in Europe — and they are structurally similar, semantically overlapping and not interchangeable.
Formally the V2X Communications Message Set Dictionary, renamed from the DSRC Message Set Dictionary.
First issued December 2006. Current revisions: J2735_202211, J2735_202309, and J2735_202409, which explicitly restores backward compatibility with the 2020 version. Encoding is ASN.1 with Unaligned Packed Encoding Rules per ISO/IEC 8825-2.
| Message | Acronym | ID |
|---|---|---|
| BasicSafetyMessage | BSM | 20 |
| MapData | MAP | 18 |
| SignalPhaseAndTiming | SPAT | 19 |
| TravelerInformation | TIM | 22 |
| RoadWeatherMessage | RWM | 23 |
| SignalRequestMessage | SRM | 24 |
| SignalStatusMessage | SSM | 25 |
| RTCMcorrections | RTCM | 28 |
| PersonalSafetyMessage | PSM | 32 |
| ProbeDataReportMessage | PDR | 34 |
| ProbeVehicleData | PVD | 35 |
| ProbeDataManagement | PDM | 42 |
| CommonSafetyRequest | CSR | 43 |
| RoadSideAlert | RSA | 44 |
| SensorDataSharingMessage | SDSM | 51 |
| CooperativeControlMessage | CCM | 52 |
| EmergencyVehicleAlert | EVA | 60 |
| RoadSafetyMessage | RSM | 61 |
| RoadGeometryAndAttributes | RGA | 64 |
| ManeuverSharingAndCoordinatingMessage | MSCM | 67 |
| TollAdvertisementMessage | TAM | 68 |
| IntersectionCollisionAvoidance | ICA | 82 |
Performance is set separately from format:
- SAE J2945/1 (J2945/1_202004) — on-board system requirements for V2V safety over DSRC. Defines the nominal 10 Hz BSM rate, path history, path prediction and the congestion-control algorithm.
- SAE J2945/9 (J2945/9_201703) — minimum performance requirements for the VRU safety message.
- SAE J3161/1 — the C-V2X analogue of J2945/1, on-board system requirements for LTE-V2X V2V safety communications. Revisions J3161/1_202203, _202409 and _202509. This is the document that defines the US C-V2X deployment profile.
Release 2, and the versions current in 2026.
| Message | Standard | Rate |
|---|---|---|
| CAM — Cooperative Awareness Message | EN 302 637-2 V1.4.1; Release 2 as TS 103 900 V2.3.1 (May 2026) | Adaptive 1–10 Hz, triggered by 4 m position, 4° heading, 0.5 m/s speed, or 1 s timer |
| DENM — Decentralized Environmental Notification Message | EN 302 637-3; Release 2 as TS 103 831 | Event-triggered, repeated ~1 Hz for the event's validity, geographically disseminated via GeoNetworking |
| CPM — Collective Perception Message | TS 103 324 | Adaptive 1–10 Hz. Shares detected-object lists from the station's own sensors — position, velocity, dimensions, classification, confidence. The European counterpart of SAE SDSM. |
| VAM — VRU Awareness Message | TS 103 300-3 V2.3.1 (Dec 2025), architecture in TS 103 300-2 | Adaptive 1–10 Hz |
| SPATEM, MAPEM, IVIM, SREM, SSEM, RTCMEM | TS 103 301 V2.3.1 (April 2026) | SPATEM ~10 Hz, MAPEM ~1 Hz, IVIM 1 Hz or event-triggered |
| MCM — Manoeuvre Coordination Message | In development; the specification number and publication status are not confirmed, so none is cited here | — |
All ETSI ITS messages share a common ItsPduHeader and are encoded with ASN.1 UPER. Crucially they are access-layer agnostic: the identical PDU rides ITS-G5 or C-V2X PC5 unchanged. The security envelope around them uses COER — Canonical Octet Encoding Rules, ITU-T X.696 — per IEEE 1609.2 and ETSI TS 103 097. The certificate and envelope formats →
A useful shorthand, loosely defined, worth knowing.
- Day 1 — awareness and warning. CAM/BSM, DENM, SPaT/MAP, IVI, roadworks warning, emergency vehicle approaching. This is what is deployed.
- Day 2 — collective perception (CPM/SDSM) and VRU awareness (VAM/PSM). Sharing what your sensors see, not just where you are. Specifications exist; deployment is early.
- Day 3 — manoeuvre coordination, cooperative driving, platooning. MCM, MSCM. Largely research and pilot.
The Day-1 to Day-2 transition is also the LTE-V2X to NR-V2X transition, because collective perception at meaningful rates does not fit in a Release-14 channel. Why →
Where this fits.
ITS station architecture
The facilities layer these messages live in, and why it is radio-independent.
V2V
The BSM and CAM in their operating context.
V2I
What a roadside unit broadcasts, message by message.
Standards
Where to download each of these, and which cost money.
Open source
The stacks and ASN.1 compilers that implement these message sets.
Glossary
Every message acronym on this page, defined in one place.
Questions this page answers.
What is a Basic Safety Message?
The core North American V2V message, SAE J2735 ID 20, broadcast at a nominal 10 Hz. Part I carries mandatory state — position, speed, heading, acceleration, brake status, vehicle size, steering angle. Part II carries optional and event-driven data including hard-braking flags, path history and path prediction.
What is the difference between a BSM and a CAM?
They serve the same purpose from two standards families. The BSM is fixed-rate at 10 Hz with a two-part structure; the CAM is adaptive between 1 and 10 Hz, triggered by change in the vehicle's state, and hands event-driven hazards to a separate message, the DENM. The field sets overlap heavily but are not identical, and the two are not interchangeable on the wire.
What is SPaT?
Signal Phase and Timing — the message an intersection broadcasts describing the current state of every signal movement and the time until it changes. Paired with MAP, which describes the intersection's lane-level geometry, it lets a vehicle work out which signal applies to its own approach.
What is a Collective Perception Message?
A CPM shares what a station's own sensors have detected — a list of objects with position, velocity, dimensions and classification — rather than only the station's own state. It lets an equipped vehicle or roadside unit act as a sensor for unequipped road users, which is the main answer to the fitment-penetration problem. The SAE equivalent is the Sensor Data Sharing Message, ID 51.