Description
A Fixed Reference Measurement Channel (FRC) is a fundamental conformance testing tool defined across multiple 3GPP technical specifications. It is not a functional channel used in live network operation but a test configuration. An FRC provides a complete, unambiguous definition of a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission for the purpose of radio frequency (RF) and demodulation performance testing. The definition includes all necessary parameters to generate a predictable signal: the exact transport block size (TBS), the modulation scheme (e.g., QPSK, 16QAM, 64QAM, 256QAM), the channel coding rate (based on a specific redundancy version), the physical resource block (PRB) allocation, and the reference signal configuration. During testing, the test equipment (a base station emulator) generates the signal exactly as specified by the FRC, and the device under test (UE or gNB) must successfully demodulate and decode it with an error rate below a specified threshold (e.g., Block Error Rate of 10%). The key components of an FRC are its unique identifier (e.g., FRC A1-1, FRC A3-3), the associated reference measurement channel configuration table in the specification, and the corresponding performance requirements table. Its role is to isolate and measure specific receiver capabilities, such as sensitivity, maximum input level, or adjacent channel selectivity, under a controlled and repeatable condition, ensuring all vendors test their equipment against the same benchmark.
Purpose & Motivation
The FRC exists to solve the problem of inconsistent and non-comparable radio performance testing for 3GPP-based devices. Without a fixed reference, different test labs or manufacturers could use slightly different signal configurations, leading to results that cannot be fairly compared and potentially allowing sub-standard devices to pass by exploiting test loopholes. The creation of FRCs was motivated by the need for rigorous type approval testing to guarantee a baseline level of network performance and spectral efficiency. Historically, as cellular technologies evolved from GSM to UMTS and LTE, the testing complexity grew exponentially. FRCs provide a standardized 'test vector' that ensures every UE or base station is evaluated under identical, challenging radio conditions. This guarantees that devices meeting the 3GPP performance specifications will interoperate reliably in real networks, maintaining overall network quality and user experience.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (266 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the FRC (Fixed Reference Channel) function was newly introduced to define test models for the Base Station's Interference Cancellation (IC) receiver, as specified in TS 36.141. This introduction supported new performance requirements for features like subslot-PUSCH and sTTI (short Transmission Time Interval). Additionally, corrections were made to the associated FRC indices to ensure accurate enhanced performance requirement testing.
- 36.104 CR for BS IC receiver - FRC definitions TS 36.104CR4694
- Performance requirements for subslot-PUSCH TS 36.104CR4800
- Introduction of FRC for BS IC in 36.141 TS 36.141CR1062
- CR for PUSCH conformance test in TS 36.141 for BS IC TS 36.141CR1080
- New Annex to TR 37.843: Power density measurements close to EUT TS 37.843CR0006
- Correction on FRC indices for enhanced performance requirement type B TS 36.104CR4781
+ 26 more changes
In Release 16, the FRC function was expanded to introduce new performance requirements for the PUSCH under an enhanced High-Speed Train (HST) scenario, including specific demodulation requirements and associated channel model annexes for testing. This release also added new Fixed Reference Channels to support URLLC PUSCH repetition Type A for base station performance requirements. Furthermore, the scope of FRCs was extended in conjunction with the introduction of wider channel bandwidths for various NR operating bands like n1, n7, n28, n38, n50, n66, n77, and n78.
- CR to 36.104 on LTE HST PUSCH conditions TS 36.104CR4873
- CR to TS 36.104: Introduction of PUSCH performance requirements for enhanced HST scenario TS 36.104CR4883
- CR to TS 36.141: Introduction of PUSCH performance requirements for enhanced HST scenario TS 36.141CR1241
- Addition channel bandwidth of 30MHz for n50 in TS 38.104 TS 38.104CR0031
- CR for TS 38.104: adding wider channel bandwidths in Band n7 TS 38.104CR0037
- CR for TS 38.104: adding wider channel bandwidths in Band n77/n78 TS 38.104CR0105
+ 65 more changes
In Release 17, the primary update for the Fixed Reference Channel (FRC) function was the introduction of new channel bandwidths, specifically 35 MHz and 45 MHz, for conformance testing. This expansion required updates to the core technical specifications, including TS 37.104, TS 37.141, and TS 37.145-2, to define the new RF requirements. The changes ensured that the FRCs and related base station measurements supported these additional channel bandwidths as defined for the relevant operating bands.
- CR to 37.104: Introduction of requirements for 35 and 45MHz channel bandwidths TS 37.104CR0949
- CR for TS 37.141: introduction of channel bandwidths 35MHz and 45MHz TS 37.141CR0990
- CR for TS 37.145-2: introduction of channel bandwidths 35MHz and 45MHz TS 37.145CR0314
- Big CR to 38.104 - Additional Channel BW TS 38.104CR0258
- Big CR to 38.104 - Additional Channel BW TS 38.104CR0291
- Big CR to TS 38.104: Adding channel BW support in existing NR bands TS 38.104CR0319
+ 28 more changes
In Release 18, the FRC (Fixed Reference Channel) function was updated to support the newly introduced 3 MHz channel bandwidth for NR, as detailed in the CR to TS 37.113. This change required the update of the specific FRCs used in performance criteria to accommodate this narrower bandwidth configuration. The update ensures that base station receiver requirements, such as demodulation performance, are properly defined and tested for this new channel bandwidth.
- CR to TS 37.141 - Consideration of NR 3 MHz channel bandwidth TS 37.141CR1068
- Big CR to TS 38.104: Adding channel BW support in existing NR bands TS 38.104CR0450
- Big CR to TS 38.104 on introduction of 3 MHz channel bandwidth TS 38.104CR0500
- Big CR to TS 38.104: Adding channel BW support in existing NR bands TS 38.104CR0512
- Big CR for 38.104 on 4Tx PUSCH demodulation requirements TS 38.104CR0537
- Big CR to TS 38.104: Adding channel BW support in existing NR bands TS 38.104CR0538
+ 77 more changes
In Release 19, the primary new development for the Fixed Reference Channel (FRC) function was the introduction of a 7 MHz channel bandwidth for NR FR1, as detailed across multiple technical specifications for base station and UE requirements. This addition required corresponding updates to related RF measurement procedures, including ACLR (Adjacent Channel Leakage power Ratio) and ACS (Adjacent Channel Selectivity), to define the performance criteria for this new bandwidth. Furthermore, the release included specific corrections and restrictions for the 7 MHz channel bandwidth within the conformance testing specifications to ensure proper implementation.
- CR to TS37.104 Introduction of 7 MHz NR FR1 channel bandwidth TS 37.104CR1028
- CR to TS 37.105: 7MHz channel bandwidth introduction TS 37.105CR0304
- CR to TS 37113 - Introduction of 7 MHz channel BW TS 37.113CR0142
- CR to TS37.141 Introduction of 7 MHz NR FR1 channel bandwidth TS 37.141CR1098
- CR to TS 37.145-2: 7MHz channel bandwidth introduction TS 37.145CR0398
- Big CR to TS 38.104: Adding channel BW support in existing NR bands TS 38.104CR0685
+ 40 more changes
Explore further
Broader topics and technologies where FRC plays a role.
Defining Specifications
3GPP specifications that define or reference FRC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TR 25.967 vj00 | Home NodeB RF Requirements Technical Report | Rel-19 |
| TS 36.101 vj30 | LTE UE Radio Transmission & Reception Requirements | Rel-19 |
| TS 36.104 vj10 | Base Station (BS) radio transmission and reception | Rel-19 |
| TS 36.108 vj10 | Satellite Access Node RF Requirements | Rel-19 |
| TS 36.113 vj00 | EMC Requirements for E-UTRA Base Stations | Rel-19 |
| TS 36.116 vj00 | E-UTRA Relay RF Requirements | Rel-19 |
| TS 36.117 vj00 | E-UTRA Relay RF Test Methods & Requirements | Rel-19 |
| TS 36.124 vj00 | EMC for E-UTRA User Equipment | Rel-19 |
| TS 36.141 vj00 | E-UTRA BS Conformance Testing | Rel-19 |
| TS 36.181 vj30 | E-UTRA RF Test Methods for Satellite Access Node | Rel-19 |
| TS 36.747 ve00 | Enhanced CRS and SU-MIMO IM Performance Requirements | Rel-14 |
| TS 36.790 vf00 | LAA/eLAA for CBRS 3.5GHz Band in US | Rel-15 |
| TS 37.104 vj10 | MSR Base Station RF Characteristics | Rel-19 |
| TS 37.105 vj10 | AAS Base Station Transmission & Reception Requirements | Rel-19 |
| TS 37.113 vj00 | EMC Requirements for Multi-Standard Radio Base Stations | Rel-19 |
| TS 37.141 vj10 | RF Test Methods for Multi-Standard Radio Base Stations | Rel-19 |
| TS 37.145 vj10 | AAS Base Station Conducted Conformance Testing | Rel-19 |
| TS 37.802 va10 | MSR BS RF Requirements for Non-Contiguous Spectrum | Rel-10 |
| TS 37.809 vb00 | E-UTRA & MSR BS Class Requirements | Rel-11 |
| TS 37.812 vb30 | Multi-band Multi-standard Radio BS Requirements | Rel-11 |
| TR 37.843 vf70 | AAS BS Radiated RF Requirement Background | Rel-15 |
| TR 37.900 vj00 | Multi-Standard Radio (MSR) Base Station Requirements | Rel-19 |
| TR 37.976 vj00 | MIMO OTA Test Methodology Study | Rel-19 |
| TR 37.977 vj00 | MIMO OTA Test Methodology | Rel-19 |
| TS 38.101 vj31 | NR User Equipment Radio Transmissions | Rel-19 |
| TS 38.104 vj20 | NR Base Station RF Requirements | Rel-19 |
| TS 38.108 vj20 | NTN NR Satellite Access Node RF Requirements | Rel-19 |
| TS 38.113 vj00 | NR Base Station EMC Specification | Rel-19 |
| TS 38.174 vj10 | NR Integrated Access and Backhaul Radio Spec | Rel-19 |
| TS 38.175 vj00 | EMC for NR IAB Nodes | Rel-19 |
| TS 38.176 vj20 | IAB Conformance Testing Specification | Rel-19 |
| TS 38.181 vj10 | NR Satellite Access Node RF Testing | Rel-19 |
| TS 38.191 vj00 | NR Ambient IoT RF Characteristics | Rel-19 |
| TS 38.194 vj00 | Ambient IoT Base Station RF Spec | Rel-19 |
| TS 38.521 vj20 | NR Physical Layer UE Conformance Testing | Rel-19 |
| TS 38.551 vi30 | User Equipment (UE) Multiple Input Multiple Output (MIMO) Over-the-Air (OTA) performance | Rel-18 |
| TS 38.741 vj00 | NTN L-/S-band for NR Technical Specification | Rel-19 |
| TS 38.817 | 3GPP TR 38.817 | Rel-8 |
| TS 38.826 vg00 | NR Vehicle UE 2Rx Exception Study | Rel-16 |
| TS 38.863 vj10 | NR NTN RF and Co-existence Spec | Rel-19 |
| TR 38.921 vj00 | IMT Parameters Study for 6.4-7.1 & 10-10.5 GHz | Rel-19 |
| TR 38.922 vj20 | Study on IMT Parameters for NR in Higher Bands | Rel-19 |