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.
Key Features
- Precisely defined transport block size and content
- Fixed modulation and coding scheme (MCS)
- Specific physical resource block allocation and duration
- Associated reference signal (DM-RS) configuration
- Linked to specific RF and demodulation performance requirements (e.g., sensitivity, ACS)
- Defined for various channel bandwidths and use cases (e.g., MIMO, carrier aggregation)
Evolution Across Releases
Introduced the foundational concept of Fixed Reference Channels for LTE (E-UTRA) conformance testing. Initial FRCs were defined for basic PDSCH and PUSCH performance testing in specifications like 36.101 (UE radio transmission and reception) and 36.104 (Base Station radio transmission and reception), establishing the framework for all subsequent enhancements.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 25.967 | 3GPP TS 25.967 |
| TS 36.101 | 3GPP TR 36.101 |
| TS 36.104 | 3GPP TR 36.104 |
| TS 36.108 | 3GPP TR 36.108 |
| TS 36.113 | 3GPP TR 36.113 |
| TS 36.116 | 3GPP TR 36.116 |
| TS 36.117 | 3GPP TR 36.117 |
| TS 36.124 | 3GPP TR 36.124 |
| TS 36.141 | 3GPP TR 36.141 |
| TS 36.181 | 3GPP TR 36.181 |
| TS 36.747 | 3GPP TR 36.747 |
| TS 36.790 | 3GPP TR 36.790 |
| TS 37.104 | 3GPP TR 37.104 |
| TS 37.105 | 3GPP TR 37.105 |
| TS 37.113 | 3GPP TR 37.113 |
| TS 37.141 | 3GPP TR 37.141 |
| TS 37.145 | 3GPP TR 37.145 |
| TS 37.802 | 3GPP TR 37.802 |
| TS 37.809 | 3GPP TR 37.809 |
| TS 37.812 | 3GPP TR 37.812 |
| TS 37.843 | 3GPP TR 37.843 |
| TS 37.900 | 3GPP TR 37.900 |
| TS 37.976 | 3GPP TR 37.976 |
| TS 37.977 | 3GPP TR 37.977 |
| TS 38.101 | 3GPP TR 38.101 |
| TS 38.104 | 3GPP TR 38.104 |
| TS 38.108 | 3GPP TR 38.108 |
| TS 38.113 | 3GPP TR 38.113 |
| TS 38.174 | 3GPP TR 38.174 |
| TS 38.175 | 3GPP TR 38.175 |
| TS 38.176 | 3GPP TR 38.176 |
| TS 38.181 | 3GPP TR 38.181 |
| TS 38.191 | 3GPP TR 38.191 |
| TS 38.194 | 3GPP TR 38.194 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.551 | 3GPP TR 38.551 |
| TS 38.741 | 3GPP TR 38.741 |
| TS 38.817 | 3GPP TR 38.817 |
| TS 38.826 | 3GPP TR 38.826 |
| TS 38.863 | 3GPP TR 38.863 |
| TS 38.921 | 3GPP TR 38.921 |
| TS 38.922 | 3GPP TR 38.922 |