Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

LCT

Layered Coding Transport

Services →

LCT is a 3GPP media delivery mechanism for streaming that uses layered video coding and file delivery protocols to enable efficient adaptive streaming and reliable multicast or broadcast distribution.

Introduced
Rel-6
Where
Services › Codecs
Specifications
5 specs
LCT Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

Layered Coding Transport is a 3GPP standardized mechanism for the delivery of media, particularly video, over broadcast/multicast and unicast networks. It is designed to work with layered video codecs, most notably Scalable Video Coding (SVC), an extension of the H.264/AVC standard. The core principle of LCT is to transport the different layers of a scalable video bitstream as separate logical channels or transport sessions. The base layer, containing the essential video information, is sent independently from one or more enhancement layers, which add spatial resolution (size), temporal resolution (frame rate), or quality (Signal-to-Noise Ratio). This separation allows receivers to subscribe to and decode only the layers they can successfully receive and process, based on factors like available radio bandwidth, device capability, and subscription level.

From a transport perspective, LCT typically utilizes the File Delivery over Unidirectional Transport (FLUTE) protocol, which itself is built on top of the Asynchronous Layered Coding (ALC) protocol suite. FLUTE/ALC provides reliable file delivery over IP multicast. In LCT, each video layer (base or enhancement) is packaged as a separate FLUTE file delivery session. These sessions are announced via a Session Description Protocol (SDP) file or a Media Presentation Description (MPD) in the context of Dynamic Adaptive Streaming over HTTP (DASH). A client device receives the announcement, identifies the available layers and their corresponding transport sessions (identified by specific Transport Session Identifiers - TSIs), and joins the multicast groups or establishes the unicast connections necessary to receive the layers it selects.

The architecture involves several key components: the Broadcast Multicast Service Centre (BM-SC) in the network, which acts as the source and controller for the FLUTE sessions; the LTE/5G broadcast entities like eMBMS (evolved Multimedia Broadcast Multicast Service) or 5G MBS (Multicast Broadcast Service) for distribution; and the client device with a media player and a FLUTE/ALC receiver. The client performs adaptive streaming logic by monitoring reception conditions (e.g., packet loss rate, signal strength) and dynamically adding or dropping enhancement layer sessions. If an enhancement layer is lost due to poor reception, the base layer can still be decoded, providing a lower-quality but continuous video experience—a key feature for robust mobile broadcast. LCT is thus a hybrid approach, combining the efficiency of multicast for widespread distribution with the flexibility of client-driven adaptation.

Purpose & Motivation

Layered Coding Transport was developed to address the challenges of delivering high-quality video streaming services efficiently over mobile networks, particularly in broadcast/multicast scenarios like Mobile TV. Traditional unicast streaming is inefficient for popular live events, as it duplicates the same stream to every user, consuming excessive network resources. Broadcast/multicast (e.g., MBMS) solves the efficiency problem but traditionally delivered a single, fixed-quality stream, which was unsuitable for the diverse and fluctuating reception conditions of mobile users.

LCT was created to combine the spectrum efficiency of broadcast with the adaptability of unicast streaming. Its primary purpose is to enable Quality of Experience (QoE)-driven adaptive streaming over broadcast channels. By splitting the video into independent layers, it allows a single broadcast transmission to serve users with different device capabilities (e.g., smartphones vs. tablets) and different radio conditions (e.g., cell-edge vs. cell-center). Users experiencing poor signal quality can decode only the robust base layer, while users with excellent reception can add enhancement layers for high definition. This maximizes service coverage and user satisfaction. Furthermore, LCT facilitates service tiering, where operators can offer basic (base layer only) and premium (base + enhancement layers) subscriptions over the same broadcast infrastructure. It was a foundational technology for eMBMS-based services and influenced later adaptive streaming standards like DASH, where the layered concept evolved into representations segmented over HTTP.

What changed in its specifications

The latest release-to-release comparison of specifications that define LCT. Each summary describes the whole specification, not only this term.

