Description
The FLUTE File Delivery Table (FDT) is a core component of the FLUTE protocol, standardized by the IETF and adopted within 3GPP for Multimedia Broadcast Multicast Service (MBMS) and evolved MBMS (eMBMS). It is an XML-based structure that acts as a manifest or catalog for files within a FLUTE session. The FDT itself is transmitted as a special file within the session, identified by a specific Transport Object Identifier (TOI). It contains a series of FDT Instance elements, each providing a snapshot of the files available at a given point in time. Each file entry within an FDT Instance includes mandatory attributes such as the TOI, Content-Location (a URI), Content-Length, and Content-Type, along with optional attributes like transfer length, expiration time, and content encoding parameters (e.g., for FEC).
The FDT's primary operational role is to provide receivers with the necessary metadata to correctly identify, request (in the case of repair flows), reassemble, and process the delivered file objects. In a unidirectional broadcast scenario, files are sent repeatedly in carousels. The FDT is also carouseled, with new instances published to add, modify, or remove file entries. A receiver tunes into the session, acquires the current FDT, and uses it to map incoming data packets (identified by their TOI and source block numbers) to the correct file and to understand when the complete file has been received. For reliable delivery, the FDT includes information for Forward Error Correction (FEC) decoding, specifying the FEC encoding ID and instance ID used for each file.
Architecturally, the FDT sits within the application layer of the FLUTE protocol stack. The BM-SC (Broadcast Multicast Service Centre) in the 3GPP network generates and manages the FDT for a given MBMS session. The FDT's structure and semantics are defined to be extensible, allowing for the inclusion of session-specific and application-specific metadata in separate namespaces. This enables advanced services like dynamic playlist updates for streaming or conditional access information. Its standardized format ensures interoperability between different network equipment and user devices, forming the essential glue that links the transport-layer delivery of data packets to the application-layer consumption of complete files.
Purpose & Motivation
The FDT was created to solve the fundamental problem of delivering discrete, identifiable files over unidirectional, best-effort IP multicast or broadcast channels. Prior to FLUTE and the FDT, broadcast systems often used proprietary encapsulation methods, making large-scale, interoperable file delivery challenging. The FDT provides a standardized, flexible, and efficient mechanism to announce and describe file content within a session. This allows receivers, which may join a session at any time, to immediately understand what files are being delivered and how to process them, without relying on out-of-band signaling or pre-configured knowledge.
Its development was motivated by the rise of MBMS in 3GPP, which aimed to enable efficient point-to-multipoint services like mobile TV, software updates, and group communications. These services required a reliable file delivery mechanism that could scale to millions of devices. The FDT addresses the limitations of simple data carousels by providing rich metadata, supporting advanced features like FEC for reliability, content compression, and dynamic updates. It abstracts the complexity of the underlying transport, allowing application developers to focus on content creation while the FLUTE protocol, guided by the FDT, handles the logistics of delivery, reassembly, and verification.
What changed in its specifications
The latest release-to-release comparison of specifications that define FDT. Each summary describes the whole specification, not only this term.
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 →Rel-19 added time synchronization parameters, target service area types, and in-session unicast object repair procedures with new data types.
Full comparison in TS 26.517 →Technology family
Broadcast and multicast · Services
- Phase 1 CBC, CBCH, CBS, SMS-CB
- Phase 2 CBE
- R99 BMC, SABP
- Rel-6 ALC, BM-SC, FDT, FLUTE, LCT, MBMS, MBMS Bearer Service, MBMS download delivery method, MBMS streaming delivery method, MBMS User Service, TMGI
- Rel-7 MBSFN
- Rel-8 ETWS, MCE, PWS
- Rel-9 CBSP, CMAS, eMBMS, MBMS-GW
- Rel-10 KPAS
- Rel-11 EU-Alert
- Rel-12 MooD
- Rel-13 MBMS group communication delivery method, SC-PTM
- Rel-14 MBMS transparent delivery method, Receive Only Mode
- Rel-15 CBCF, PWS-IWF
- Rel-16 5G Broadcast
- 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
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 11 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.
The FDT is specified for the first time for MBMS download in Rel-6: FDT instances carry file URIs, grouping, expiry times and TOI 0, and are integrity protected.
- “Only Transport Object Identifier (TOI) 0 (zero) shall be used for FDT Instances.” TS 26.346 v6.14.0
- “One FDT instance is typically bound to one MBMS transmission session.” TS 26.346 v6.14.0
- “the FDT of the FLUTE protocol shall be integrity protected by wrapping the FDT in a DCF of its own” TS 33.246 v6.12.0
Rel-7 adds 3GPP FDT extensions, FDT delivery over OMA Push, file repair of all files in an FDT instance, and changes FDT instance content encoding from ZLIB to GZIP.
- “The FLUTE FDT instance is identified by the MIME type “application/fdt+xml”” TS 26.346 v7.11.0
- “A client may request all files from a specific FDT instance or a specific logical group of a particular MBMS User Services.” TS 26.346 v7.11.0
- “Content Encoding for FDT Instances: FDT Instance may be content encoded for more efficient transport, e.g. using GZIP.” TS 26.346 v7.11.0
A new "FullFDT" attribute in the FLUTE FDT instance lets the server signal a full FDT snapshot, with rules for receivers handling multiple full FDT instances.
- “If the server wants to inform the client about the current FDT snapshot, the server shall set the “FullFDT” attribute in the FLUTE FDT instance file.” TS 26.346 v8.7.0
- “the FDT instance with the highest FDT Instance ID shall be used by the terminal.” TS 26.346 v8.7.0
- “A new attribute "FullFDT" is created within the element "FDT-Instance" of the FDT” TS 26.346 v8.7.0
MBMS FDT handling was strengthened: UEs shall not use an FDT Instance beyond its expiry, and schema version selection rules and 2009 FDT extension namespaces were added.
- “For MBMS operation, the UE shall not use a received FDT Instance to interpret packets received beyond the expiration time of the FDT Instance.” TS 26.346 v9.15.0
- “then the UE shall use the schema that has the highest schema version attribute value that is equal to or less than the value in the received schemaVersion element.” TS 26.346 v9.15.0
Requirements were added that the FDT Content-Location element of delivered objects must match the Segment URL, the mpdURI, or the object URL in the MPD for DASH delivery over MBMS.
- “The Content-Location element in the FDT for the delivered object shall match the Segment URL in the MPD.” TS 26.346 v10.13.0
- “The Content-Location element in the FDT for the delivered object shall match the mpdURI of the mediaPresentationDescription element.” TS 26.346 v10.13.0
Rel-11 extends the FLUTE FDT schema with a new FEC-Redundancy-Level attribute (taking precedence over SDP) and a File-ETag attribute used for conditional byte-range repair requests.
- “the declaration in the FDT shall take precedence from the UE processing perspective.” TS 26.346 v11.14.0
- “The Release 11 extension of the FLUTE FDT schema is as follows:” TS 26.346 v11.14.0
- “If "File-ETag" is present in the FDT Instance, its value shall be used as the entity-tag” TS 26.346 v11.14.0
FDT requirements changed: Content-Location must match referenced MPD URI or application service document URL, and new FDT-instance-expiry conditions and a full file repair without the FDT procedure were added.
- “The Content-Location element in the FDT for the delivered object shall match the URL in the application service document.” TS 26.346 v12.12.0
- “If an update to the application service document is delivered as a FLUTE object then the Content-Location element in the FDT for the delivered object” TS 26.346 v12.12.0
- “The end of the file transmission time (end attribute in the fileSchedule element) per the Schedule Description fragment is reached even when the FDT Instance is not received;” TS 26.346 v12.12.0
FDT Instances gained new roles in Rel-13: signalling Independent Units via mbms2015:IndependentUnitPositions, and supplying Content-Type and Content-Length for partial-file responses and URL matching.
- “Independent Units may be signalled in the File entry of an FDT Instance using the attribute mbms2015: IndependentUnitPositions.” TS 26.346 v13.7.0
- “The Content-Range shall be set to bytes */Content-Length with Content-Length the value of the attribute Content-Length provided in the FDT Instance for this file.” TS 26.346 v13.7.0
Content-MD5 may now be included in the FDT for DASH Segments, and Media Playlists are recommended to carry a new Content-MD5 and Cache-control Expires in the FDT.
- “This attribute may be included in the FDT for DASH Segments.” TS 26.346 v16.11.1
- “It is also recommended to use Cache-control directives in the FDT (7.2.10.5) for Media Playlists, to provide an expiration date with the Expires subelement” TS 26.346 v16.11.1
The FDT schema and attributes in TS 26.346 were restructured (extended FDT syntax, 3GPP extension schemas, File-ETag now RFC 9110), and TS 26.517 newly specifies FDT use for MBS distribution sessions.
- “This schema extends the baseline IETF schema reproduced in clause 7.2.10.3 by importing the 3GPP extensions specified in clauses 7.2.10.2 and J.2.” TS 26.346 v17.6.0
- “The MBSTF shall use the Profiled FDT Schema according to clause L.6 of TS 26.346 [7]” TS 26.517 v17.11.0
- Feature reduced FLUTE FDT Schema TS 26.346CR0661
FDT Instances gain object repair roles: File@RepairStart, RepairMaxAttempts and FEC-Redundancy-Level attributes drive unicast repair, and FDT timestamps are tied to the E-UTRAN SIB16 wallclock instead of SNTP.
- “Repair-Start: the earliest date–time at which unicast repair may be started for the file object described by the FDT Instance.” TS 26.346 v19.3.0
- “When the object delivery client receives an FDT Instance document that includes at least one File element, it shall parse the FDT Instance” TS 26.517 v19.3.0
- “Timestamps in MBMS metadata fragments and File Delivery Table (FDT) instances of any ROM service are derived from the same wallclock as E-UTRAN SIB16 information.” TS 26.346 v19.3.0
Defining Specifications
3GPP specifications that define or reference FDT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 26.346 vj30 | MBMS User Services Specification | Rel-19 read |
| TS 26.517 vj30 | 5G MBS User Service Protocols | Rel-19 read |
| TS 26.802 vk00 | 5G Media Streaming Multicast Enhancements | Rel-20 read |
| TS 26.804 vk10 | 5G Media Delivery Architecture Extensions | Rel-20 read |
| TS 26.827 vc00 | IMS-based Streaming & Download Delivery Enhancements | Rel-12 read |
| TS 26.848 vc00 | Enhanced MBMS for DASH over broadcast/unicast | Rel-12 read |
| TS 26.851 vb20 | MBMS Multimedia Service Enhancements | Rel-11 read |
| TS 26.852 ve20 | MBMS user service profiles, APIs and transport enabler study | Rel-14 read |
| TR 26.917 vj00 | TV Service Enhancements over 3GPP | Rel-19 read |
| TR 26.946 vj00 | MBMS User Services Overview | Rel-19 read |
| TR 26.947 vj00 | FEC Evaluation for MBMS Enhancement | Rel-19 read |
| TS 33.246 vj00 | MBMS Security Specification | Rel-19 read |