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 324 V2.1.1 (June 2023), Release 2Generation events every 100–1,000 ms for a vehicle, down to 50 ms for some roadside uses. 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 → Which family a station speaks depends on where it is deployed: the V2X stack in India, Europe and the US.

On Ambimat's AmbiRSU and AmbiOBU development platforms, Ambimat's AmbiV2X stack implements CAM, DENM, SPATEM and MAPEM for its European development profile, with CPM partially implemented, and the SAE J2735 BSM as a US engineering demonstration. SPaT, TIM and MAP remain candidate J2735 development messages, chosen per programme. All of it is development and integration, verified in host-based software testing — over-the-air PC5 operation is not yet claimed, and none of it is conformance-tested or certified. What is implemented, row by row →

3 · Collective perception

CPM and SDSM: sharing what a station sees, and what that depends on.

A CAM or a BSM says where the sender is. A Collective Perception Message says what the sender’s own sensors perceive: the objects they have detected and, optionally, the parts of the road they can and cannot see. ETSI specifies it as the Collective Perception Service in TS 103 324 V2.1.1 (June 2023), part of ITS Release 2. The point is the road users who carry no V2X at all — a pedestrian, a cyclist, an unequipped car. A vehicle or a roadside unit with sensors can describe them to everyone in range, which is why collective perception is the main lever on safety while fitment is still low.

CPM partWhat it carries (TS 103 324 V2.1.1)
Management containerAlways present: the message’s reference time and reference position. For a vehicle, the reference position is the ground point at the centre of the front of its bounding box; a roadside station chooses its own (Clause 7.1.3)
Originating vehicle or RSU containerWho is sending. A vehicle must include its orientation angle, because the sensor data cannot be interpreted without it (Clauses 7.1.4, 7.1.5)
Sensor information containerThe sensors or sensor systems behind the message and the regions they can perceive. Sent in the first CPM and again once at least 1,000 ms have passed since it was last sent (Clauses 6.1.2.2, 7.1.6)
Perception region containerWhere the sender’s actual view departs from its static capability — for example an area shadowed by a parked lorry — with a confidence for each region; at most eight regions per message (Clause 7.1.7; Annex F)
Perceived object containerOne entry per object: kinematic state, dimensions, classification and confidence, and a measurement time relative to the reference time (Clause 7.1.8)

When an object is sent. CPMs are generated at periodic events between a minimum and a maximum interval — 100 ms and 1,000 ms by default, with roadside stations allowed down to 50 ms for some uses. At each event an object qualifies only if its perception quality clears a threshold, and then by type. Pedestrians, cyclists, animals and groups are sent when first detected, and all of them are refreshed together once any has gone unsent for half the maximum interval. Vehicles and motorcyclists are sent when first detected, or when they have moved more than 4 m, changed ground speed by more than 0.5 m/s or turned their velocity by at least 4° since they were last sent, or after 1,000 ms regardless. Those are the same 4 m, 0.5 m/s and 4° that trigger a CAM, applied to the objects a station sees rather than to itself. A roadside station may instead be configured to apply its own inclusion rules. (TS 103 324 clauses 6.1.2.1 and 6.1.2.3; default values in Annex F.)

What collective perception depends on. The message is the easy part. What makes it useful sits outside it:

  • A perception system. The CPM carries the output of sensors and fusion — object lists with confidence — not raw sensor data. A station with no sensors has nothing to put in one, and the quality threshold means a poor perception system mostly sends nothing.
  • One timebase. Each object’s measurement time is stated relative to the message’s reference time, and the standard requires it to include the sensor’s and the fusion system’s processing delay (clause 7.1.8.2). Sensor timestamps and the station’s ITS clock therefore have to agree. Where that time comes from →
  • The sender’s own pose. Objects are described relative to the sender’s reference position and orientation, so an error in the sender’s own position or heading moves every object it reports by the same amount.
  • Channel capacity. Object lists are larger than a CAM, and the standard ties the generation interval and the number of objects to the channel resources available, through multi-channel operation where a station supports it (clause 6.1.2.1; ETSI TS 103 141). That is why collective perception is usually discussed alongside wider channels and NR-V2X. LTE-V2X and NR-V2X →
  • Receivers that can use it. Object identifiers are local to the sender, chosen at random and replaced at every pseudonym change (clause 7.1.8.2). A receiver hearing the same pedestrian from three stations gets three unrelated identifiers; associating them, and deciding how far to trust each sender, is the receiver’s work. Misbehaviour detection →

The SAE counterpart. In the SAE family the equivalent role is sensor data sharing — the SDSM in the J2735 table above. SAE J3224 (issued 17 August 2022), V2X Sensor-Sharing for Cooperative and Automated Driving, describes the Sensor Sharing Service: its concept of operation, use cases and message flows, and the message structure, V2X entity requirements and information elements that let roadside units and vehicles describe detected objects. J3224 is a purchased standard, so its field-level detail and triggers are not summarised here.

Why the ecosystem role matters. A sensor-equipped roadside unit at an intersection can describe a pedestrian to every approaching vehicle that cannot see one, and it delivers that value without waiting for the other road users to be equipped. The cost is everything in the list above: sensors and fusion at the site, a shared timebase, a calibrated mounting, channel capacity and receivers that consume the result. Collective perception is therefore a site-and-programme decision, not a message to switch on. Where it appears among the use cases →

On Ambimat’s development platforms, AmbiV2X’s CPM support is partial: it encodes and decodes CPMs carrying perceived objects that an external sensor system supplies, and received CPMs can be inspected by a read-only engineering consumer, with no sensor fusion and no driver alert. Neither platform includes perception hardware as standard: AmbiOBU has no perception sensors, and cameras, radar or environmental sensors on an AmbiRSU are customer-specific integrations, scoped per programme and quoted at additional cost. No perception pipeline and no CPM transmission feature is claimed, and what exists is verified in host-based software testing — over-the-air PC5 operation is under development, with target readiness in late November 2026. What is implemented →

4 · 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.

What does collective perception depend on?

More than the message. A CPM carries the output of a perception system, so the sender needs sensors and fusion; each object's measurement time must include sensor and fusion delay, so sensors and the ITS clock need one timebase; objects are placed relative to the sender's own position and heading, so pose error moves every object; and object lists compete for channel capacity. ETSI TS 103 324 V2.1.1 specifies the message and its inclusion rules; SAE J3224 describes the SAE sensor-sharing service.

Last updated 2026-10-22 · Technical reference maintained by Ambimat Electronics, Ahmedabad, India. Corrections: v2x@ambimat.com