Ambimat GroupAmbimatAmbiSecureV2XeSIMAmbiAutomationAhmedabad · India · Est. 1982
Technology reference

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.

1 · SAE J2735

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.

MessageAcronymID
BasicSafetyMessageBSM20
MapDataMAP18
SignalPhaseAndTimingSPAT19
TravelerInformationTIM22
RoadWeatherMessageRWM23
SignalRequestMessageSRM24
SignalStatusMessageSSM25
RTCMcorrectionsRTCM28
PersonalSafetyMessagePSM32
ProbeDataReportMessagePDR34
ProbeVehicleDataPVD35
ProbeDataManagementPDM42
CommonSafetyRequestCSR43
RoadSideAlertRSA44
SensorDataSharingMessageSDSM51
CooperativeControlMessageCCM52
EmergencyVehicleAlertEVA60
RoadSafetyMessageRSM61
RoadGeometryAndAttributesRGA64
ManeuverSharingAndCoordinatingMessageMSCM67
TollAdvertisementMessageTAM68
IntersectionCollisionAvoidanceICA82

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.
2 · The ETSI ITS message set

Release 2, and the versions current in 2026.

MessageStandardRate
CAM — Cooperative Awareness MessageEN 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 MessageEN 302 637-3; Release 2 as TS 103 831Event-triggered, repeated ~1 Hz for the event's validity, geographically disseminated via GeoNetworking
CPM — Collective Perception MessageTS 103 324Adaptive 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 MessageTS 103 300-3 V2.3.1 (Dec 2025), architecture in TS 103 300-2Adaptive 1–10 Hz
SPATEM, MAPEM, IVIM, SREM, SSEM, RTCMEMTS 103 301 V2.3.1 (April 2026)SPATEM ~10 Hz, MAPEM ~1 Hz, IVIM 1 Hz or event-triggered
MCM — Manoeuvre Coordination MessageIn 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 →

3 · Day 1, Day 2 and beyond

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 →

Frequently asked

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.