NR sidelink lets nearby devices exchange data directly, without sending it through a base station. It was created for advanced vehicle communication, and later releases opened it to power-limited devices, coverage extension and commercial uses.
Two interfaces matter throughout. UEs talk to each other over the PC5 interface, which is the direct UE-to-UE sidelink interface. A UE talks to the gNB over Uu. This article follows how TS 38.331 (RRC) and TS 38.300 (stage-2 description) changed from Release 16 to Release 19. Sidelink positioning and core-network aspects are out of scope.
PC5 (UE to UE) Uu (UE to gNB)
The diagram is a map of the article: it shows how the topology grows from direct PC5 links to relays, multi-path and relay chains.
Release 16: a first NR sidelink
LTE-based V2X from Releases 14 and 15 was judged sufficient only for basic road safety. Advanced use cases were identified in four groups: platooning, extended sensors, advanced driving and remote driving. These called for a new NR sidelink.
Release 16 therefore defined UEs that communicate directly over PC5 using unicast, groupcast and broadcast, while the network can still control them over Uu.
- Two resource allocation modes. In mode 1 the network schedules sidelink resources, including configured grants. In mode 2 the UE selects resources itself from configured or pre-configured pools.
- Physical layer procedures. UEs can exchange data and control on dedicated sidelink channels, use feedback for unicast and groupcast, report channel state and apply sidelink power control.
- PC5-RRC signalling. This is the Radio Resource Control (RRC) signalling carried between peer UEs over PC5. Peer UEs can configure sidelink radio bearers, exchange capabilities and handle sidelink radio link failure between themselves.
- Synchronization. UEs can synchronize even without GNSS and without a base station, by selecting a synchronization reference and sending sidelink synchronization signals.
- Congestion control. A UE can measure how busy the sidelink channel is and report it, so that transmission parameters can depend on how busy the channel is.
On the network side, the gNB can configure sidelink for idle and inactive UEs through system information and for connected UEs through dedicated signalling.
Release 17: power saving and coverage
The Release 16 design assumed always-on vehicle UEs with ample battery.
Power-constrained UEs, such as vulnerable road users and public safety or commercial devices, needed ways to save energy.
Busy channels also limited reliability and latency.
Separately, coverage was a problem. A study found that two relaying approaches were feasible, one forwarding below PDCP and one forwarding IP traffic, and recommended NR sidelink relay for coverage extension. The earlier LTE-based UE-to-network relay could not serve NR.
- Power-saving resource allocation. Mode 2 UEs can use partial sensing, which means sensing only part of the resources, or random resource selection, with the allowed scheme configured per resource pool. This lets a UE sense less and spend less energy.
- Inter-UE coordination. One UE can send resource information to a peer, which takes it into account for its own transmission. This improves reliability and latency when the channel is busy.
- Sidelink DRX. Sidelink UEs can use on and off durations to save power. It applies to unicast, groupcast and broadcast, and in connected state it can be aligned with Uu DRX.
- Layer-2 (L2) UE-to-Network relay. A Remote UE is a UE that reaches the network through another UE, and that other UE is the Relay UE. A Remote UE reaches the gNB through a Relay UE and keeps its own connection to the gNB. The Relay UE forwards traffic below PDCP, and the Sidelink Relay Adaptation Protocol (SRAP) sublayer lets it map the Remote UE's traffic onto relay channels. SRAP is the adaptation layer used for bearer mapping and Remote UE identification.
- Relay discovery, selection and path switch. A Remote UE can discover relays and choose either a cell or a relay using configured thresholds. The network can use new measurement events to move a UE between a direct path and an indirect path.
A Remote UE can also obtain system information and paging through its relay, and set up, resume or re-establish its connection via the relay.
Release 18: more relay types and more spectrum
Release 17 relaying covered only UE-to-network relay. In Layer-2 relay, service continuity was limited to switching between direct and indirect paths within one gNB.
Release 18 therefore added UE-to-UE relay, wider service continuity and multi-path relay, aiming at coverage extension, reliability and throughput.
Separately, NR sidelink had been built for V2X, while commercial use cases need higher data rates and new carrier frequencies.
- Layer-2 UE-to-UE relay. Two Remote UEs can communicate through a relay UE, with end-to-end sidelink bearers configured over per-hop PC5 links. This extends sidelink coverage without relying on uplink and downlink. Discovery and selection work for both relay architectures.
- Multi-path. A connected UE can use one direct Uu path plus one indirect path to the same gNB. The indirect path runs either over a PC5 relay or over a non-3GPP connection. The UE can add or change the indirect path and report its failure, and split bearers can use both paths. For a split bearer, the primary path is the one used for uplink data by default, and it can be placed on the indirect path.
- Enhanced service continuity. A Layer-2 Remote UE can switch between gNBs and between relays, including indirect-to-indirect path switching. A new measurement event compares the serving relay against candidate relays.
- Sidelink carrier aggregation. A UE can use several sidelink carriers in mode 2, where the UE selects resources itself, with carrier selection, adding and releasing of carriers, and a total transmit power limit. This raises the sidelink data rate.
- Unlicensed spectrum. Sidelink can run in shared spectrum for both mode 1 and mode 2. Listen before talk means a device senses the channel and transmits only if it is free. The ITS band is limited to safety applications, so shared spectrum makes sidelink usable by commercial devices.
LTE and NR sidelink can also coexist dynamically on the same carrier through overlapping resource pools, so devices of both technologies do not harm each other.
Sidelink operation in FR2 was only studied in this release.
Release 19: relay chains
A single sidelink hop has limited range, so single-hop relays from Releases 17 and 18 have limited applicability. Release 19 specifies multi-hop Layer-2 UE-to-Network relay.
Two terms are needed. A parent is the next hop of a UE in the direction of the network. A child is the next hop of a relay in the direction of the Remote UE, and it can be the Remote UE or another relay.
- Relay chain. Up to three relay UEs can serve one Remote UE: a First relay next to the Remote UE, optionally an Intermediate relay, and a Last relay holding the Uu connection to the network. Each relay keeps one PC5 connection to its parent and one to each child.
- Discovery and selection. Relays announce multi-hop service when system information enables it. Last and intermediate relays check threshold conditions before sending discovery messages. A Remote UE can tell single-hop from multi-hop relays by hop type and can prefer relays by their RRC state.
- Hop-by-hop forwarding. A relay can be configured with SRAP entries for each indirectly connected child. It maps ingress traffic to egress RLC channels on the next PC5 hop in uplink and downlink, and the Last relay terminates the Uu relay channels.
- Control plane. An intermediate relay can trigger RRC connection establishment or resumption when a message arrives from a child relay, and can pass system information and paging requests upstream. If a relay reselects, loses its parent link or suffers a Uu failure, it informs its children with a notification message. The Remote UE's connection timers are scaled by hop count.
- Path switching. Within one gNB, a Remote UE can switch between multi-hop indirect, single-hop indirect and direct paths. For a multi-hop target path, all relays on it must be connected, and the gNB reconfigures every relay on that path.
UEs signal multi-hop capabilities, and relay behaviour can come from dedicated configuration, system information or preconfiguration.
How the role of NR sidelink changed
In Release 16 a UE could reach only other UEs within direct PC5 range, with the network able to control it. By Release 19 a UE can reach the gNB or another UE through up to three relays, or over direct and indirect paths at once.
What remains open
Sidelink operation in FR2 was only studied in Release 18, so no specification support exists yet. Path switching with multi-hop paths is limited to one gNB. Signalling for relay and Remote UE authorization is waiting on the core-network conclusions, in both Release 18 and Release 19.
Reference
Work items, clauses and information elements are generated from the specification data. The work-item objectives handled outside these specifications are quoted from the work item descriptions, which assign them to another working group or to a study.
Work items and where their changes appear
| Release | Work item | Changes found in | Note |
|---|---|---|---|
| Release 16 | 5G_V2X_NRSL5G V2X with NR sidelink · WID RP-200129 | TS 38.300, TS 38.331 | |
| Release 17 | NR_SL_enhNR sidelink enhancement · WID RP-202846 | TS 38.300, TS 38.331 | |
| Release 17 | NR_SL_relayNR sidelink relay · WID RP-212819 | TS 38.300, TS 38.331 | |
| Release 17 | NR_LTE_V2X_PC5_combosNR/LTE V2X PC5 band combinations · WID RP-213297 | None | Radio requirements (RAN4); no RRC or stage-2 content is expected |
| Release 18 | NR_SL_enh2NR sidelink evolution · WID RP-232789 | TS 38.300, TS 38.331 | |
| Release 18 | NR_SL_relay_enhNR sidelink relay enhancements · WID RP-232972 | TS 38.300, TS 38.331 | |
| Release 18 | NR_LTE_V2X_PC5_combos_R18NR/LTE V2X band combinations, Release 18 · WID RP-230390 | None | Radio requirements (RAN4); no RRC or stage-2 content is expected |
| Release 19 | NR_SL_relay_multihopNR sidelink multi-hop relay · WID RP-250188 | TS 38.300, TS 38.331 | |
| Release 19 | NR_SL_intraB_CA_ITSNR sidelink intra-band carrier aggregation in the ITS band · WID RP-250997 | None | Radio requirements (RAN4); no RRC or stage-2 content is expected |
Work-item objectives handled outside these specifications
| Release | Work item | Objective | Where it belongs |
|---|---|---|---|
| Release 16 | 5G_V2X_NRSL | Network solutions to support NR sidelink: V2X service authorization [RAN3] | RAN3 (network interfaces) |
| Release 16 | 5G_V2X_NRSL | F1 signalling for support of NR V2X [RAN3] | RAN3 (network interfaces) |
| Release 16 | 5G_V2X_NRSL | Resource coordination between NG-RAN nodes for V2X sidelink communication [RAN3] | RAN3 (network interfaces) |
| Release 16 | 5G_V2X_NRSL | UE Tx and Rx RF requirement [RAN4] | RAN4 (RF and RRM requirements) |
| Release 16 | 5G_V2X_NRSL | RRM core requirement [RAN4] | RAN4 (RF and RRM requirements) |
| Release 17 | NR_SL_enh | Support of new sidelink frequency bands for single-carrier operations [RAN4] | RAN4 (RF and RRM requirements) |
| Release 17 | NR_SL_enh | UE Tx and Rx RF requirement for the new features introduced in this WI [RAN4] | RAN4 (RF and RRM requirements) |
| Release 17 | NR_SL_enh | UE RRM core requirement for the new features introduced in this WI [RAN4] | RAN4 (RF and RRM requirements) |
| Release 17 | NR_SL_relay | Specify mechanisms for Relay and Remote UE authorization for L3 and L2 relaying [RAN3] | RAN3 (network interfaces) |
| Release 17 | NR_SL_relay | Define additional RRM performance requirements for Relay discovery and (re)selection [RAN4] | RAN4 (RF and RRM requirements) |
| Release 18 | NR_SL_enh2 | Study enhanced sidelink operation on FR2 licensed spectrum (sidelink beam management) [RAN1, RAN2] | study only |
| Release 18 | NR_SL_relay_enh | Specify RRM core requirements for relay discovery and (re)selection in UE-to-UE relay [RAN4] | RAN4 (RF and RRM requirements) |
| Release 18 | NR_SL_relay_enh | Signalling support for Relay and remote UE authorization if SA2 concludes it is needed [RAN3] | RAN3 (network interfaces) |
| Release 18 | NR_SL_relay_enh | Define RRM performance requirements for relay discovery and (re)selection in UE-to-UE relay [RAN4] | RAN4 (RF and RRM requirements) |
| Release 19 | NR_SL_relay_multihop | Signalling support for relay UEs and remote UE authorization if SA2 concludes it is needed [RAN3] | RAN3 (network interfaces) |
Clauses and information elements by release
Release 16
| Specification | Work item | New clauses | Changed clauses | New IEs and messages | Extended IEs |
|---|---|---|---|---|---|
| TS 38.331 | 5G_V2X_NRSL | 63
| 23
| 63
| 14
|
| TS 38.300 | 5G_V2X_NRSL | 21
| 4
| None | None |
Release 17
| Specification | Work item | New clauses | Changed clauses | New IEs and messages | Extended IEs |
|---|---|---|---|---|---|
| TS 38.331 | NR_SL_relay | 32
| 58
| 17
| 22
|
| TS 38.331 | NR_SL_enh | 6
| 17
| 11
| 13
|
| TS 38.331 | Other NR sidelink changes | None | 3
| None | None |
| TS 38.300 | NR_SL_relay | 15
| 1
| None | None |
| TS 38.300 | NR_SL_enh | 7
| 5
| None | None |
Release 18
| Specification | Work item | New clauses | Changed clauses | New IEs and messages | Extended IEs |
|---|---|---|---|---|---|
| TS 38.331 | NR_SL_relay_enh | 32
| 61
| 11
| 18
|
| TS 38.331 | NR_SL_enh2 | 10
| 16
| 4
| 23
|
| TS 38.331 | Other NR sidelink changes | None | None | None | None |
| TS 38.300 | NR_SL_relay_enh | 3
| 8
| None | None |
| TS 38.300 | NR_SL_enh2 | 7
| 4
| None | None |
| TS 38.300 | Other NR sidelink changes | None | 1
| None | None |
Release 19
| Specification | Work item | New clauses | Changed clauses | New IEs and messages | Extended IEs |
|---|---|---|---|---|---|
| TS 38.331 | NR_SL_relay_multihop | 3
| 46
| 3
| 12
|
| TS 38.331 | Other NR sidelink changes | None | 1
| None | None |
| TS 38.300 | NR_SL_relay_multihop | None | 13
| None | None |
Abbreviations
DRX | Discontinuous Reception | RAN2 | 3GPP radio protocols working group |
F1 | Interface between the central and distributed units of a gNB | RAN3 | 3GPP radio network interfaces working group |
FR2 | Frequency Range 2 (millimetre wave) | RAN4 | 3GPP radio performance and requirements working group |
gNB | NR base station | RF | Radio Frequency |
GNSS | Global Navigation Satellite System | RLC | Radio Link Control |
IP | Internet Protocol | RRC | Radio Resource Control |
ITS | Intelligent Transport Systems | RRM | Radio Resource Management |
L2 | Layer 2 | Rx | Receive |
L3 | Layer 3 | SA2 | 3GPP architecture working group |
LTE | Long Term Evolution | SRAP | Sidelink Relay Adaptation Protocol |
NG-RAN | Next Generation Radio Access Network | TS | Technical Specification |
NR | New Radio | Tx | Transmit |
PC5 | Radio interface between two UEs (sidelink) | UE | User Equipment |
PC5-RRC | Radio Resource Control signalling between two UEs over PC5 | Uu | Radio interface between a UE and the base station |
PDCP | Packet Data Convergence Protocol | V2X | Vehicle-to-Everything |
RAN1 | 3GPP physical layer working group | WI | Work Item |