Skip to main content
Content Delivery Protocols and Tools

Architecture

At a glance
  • Unprofiled FLUTE: a file delivery session is an ALC/LCT session: one sender, one or more channels, identified by the sender's IP address and the TSI.
  • MBMS download: the BM-SC sends files, including DASH segments and MPDs, over MBMS bearers with FLUTE.
  • MBS Object Distribution: the MBSTF segments objects, optionally adds FEC and sends them over FLUTE; the MBS AS serves repair.

Unprofiled FLUTE: a file delivery session​

When FLUTE is used for file delivery over ALC, the ALC/LCT session is called the file delivery session (RFC 3926 section 3.1).

  • The session: a set of logically grouped ALC/LCT channels, associated with a single sender sending packets with ALC/LCT headers for one or more objects (RFC 3926 section 3.1). The pair of the source IP address and the Transport Session Identifier (TSI) uniquely identifies the session.
  • Channels: a channel is the combination of a sender and an address the sender associates with it (RFC 3926 section 3.1; TS 26.346 V19.3.0 clause 3.1). A receiver joins a channel to start receiving its packets and leaves it to stop.
  • Files and the FDT: each file in the session is associated with a Transport Object Identifier (TOI) (RFC 3926 section 3.1; RFC 3926 section 3.2). Each session has an FDT that provides a file description entry for every file it delivers; TOI 0 is reserved for the FDT Instances.

RFC 3926 envisages four ways to use channels and congestion control: a single channel with single-rate congestion control; multiple channels with multiple-rate congestion control; and a single channel, or multiple channels, without the congestion control of ALC, but only in a controlled network where flow and congestion control are provided by other means (RFC 3926 section 4).

MBMS download from the BM-SC​

Two stacks. Left, over a ptp bearer, IP unicast, TCP and UDP: HTTP(S) with HTTP-digest and MIKEY, carrying service announcement and metadata, associated-delivery procedures (ptp file repair, reception reporting) and MBMS security (registration, key distribution MSK). Right, over MBMS or ptp bearers, IP multicast or unicast, UDP/TCP: FLUTE with FEC carrying download of 3GPP files, binary data, still images and text, ptm file repair and service announcement; RTP/RTCP with SRTP and FEC for streaming codecs; HTTP(S) with HTTP digest for 3GP-DASH; MBMS security (key distribution MTK, MIKEY).
Protocol stack view of the MBMS User Services for Streaming and Download DeliveryRedrawn from TS 26.346 V19.3.0, figure 9Scroll sideways, or tap the figure to open it full size.

The figure shows the protocols MBMS User Services use for streaming and download delivery. The grey-shaded protocols and functions are outside the scope of TS 26.346.

  • The download delivery method uses FLUTE (RFC 3926) when it delivers content over MBMS bearers (TS 26.346 V19.3.0 clause 7.1). Over other bearers it may use OMA Push.
  • Files: a file may contain any type of MBMS data, for example 3GPP audio and video files, binary data, still images, text or Service Announcement metadata (TS 26.346 V19.3.0 clause 7.2.0). The term file covers every object FLUTE carries, except the FDT Instances.
  • Getting files from the FLUTE receiver: UE applications instruct it to receive all files available (promiscuous), one copy of specific files (one-copy), or specific files and every update to them (keep-updated) (TS 26.346 V19.3.0 clause 7.2.0).
  • Reliability: MBMS download delivery defines several methods to increase reliability, such as FEC and file repair (TS 26.346 V19.3.0 clause 5.6).
  • The MBMS Download Profile sets the usage of the FDT attributes and elements by the BM-SC, as the FLUTE sender, and their support by the MBMS Client, as the FLUTE receiver (TS 26.346 V19.3.0 clause L.4.1).

DASH over MBMS download​

