FD

File Distribution

Services →
Introduced in Rel-14

FD is a 3GPP service capability for ProSe and V2X that enables the efficient broadcast or multicast of files to a group of devices for uses like software updates or content distribution.

Category
Services
Introduced
Rel-14
Where
Services › IMS
Specifications
6 specs
FD Description Purpose Related Classification Detected Changes Specifications

Description

File Distribution is a service layer capability that facilitates the transfer of files from a content provider or application server to multiple recipient UEs. It is not a single protocol but a set of architectural functions and procedures defined across the service and application layer specifications. A key enabler for FD is the underlying broadcast/multicast bearer capabilities of the network, such as evolved Multimedia Broadcast Multicast Service (eMBMS) in 4G/5G or sidelink communication for direct device-to-device transfer. The FD service manages the session announcement, file delivery, and reception reporting.

The architecture typically involves a File Distribution Server (or Application Server), the broadcast/multicast core network (e.g., BM-SC for eMBMS), and the UEs. The process begins with the server preparing the file for distribution, often segmenting it into smaller source blocks for forward error correction (e.g., using Raptor or RaptorQ codes as defined for MBMS). This creates a repair flow alongside the source flow to allow UEs to recover lost packets without feedback. The service then announces the upcoming file distribution session via a service announcement mechanism, providing UEs with the necessary parameters to join the session, such as session description, timing, and TMGI (Temporary Mobile Group Identity).

During the distribution phase, the file data is delivered over the broadcast/multicast bearer. UEs monitor the transmission and use the repair data to reconstruct the original file. For ProSe-based FD, specified for public safety and V2X, the distribution can occur over PC5 sidelink interfaces between UEs without network infrastructure. Here, one UE (the distributor) can broadcast a file to neighboring UEs within proximity. The 3GPP specifications define protocols for session management, congestion control, and security for such direct FD. The service also includes mechanisms for the server to obtain delivery reports, indicating how many UEs successfully received the file, which is crucial for applications like firmware updates over-the-air (FOTA).

Purpose & Motivation

File Distribution was created to address the need for efficient, scalable, and network-friendly dissemination of bulk data to large groups of users or devices. Unicast delivery (a separate stream to each UE) is highly inefficient for popular content or mandatory updates, causing network congestion and wasting radio resources. FD leverages broadcast/multicast technologies to transmit the data once over a shared radio resource, serving all interested UEs within a coverage area simultaneously.

Its introduction in Rel-14 was strongly motivated by the evolution of Proximity Services (ProSe) for public safety and the emergence of Vehicle-to-Everything (V2X) communication. Use cases such as distributing safety-critical maps, software updates for vehicle fleets, or multimedia content to a crowd at an event required a standardized method for group file transfer. Prior to this, such services relied on proprietary applications or inefficient unicast pulls. FD standardizes the procedures, enabling interoperability between devices and networks from different vendors. It solves the problem of congested unicast links in dense scenarios (like stadiums or traffic jams) and supports off-network operation for public safety, where devices must share files directly when cellular infrastructure is unavailable or damaged.

Classification

Part ofAL-FEC
Related approachesProSeV2X

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (12 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 3 changes

In Release 15, the specification newly introduced the functional model and information flow for the File Distribution (FD) capability for off-network operations. This included defining specific application plane reference points, such as MCData-FD-1 for session signalling and MCData-FD-5 for server access to stored files, to handle file distribution requests and responses. The release also detailed the integration with MBMS for multicast delivery, including procedures for using pre-established or dynamic MBMS bearers and the file fetching process by the MCData server.

  • Information flow of File Distribution for off-network TS 23.282CR0040
  • Functional model of File Distribution for off-network TS 23.282CR0041
  • Functional model of File Distribution for off-network TS 23.282CR0075
Rel-16 3 changes

In Release 16, the File Distribution (FD) function for MCData was enhanced with three key new capabilities. It introduced interconnection for file distribution, enabling service across different operator networks, and added support for using the MBMS download delivery method as a broadcast mechanism for efficient group file delivery. Furthermore, the release provided functional alias support, allowing file distribution to be addressed to a user's alias identifier rather than only their direct identity.

  • Interconnection for file distribution TS 23.282CR0138
  • MCData File Distribution using the MBMS download delivery method TS 23.282CR0150
  • Functional alias support for MCData File Distribution TS 23.282CR0157
Rel-17 5 changes

In Release 17, the File Distribution (FD) function received enhancements and corrections for procedures using HTTP, both for one-to-one and group communications. It also introduced clarifications for FD over MBMS, specifically regarding the MCData server's role in fetching files and using pre-established MBMS user services. Furthermore, a new addressing capability based on functional alias was added to the FD function.

  • File distribution addressing based on functional alias TS 23.282CR0181
  • Enhancement and corrections to group file distribution using HTTP TS 23.282CR0272
  • Enhancement and corrections to one-to-one file distribution using HTTP TS 23.282CR0273
  • Clarifications for MCData file distribution over MBMS TS 23.282CR0208
  • Corrections to the file distribution using HTTP procedures TS 23.282CR0264
Rel-19 1 change

In Release 19, the new development for the File Distribution (FD) function is the introduction of procedures to support ad hoc group standalone file distribution using HTTP. This enhancement builds upon the existing FD capabilities for one-to-one and group communications, which already support unicast, broadcast, and MBMS delivery methods. The new HTTP-based procedures provide an alternative method for establishing sessions and distributing files to MCData groups.

  • Information flows and procedures to support ad hoc group standalone file distribution using HTTP procedures TS 23.282CR0349

Explore further

Broader topics and technologies where FD plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.282 vk00 MCData Functional Architecture & Info Flows Rel-20
TS 23.784 vg00 Discreet Listening for Mission Critical Services Rel-16
TS 24.582 vj00 MCData Media Plane Control Protocols Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 37.579 vi40 Mission Critical services conformance testing Rel-18
TR 38.808 vh00 Study on NR above 52.6 GHz to 71 GHz Rel-17
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.