RC

Rate Control Procedure Acknowledgement

Protocol →
Introduced in Rel-5 Also in: Services, Management, Testing

RC is a control plane message used on the Iu interface in UMTS networks to acknowledge the receipt and processing of a Rate Control command as part of Radio Access Bearer management.

Category
Protocol
Introduced
Rel-5
Where
Core Network › Legacy Core
Also touches
3 segments
Specifications
11 specs
RC Description Purpose Related Classification Detected Changes Specifications

Description

The Rate Control Procedure Acknowledgement (RC) is a specific control message within the Radio Access Network Application Part (RANAP) protocol, which operates over the Iu interface connecting the Radio Network Controller (RNC) and the Core Network (CN) in a 3GPP UMTS network. The Iu interface is split into Iu-CS (Circuit Switched) for voice and Iu-PS (Packet Switched) for data; RC messages are relevant to both domains for managing bearer rates. The RC acknowledgement is sent in response to a RANAP 'Rate Control' message, which is initiated by the CN to request a change in the maximum allowed bit rate for an existing Radio Access Bearer (RAB). This forms part of the RAB modification procedure.

Operationally, when the CN decides to modify the bit rate of an active user session (e.g., due to changing service requirements, network congestion, or subscriber policy), it sends a RANAP Rate Control message to the serving RNC. This message contains the new requested maximum bit rate for uplink and/or downlink. Upon receiving this, the RNC performs admission control and radio resource calculations to determine if the new rate can be supported. If the RNC accepts the request, it will reconfigure the radio bearer with the UE and then send back an RC acknowledgement message to the CN, confirming the successful application of the new rate. If the request cannot be accommodated, the RNC would respond with a Rate Control Failure message instead. The RC acknowledgement itself is a simple confirmation but triggers subsequent actions in both entities to enforce the new data rate limits.

The RC procedure is crucial for dynamic quality of service (QoS) management in UMTS. It allows the network to adapt to changing conditions in real-time, optimizing resource utilization and user experience. The procedure relies on the reliable transport provided by the Signalling Connection Control Part (SCCP) and Message Transfer Part (MTP) layers beneath RANAP. While the term 'RC' specifically denotes the acknowledgement message, the overall 'Rate Control Procedure' encompasses the request, the RNC's internal processing, the radio reconfiguration with the UE, and the final acknowledgement or failure notification, ensuring synchronized QoS states between the RAN and CN.

Purpose & Motivation

The Rate Control Procedure and its Acknowledgement (RC) were created to enable dynamic, in-session adjustment of data rates for user connections in UMTS networks. Prior cellular systems like GSM/GPRS had more static bearer management, where data rates were largely set at connection establishment. UMTS introduced richer multimedia services with variable bandwidth demands, necessitating a mechanism for the core network to request rate changes from the RAN during an active session. This solved the problem of inefficient fixed resource allocation, allowing network resources to be matched to actual service needs and congestion levels.

The introduction of the RC procedure in Release 5 was closely tied to the development of the Iu interface and the RANAP protocol, which separated RAN and CN functionalities. It addressed the need for coordinated QoS management between the service-aware core network (which knows subscriber profiles and service requirements) and the radio-resource-aware RNC (which knows cell load and radio conditions). The RC acknowledgement provides the necessary confirmation to ensure both sides maintain a consistent view of the active bearer's capabilities, preventing service interruptions or billing discrepancies. This dynamic control was particularly important for early 3G data services and video telephony, enabling smooth adaptation between different quality levels.

Classification

Part ofRANAP
Related approachesQoS

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-5, normative work from Rel-15.

Rel-15 2 changes

In Release 15, the Rate Control Procedure Acknowledgement (RC) function was introduced as part of the new, dynamic "plug and play" Network Composition procedure. This uniform procedure enables the integration and interworking of heterogeneous networks, such as ad-hoc networks and PANs, by defining a set of phases for Composition and Decomposition processes. The RC function specifically relates to the control and provisioning of resources, where usage, control, and access provisioning to a given resource can be performed by different Composition Capable Networks (CCNs) according to a negotiated Composition Agreement (CA).

  • Upgrade to version under change control TS 32.856
  • Approved by plenary – Rel-15 spec under change control TS 37.941