TS 26.346Rel-16 → Rel-17

Added a profiled FLUTE FDT schema with semantics and versioning, plus 5GMS references and requirements, removing old schema clauses. Updated User Service Bundle Description schema versions and added a new unicast announcement FQDN format.

Full comparison in TS 26.346 →
TS 26.852Rel-13 → Rel-14

Rel-14 added MBMS URL DNS resolution and resource retrieval procedures. It also added HTTP/HTTPS fallback behavior for MBMS transport.

Full comparison in TS 26.852 →

Technology family

Broadcast and multicast · Services

  1. Phase 1 CBC, CBCH, CBS, SMS-CB
  2. Phase 2 CBE
  3. R99 BMC, SABP
  4. Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
  5. Rel-7 MBSFN
  6. Rel-8 ETWS, MCE, PWS
  7. Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
  8. Rel-10 KPAS
  9. Rel-11 EU-Alert
  10. Rel-12 MooD
  11. Rel-13 MBMS group communication delivery method, SC-PTM
  12. Rel-14 MBMS transparent delivery method, Receive Only Mode
  13. Rel-15 CBCF, PWS-IWF
  14. Rel-16 5G Broadcast
  15. Rel-17 5MBS, Broadcast MBS session, MB-SMF, MB-UPF, MBS, MBS Distribution Session, MBS User Service, MBSF, MBSSF, MBSTF, Multicast MBS session, Object Distribution Method, Packet Distribution Method
  • LCT extended by ALC
    “ALC combines the Layered Coding Transport (LCT) building block [11], a congestion control building block and the Forward Error Correction (FEC) building block” TS 26.346

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 sources

Documented changes in 4 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.

Rel-6 introduced

TS 26.346 first specifies MBMS download delivery that requires clients and servers to implement FLUTE with the ALC and LCT features it inherits, including LCT header settings.

  • “MBMS clients and servers supporting MBMS download shall implement the FLUTE specification (RFC 3926 [9]), as well as ALC (RFC 3450 [10]) and LCT (RFC 3451 [11]) features” TS 26.346 v6.14.0
  • “The LCT header length (HDR_LEN) shall be set to the total length of the LCT header in units of 32-bit words.” TS 26.346 v6.14.0
Rel-12 specification text

TS 26.346 added a requirement on the LCT EXT_TIME header extension: the sender may include it in some or all packets of a file transmission, and if included it shall carry the ERT value.

  • “If EXT_TIME is included, it shall contain the ERT time value set according to [119].” TS 26.346 v12.12.0
Rel-13 specification text

The MBMS download profile now specifies LCT header usage: the Close Session flag is set to 0 and ignored by the UE when a Schedule Description is present, EXT_FTI is used for FDT packets, and SCT/ERT timing fields are unused.

  • “the LCT header’s ‘Close Session’ flag (A) shall be set by the network to “0”, and the UE should ignore this flag.” TS 26.346 v13.7.0
  • “are not used in the Download Delivery Profile. The network should set these flags/fields to zero, and the UE should ignore them.” TS 26.346 v13.7.0
  • “should be used in FLUTE packets that carry symbols of FDT Instance(s).” TS 26.346 v13.7.0
Rel-19 specification text

The FLUTE sender must now send all packets of one object before sending any LCT packet of another object, letting receivers detect object completion from a new object's packet.

  • “The FLUTE sender completes the sending of all packets of one object before it sends any LCT packet of another object” TS 26.346 v19.3.0

Defining Specifications

3GPP specifications that define or reference LCT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 26.346 vj30 MBMS User Services Specification Rel-19 read
TS 26.802 vk00 5G Media Streaming Multicast Enhancements Rel-20 read
TS 26.852 ve20 MBMS user service profiles, APIs and transport enabler study Rel-14 read
TR 26.946 vj00 MBMS User Services Overview Rel-19 read
TR 26.947 vj00 FEC Evaluation for MBMS Enhancement Rel-19 read