Description
The Cyclic Redundancy Check (CRC) is a non-secure hash function designed to detect accidental errors in digital data. It operates by treating the message (data block) as a large binary number, which is divided by a predetermined generator polynomial. The remainder from this polynomial division becomes the CRC checksum, which is appended to the original data block before transmission. At the receiver, the same calculation is performed on the received data (including the appended CRC). If the calculated remainder is zero, the data is assumed to be error-free; a non-zero remainder indicates that one or more bits have been corrupted during transmission. This process is a form of binary polynomial arithmetic performed modulo-2, typically implemented efficiently in hardware using linear feedback shift registers (LFSRs).
In 3GPP systems, CRC is applied at multiple layers and for various channel types. For instance, in the physical layer of LTE and NR, a CRC is attached to transport blocks (TB CRC) before channel coding (like LDPC or Polar codes) to detect errors after decoding. Separate CRCs are also attached to code block segments when a transport block is large, forming Code Block Groups (CBGs) for more efficient retransmissions in NR. The length of the CRC (e.g., 24 bits, 16 bits, 8 bits) is chosen based on the required error detection probability and the size of the data block. Common polynomials defined in 3GPP specs include CRC24A, CRC24B, CRC24C, CRC16, and CRC8.
The role of CRC extends beyond mere error detection. It is integral to the Hybrid Automatic Repeat Request (HARQ) process. The receiver uses the CRC check to generate an ACK (positive acknowledgment) or NACK (negative acknowledgment), triggering retransmissions if errors are detected. Furthermore, CRC is used for in-band control signaling. For example, the Downlink Control Information (DCI) in the PDCCH carries its own CRC, which is then scrambled with a Radio Network Temporary Identifier (RNTI). This allows the UE to verify if the control message is intended for it, as a successful CRC check after descrambling with its assigned RNTI confirms address validity.
Architecturally, CRC calculation is a mandatory step in the processing chains of both the User Plane and Control Plane. It is specified in detail for physical channels (PDSCH, PUSCH, PDCCH), transport channels (DL-SCH, UL-SCH), and logical channels. Its implementation is a critical factor in achieving the high reliability and low latency targets of 5G NR, especially for Ultra-Reliable Low-Latency Communication (URLLC) services, where undetected errors could have severe consequences.
Purpose & Motivation
CRC exists to provide a reliable, lightweight mechanism for detecting random bit errors introduced during data transmission over noisy communication channels. In wireless systems, signals are susceptible to interference, fading, and noise, making error detection paramount. Without such a mechanism, corrupted data would be passed to higher layers, leading to corrupted content, failed procedures, and system instability. CRC solves this by providing a high-probability detection capability for burst errors common in radio environments.
The motivation for its use in 3GPP, dating back to Release 99, stems from its excellent balance of detection capability, computational simplicity, and low overhead. Compared to simpler checksums like parity bits, CRC polynomials can be designed to detect all single-bit errors, all double-bit errors, any odd number of errors, and any burst error shorter than the CRC length itself. This makes it vastly superior for protecting packet data in UMTS, LTE, and NR. Its hardware-friendly implementation using LFSRs allows for high-speed, low-latency processing, which is essential for meeting the tight timing requirements of radio frame processing.
Prior to standardized CRC application, systems relied on less robust error detection or more complex forward error correction (FEC) alone. CRC complements FEC schemes (like Turbo or LDPC codes) by detecting residual errors that the FEC decoder fails to correct. This hybrid approach—FEC for correction, CRC for detection—forms the backbone of modern link adaptation and HARQ, enabling efficient use of radio resources by triggering retransmissions only when necessary. Its creation and standardization were driven by the need for a universally applicable, robust error detection layer to ensure end-to-end data integrity in evolving mobile broadband systems.
What changed in its specifications
The latest release-to-release comparison of specifications that define CRC. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 23.107: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.107 →Technology family
Channel coding schemes · Radio Access Network
Also in this family (introduction release not pinned to a single defining specification): Bi-orthogonal code, Reed-Solomon code, Repetition code
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 9 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
Introduced in Phase 1 (release dating of the term; no individual change cited).
The CRC calculation for LTE channel coding is specified for the first time, with generator polynomials, parity bit attachment, code block segmentation with per-block CRC, and transport block CRC attachment.
- “A is the size of the input sequence and L is the number of parity bits.” TS 36.212 v8.8.0
- “gCRC16(D) = [D16 + D12 + D5 + 1] for a CRC length L = 16.” TS 36.212 v8.8.0
- “Error detection is provided on UL-SCH transport blocks through a Cyclic Redundancy Check (CRC).” TS 36.212 v8.8.0
CRC text in 36.212 and 36.213 was updated: CQI/PMI CRC length is 0 bits for payloads up to 11 bits and 8 bits otherwise, and CRC-scrambled PDCCH rules cover the carrier indicator field.
- “LL is the number of CRC bits given by L={0O≤118otherwiseL” TS 36.212 v10.9.0
- “For payload sizes greater than 11 bits, the CRC attachment, channel coding and rate matching of the channel quality information is performed” TS 36.212 v10.9.0
- “configured by higher layers to decode PDCCH with CRC scrambled by the C-RNTI, then the UE shall decode PDSCH of the serving cell indicated” TS 36.213 v10.13.0
CRC attachment and scrambling text for DCI changed: CRC masking now conditioned on closed-loop UE transmit antenna selection, and the DCI description now includes sidelink scheduling information.
- “In the case where closed-loop UE transmit antenna selection is not configured or applicable, after attachment, the CRC parity bits are scrambled with the corresponding RNTI” TS 36.212 v12.9.1
- “Clarification on UE antenna port based CRC masking” TS 36.212 v12.9.1
- “In the step of CRC attachment, no scrambling is performed.” TS 36.212 v12.9.1
CRC attachment with L set to 8 bits is specified for aggregated HARQ-ACK/RI feedback and for the new PUCCH formats 4 and 5, extending how CRC is applied to uplink control information.
- “The CRC attachment, channel coding and rate matching are performed according to clauses 5.1.1 by setting L to 8 bits, 5.1.3.1 and 5.1.4.2, respectively.” TS 36.212 v13.11.0
- “The CRC attachment, channel coding and rate matching of the HARQ-ACK bits are performed according to clauses 5.1.1 setting L to 8 bits” TS 36.212 v13.11.0
CRC attachment is specified for the first time in the NR specifications TS 38.212 and 38.213, covering transport block CRC, code block CRC, CRC polynomials and CRC-scrambled DCI.
- “Denote the input bits to the CRC computation by , and the parity bits by , where is the size of the input sequence” TS 38.212 v15.13.0
- “Error detection is provided on each UL-SCH transport block through a Cyclic Redundancy Check (CRC).” TS 38.212 v15.13.0
- “an additional CRC sequence of bits is attached to each code block.” TS 38.212 v15.13.0
Rel-16 extends CRC use: CRC bit counts for CG-UCI and HARQ-ACK in CG-UCI PUSCH multiplexing, and new CRC scrambling with PUR-RNTI, G-RNTI, CI-RNTI, AI-RNTI, PS-RNTI and SL-RNTI for DCI formats.
- “LCG−UCIL_{CG - UCI} is the number of CRC bits for CG-UCI determined according to Clause 6.3.1.2.1;” TS 38.212 v16.15.0
- “If format 6-0A CRC is scrambled by PUR-RNTI and Resource block assignment is set to all ones, the remaining fields are set as follows:” TS 36.212 v16.7.0
- “The following information is transmitted by means of the DCI format 2_4 with CRC scrambled by CI-RNTI:” TS 38.212 v16.15.0
New DCI formats 2_7, 4_0, 4_1 and 4_2 are defined with CRC scrambled by PEI-RNTI, MCCH-RNTI, G-RNTI and G-CS-RNTI, and the CRC bit count for UCI is specified for HARQ-ACK of different priorities.
- “The following information is transmitted by means of the DCI format 2_7 with CRC scrambled by PEI-RNTI:” TS 38.212 v17.13.0
- “The following information is transmitted by means of the DCI format 4_1 with CRC scrambled by G-RNTI for multicast or G-CS-RNTI” TS 38.212 v17.13.0
- “LL is the number of CRC bits determined according to clause 6.3.1.2.1” TS 38.212 v17.13.0
DCI CRC scrambling and CRC-bit usage were extended: new DCI format 2_9 with CRC scrambled by adaptSSB-PeriodicityIndication-RNTI, and CB-RNTI CRC scrambling for NPDCCH/MPDCCH decoding.
- “DCI format 2_9 with CRC scrambled by adaptSSB-PeriodicityIndication-RNTI is used for adapting SSB periodicity of one or multiple serving cells for one or more UEs.” TS 38.212 v19.4.0
- “If a UE is configured by higher layers to decode NPDCCH with CRC scrambled by the CB-RNTI during the CB-Msg3-EDT procedure” TS 36.213 v19.5.0
- “When the format 6-1A CRC is scrambled with a RA-RNTI or a CB-RNTI, then the following fields among the fields above are reserved:” TS 36.212 v19.3.0
Defining Specifications
3GPP specifications that define or reference CRC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 23.107 vj00 | UMTS QoS Framework | Rel-19 read |
| TS 23.207 vj00 | End-to-End QoS Framework for GPRS | Rel-19 read |
| TS 25.212 vj00 | UTRA FDD Layer 1 Multiplexing & Channel Coding | Rel-19 read |
| TS 25.214 vj00 | UTRA FDD Physical Layer Procedures | Rel-19 read |
| TS 25.222 vj00 | UTRA TDD Multiplexing & Channel Coding | Rel-19 read |
| TS 25.224 vj00 | UTRA TDD Physical Layer Procedures | Rel-19 read |
| TS 25.225 vj00 | UTRA TDD Physical Layer Measurements | Rel-19 read |
| TS 25.301 vj00 | UE-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 25.302 vj00 | UTRA Physical Layer Services | Rel-19 read |
| TS 25.321 vj00 | MAC Protocol Specification for UTRAN | Rel-19 read |
| TS 25.322 vj00 | RLC Protocol Specification | Rel-19 read |
| TS 25.425 vj00 | UTRAN Iur Interface User Plane Protocols | Rel-19 read |
| TS 25.427 vj00 | UTRAN Iub/Iur User Plane Protocols | Rel-19 read |
| TS 25.435 vj00 | UTRAN Iub Interface User Plane Protocols | Rel-19 read |
| TS 25.766 vd10 | UMTS Network-Assisted Interference Cancellation | Rel-13 read |
| TS 25.800 vc10 | UMTS Heterogeneous Networks Study | Rel-12 read |
| TR 25.903 vj00 | Continuous Connectivity for Packet Data Users | Rel-19 read |
| TR 25.912 vj00 | Evolved UTRA and UTRAN Technical Report | Rel-19 read |
| TR 25.914 vj00 | 3G UE Radio Performance Test Methods | Rel-19 read |
| TR 25.927 ve00 | Energy Saving Solutions for UMTS Node B | Rel-14 read |
| TR 25.929 vj00 | Continuous Connectivity for Packet Data Users | Rel-19 read |
| TS 26.091 vj00 | AMR Error Concealment Procedure | Rel-19 read |
| TS 26.101 vj00 | Generic frame format for AMR and GSM-EFR speech codecs | Rel-19 read |
| TS 26.191 vj00 | AMR-WB Error Concealment Procedure | Rel-19 read |
| TS 26.201 vj00 | AMR-WB Speech Codec Frame Format | Rel-19 read |
| TS 26.267 vj00 | eCall In-band Modem Specification | Rel-19 read |
| TS 26.268 vj00 | eCall In-band Modem ANSI-C Code | Rel-19 read |
| TS 26.269 vj00 | eCall In-band Modem Conformance Testing | Rel-19 read |
| TR 26.935 vj00 | Speech Codec Performance for Packet Switched Multimedia | Rel-19 read |
| TR 26.969 vj00 | eCall In-band Modem Performance Characterization | Rel-19 read |
| TR 26.975 vj00 | AMR Speech Codec Performance Background | Rel-19 read |
| TR 26.978 vj00 | AMR Noise Suppression Selection Phase Technical Report | Rel-19 read |
| TS 29.333 vj00 | MRFC-MRFP Mp Interface Protocol | Rel-19 read |
| TS 32.425 vj00 | E-UTRAN Performance Measurements | Rel-19 read |
| TS 34.114 vc20 | Radiated Performance Test Procedure for UE/MS | Rel-12 read |
| TS 36.104 vj20 | E-UTRA/NB-IoT Base Station RF Requirements | Rel-19 read |
| TS 36.116 vj00 | E-UTRA Relay RF Requirements | Rel-19 read |
| TS 36.117 vj00 | E-UTRA Relay RF Test Methods & Requirements | Rel-19 read |
| TS 36.201 vj00 | LTE Physical Layer General Description | Rel-19 read |
| TS 36.213 vj50 | LTE Physical Layer Procedures | Rel-19 read |
| TS 36.216 vj00 | LTE Relay Node Physical Layer | Rel-19 read |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 read |
| TS 36.302 vj00 | E-UTRA Physical Layer Services | Rel-19 read |
| TS 37.141 vj40 | RF Test Methods and Conformance for Multi-Standard Radio Base Stations | Rel-19 read |
| TS 37.145 vj40 | AAS Base Station Radiated Requirements | Rel-19 read |
| TS 37.462 vj00 | Iuant Interface Data Link Layer for RETAP/TMAAP | Rel-19 read |
| TS 37.544 vg70 | UE Radiated Performance Test Procedures | Rel-16 read |
| TS 37.802 va10 | MSR BS Non-Contiguous RF Requirements | Rel-10 read |
| TR 37.900 vj00 | Multi-Standard Radio (MSR) Base Station Requirements | Rel-19 read |
| TR 37.901 vf10 | UE Application Layer Data Throughput Performance | Rel-15 read |
| TS 38.202 vj00 | 5G NR Physical Layer Services | Rel-19 read |
| TS 38.212 vj40 | NR Multiplexing and Channel Coding | Rel-19 read |
| TS 38.213 vj50 | NR Physical Layer Control Procedures | Rel-19 read |
| TS 38.214 vj50 | NR Physical Layer Data Channel Procedures | Rel-19 read |
| TS 38.291 vj30 | Ambient IoT Physical Layer | Rel-19 read |
| TR 38.869 vi00 | Study on low-power wake up signal and receiver for NR | Rel-18 read |
| TR 38.889 vg00 | NR-based access to unlicensed spectrum study | Rel-16 read |
| TS 46.055 vj00 | GSM Enhanced Full Rate Speech Codec Performance | Rel-19 read |
| TS 46.061 vj00 | GSM EFR Frame Substitution and Muting Procedure | Rel-19 read |