Description
Con-current operation is a 5G NR capability defined in 3GPP TS 38.101 and tested per TS 38.521, with additional specifications in TS 38.785 and TS 38.786. It refers to the simultaneous transmission and reception of the sidelink interface (PC5) and the Uu interface (the radio link between UE and gNB). In other words, a UE can communicate directly with other UEs over sidelink while simultaneously maintaining a cellular connection to the network over Uu. The operation is agnostic of the service used on each interface — the UE does not need to be running a specific application or service type for the capability to apply.
Architecturally, con-current operation involves a UE with the RF and baseband capability to support two active radio links at once. The sidelink interface is used for direct device-to-device communication, most prominently in V2X (vehicle-to-everything) scenarios, public safety, and other proximity services. The Uu interface connects the UE to the gNB for normal cellular services. Supporting both simultaneously requires careful RF design to manage self-interference, since the UE's own sidelink transmission can desensitize its Uu reception and vice versa. It also requires baseband processing capable of handling two concurrent protocol stacks.
The standard distinguishes between TDM (time-division multiplexing) and FDM (frequency-division multiplexing) modes. In TDM mode, sidelink and Uu transmissions are separated in time, which relaxes some RF requirements. In FDM mode, they occur simultaneously in different frequency resources, which places stricter demands on the UE's filtering and isolation. Con-current operation, as defined, applies irrespective of which mode is used, meaning the capability and its associated requirements cover both. This makes the definition broad and technology-neutral with respect to the multiplexing scheme.
Con-current operation is important because many advanced use cases require both direct and network connectivity at the same time. A vehicle, for example, may need to exchange cooperative awareness messages with nearby vehicles over sidelink while also receiving traffic information or remote commands from the network over Uu. Without con-current operation, the UE would have to interrupt one link to use the other, degrading service continuity and latency. The capability therefore underpins seamless V2X and other mission-critical services.
The definition of con-current operation has evolved in its wording across releases. It was introduced in Rel-16 with a definition that described simultaneous sidelink and Uu operation agnostic of service. In Rel-17, the wording was revised to explicitly state that the operation applies irrespective of TDM mode and FDM mode, clarifying the scope. In Rel-19, the wording changed again, removing the explicit TDM/FDM clause and returning to a more concise formulation. These revisions reflect ongoing refinement of how the requirement is expressed as the technology and its test specifications matured.
Purpose & Motivation
Con-current operation exists to enable UEs to use sidelink and cellular connectivity at the same time, which is essential for advanced services such as V2X, public safety, and industrial IoT. Before this capability was standardized, a UE supporting sidelink typically had to coordinate or alternate between sidelink and Uu usage, because simultaneous operation placed demanding RF and baseband requirements that were not formally specified. This limited the practicality of use cases where both links must be active continuously.
The motivation for defining con-current operation in Rel-16 was the maturation of NR sidelink, particularly for V2X. Vehicles need to broadcast safety messages to nearby vehicles over sidelink while remaining connected to the network for traffic management, remote assistance, and infotainment. Interrupting either link to use the other would introduce latency and reduce reliability, which is unacceptable for safety-critical applications. By standardizing con-current operation, 3GPP provided a clear framework for UE vendors to design and test devices that can sustain both links.
The definition's evolution reflects the need to make the requirement precise and testable. The Rel-17 revision explicitly addressed TDM and FDM modes, clarifying that the capability covers both multiplexing approaches and thereby guiding test specifications. The Rel-19 revision simplified the wording, likely reflecting a consolidated understanding after several releases of implementation experience. Throughout, the core principle has remained: a UE must be able to transmit and receive on sidelink and Uu simultaneously, regardless of the service, to support seamless advanced connectivity.
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 Con-current operation, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.101 vj40 | UE Radio Transmission and Reception; Satellite Access | Rel-19 read |
| TS 38.521 vj10 | UE Conformance Spec for NR Satellite Access | Rel-19 read |
| TR 38.785 vh00 | UE radio transmission for enhanced NR sidelink | Rel-17 read |
| TR 38.786 vi20 | Technical Report for NR Sidelink Evolution | Rel-18 read |