Description
V2I Service (Vehicle-to-Infrastructure Service) is one of the service types defined under the broader Vehicle-to-Everything (V2X) framework in 3GPP. It specifically describes communication where one party is a User Equipment (UE) — typically a vehicle-mounted or handheld device — and the other party is a Road Side Unit (RSU), with both parties using V2I applications. The RSU is an infrastructure node deployed along roads or at strategic locations that can communicate with passing vehicles to exchange information such as traffic conditions, signal phases, hazard warnings, or local map data.
In the 3GPP architecture, V2I Service is realized using V2X communication capabilities. The UE and RSU communicate either directly over the PC5 sidelink interface or indirectly through network infrastructure (e.g., via Uu interface and core network entities), depending on deployment and coverage. The RSU may be a UE-type RSU or an eNB/gNB-type RSU, and it can be integrated with traffic management systems. V2I applications run on both the vehicle side and the infrastructure side, and the service is supported by V2X control and user plane procedures defined in specifications such as 22.885, 23.785, and 26.985.
V2I Service is important because it enables vehicles to interact with the road environment, improving safety and traffic efficiency. Examples include traffic signal priority for emergency vehicles, intersection collision warnings, roadwork alerts, and speed limit notifications. By leveraging cellular V2X (C-V2X) technology, V2I can benefit from network coverage, QoS management, and security mechanisms provided by 3GPP networks, while also supporting direct sidelink communication when low latency is required.
The service is closely related to other V2X service types: V2V (Vehicle-to-Vehicle), V2P (Vehicle-to-Pedestrian), and V2N (Vehicle-to-Network). Together they form a comprehensive framework for connected vehicles. V2I specifically focuses on the vehicle-to-infrastructure link, which is often critical for coordinated traffic management and safety applications that require knowledge of the road infrastructure.
From Release 14 through Release 19, the definition of V2I Service has remained unchanged in the quoted 3GPP texts, indicating a stable concept. The service continues to be referenced in V2X specifications as the basis for infrastructure-based applications, and it evolves alongside enhancements to C-V2X, such as improved sidelink capabilities in later releases.
Purpose & Motivation
V2I Service exists to enable vehicles to communicate with roadside infrastructure, addressing the need for coordinated safety and traffic efficiency applications that cannot be achieved by vehicle-to-vehicle communication alone. Infrastructure nodes can provide a global view of traffic conditions, signal states, and road hazards, complementing the local awareness of individual vehicles.
Before standardized V2I, infrastructure-to-vehicle communication relied on proprietary or non-cellular technologies with limited integration into cellular networks. 3GPP introduced V2I as part of the V2X framework in Release 14 to leverage cellular technology for reliable, secure, and QoS-aware communication between vehicles and infrastructure. This allows operators and road authorities to deploy V2I applications using licensed spectrum and standard network procedures.
The service solves problems such as intersection collision avoidance, traffic signal optimization, and dissemination of road condition warnings. By defining V2I as a distinct service type with clear roles (UE and RSU), 3GPP provides a common basis for interoperability and deployment across regions and vendors.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference V2I Service, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.885 ve00 | LTE Support for V2X Services | Rel-14 read |
| TR 23.785 ve00 | Architecture enhancements for LTE V2X services | Rel-14 read |
| TR 26.985 vj00 | Media Handling for Advanced V2X Services | Rel-19 read |