Description
File Delivery over Unidirectional Transport (FLUTE) is an application-layer protocol standardized within the IETF and adopted by 3GPP for broadcast/multicast file delivery. It operates on top of the Asynchronous Layered Coding (ALC) protocol suite, which itself uses the Layered Coding Transport (LCT) building block and congestion control. FLUTE is designed for one-to-many distribution scenarios where feedback from receivers to the sender is impractical or impossible due to the unidirectional nature of the transport (e.g., terrestrial broadcast radio). Its primary function is to reliably deliver one or more files, or a collection of data objects, to potentially millions of receivers simultaneously.
Architecturally, in a 3GPP MBMS/eMBMS context, FLUTE runs between a Broadcast Multicast Service Center (BM-SC) and the User Equipment (UE). The BM-SC acts as the FLUTE sender, while the UE hosts the FLUTE receiver. FLUTE packages files into source blocks, which are then encoded using Forward Error Correction (FEC) schemes, like Raptor or RaptorQ, specified in 3GPP. This FEC encoding generates repair symbols that are transmitted alongside the original source symbols. This allows receivers to recover lost packets without requesting retransmissions, which is crucial for broadcast where return channels are unavailable or inefficient. FLUTE uses a File Delivery Table (FDT) to describe the files being delivered, including attributes like content type, size, and URI. The FDT itself is delivered as a FLUTE object, providing receivers with a manifest of the session.
FLUTE works by establishing a session identified by a Transport Session Identifier (TSI). Within this session, each file is assigned a Transport Object Identifier (TOI). The sender transmits source and repair symbols for each TOI in data packets. The receiver listens to these packets, collects symbols, and uses the FEC decoder to reconstruct the original file once enough symbols are received, regardless of which specific symbols arrived. The protocol supports carousel-based delivery, where content is repeated cyclically, allowing receivers that join late to still acquire all files. FLUTE is agnostic to the underlying transport; in 3GPP, it typically runs over UDP/IP, which is carried over the eMBMS bearer through the LTE or 5G broadcast radio interface. This combination provides an efficient pipeline for mass content distribution, offloading traffic from the unicast core network and enabling services like public warning systems, over-the-air updates, and linear TV broadcast to mobile devices.
Purpose & Motivation
FLUTE was developed to solve the fundamental challenge of scalable, reliable file distribution over broadcast networks. Traditional file transfer protocols like FTP or HTTP/TCP rely on acknowledgments and retransmissions, which create a feedback implosion problem when serving millions of users simultaneously—this is impossible in pure broadcast scenarios like TV or radio transmission. Before FLUTE and MBMS, mobile operators had no efficient way to send the same large file (e.g., an OS update) to all subscribers without crippling their unicast networks.
The protocol's creation was motivated by the need for a unidirectional, reliable content delivery method for emerging broadcast services. It addresses the limitations of simple, unreliable multicast by incorporating built-in FEC, which provides reliability without feedback. This was a paradigm shift. FLUTE also introduced a structured way to describe and deliver multiple files within a single session, which was essential for complex content like a website with multiple assets or a video with associated metadata. Its adoption by 3GPP for MBMS enabled a range of broadcast services that would otherwise be infeasible, transforming the mobile network from a purely point-to-point system into a hybrid one capable of efficient point-to-multipoint communication. This is critical for use cases requiring simultaneous delivery, such as emergency alerts where every device in an area must receive the information instantly and reliably.
What changed in its specifications
The latest release-to-release comparison of specifications that define FLUTE. Each summary describes the whole specification, not only this term.
Rel-18 adds IVAS sample entry signalling to the 3GP file format. It introduces the new IVASSampleEntry, IVASCodedFormatBox and IVASVersionBox structures, and extends codec registration to IVAS.
Full comparison in TS 26.244 →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 →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
- FLUTE builds on ALC
“FLUTE is built on top of the Asynchronous Layered Coding (ALC) protocol instantiation (RFC 3450 [10]).” 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 sourcesDocumented changes in 12 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.
TS 26.346 specifies for the first time how MBMS download delivery uses FLUTE, including support requirements and a close-session flag, and TS 33.246 specifies protection of FLUTE channels.
- “MBMS download delivery method uses the FLUTE protocol (RFC 3926 [9]) when delivering content over MBMS bearers.” TS 26.346 v6.14.0
- “FLUTE provides a "Close session flag" (see sub-clause 7.2.7) which, when used, indicates to the UE that the session is complete.” 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
TS 26.346 Rel-7 extends FLUTE usage with caching directives for FLUTE-delivered files, FLUTE FDT delivery via OMA Push, and FLUTE session setup and control with RTSP using the FLUTE/UDP transport.
- “The RTSP transport protocol specifier for FLUTE as defined in [88] shall be "FLUTE/UDP". One and only one UDP port is allocated for each FLUTE channel.” TS 26.346 v7.11.0
- “The BM-SC distributes FLUTE FDT instance which allows the MBMS UE to fetch files of interest.” TS 26.346 v7.11.0
- “A file download service may indicate the caching recommendations for a specific file or set of files that are delivered using FLUTE.” TS 26.346 v7.11.0
MBMS download delivery gained a new FLUTE FDT extension: a "FullFDT" attribute in the FDT-Instance lets the server signal that an FDT instance equals the full File Delivery Table.
- “A new attribute "FullFDT" is created within the element "FDT-Instance" of the FDT to indicate to the receivers” TS 26.346 v8.7.0
- “the server shall set the “FullFDT” attribute in the FLUTE FDT instance file” TS 26.346 v8.7.0
FLUTE usage in MBMS download changed: a new "Decryption-KEY-URI" FDT file attribute links protected files to decryption key files, FDT schemas/namespaces were updated for 2009, and segment URIs are described with FLUTE.
- “A new attribute "Decryption-KEY-URI" is created within element "file" of the FDT to indicate the association between protected download file and relevant decryption key file.” TS 26.346 v9.15.0
- “the UE may instruct its FLUTE receiver to download the relevant decryption key file according to "Decryption-KEY-URI" field in file element of FDT instance.” TS 26.346 v9.15.0
- “The download delivery method allows the delivery of AHS segments and Media Presentation Descriptions as defined in [47]. Segment URIs are described using FLUTE.” TS 26.346 v9.15.0
TS 26.346 added requirements for DASH over MBMS using FLUTE: download delivery user services must reference an SDP describing FLUTE, and Segments and MPD updates delivered as FLUTE objects must meet specified conditions.
- “the user service shall be a download delivery service, i.e. shall include at least one downloadDelivery method element referencing an SDP that describes FLUTE transport.” TS 26.346 v10.13.0
- “If a Segment is delivered as a FLUTE object then all of the following shall hold:” TS 26.346 v10.13.0
- “the UE should expect MPD updates to be sent in the FLUTE session with the media segments” TS 26.346 v10.13.0
FLUTE FDT schema was extended in Rel-11 with a FEC-Redundancy-Level attribute, a new 3GPP FDT namespace, and support for alternative TMGIs and partial file delivery in FLUTE sessions.
- “The attribute " FEC-Redundancy-Level" is included within element "file" of the FDT to indicate the FEC redundancy level for the file.” TS 26.346 v11.14.0
- “The Release 11 extension of the FLUTE FDT schema is as follows:” TS 26.346 v11.14.0
- “the alternative-tmgi attribute as defined in clause 7.3.2.12 shall be used.” TS 26.346 v11.14.0
MBMS download delivery over FLUTE gained new requirements: FLUTE-delivered objects with availability times, application service document updates carried as FLUTE objects, and r12:broadcastAppService declaring content delivered over the FLUTE session.
- “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 shall match” TS 26.346 v12.12.0
- “shall declare the one or more application service content items delivered over the FLUTE session associated with that deliveryMethod instance.” TS 26.346 v12.12.0
- “If an object is delivered as a FLUTE object with an availability time defined by service is delivered then all of the following shall hold:” TS 26.346 v12.12.0
TS 26.346 added FLUTE-related requirements: Initialization Segments and MPD updates delivered as FLUTE objects, HTML5 resources on the same FLUTE session, in-band metadata fragments sent on the FLUTE session, and Content-MD5 versioning of SA files.
- “If an Initialization Segment (with or without a metadata envelope) is delivered as a FLUTE object then the URI of the delivered object shall match the appropriate reference in the MPD.” TS 26.346 v13.7.0
- “In-band metadata fragments shall be sent on the FLUTE session of a MBMS User Service together with the actual content for that MBMS User Service, not on the SACH.” TS 26.346 v13.7.0
- “an updated SA file shall be transmitted with a new Content-MD5 value in the FLUTE FDT Instance describing the file with the same URL.” TS 26.346 v13.7.0
FLUTE usage in MBMS was extended: Receive-Only-Mode services are delivered over FLUTE sessions via the ROM SACH, FLUTE multicast addresses are assigned for it, and FLUTE headers count toward transparent-session bandwidth.
- “The TV service configuration Management Object as defined in TS 24.117 [132] may include the session parameters for FLUTE sessions that carry ROM services.” TS 26.346 v14.8.0
- “The assigned multicast address will be contained in the header of FLUTE packets carrying the contents of a Service Announcement service” TS 26.346 v14.8.0
- “The size of a packet shall include the complete packet, i.e. IP, UDP and FLUTE headers, and the data payload.” TS 26.346 v14.8.0
The MBMS Download Profile and an SDP implementation profile for FLUTE sessions were specified in TS 26.346 for Rel-16, covering FDT usage, 'FLUTE/UDP' proto field, MPD updates, and Media Playlist handling.
- “For the MBMS download delivery method, the <proto> field of the media descriptions ("m=") line of the SDP shall be set to 'FLUTE/UDP'.” TS 26.346 v16.11.1
- “In addition, an implementation profile of the SDP for a FLUTE session is included, based on the description in clause 7.3 of this specification.” TS 26.346 v16.11.1
- “It is recommended to transmit the updated Media Playlist with a new Content-MD5 value in the FLUTE FDT” TS 26.346 v16.11.1
Rel-17 specifies FLUTE usage for 5G MBS in TS 26.517 (Object Distribution Method, SDP, object repair) and adds a reduced FLUTE FDT schema in TS 26.346.
- “If FLUTE [12] is used to realise the Object Distribution Method, the MBS Distribution Session shall conform to the MBMS Download Profile” TS 26.517 v17.11.0
- “The Object Repair mechanism for FLUTE shall not be used with the OBJECT_STREAMING mode” TS 26.517 v17.11.0
- [5MBP3]: Feature reduced FLUTE FDT Schema TS 26.346CR0661
FLUTE gained optional sender sending rules (object sequence number, sequential object sending) signalled via SDP, and receivers use them to detect object completion and loss for repair.
- “The FLUTE sender increments the TOI to sequentially with every object sent, allowing the receiving end to detect object loss.” TS 26.346 v19.3.0
- “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
- “the SDP indicates that the sequential sending FLUTE sending rule for multiple objects is in use for the object streaming session” TS 26.517 v19.3.0
Defining Specifications
3GPP specifications that define or reference FLUTE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.792 vg00 | MBMS API for Mission Critical Services | Rel-16 read |
| TS 26.142 vj00 | 3GPP TS 26.142: Dynamic and Interactive Multimedia Scenes (DIMS) | Rel-19 read |
| TS 26.244 vj10 | 3GPP File Format (3GP) Specification | Rel-19 read |
| 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.849 vc10 | MBMS Operation on Demand (MooD) | Rel-12 read |
| TS 26.850 vg00 | Massive File Delivery for IoT Devices | Rel-16 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.938 vj00 | DASH Deployment Guidelines for 3GPP Networks | 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 29.116 vj00 | REST-based protocol for xMB reference point | Rel-19 read |
| TS 33.246 vj00 | MBMS Security Specification | Rel-19 read |