Description
UE Radio Capability Signalling optimization (RACS) is a network feature designed to minimize the signaling overhead associated with transmitting a User Equipment's (UE) radio capability information. A UE's radio capabilities are a comprehensive set of parameters detailing its supported features, bands, frequency ranges, and technical limits (e.g., maximum number of carriers, supported modulation schemes). Traditionally, this information, contained in the UE Radio Capability ID (UECapabilityInformation), is sent from the UE to the network during initial registration and potentially during each connection setup or inter-RAT mobility, leading to significant signaling load, especially for large-capability containers in advanced UEs.
RACS works by enabling the Core Network (specifically the Access and Mobility Management Function, AMF, in 5GC, or the MME in EPS) to store the UE's radio capability information after the first successful retrieval. The network assigns a UE Radio Capability ID to this stored information. Subsequently, instead of the UE transmitting the full capability set, the network can signal using this much shorter ID. The AMF/MME provides this ID to the Radio Access Network (RAN) node (gNB or eNB). If the RAN node does not have the corresponding capability data cached locally, it can request the full information from the core network using the ID.
The architecture involves coordination between the UE, RAN, and Core Network. Key signaling messages are modified to carry the UE Radio Capability ID. For example, in 5G, the AMF includes the `UE Radio Capability ID` in the `INITIAL CONTEXT SETUP REQUEST` or `UE RADIO CAPABILITY CHECK REQUEST` messages to the gNB. The gNB checks its local storage. If the data is missing or potentially outdated (e.g., after a software update), the gNB can request the AMF to provide the full `UE Radio Capability Information` via a retrieval procedure. The network also manages the lifecycle of this stored data, including mechanisms to detect when capabilities might have changed (e.g., via indication from the UE or a timer-based refresh).
This optimization significantly reduces the size of signaling messages on the radio interface (Uu) and the NG/E1 interfaces. It is particularly beneficial for latency-sensitive procedures like connection resumption from RRC_INACTIVE state and for UEs with extensive capability lists, such as those supporting many NR and LTE bands, carrier aggregation combinations, and features like dual connectivity. By minimizing the amount of data transferred, RACS improves connection setup times, reduces UE battery consumption for signaling, and decreases the processing load on network nodes.
Purpose & Motivation
RACS was introduced to address the growing signaling overhead problem caused by increasingly complex UE radio capabilities. As 3GPP standards evolved through LTE-Advanced and into 5G, the number of supported frequency bands, carrier aggregation combinations, and optional features exploded. Transmitting the full, verbose `UECapabilityInformation` message during every relevant procedure became a significant source of latency and consumed valuable radio resources.
The primary problem RACS solves is the inefficient repetition of large, static data sets. A UE's core radio capabilities change infrequently, typically only after a software update or a major hardware change. Transmitting this multi-kilobyte block repeatedly was wasteful. Prior to RACS, the network had no standardized, efficient way to avoid this repetition, leading to longer call setup times and increased signaling congestion, especially in dense networks.
Its creation was motivated by the need to optimize network performance for massive IoT deployments and enhanced mobile broadband scenarios where fast connection establishment is critical. By shifting to an ID-based model, RACS aligns with general network optimization principles of caching and indirection. It also future-proofs the system for even more complex capability definitions in beyond-5G systems, ensuring that signaling scales efficiently regardless of how detailed UE capabilities become.
Key Features
- Storage of UE radio capabilities in the core network (AMF/MME)
- Use of a compact UE Radio Capability ID for signaling instead of full data
- On-demand retrieval of full capabilities from core network by RAN
- Reduction in radio interface (Uu) signaling message size
- Support for detection of outdated capability information
- Applicability to connection setup, mobility, and resumption procedures
Evolution Across Releases
Initially introduced for EPS (LTE) as an optimization where the MME could store UE radio access capabilities and provide a UE Radio Capability ID to the eNB. The eNB could then use this ID to request the full capabilities from the MME if not locally available, reducing the need for the UE to transmit them over the air repeatedly.
Re-defined and enhanced for the 5G System (5GS). The AMF assumes the role of storing UE radio capabilities for both NR and E-UTRAN. The feature was integrated into the 5G service-based architecture, with procedures defined for the AMF to provide the UE Radio Capability ID to the NG-RAN via the NGAP interface.
Enhanced with the 'UE Radio Capability for Paging' feature, allowing the AMF to provide a separate, possibly restricted, set of radio capabilities to the RAN for paging optimization. Improved procedures for handling capability mismatch and updates.
Further refinements for efficiency, including optimizations for the retrieval procedure and enhanced interaction with other features like support for RedCap (Reduced Capability) UEs, ensuring the signaling optimization works effectively for diverse device types.
Defining Specifications
| Specification | Title |
|---|---|
| TS 23.003 | 3GPP TS 23.003 |
| TS 23.401 | 3GPP TS 23.401 |
| TS 23.417 | 3GPP TS 23.417 |
| TS 23.501 | 3GPP TS 23.501 |
| TS 23.517 | 3GPP TS 23.517 |
| TS 24.301 | 3GPP TS 24.301 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 24.523 | 3GPP TS 24.523 |
| TS 24.524 | 3GPP TS 24.524 |
| TS 29.421 | 3GPP TS 29.421 |
| TS 29.675 | 3GPP TS 29.675 |
| TS 36.413 | 3GPP TR 36.413 |