Rel-16 1 change

In Release 16, the new RC function was introduced as part of the broader, dynamic Network Composition procedure, enabling a uniform method for control plane cooperation between Composition Capable Networks (CCNs). This procedure standardized the acknowledgment for delegating or sharing control of specific resources like QoS, mobility, or AAA functionality between networks. It provided a flexible framework for these acknowledgments, allowing the phases of the Composition Process to be adapted or omitted based on the specific type of network integration being established.

  • CR to TR 37.941: Corrections to TRP measurement procedures TS 37.941CR0020
Rel-17 3 changes

In Release 17, the Rate Control (RC) procedure acknowledgement function was enhanced through clarifications and improvements to its technical description. The updates specifically refined the RC descriptions within the core procedural clauses and the performance test descriptions for various radio frequency bands. These modifications aimed to provide a more precise and comprehensive specification of the RC function's operation and verification.

  • CR to TR 37.941: Improvement of RC description in clause 2 and sub-clause 7.8 TS 37.941CR0031
  • CR to TR 37.941: Improvement of RC description in subclause 7.8, 8.8, 11.2.5, 11.3.5 and 11.4.5 TS 37.941CR0043
  • Under change control TS 38.161
Rel-18 5 changes

In Release 18, the Rate Control (RC) procedure saw updates focused on test methodology and alignment. Specifically, the work introduced an alternative RC test method and updated the technical report to reflect harmonized results from laboratory alignment activities. These changes aimed to refine the definition and implementation of the RC procedure for more consistent testing and deployment.

  • CR to TS 38.161 on alternative RC test method TS 38.161CR0013
  • CR to TR 38.870 on Rel-18 RC lab alignment and harmonization outcome TS 38.870CR0010
  • CR to TR 38.870 to update RC TRS definition in 5.22 and 8.6.1.1 TS 38.870CR0011
  • CR to TR 38.870 on updating Rel-18 RC harmonization results TS 38.870CR0013
  • Approved by plenary – Rel-18 spec under change control TS 38.870
Rel-19 2 changes

In Release 19, the new developments for the RC function are not detailed in the provided grounding context. The listed Change Requests pertain to introducing alternate test procedures for TRS and TRP specifically for XR devices, as indicated in the titles for TS38.161 and TR 38.870. The grounding context exclusively discusses the broader Network Composition framework for integrating heterogeneous networks, with no mention of the Rate Control Procedure Acknowledgement or its specific enhancements.

  • CR to TS38.161 for an alternate TRS and TRP test procedure for XR devices TS 38.161CR0025
  • CR to TR 38.870 for an alternate TRP test procedure for XR devices TS 38.870CR0019

Explore further

Broader topics and technologies where RC plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 22.980 vj00 Network Composition Feasibility Study Rel-19
TS 23.048 v1400 Secured Packets for UICC Remote Management Rel-5
TS 26.454 vj00 EVS Codec Mapping for 3G CS Networks Rel-19
TR 26.935 vj00 Speech Codec Performance for Packet Switched Multimedia Rel-19
TS 31.114 v1800 USAT Interpreter Transmission Protocol Rel-8
TS 32.832 va00 Alarm Correlation and Root Cause Analysis Study Rel-10
TS 32.856 vf00 Energy Efficiency Assessment for RAN OAM Rel-15
TR 37.941 vj20 RF Conformance Testing Background for Radiated BS Requirements Rel-19
TR 37.977 vj00 MIMO OTA Test Methodology Rel-19
TS 38.161 vj10 NR UE TRP and TRS Requirements for FR1 Rel-19
TS 38.870 vj20 Enhanced OTA Test Methods for NR FR1 TRP/TRS Rel-19