Description
In 3GPP UMTS and evolved LTE/5G NR architectures, the Transport Channel (TC) is a fundamental concept in the Radio Access Network (RAN) layer 2 protocol stack, specifically at the interface between the Medium Access Control (MAC) sublayer and the physical layer (Layer 1). It serves as a logical pipe that dictates the format and method for transporting data blocks (Transport Blocks) over the radio interface. The physical layer is responsible for the actual transmission and reception of radio signals, but it operates based on the parameters and procedures defined by the Transport Channel. Each Transport Channel type is characterized by a specific set of attributes, including the Transport Format (TF), which defines the dynamic aspects like the size of the Transport Block and the type of channel coding (e.g., convolutional, turbo), and the Transport Format Set (TFS), which is the collection of all allowed Transport Formats for that channel.
The operation involves the MAC layer delivering a Transport Block (TB) to the physical layer over a defined Transport Channel at each Transmission Time Interval (TTI). The physical layer then applies the corresponding processing chain: cyclic redundancy check (CRC) attachment, channel coding, rate matching, interleaving, and modulation, as dictated by the selected Transport Format. This processed data is then mapped onto physical channels (like the Physical Downlink Shared Channel - PDSCH) for actual radio transmission. Key Transport Channel types include the Dedicated Transport Channel (DCH) for dedicated user data, the Random Access Channel (RACH) for initial uplink access, the Broadcast Channel (BCH) for system information, and shared channels like the Downlink Shared Channel (DL-SCH) and Uplink Shared Channel (UL-SCH) in LTE/5G NR, which enable efficient packet-switched data transmission.
In the network architecture, Transport Channels are a critical part of the air interface protocol stack, managed by the NodeB/gNB and the UE. Their configuration and dynamic selection (Transport Format Combination Selection - TFCS) are controlled by higher layers (RRC) based on radio conditions, QoS requirements, and available resources. The evolution from UMTS to LTE and 5G NR saw a simplification and enhancement of Transport Channel concepts, with a move towards more flexible and dynamic shared channels to support high-speed packet data services, but the core principle of defining the logical transmission characteristics between MAC and PHY remains central to RAN operation.
Purpose & Motivation
The Transport Channel concept was introduced to abstract and standardize the method of data transfer over the radio interface, separating the logical data transport requirements from the physical transmission details. Prior to its formalization in 3GPP UMTS, 2G systems like GSM had more rigid and less layered channel structures. The TC provides a clear interface between Layer 2 (MAC) and Layer 1 (PHY), enabling independent evolution and optimization of radio transmission techniques (like new modulation or coding schemes in the physical layer) without drastically altering the higher-layer data handling procedures. This layered approach is fundamental to modern telecommunications standards.
It solves the problem of efficiently supporting diverse services (voice, video, data) with different Quality of Service (QoS) requirements over a shared radio medium. By defining specific Transport Channels with attributes like variable bit rates, error protection levels, and transmission timing, the system can dynamically allocate resources. For instance, a voice call uses a Dedicated Channel (DCH) with a constant, low-latency format, while web browsing uses a Shared Channel (DL-SCH) with adaptive modulation and coding. This flexibility was a key motivation for 3G and beyond, moving beyond circuit-switched voice to packet-switched multimedia.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (44 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, a correction was introduced for the NR Transport Channel (TC) procedures, interactions, and capabilities (PICs). This update provided necessary clarifications and fixes to the existing transport channel specifications to ensure proper functionality.
- Correction to NR TC PICs TS 38.508CR0060
In Release 17, the primary update for the Transport Channel (TC) function was the formal introduction of new conformance testing specifications for the Multicast/Broadcast Service (MBS) transport channel. This was documented through the addition of multiple Protocol Implementation Conformance Statement (PICS) proforma items specifically for the MBS TC. Furthermore, the release included corrections and additions to the applicability statements for EN-DC TC and RRM TC, as well as for CADC (Carrier Aggregation Dual Connectivity) related Maximum Power Reduction (MPR) and Maximum Output Power (MOP) requirements.
- Addition of PICS for MBS TC TS 38.508CR0411
- Addition of PICS for MBS TC TS 38.508CR0431
- Addition of PICS for MBS TC TS 38.508CR0475
- Add pics for MBS new TC. TS 38.508CR0507
- Addition of applicability for CADC MPR TC 6.2B.2.4_1.1 TS 38.522CR0152
- Correction to Applicability and Additional information for EN-DC TC and RRM TC TS 38.522CR0139
+ 2 more changes
In Release 18, the Transport Channel (TC) function introduced new capabilities for UE operation on cells with less than 5 MHz channel bandwidth and added specific test configurations (TC) for Adjacent Channel Selectivity (A-SEM) for UE categories M1, NB1, and NB2. It also updated applicability for NB-NTN demodulation test cases and added new TC applicability statements for ATG (Air-to-Ground) UE. Furthermore, the release corrected reference sensitivity power level test cases for UE category M1 and updated Additional Maximum Power Reduction (A-MPR) test configurations for the NS_24 network signaling scenario.
- CR to TS 38.113 on introduction of 3 MHz channel bandwidth in clause 6.1 TS 38.113CR0059
- Update of reference measurement channels in Annex A.3.12 TS 36.521CR0006
- Update applicability for NB-NTN Demod TC 8.3.1.1.1 TS 36.521CR0028
- Addition of IoT NTN band 254 in Operating bands and channel arrangement TS 36.521CR0040
- Update of A-MPR TC 6.2A.3 for NS_24 TS 36.521CR0058
- Update of A-MPR TC 6.2B.3 for NS_24 TS 36.521CR0059
+ 17 more changes
In Release 19, key updates to the Transport Channel (TC) function included the introduction of a new 7 MHz channel bandwidth for NR FR1, requiring updated performance criteria for continuous phenomena. Furthermore, support for Non-Terrestrial Networks (NTN) was expanded with the addition of IoT band 252, integrating it into relevant TC specifications for M1 and NB-IoT device categories. These changes necessitated updates to the applicability of several RRM and performance Test Cases (TCs), including those for RedCap and High-Speed Train (HST) scenarios.
- CR to TS 37113 - Introduction of 7 MHz channel BW TS 37.113CR0142
- CR to TS38.113 Introduction of 7 MHz NR FR1 channel bandwidth TS 38.113CR0084
- Addition of IoT NTN band 252 in Operating bands and channel arrangement TS 36.521CR0111
- Addition of band 252 into MOP TC for category M1 and NB-IoT NTN TS 36.521CR0112
- Addition of band 252 into A-MPR TC for category M1 and NB-IoT NTN TS 36.521CR0113
- (NR_FR1_7MHz_BW-Perf) CR to TS 37.113: Correction of channel bandwidths for performance criteria for continuous phenomena TS 37.113CR0143
+ 6 more changes
Explore further
Broader topics and technologies where TC plays a role.
Defining Specifications
3GPP specifications that define or reference TC, 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 22.867 vi20 | Study on 5G Smart Energy and Infrastructure | Rel-18 |
| TR 22.967 vj00 | eCall Emergency Data Transmission | Rel-19 |
| TR 22.975 v1310 | UMTS Numbering and Addressing Requirements | Rel-4 |
| TS 25.141 vj00 | UTRA FDD Base Station RF Conformance Testing | Rel-19 |
| TS 25.142 vj00 | UTRA TDD Base Station RF Test Methods | Rel-19 |
| TS 25.411 vj00 | Iu Interface Layer 1 Specification | Rel-19 |
| TS 26.253 vj00 | IVAS Codec Algorithmic Description | Rel-19 |
| TS 26.260 vj00 | Immersive Audio Objective Test Methods | Rel-19 |
| TR 26.996 vj00 | ISAR Split Rendering Audio Characterization | Rel-19 |
| TR 26.997 vj00 | IVAS Codec Specification | Rel-19 |
| TS 29.013 vj00 | MAP-SSAP Interworking for CCBS Service | Rel-19 |
| TS 29.078 vj00 | CAMEL Phase 4 CAP Specification | Rel-19 |
| TS 29.278 vj00 | CAMEL Application Part (CAP) for IMS Phase 4 | Rel-19 |
| TS 34.109 vj00 | UE Conformance Test Functions for UMTS | Rel-19 |
| TS 36.141 vj00 | E-UTRA BS Conformance Testing | Rel-19 |
| TS 36.509 vh40 | EPC Special UE Conformance Testing Functions | Rel-17 |
| TS 36.521 vj00 | E-UTRA UE Conformance ICS Proforma | Rel-19 |
| TS 36.523 vj00 | UE Conformance Test Spec for Idle Mode | Rel-19 |
| TS 37.113 vj00 | EMC Requirements for Multi-Standard Radio Base Stations | Rel-19 |
| TS 37.571 vj00 | UE Conformance for Positioning | Rel-19 |
| TS 37.579 vi40 | Mission Critical services conformance testing | Rel-18 |
| TS 37.802 va10 | MSR BS RF Requirements for Non-Contiguous Spectrum | Rel-10 |
| TR 37.900 vj00 | Multi-Standard Radio (MSR) Base Station Requirements | Rel-19 |
| TS 38.113 vj00 | NR Base Station EMC Specification | Rel-19 |
| TS 38.175 vj00 | EMC for NR IAB Nodes | Rel-19 |
| TS 38.508 vj11 | 5G NR UE Radio Transmission & Reception | Rel-19 |
| TS 38.522 vj11 | UE Conformance Test Applicability Statement | Rel-19 |
| TS 38.523 vj20 | 5G NR UE Conformance Testing: Idle/Inactive | Rel-19 |
| TS 43.318 vj00 | Generic Access Network (GAN) Stage 2 | Rel-19 |
| TR 43.902 vj00 | GAN Enhancements Feasibility Study | Rel-19 |
| TS 44.318 vj00 | Generic Access Network (GAN) Interface Procedures | Rel-19 |