Description
The Transceiver Array Boundary (TAB) is a fundamental architectural concept within 3GPP specifications that defines the functional and physical separation point between the baseband processing unit (BBU) and the radio transceiver array (often part of the Remote Radio Head or Active Antenna Unit) in a base station. It establishes a standardized interface that delineates where digital baseband signal processing ends and analog radio frequency (RF) transmission/reception begins. This boundary is critical for disaggregating the traditional monolithic base station, enabling more flexible and scalable network deployments.
Architecturally, the TAB sits within the gNB in 5G NR or the eNB in LTE. On one side of the boundary, the baseband unit handles digital signal processing tasks such as channel coding, modulation/demodulation, and layer mapping for MIMO. On the other side, the transceiver array encompasses the RF components, including digital-to-analog converters (DACs), analog-to-digital converters (ADCs), power amplifiers, low-noise amplifiers, filters, and the physical antenna elements. The interface at the TAB typically involves the exchange of digitized time-domain IQ (In-phase and Quadrature) samples or frequency-domain resource element data, along with necessary control and synchronization signals.
The TAB's role is pivotal for implementing advanced antenna systems (AAS) and massive MIMO. By standardizing this boundary, 3GPP ensures interoperability between baseband and RF units from different vendors, fostering a competitive ecosystem. It underpins key technologies like beamforming, where precise control over the phase and amplitude of signals at each antenna element is required. The TAB defines the point up to which beamforming weights can be applied digitally and where the analog RF chain takes over. This separation is essential for network architectures such as Centralized RAN (C-RAN), where the baseband processing is pooled in a central location, connected via fronthaul to remote radio units, with the TAB defining the functional split options for this fronthaul interface.
Purpose & Motivation
The Transceiver Array Boundary was introduced to address the growing complexity and performance demands of multi-antenna systems in LTE-Advanced and 5G NR. Prior to its formal definition, base station implementations were largely integrated, vendor-specific solutions, making it difficult to mix and match baseband and radio units. This lack of standardization hindered innovation, increased costs, and limited deployment flexibility for operators. The TAB was created to decouple these components, enabling a modular approach to base station design.
The primary motivation was to support the evolution towards Advanced Antenna Systems (AAS) and massive MIMO, which require a high degree of coordination between numerous transceiver paths. A standardized boundary allows for specialized development of baseband processors (focusing on computational power and algorithms) and radio units (focusing on RF performance and energy efficiency) independently. This is particularly important for new deployment models like Cloud RAN (C-RAN), where the baseband processing is virtualized and centralized, necessitating a well-defined, low-latency, high-bandwidth interface to the remote radio heads. The TAB provides the architectural foundation for these split architectures, specifying functional splits (like Option 7-2x) that determine which processing happens before and after the boundary, directly impacting fronthaul requirements and overall system performance.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Explore further
Broader topics and technologies where TAB plays a role.
Defining Specifications
3GPP specifications that define or reference TAB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.108 vj40 | SAN RF & Performance for NB-IoT and 5G Broadcast | Rel-19 |
| TS 36.181 vj40 | RF Test Methods and Conformance for Satellite Access Nodes | Rel-19 |
| TS 36.214 vj00 | E-UTRA Physical Layer Measurements | Rel-19 |
| TS 37.105 vj30 | Active Antenna System (AAS) Base Station (BS) transmission and reception | Rel-19 |
| TS 37.114 vj00 | EMC for Active Antenna System Base Stations | Rel-19 |
| TS 37.145 vj40 | AAS Base Station Radiated Requirements | Rel-19 |
| TS 37.842 vd30 | BS RF Requirements for Active Antenna Systems | Rel-13 |
| TR 37.843 vf70 | AAS BS Radiated RF Requirement Background | Rel-15 |
| TS 38.104 vk00 | NR and NB-IoT Base Station RF Characteristics and Performance | Rel-20 |
| TS 38.108 vj40 | Satellite Access Node radio transmission and reception | Rel-19 |
| TS 38.115 vj20 | Repeater Conformance Testing - Part 2: Radiated | Rel-19 |
| TS 38.141 vj40 | BS Conformance Testing (TR 38.141) | Rel-19 |
| TS 38.174 vj20 | NR Integrated Access and Backhaul (IAB) Requirements | Rel-19 |
| TS 38.176 vj40 | IAB Conformance Testing | Rel-19 |
| TS 38.181 vj40 | NR Satellite Access Node RF Conformance Testing | Rel-19 |
| TS 38.817 | 3GPP TR 38.817 | Rel-13 |
| TR 38.820 vg10 | NR; 7-24 GHz Frequency Range Study | Rel-16 |
| TR 38.876 vi20 | Technical Report on Air-to-Ground Network for NR | Rel-18 |
| TR 38.922 vj30 | IMT parameters study for NR in higher frequency ranges | Rel-19 |