The download delivery method also carries 3GP-DASH Segments, Media Presentation Descriptions (MPDs) and the other objects an MPD references (TS 26.346 V19.3.0 clause 5.6). When a Segment is delivered as a FLUTE object:

  • the last packet of the delivered object is available at the UE at its segment availability start time at the latest, as announced in the MPD; (TS 26.346 V19.3.0 clause 5.6)
  • the Content-Location element in the FDT for the delivered object matches the Segment URL in the MPD (TS 26.346 V19.3.0 clause 5.6).

MBS Object Distribution from the MBSTF​

Inside the MBSTF, Object ingest (fed at MBS-11, Nmb2 and Nmb8), Object segmentation, Application Layer FEC, Packetisation and Packet scheduling in sequence towards Nmb9, with a Control subfunction at Nmb2 and egest towards the MBS AS at MBS-12.
MBSTF architecture overview for Object Distribution MethodRedrawn from TS 26.502 V19.6.0, figure 4.3.3.2-1Scroll sideways, or tap the figure to open it full size.

The Object Distribution Method distributes discrete binary objects, including media segments, to MBS Clients as part of an MBS Session, in real time or not (TS 26.502 V19.6.0 clause 4.2.3; TS 26.502 V19.6.0 clause 6.1; TS 26.502 V19.6.0 clause 4.3.3.2). Inside the MBSTF:

  • Object ingest takes objects from the MBS Application Provider at Nmb8, pulled or pushed, and objects for the User Service Announcement Channel from the MBS AF at MBS-11 (TS 26.502 V19.6.0 clause 4.3.3.2; TS 26.502 V19.6.0 clause 4.4.1). To support object repair, it can make ingested objects available to the MBS AS at MBS-12.
  • Object segmentation partitions an object into payload units suitable for MBS transmission (TS 26.502 V19.6.0 clause 4.3.3.2).
  • Application Layer FEC, optional, supports object recovery when some packets are not received (TS 26.502 V19.6.0 clause 4.3.3.2).
  • Packetisation places the payload units, and optionally the FEC data, into Nmb9 transmission packets (TS 26.502 V19.6.0 clause 4.3.3.2).
  • Packet scheduling schedules the outgoing packet stream according to the target bit rate configuration (TS 26.502 V19.6.0 clause 4.3.3.2).

When FLUTE realises the Object Distribution Method, the MBSTF describes the objects it is currently transmitting with the profiled FDT schema of TS 26.346 annex L.6. To fetch missing portions of an object, the MBS Client may use the Object Repair mechanism for FLUTE, which the MBS AS provides at reference point MBS-4-UC.

Segment streaming​

The OBJECT_STREAMING operating mode is recommended for streaming DASH or HLS content to a Media Player in the UE (TS 26.517 V19.3.0 clause 6.2.3.5; TS 26.346 V19.3.0 clause 5.6). In it, as in DASH over MBMS download:

  • the MBSTF transmits each object so that the last packet of the FLUTE transmission object, FEC repair packets included, is available at the MBSTF Client no later than its availability start time; (TS 26.517 V19.3.0 clause 6.2.3.5)
  • the Content-Location element in the FDT Instance matches the URL of the corresponding object in the object list (TS 26.517 V19.3.0 clause 6.2.3.5).
Sources for this page
  • Unprofiled FLUTE: RFC 3926, sections 3.1 and 4 (RFC 3926 section 3.1; RFC 3926 section 4).
  • MBMS download: TS 26.346 V19.3.0, clauses 5.5, 5.6, 7.1, 7.2.0 and L.4.1.
  • Figure (MBMS): redrawn from TS 26.346 V19.3.0, figure 9.
  • MBS Object Distribution: TS 26.502 V19.6.0, clauses 3.1 (Object Distribution Method) and 4.3.3.2; TS 26.517 V19.3.0, clauses 6.2.1 and 6.2.3.5.
  • Figure (MBS): redrawn from TS 26.502 V19.6.0, figure 4.3.3.2-1.