Chapter 2

Current Challenges

Overview

2.1 Four Kinds of Peers, One Shared Radio Environment

V2X is hard because "everything" covers very different communication partners. WIA-COMM-003 splits the problem into four modes. Each has different timing needs, different failure consequences and a different kind of counterpart.

• V2V (Vehicle-to-Vehicle): direct exchange between vehicles, built around Cooperative Awareness (CAM), Decentralized Environmental Notification (DENM) and Collective Perception (CPM). The purpose is collision avoidance.
• V2I (Vehicle-to-Infrastructure): traffic signal phase and timing (SPaT), map data (MAP) and Road Side Unit (RSU) communication.
• V2P (Vehicle-to-Pedestrian): pedestrian detection, cyclist awareness and emergency vehicle warning, all aimed at vulnerable road users.
• V2N (Vehicle-to-Network): cloud traffic management, remote monitoring and OTA updates.

The first challenge is that these modes do not share a single quality-of-service profile. A warning that a vehicle ahead is braking hard has to arrive almost instantly, and a few missed messages may be survivable. A map of an intersection's lane geometry changes rarely but must be complete and correct. An over-the-air update tolerates delay, but it cannot tolerate corruption. The specification therefore states performance requirements (latency, packet rate, range) next to the message formats. They constrain which encodings and transports are valid for a given message.

The second challenge is that two device roles are involved. The On-Board Unit (OBU) sits in the vehicle and the Road Side Unit (RSU) sits at the roadside. Vehicles from different manufacturers must interoperate without a prior relationship, and the radio link must work without any association step. The standard also has to accommodate two radio families, DSRC and C-V2X, behind a single application-facing model. The rest of this chapter looks at how the specification handles each of these tensions.

2.2 Latency Budgets and Message Rates

The standard defines five canonical message types. Their rates and latency targets show how a single stack carries traffic with very different urgency.

Message	Frequency	Purpose	Latency
BSM (Basic Safety Message)	10 Hz	Position, speed, heading	<10 ms
CAM (Cooperative Awareness)	1-10 Hz	Vehicle status	<100 ms
DENM (Event Notification)	Event-driven	Hazard warnings	<10 ms
SPaT (Signal Phase/Timing)	10 Hz	Traffic signal info	<100 ms
MAP (Map Data)	1 Hz	Road geometry	<500 ms

Three observations follow from the table.

• Periodic and event-driven traffic coexist. BSM, CAM, SPaT and MAP are periodic beacons. DENM is generated only when a hazard exists. The radio must absorb a steady background of beacons and still deliver a sudden DENM within its tight budget.
• Rate is a safety parameter. A BSM at 10 Hz means a fresh position every 100 ms. A vehicle at the 65 km/h used in the SDK example covers roughly 1.8 m between two consecutive messages. Lowering the rate to save channel capacity directly widens the gap between what a receiver believes and where the sender actually is.
• The same standard family appears under two names. The terminology section attributes BSM to SAE J2735 and CAM to ETSI. Both express vehicle awareness, so an implementation serving several regions may need to produce or consume both.

The SDK example shows how the BSM fields look to an application developer:

const bsm: V2VMessage = {
  type: MessageType.BSM,
  position: { lat: 37.7749, lon: -122.4194, alt: 10 },
  speed: 65, // km/h
  heading: 270, // degrees
  acceleration: { x: 0.5, y: 0, z: 0 },
  timestamp: Date.now()
};

await v2x.sendV2V(bsm);

The envelope carries only what a neighbour needs for a collision assessment: where the vehicle is, how fast, which way, how it is accelerating, and when the sample was taken. The timestamp matters because a receiver evaluating collision risk must know how old a position is. A stale position, even a correct one, produces misleading warnings. The broadcast also carries the sender's position ten times per second, so privacy protection is a design requirement alongside safety. The standard lists "end-to-end encryption and privacy protection" among its key features for this reason.

2.3 Radio Access: DSRC, C-V2X and the Spectrum Patchwork

The standard supports two access technologies and describes them in parallel.

DSRC (Dedicated Short-Range Communications) is based on IEEE 802.11p in the 5.9 GHz band. Its physical layer uses 10 MHz channels with OFDM modulation (BPSK, QPSK, 16-QAM or 64-QAM), giving data rates of 3-27 Mbps. At the MAC layer it uses CSMA/CA. No association is required before a station can transmit, and both broadcast and unicast are supported, with Quality of Service provided through EDCA. The specification gives its range as up to 1000 meters in line of sight and 300-500 meters in urban settings, with latency of 5-10 ms.

C-V2X (Cellular V2X) covers LTE-V2X and 5G NR-V2X. It has two operating modes:

