Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · IoT

RSU

Road Side Unit

IoT →

RSU is a roadside communication infrastructure component that enables Vehicle-to-Everything (V2X) services for direct and network-based communication between vehicles, pedestrians, and traffic systems.

Introduced
Rel-14
Where
Services › IMS
Specifications
13 specs
Also in
Radio Access Network
RSU Description Purpose What changed Neighbours Detected Changes Specifications

Description

A Road Side Unit (RSU) is a critical element in Cellular Vehicle-to-Everything (C-V2X) ecosystems, standardized by 3GPP to support intelligent transportation systems (ITS). It is typically installed at roadside locations such as intersections, highways, or parking areas, and acts as a communication hub. RSUs operate using both direct communication (PC5 interface) and network-based communication (Uu interface) to exchange messages with vehicles (V2V), pedestrians (V2P), infrastructure (V2I), and networks (V2N).

Architecturally, an RSU consists of hardware and software components including processing units, memory, wireless communication modules (supporting LTE or NR), sensors (e.g., cameras, radar), and backhaul connectivity (e.g., fiber, wireless). It runs applications for traffic management, safety alerts, and data aggregation. RSUs use protocols defined in 3GPP specs, such as the V2X application layer for message formats (e.g., Cooperative Awareness Messages, Decentralized Environmental Notification Messages) and access stratum protocols for radio transmission.

How it works: RSUs broadcast safety-related information (e.g., traffic light status, road hazard warnings) to nearby vehicles via PC5 sidelink communication, which operates in dedicated ITS spectrum bands like 5.9 GHz. They also relay data to central traffic management systems via the Uu interface using cellular networks. Key functions include message forwarding, location-based services, and data caching. For instance, an RSU can detect an accident via sensors and immediately disseminate warnings to approaching vehicles, reducing collision risks.

In the network, RSUs integrate with V2X application servers, edge computing platforms, and core network functions. They support low-latency communication critical for real-time safety applications. Advanced RSUs in later 3GPP releases may incorporate MEC (Multi-access Edge Computing) capabilities to process data locally, minimizing latency. Their role extends to supporting autonomous driving by providing high-definition maps and environmental data, making them indispensable for future transportation networks.

Purpose & Motivation

RSUs were developed to address the growing need for enhanced road safety, traffic efficiency, and support for autonomous vehicles. Traditional transportation systems relied on passive infrastructure with limited communication, leading to high accident rates and congestion. RSUs enable proactive, connected environments where vehicles and infrastructure share real-time information to prevent accidents and optimize traffic flow.

The creation of RSUs within 3GPP standards was motivated by the evolution of V2X communication from dedicated short-range communication (DSRC) to cellular-based solutions. Starting in Release 14, 3GPP introduced C-V2X to leverage existing cellular networks for broader coverage and reliability. RSUs solve limitations of ad-hoc vehicle networks by providing fixed, powered nodes that ensure continuous service availability, extended communication range, and integration with network services.

Historically, early ITS systems lacked interoperability and scalability. RSUs standardized by 3GPP provide a unified framework for global deployment, supporting both safety and non-safety applications like platooning and intersection management. They address challenges such as non-line-of-sight awareness and network congestion by acting as reliable intermediaries, ultimately contributing to the vision of smart cities and reduced road fatalities.

What changed in its specifications

The latest release-to-release comparison of specifications that define RSU. Each summary describes the whole specification, not only this term.

TS 22.186Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 22.186: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 22.186 →
TS 22.886Rel-15 → Rel-16

Remote driving, extended sensors, QoS estimation, service flows for platooning and automated driving, and MNO interactions.

Full comparison in TS 22.886 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 1 change
  • RSU Implementation Options and Deployment Use Case TS 23.287CR0127

Defining Specifications

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

SpecificationTitleRelease
TS 22.185 vj00 LTE Support for V2X Services Requirements Rel-19 read
TS 22.186 vj10 Service requirements for V2X scenarios in 3GPP systems Rel-19 read
TR 22.885 ve00 LTE support for V2X services Rel-14 read
TS 22.886 vg20 eV2X Use Cases and Requirements Rel-16 read
TS 23.285 vj00 V2X Architecture Enhancements for LTE Rel-19 read
TS 23.287 vk00 5G V2X Architecture Enhancements Rel-20 read
TR 23.785 ve00 Architecture enhancements for LTE V2X services Rel-14 read
TS 23.795 vg10 V2X Application Architecture Study Rel-16 read
TR 26.985 vj00 Media Handling for Advanced V2X Services Rel-19 read
TS 33.885 ve10 Security Study for V2X Services Rel-14 read
TR 37.885 vf30 Study on V2X Evaluation Methodology for LTE/NR Rel-15 read
TR 37.985 vj00 Overview of V2X features in LTE and NR Rel-19 read
TR 38.913 vj00 Next Gen Access Tech Scenarios & Requirements Rel-19 read