RFC Indicator

Description

The RFC Indicator (RFCI) is a critical parameter within the 3GPP Radio Access Network (RAN), specifically in the context of the Iu and Iub interfaces for UMTS and the evolved UTRAN. It functions as an index or label that uniquely identifies a predefined set of transport format combinations for a Radio Access Bearer (RAB) or a Radio Bearer (RB). The RFCI is communicated between the Radio Network Controller (RNC) and the User Equipment (UE) during RAB assignment or reconfiguration procedures. It essentially points to a specific row in a Transport Format Combination Set (TFCS) table, which defines the allowable combinations of transport formats for the dedicated transport channels (DCHs) associated with that bearer. This table includes parameters like transport block size, transmission time interval (TTI), and channel coding scheme.

Architecturally, the RFCI is part of the Radio Access Bearer Service (RABs) and Radio Bearer Service (RBs) definitions managed by the Radio Resource Control (RRC) protocol. When the RNC establishes a bearer for a user session, it selects an appropriate RFCI based on the requested QoS profile (e.g., data rate, delay tolerance). This RFCI value is then sent to the UE within RRC signaling messages, such as RADIO BEARER SETUP or RADIO BEARER RECONFIGURATION. The UE uses the received RFCI to locate the corresponding transport format combination set in its configuration, thereby aligning its physical and MAC layer processing with the network's expectations.

The parameter's role is to decouple the detailed, voluminous transport format information from the frequent signaling messages. Instead of transmitting the entire TFCS table repeatedly, only the compact RFCI index is exchanged, significantly reducing signaling overhead. This efficiency is vital for mobility events like handovers or service changes, where bearers must be quickly reconfigured. The RFCI ensures both ends of the radio link have a synchronized understanding of how data blocks are formatted, sized, and timed for transmission, which is fundamental for reliable data transfer and radio resource optimization. Its definition spans multiple 3GPP specifications, including those detailing RANAP (25.413), the Iu interface user plane (25.415), and codec specifications (26.102, 26.202, 26.454) where it relates to configuring the transport for speech and multimedia data.

Purpose & Motivation

The RFCI was introduced to solve the problem of signaling efficiency and unambiguous bearer configuration in 3G UMTS networks. Prior to its standardization, conveying the complete set of transport formats for a bearer during setup or reconfiguration would have required transmitting large, complex parameter sets over the air interface and between network nodes. This would consume valuable radio resources and increase call setup times, negatively impacting user experience and network capacity.

Its creation was motivated by the need for a scalable and flexible mechanism to support a wide variety of services with different QoS requirements, from voice calls to packet-switched data. By using an indicator, the network can pre-define and manage libraries of transport format combinations suited for different service types. The RFCI allows the core network and RNC to request a bearer with specific characteristics, and the RNC to command the UE to use a corresponding pre-negotiated configuration swiftly. This abstraction layer is crucial for dynamic resource management, enabling features like adaptive multi-rate (AMR) codec rate changes or switching between conversational and streaming bearer types without exhaustive re-signaling.

Key Features

• Uniquely identifies a Transport Format Combination Set (TFCS) for a RAB/RB
• Reduces signaling overhead by acting as a compact index instead of transmitting full parameter sets
• Enables synchronized configuration between RNC and UE for reliable data transmission
• Supports dynamic bearer reconfiguration during handover and service change procedures
• Integral part of RRC protocol messages for radio bearer management
• Defined in conjunction with codec specifications to ensure proper transport of media

Evolution Across Releases

Defining Specifications