• Mode 3 (network-based): the cellular network takes part in coordinating radio resources.
• Mode 4 (direct): vehicles communicate over the PC5 interface without relying on network infrastructure.

Mode 4 is what makes C-V2X usable for safety messaging where no cellular coverage exists. The standard describes the benefit of C-V2X as enhanced reliability and range.

The difficulty is that neither technology is a drop-in replacement for the other. DSRC's CSMA/CA is contention-based. Every station listens before it transmits, so a dense stretch of road produces more collisions on the shared channel. The standard's range figures also show how much the environment matters: the urban figure is well below the line-of-sight figure because buildings and other vehicles obstruct the path. Whichever technology is chosen, the application sees the same V2X message model, and the choice is a single constructor parameter (technology: 'C-V2X').

Spectrum itself is a further challenge, because the ITS band is allocated differently by region:

Region	Range	Width
US	5.850 - 5.925 GHz	75 MHz
EU	5.875 - 5.905 GHz	30 MHz
Japan	5.770 - 5.850 GHz	80 MHz

The channel plan runs from channel 172 at 5.860 GHz up to channel 184 at 5.920 GHz in 10 MHz steps. Channel 172 is designated the safety-critical control channel (CCH), and channels 174 to 184 are service channels. Splitting traffic this way keeps urgent safety broadcasts from competing with bulk or commercial services. A device built for one region cannot assume the same frequencies elsewhere. The SDK example sets frequency: 5900 (MHz), so the radio configuration must be validated against the local allocation.

2.4 From Stack to Safe Behaviour: Security, Collision Risk and Cooperation

The specification organises the communication stack as six layers:

Application Layer           V2X Applications
Facilities Layer            Message generation/processing
Security Layer              Authentication, Encryption
Network & Transport Layer   IPv6, TCP/UDP
Access Layer                DSRC (802.11p) or C-V2X
Physical Layer              5.9 GHz radio

Two placements are worth noting. First, the facilities layer is where messages such as BSM and DENM are built and interpreted, so applications work with structured messages rather than radio frames. Second, the security layer sits directly above the access layer and below the network layer, so authentication and encryption apply to everything the applications and facilities produce. A forged hazard warning is as dangerous as a lost one, which is why the standard treats authentication as part of the baseline. The SDK exposes this through a securityLevel setting (the example uses 'high').

On the receiving side, the SDK example ties message handling to a safety decision:

v2x.onV2V((message) => {
  console.log('Received V2V:', message);

  // Collision detection
  if (v2x.detectCollisionRisk(message)) {
    console.warn('Collision warning!');
  }
});

v2x.subscribeToInfrastructure('SIGNAL-001', (spat) => {
  console.log('Traffic signal:', spat.phase, spat.timeRemaining);
});

The first handler turns an incoming neighbour message into a collision-risk judgement. The second shows the V2I pattern, in which a vehicle subscribes to a named piece of infrastructure and receives signal phase and remaining time. The standard lists collision avoidance algorithms in its scope, so the risk check is part of the specified behaviour and not an afterthought.

Cooperation raises the stakes further. A platoon, in which vehicles follow one another at close, coordinated spacing, depends on all members receiving each other's data reliably. The CLI shows how a leader is configured:

wia-comm-003 platoon --mode leader --max-vehicles 5 --spacing 10m

The same tool provides the checks operators need in the field. measure-latency --target VEH-789 --count 100 samples round-trip behaviour against a peer, test-rsu --rsu-id RSU-001 verifies a roadside connection, and monitor --type V2V --filter collision-warning watches live safety traffic. Latency targets such as "<10 ms" are only meaningful if they can be measured, and the tooling makes that measurement routine.

Summary

2.5 Summary and Bridge to the Next Chapter

The challenges in this chapter come down to reconciling differences. The four communication modes (V2V, V2I, V2P and V2N) place different demands on timing and reliability. The five message types run from 10 Hz safety beacons with a latency under 10 ms to a 1 Hz MAP broadcast with a 500 ms allowance. Two radio families, DSRC with CSMA/CA contention and C-V2X with network-assisted Mode 3 and direct PC5 Mode 4, must present one application model. Regional spectrum allocations of 75 MHz, 30 MHz and 80 MHz mean the same device cannot assume the same channels everywhere. Because the vehicle broadcasts its position continuously, security and privacy are baseline requirements.

The specification answers these differences by keeping the message set small and fixed, stating performance targets next to each format, layering the stack so that security covers every message, and hiding the radio choice behind a single technology setting. A collision-risk check, an infrastructure subscription and platoon parameters then let applications act on the data.

These challenges set up the next chapter, which moves from the problems to the concrete foundations: how the message envelopes (BSM, CAM, DENM, SPaT and MAP) are structured, how the access technologies carry them, and how the performance requirements constrain valid encodings.