CAM

Cooperative Awareness Message

Services →
Introduced in Rel-15

CAM is a periodic broadcast message in V2X communication that shares a vehicle's dynamic state and basic attributes with nearby road users to enable cooperative awareness for safety and traffic efficiency.

Category
Services
Introduced
Rel-15
Where
Services
Specifications
3 specs
CAM Description Purpose Related Classification Specifications

Description

The Cooperative Awareness Message (CAM) is a fundamental data structure defined within the 3GPP standards for Cellular Vehicle-to-Everything (C-V2X) services, specifically under the umbrella of Vehicle-to-Vehicle (V2V) and Vehicle-to-Infrastructure (V2I) communications. It operates within the Facilities Layer of the ETSI ITS (Intelligent Transport Systems) protocol stack, which is adapted for use over 3GPP's PC5 interface (sidelink) and Uu interface. A CAM is not a 3GPP protocol message itself but an application-layer message whose generation, management, and transmission are facilitated by 3GPP system capabilities. Its primary function is to create and maintain a real-time, localized dynamic map of the vehicle's immediate surroundings by periodically broadcasting its own status and receiving status updates from other CAM-enabled entities within communication range.

The technical operation of CAM involves several key processes managed by the vehicle's ITS station. The CAM generation is triggered based on specific conditions defined in ETSI EN 302 637-2, such as a minimum change in position (e.g., 4 meters), a minimum change in heading (e.g., 4 degrees), or the elapse of a maximum time interval (typically 100-1000 ms, adjustable based on vehicle dynamics). Each generated CAM contains a standardized set of data elements defined in ASN.1 format. The core 'Basic Container' includes the vehicle's precise geographic position (latitude, longitude, altitude), speed, heading, and acceleration. The 'High Frequency Container' adds more dynamic data like vehicle curvature and yaw rate. Optional containers can include vehicle role (e.g., emergency vehicle), path history, and exterior lighting status.

Once generated, the CAM is passed down the protocol stack. For direct C-V2X communication (Mode 4 or Mode 2 sidelink), the message is scheduled for transmission over the PC5 interface using the NR-V2X or LTE-V2X physical layer in the 5.9 GHz ITS band. The 3GPP layer-2 protocols handle the actual radio resource selection, modulation, and coding. The transmission uses a broadcast mechanism without requiring a connection setup, enabling low-latency dissemination to all receivers within range, typically several hundred meters. For network-assisted communication (via Uu), the CAM can be sent to the network for distribution to a relevant geographical area, as determined by the V2X application server.

Upon reception, other vehicles or roadside units (RSUs) decode the CAM and update their local dynamic maps. This map is a software construct that fuses data from multiple received CAMs, along with sensor data, to provide a coherent representation of the traffic environment. The system architecture supporting CAM involves the Vehicle ITS Station, which includes the V2X application generating CAMs, the 3GPP Access Stratum for radio communication, and potentially a V2X application server in the network for wider dissemination. The role of CAM in the 3GPP network is foundational; it provides the raw situational awareness data upon which higher-layer safety and traffic efficiency applications—such as Forward Collision Warning, Intersection Movement Assist, or Green Light Optimal Speed Advisory—are built, making it a critical enabler for automated and cooperative driving.

Purpose & Motivation

CAM was created to address the fundamental safety challenge in road transportation: the lack of cooperative awareness between road users. Traditional vehicle safety systems (like anti-lock brakes, electronic stability control, or radar-based adaptive cruise control) rely solely on onboard sensors, which have inherent limitations. These sensors (cameras, radar, lidar) are limited by line-of-sight, weather conditions, and occlusions (e.g., a large truck blocking the view of a car ahead). This creates 'non-line-of-sight' blind spots where critical hazards remain undetected until it is too late for a human driver or an automated system to react safely.

The purpose of CAM is to electronically extend a vehicle's perception horizon beyond the limits of its physical sensors. By broadcasting its core state information, a vehicle essentially declares, "I am here, moving in this direction at this speed." When all vehicles and infrastructure participate, this creates a shared, cooperative perception field. This solves the occlusion problem and provides predictive awareness. For example, a vehicle approaching a blind intersection can be warned of a fast-approaching vehicle on the cross street before either driver has a visual on the other. Historically, the concept originated in dedicated short-range communication (DSRC/WAVE) standards. 3GPP adopted and integrated CAM into its C-V2X standards (starting in Release 14 for LTE-V2X and enhanced in Release 15+ for NR-V2X) to leverage the global scale, security framework, and evolving performance of cellular technology, creating a unified communication system for both telematics and direct safety-critical exchanges.

Classification

Part ofV2X
Specific typesDENM

Evolution Across Releases

Rel-15 Initial

Introduced foundational support for CAM as part of the enhanced LTE-based V2X (eV2X) framework. 3GPP specifications defined the system architecture and procedures for CAM service support over both PC5 sidelink and Uu interfaces. This included QoS handling for CAM traffic, resource allocation mechanisms for Mode 3 (network-scheduled) and Mode 4 (autonomous) sidelink transmission, and integration with the V2X application server for wider-area dissemination.

Explore further

Broader topics and technologies where CAM plays a role.

Defining Specifications

3GPP specifications that define or reference CAM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 23.795 vg10 V2X Application Architecture Study Rel-16
TR 37.985 vj00 Overview of V2X features in LTE and NR Rel-19