Every requirement the documents place on FLUTE, grouped by feature, and for each one whether unprofiled FLUTE, MBMS download and MBS Object Distribution require it.
At a glance
- Unprofiled FLUTE: the IETF documents alone. Version 1 is RFC 3926, on ALC (RFC 3450) and LCT (RFC 3451); version 2 is RFC 6726, on ALC (RFC 5775) and LCT (RFC 5651). The FEC building block, the FEC schemes and WEBRC congestion control complete it.
- MBMS download: MBMS clients and servers implement RFC 3926 with the ALC and LCT features it inherits, plus the extended aspects of TS 26.346 clause 7.2, the session description of clause 7.3 and the MBMS Download Profile of annex L.4.
- MBS Object Distribution: the MBS Distribution Session conforms to the MBMS Download Profile, describes its objects with the Profiled FDT Schema of TS 26.346 annex L.6, and takes its session description from TS 26.346 clause 7.3 with the restrictions and extensions of TS 26.517 clause 6.2.2.
- Releases: the documents read are TS 26.346 V17.6.0, V18.2.0 and V19.3.0, and TS 26.517 V17.11.0, V18.7.0 and V19.3.0. What changes between them is listed at the end.
How to read the tables
- Each row is one requirement, gathered from the sentences of one or more documents that state it. The cell names the sections or clauses, and the strongest keyword they use: shall (MUST, SHALL, REQUIRED, or a plain statement that something is mandatory, supported or contained), shall not (including a statement that something is not used or excluded), should (SHOULD, RECOMMENDED), may (MAY, OPTIONAL). If used marks an FEC scheme or a congestion control scheme, whose rules apply when it is chosen.
- Unprofiled FLUTE lists the sections of FLUTE version 1 (v1) and version 2 (v2).
- On an IETF row, the 3GPP columns say whether the profile takes the requirement as the RFC has it, or which clause changes, strengthens or replaces it (not used). Not named in the profile marks an FEC scheme the profile does not list.
- A 3GPP row applies only where its clause is given; a dash means the profile does not carry it.
- Side says who the requirement falls on: the sender, the receiver, both, or the session description that reaches the receiver before it joins.
Sessions, objects and packets
How a session and its objects are identified in each packet, and what a receiver checks before it accepts one.
Defined in RFC 3450, RFC 3451, RFC 3738, RFC 3926, RFC 5651, RFC 5775, RFC 6726, TS 26.346, TS 26.517
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Transport Session Identifier: one per session, in every packet, unique per sender | Sender | v1: RFC 3450 sections 1.3, 2.1, 4.2, 4.4; RFC 3451 sections 4.1, 5.1 · v2: RFC 5775 section 2.1; RFC 5651 section 4.1 (shall) | As the RFC | As the RFC | |
| Receiver demultiplexes on sender address and TSI and validates each packet | Receiver | v1: RFC 3450 sections 1.3, 4.5; RFC 3451 section 4.1; RFC 3738 section 4.1 · v2: RFC 6726 section 3.1; RFC 5775 section 4.4 (shall) | As the RFC | As the RFC | |
| Transport Object Identifier: a unique TOI per object, in every packet of the session | Sender and receiver | v1: RFC 3926 section 3.1; RFC 3450 sections 2.1, 2.3, 4.1, 4.2, 4.4, 4.5; RFC 3451 sections 5.1, 6.1 · v2: RFC 6726 section 3.1; RFC 5775 section 4.3; RFC 5651 section 6.1 (shall) | As the RFC | As the RFC | |
| A receiver processes the ALC/LCT header or leaves; it obtains the session description first | Receiver | v1: RFC 3450 section 4.5; RFC 3451 sections 4, 6.1, 6.2; RFC 3738 section 3 · v2: RFC 5651 section 6.2 (shall) | As the RFC | As the RFC | |
| Objects and FDT Instances multiplexed within a session | Sender | v1: RFC 3926 section 3.5; RFC 3450 section 4.4; RFC 3451 section 6.1 · v2: RFC 6726 section 3.5 (should) | As the RFC | As the RFC | |
| MBMS clients and servers implement RFC 3926 with the ALC and LCT features FLUTE inherits | Sender and receiver | – | TS 26.346 clause 7.2.0 (shall) | – | |
| The MBS Distribution Session conforms to the MBMS Download Profile, with the Profiled FDT Schema | Sender | – | – | TS 26.517 clause 6.2.1 (shall) |
LCT header and extensions
The fields of the LCT header and the header extensions FLUTE uses.
Defined in RFC 3450, RFC 3451, RFC 5651, RFC 5775, RFC 6726, TS 26.346
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Default LCT header, version 1, its field lengths and reserved bits | Sender and receiver | v1: RFC 3450 sections 2, 2.1, 4.1, 4.2; RFC 3451 sections 5, 5.1 · v2: RFC 6726 sections 3.1, 11.1; RFC 5775 sections 2, 4.1; RFC 5651 sections 5, 5.1 (shall) | Changed by TS 26.346 clause 7.2.7 | As the RFC | |
| Close Session (A) and Close Object (B) flags | Sender and receiver | v1: RFC 3450 section 4.2; RFC 3451 section 5.1 (should) | Changed by TS 26.346 clause 7.2.7 | As the RFC | |
| Expected Residual Time bound | Sender | v1: RFC 3450 section 4.2; RFC 3451 sections 5, 5.1 (shall not) | Changed by TS 26.346 clauses 7.2.7, L.4.7 | Changed by TS 26.346 clause L.4.7 | |
| Header extensions: processed before acceptance, EXT_NOP supported, EXT_AUTH recognised | Sender and receiver | v1: RFC 3450 section 4.3; RFC 3451 section 5.2 · v2: RFC 5651 sections 5.2.1, 5.2.2 (shall) | As the RFC | As the RFC | |
| Codepoint field | Sender and receiver | v1: RFC 3450 section 2.1 (may) | As the RFC | As the RFC | |
| ALC/LCT header specialisations: 32-bit zero CCI, 16-bit TSI, 16-bit TOI, TOI 0 for FDT Instances, T and R zero, HDR_LEN | Sender and receiver | – | TS 26.346 clause 7.2.7 (shall) | – | |
| Close Session and Close Object flags may signal the end of session and of object | Sender | – | TS 26.346 clause 7.2.7 (may) | – | |
| EXT_TIME, when included, carries the Expected Residual Time | Sender | – | TS 26.346 clause 7.2.7 (shall) | – | |
| EXT_FTI in every packet of an FDT Instance and never in packets of files; no EXT_CENC | Sender | – | TS 26.346 clause 7.2.8 (shall) | – | |
| MBMS Download Profile: EXT_FTI for FDT Instances, the FDT for the FEC Object Transmission Information of files | Sender and receiver | – | TS 26.346 clause L.4.7 (should) | TS 26.346 clause L.4.7 (should) | |
| MBMS Download Profile: Sender Current Time and Expected Residual Time not used (T and R flags, EXT_TIME); set to zero, ignored by the UE | Sender and receiver | – | TS 26.346 clause L.4.7 (shall not) | TS 26.346 clause L.4.7 (shall not) | |
| Annex A: A, B, T and R flags at the MBMS client and server | Sender and receiver | – | TS 26.346 table A.1 (shall) | – |
File Delivery Table
The in-band table that describes each file: its instances, syntax, schema, expiry and the attributes each profile requires or excludes.
Defined in RFC 3926, RFC 6726, TS 26.346, TS 26.517
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| An FDT local to each session, with an entry mapped to a TOI for every file | Sender | v1: RFC 3926 sections 3.2, 3.3 · v2: RFC 6726 section 3.2 (shall) | As the RFC | As the RFC | |
| FDT Instances on TOI 0, each packet with the FDT Instance Header (EXT_FDT), version field | Sender and receiver | v1: RFC 3926 sections 3.3, 3.4, 3.4.1, 5.1 · v2: RFC 6726 sections 3.3, 3.4, 3.4.1, 11.1 (shall) | As the RFC | As the RFC | |
| FDT Instance syntax: Expires; per file TOI and Content-Location; the HTTP attributes | Sender and receiver | v1: RFC 3926 sections 3, 3.4.2 · v2: RFC 6726 sections 3, 3.4.2 (shall) | Changed by TS 26.346 clauses 7.2.9, L.4.2, L.4.3, L.4.4 | Changed by TS 26.346 clauses L.4.2, L.4.3, L.4.4; TS 26.517 clause 6.2.1 | |
| Extending the FDT schema: per-file descriptors in File, common ones in FDT-Instance | Sender | v1: RFC 3926 section 3.4.2 (shall) | Changed by TS 26.346 clauses 7.2.10.1, L.4.5 | Changed by TS 26.346 clauses L.4.5, L.6.2, L.6.3 | |
| FDT dynamics: a TOI described more than once never changes; expiry in the future; no use after expiry | Sender and receiver | v1: RFC 3926 section 3.3 · v2: RFC 6726 section 3.3 (shall) | Strengthened by TS 26.346 clause 7.2.9 | As the RFC | |
| FDT Instances sent first and at least as reliably as the files they describe | Sender | v1: RFC 3926 sections 3.3, 4 · v2: RFC 6726 sections 3.3, 4, 11.1 (should) | As the RFC | As the RFC | |
| Transport file grouping by group names in the FDT | Sender and receiver | – | TS 26.346 clause 7.2.6 (shall) | – | |
| FDT data: extended schema used; Content-Location, TOI, Expires, Content-Length, Content-Type, FEC Encoding ID and FEC OTI mandatory; optional elements listed | Sender | – | TS 26.346 clause 7.2.9 (shall) | – | added in Release 19 |
| The UE shall not use an FDT Instance beyond its expiry | Receiver | – | TS 26.346 clause 7.2.9 (shall not) | – | |
| Extended FDT schema, schemaVersion element and schema version selection at the UE | Sender and receiver | – | TS 26.346 clause 7.2.10.1 (shall) | – | Release 17 and 18 text replaced in Release 19, added in Release 19 |
| FullFDT: an FDT Instance equivalent to the full File Delivery Table | Sender and receiver | – | TS 26.346 clause 7.2.14 (shall) | – | |
| MBMS Download Profile, attributes at both levels: required, permitted and excluded | Sender and receiver | – | TS 26.346 clause L.4.2 (shall) | TS 26.346 clause L.4.2 (shall) | |
| MBMS Download Profile, FDT-Instance level: parameters the sender does not use | Sender and receiver | – | TS 26.346 clause L.4.3 (shall) | TS 26.346 clause L.4.3 (shall) | |
| MBMS Download Profile, File level: required, permitted, override-only and excluded attributes | Sender and receiver | – | TS 26.346 clause L.4.4 (shall) | TS 26.346 clause L.4.4 (shall) | |
| schemaVersion and delimiter elements: delimiter set to 0, its content ignored | Sender and receiver | – | TS 26.346 clause L.4.5 (should) | TS 26.346 clause L.4.5 (should) | |
| Profiled FDT schema: semantics, schemaVersion, version selection and extensibility | Sender and receiver | – | – | TS 26.346 clauses L.6.2, L.6.3 (shall) | Release 17 and 18 text replaced in Release 19, added in Release 19 |
| Objects described in an FDT Instance with Expires; File-ETag and Content-MD5 optional | Sender | – | – | TS 26.517 clause 6.2.1 (shall) | |
| MBMS Session Identity in the FDT | Sender and receiver | – | TS 26.346 clause 7.2.11 | – | |
| Extended FDT schema listing and its 3GPP extension schemas | Sender and receiver | – | TS 26.346 clause 7.2.10 | – | |
| Profiled FDT schema listing | Sender and receiver | – | – | TS 26.346 clause L.6.1 | |
| Annex A: FDT attributes and FEC OTI elements required at the MBMS client and server | Sender and receiver | – | TS 26.346 table A.1 (shall) | – |
FEC and blocking
How files are split into source blocks and encoding symbols, the FEC schemes, and how the FEC Object Transmission Information reaches the receiver.
Defined in RFC 3450, RFC 3452, RFC 3695, RFC 3926, RFC 5052, RFC 5053, RFC 5445, RFC 5775, RFC 6330, RFC 6726, TS 26.346
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| An FEC Payload ID in every packet, used by the receiver to place the symbols | Sender and receiver | v1: RFC 3450 sections 2.3, 4.4; RFC 3452 section 3; RFC 5052 sections 6, 6.1 · v2: RFC 5775 section 2.3 (shall) | Changed by TS 26.346 clause 7.2.7 | As the RFC | |
| FEC Object Transmission Information delivered in band, by EXT_FTI and the FDT, identical in both | Sender and receiver | v1: RFC 3926 sections 5, 5.2; RFC 3450 sections 2.3, 4.4, 4.5 · v2: RFC 6726 section 5 (shall) | Changed by TS 26.346 clauses 7.2.8, L.4.7 | Changed by TS 26.346 clause L.4.7 | |
| Encoding symbol length and the source block structure algorithm | Sender and receiver | v1: RFC 3926 sections 5.1.2.1, 5.1.2.2 (shall) | Changed by TS 26.346 clauses 7.2.3, L.4.7 | Changed by TS 26.346 clause L.4.7 | |
| Compact No-Code FEC scheme (FEC Encoding ID 0) | Sender and receiver | v1: RFC 3695 sections 2.1, 2.2, 3.1, 3.2 (shall) | Changed by TS 26.346 clauses 7.2.1, 7.2.2, L.4.7 | Changed by TS 26.346 clause L.4.7 | |
| Compact FEC scheme (FEC Encoding ID 130) | Sender and receiver | v1: RFC 3695 section 2.3 (if used) | Not named in the profile | Not named in the profile | |
| Raptor FEC scheme (FEC Encoding ID 1) | Sender and receiver | v1: RFC 5053 sections 3.1, 3.2.1, 4.1, 5.2, 5.3.1.2, 5.3.2, 5.4.1, 5.5.2.1 (if used) | Changed by TS 26.346 clauses 7.2.1, 7.2.2, L.4.7 | Changed by TS 26.346 clause L.4.7 | |
| RaptorQ FEC scheme (FEC Encoding ID 6) | Sender and receiver | v1: RFC 6330 sections 3.2, 3.3.1, 4.2, 4.3, 4.4.1.2, 4.4.2, 5.3.2, 5.8 (if used) | Not named in the profile | Not named in the profile | |
| Basic FEC schemes of RFC 5445 (Compact No-Code, Small Block Large Block Expandable) | Sender and receiver | v1: RFC 5445 sections 3.2.1, 3.2.2.2, 3.3, 3.4.2, 4.2.2.3, 4.3, 5.2.2.2, 5.2.2.3, 5.3, 6.2.1, 6.2.2.3, 6.3 (if used) | Not named in the profile | Not named in the profile | |
| FEC Payload ID: 16-bit SBN and 16-bit ESI for Compact No-Code; clause 7.2.12.1 for the MBMS FEC scheme | Sender and receiver | – | TS 26.346 clause 7.2.7 (shall) | – | |
| Compact No-Code supported; every UE decodes Raptor and recovers any source block RFC 5053 encodes | Sender and receiver | – | TS 26.346 clauses 7.2.1, 7.2.2 (shall) | – | |
| Blocking: RFC 3926 algorithm for Compact No-Code, RFC 5053 for Raptor; sub-blocks under 256 KB | Sender | – | TS 26.346 clause 7.2.3 (shall) | – | |
| MBMS Download Profile: Compact No-Code and Raptor optional to implement by the BM-SC, mandatory to support by the UE | Sender and receiver | – | TS 26.346 clause L.4.7 (shall) | TS 26.346 clause L.4.7 (shall) | |
| MBMS Download Profile: blocking per RFC 3695 for Compact No-Code and RFC 5053 for Raptor | Sender | – | TS 26.346 clause L.4.7 (shall) | TS 26.346 clause L.4.7 (shall) | |
| FEC-Redundancy-Level of individual transport objects in the FDT | Sender and receiver | – | TS 26.346 clause 7.2.16 (may) | – | |
| MBMS FEC scheme definition (Raptor, FEC Encoding ID 1): FEC Payload ID and OTI | Sender and receiver | – | TS 26.346 clause 7.2.12 | – | |
| Annex A: blocking and symbol encoding required at the MBMS client and server | Sender and receiver | – | TS 26.346 table A.1 (shall) | – |
Congestion control and channels
Multiple-rate congestion control, which FLUTE requires and the 3GPP profiles replace with one channel at one rate.
Defined in RFC 3450, RFC 3451, RFC 3452, RFC 3738, RFC 5052, RFC 5651, RFC 5775, RFC 6726, TS 26.346
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| A multiple-rate, feedback-free congestion control building block, applied to every packet | Sender and receiver | v1: RFC 3450 sections 2.1, 2.2, 4.1, 4.2; RFC 3451 sections 3, 4, 7; RFC 3452 sections 4, 6; RFC 5052 sections 5, 10 · v2: RFC 6726 section 1.1.4; RFC 5775 section 2.2; RFC 5651 sections 3, 4.3, 7 (shall) | Not used (TS 26.346 clauses 7.1, 7.2.4, L.4.7) | Not used (TS 26.346 clause L.4.7) | |
| Sender fills the CCI and sends at the rates the building block dictates | Sender | v1: RFC 3450 section 4.4; RFC 3451 section 6.1 (shall) | Not used (TS 26.346 clauses 7.1, 7.2.4, L.4.7) | Not used (TS 26.346 clause L.4.7) | |
| Receiver runs the congestion control on each session, or does not join | Receiver | v1: RFC 3450 section 4.5; RFC 3451 section 6.2 (shall) | Not used (TS 26.346 clauses 7.1, 7.2.4, L.4.7) | Not used (TS 26.346 clause L.4.7) | |
| WEBRC sender: waves, rates and the CCI formats | Sender | v1: RFC 3738 sections 3.1.1, 3.1.2, 4.1, 5, 5.1, 5.2 (if used) | Not used (TS 26.346 clauses 7.1, 7.2.4, L.4.7) | Not used (TS 26.346 clause L.4.7) | |
| WEBRC receiver: joining, leaving, rate estimation and timeouts | Receiver | v1: RFC 3738 sections 3, 3.2.1, 3.2.2.1, 3.2.2.2, 3.2.2.4, 3.2.2.5, 3.2.2.6, 3.2.3.3, 3.2.3.4, 3.2.3.6, 3.2.3.7, 3.2.3.8 (if used) | Not used (TS 26.346 clauses 7.1, 7.2.4, L.4.7) | Not used (TS 26.346 clause L.4.7) | |
| No congestion control: a single FLUTE channel at a single rate | Sender | – | TS 26.346 clauses 7.1, 7.2.4 (shall) | – | |
| MBMS Download Profile: congestion control not used, a single channel at a single rate | Sender | – | TS 26.346 clause L.4.7 (shall not) | TS 26.346 clause L.4.7 (shall not) | |
| Annex A: single channel support required at the MBMS client and server | Sender and receiver | – | TS 26.346 table A.1 (shall) | – |
Content encoding
Compression of files and of FDT Instances before transport.
Defined in RFC 3926, RFC 6726, TS 26.346
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Content encoding of FDT Instances, signalled by EXT_CENC | Sender and receiver | v1: RFC 3926 section 3.4.3 · v2: RFC 6726 section 3.4.3 (shall) | Not used (TS 26.346 clause 7.2.8) | As the RFC | |
| Files may be gzip encoded for transport; every UE decodes gzip | Sender and receiver | – | TS 26.346 clause 7.2.5 (shall) | – | |
| FDT Instances are not content encoded and EXT_CENC is not used | Sender | – | TS 26.346 clause 7.2.8 (shall not) | – | |
| Annex A: content encoding of files required at the MBMS client; FDT Instances not encoded by the server | Sender and receiver | – | TS 26.346 table A.1 (shall) | – |
Session description
What a receiver obtains before joining, and the SDP the 3GPP profiles define for it.
Defined in RFC 3450, RFC 3451, RFC 3926, RFC 5651, RFC 5775, RFC 6726, TS 26.346, TS 26.517
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Session description content and its delivery before joining | Session description | v1: RFC 3926 section 6; RFC 3450 sections 2.4, 4.2, 4.4; RFC 3451 sections 4, 6.1 · v2: RFC 6726 section 6; RFC 5775 section 2.4; RFC 5651 section 4 (shall) | Changed by TS 26.346 clauses 7.3.2.0, 7.3.2.1, 7.3.2.3, 7.3.2.4, 7.3.2.5, 7.3.2.6, 7.3.2.7, 7.3.2.8, 7.3.2.10, 7.3.2.11, 7.3.2.12, 7.3.2.13, 7.3.2.14, L.4.7, L.4.8 | Changed by TS 26.346 clauses 7.3.2.0, 7.3.2.1, 7.3.2.3, 7.3.2.4, 7.3.2.5, 7.3.2.6, 7.3.2.7, 7.3.2.8, 7.3.2.10, 7.3.2.11, 7.3.2.12, 7.3.2.13, 7.3.2.14, L.4.7, L.4.8; TS 26.517 clauses 6.2.2.1, 6.2.2.2 | |
| SDP for a FLUTE session: source address, channels, TSI, timing, bearer mode, FEC, bandwidth, protocol and media | Session description | – | TS 26.346 clauses 7.3.2.0, 7.3.2.1, 7.3.2.3, 7.3.2.4, 7.3.2.5, 7.3.2.6, 7.3.2.7, 7.3.2.8, 7.3.2.10, 7.3.2.11, 7.3.2.12, 7.3.2.13, 7.3.2.14 (shall) | TS 26.346 clauses 7.3.2.0, 7.3.2.1, 7.3.2.3, 7.3.2.4, 7.3.2.5, 7.3.2.6, 7.3.2.7, 7.3.2.8, 7.3.2.10, 7.3.2.11, 7.3.2.12, 7.3.2.13, 7.3.2.14 (shall) | added in Release 19 |
| MBMS Download Profile: SDP parameters mandatory, optional or not applicable (table L.4.8-1) | Session description | – | TS 26.346 clauses L.4.7, L.4.8 (shall) | TS 26.346 clauses L.4.7, L.4.8 (shall) | |
| MBMS Download Profile: OMA Push and RTSP excluded | Session description | – | TS 26.346 clause L.4.1 (shall not) | TS 26.346 clause L.4.1 (shall not) | |
| Transparent delivery services: announcement profile | Session description | – | TS 26.346 clause L.5 (shall) | – | |
| OMA Push over other bearers | Session description | – | TS 26.346 clause 7.1 (may) | – | |
| MBS session description: restrictions on TS 26.346 clause 7.3 and the mbs-servicetype attribute | Session description | – | – | TS 26.517 clauses 6.2.2.1, 6.2.2.2 (shall) | |
| SDP parameters for a FLUTE session (table L.4.8-1) | Session description | – | TS 26.346 clause L.4.8 | TS 26.346 clause L.4.8 |
Reception and operating modes
How objects are organised for delivery in an MBS Distribution Session.
Defined in TS 26.517
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Operating modes: single object, collection, carousel and segment streaming | Sender | – | – | TS 26.517 clauses 6.2.3.1, 6.2.3.3, 6.2.3.4, 6.2.3.5 (shall) |
Caching directives
How a file download service signals how long received files may be cached.
Defined in TS 26.346
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Caching directives (no-cache, max-stale, Expires) and their use with the download modes | Sender and receiver | – | TS 26.346 clause 7.2.13 (should) | – |
Repair
Recovery of missing data over unicast, during or after the session, and reporting of reception.
Defined in TS 26.346, TS 26.517
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Post-session Object Repair | Receiver | – | – | TS 26.517 clauses 6.2.1, 6.2.4.1, 6.2.4.2, 6.2.4.4, 6.2.4.5, 6.2.4.6 (shall) | |
| In-session unicast Object Repair (Release 19) | Receiver | – | – | TS 26.517 clauses 6.2.4.3.3, 6.2.4.3.4, 6.2.4.3.5 (shall) | Release 19 |
| Post-delivery file repair (associated delivery procedure) | Receiver | – | TS 26.346 clause 9.3 | – | |
| Reception reporting (associated delivery procedure) | Receiver | – | TS 26.346 clause 9.4 | – | |
| In-session unicast file repair (Release 19) | Receiver | – | TS 26.346 clause 9.4B | – | Release 19 |
Security
Integrity, authentication and protection of the session description and of protected files.
Defined in RFC 3450, RFC 3451, RFC 3452, RFC 3738, RFC 3926, RFC 5052, RFC 5053, RFC 5651, RFC 5775, RFC 6330, RFC 6726, TS 26.346
Requirements by profile
| Requirement | Side | Unprofiled FLUTE | MBMS download | MBS Object Distribution | Releases |
|---|---|---|---|---|---|
| Integrity check of each reconstructed object and FDT Instance | Receiver | v1: RFC 3926 section 7; RFC 3450 section 5; RFC 3451 section 8; RFC 3452 section 7; RFC 5052 section 11; RFC 5053 section 6; RFC 6330 section 6 · v2: RFC 6726 sections 7.2.1, 7.2.2, 7.3.2 (should) | As the RFC | As the RFC | |
| Packet authentication (EXT_AUTH, TESLA) | Sender and receiver | v1: RFC 3926 section 7; RFC 3450 sections 2.5, 4.3, 4.4, 4.5, 5; RFC 3451 sections 5.2, 6.2, 8; RFC 3452 section 7; RFC 5052 section 11; RFC 5053 section 6; RFC 6330 section 6; RFC 3738 section 7 · v2: RFC 6726 sections 7.3.3, 7.3.4, 7.4, 7.5; RFC 5775 sections 2.5, 5, 5.1, 5.1.1, 5.1.2.1, 5.1.2.2, 5.1.2.3, 5.1.2.4, 5.1.2.5; RFC 5651 sections 8, 8.1, 8.2, 8.3 (shall) | As the RFC | As the RFC | |
| Protecting the session description and the receivers that obtain it | Session description | v1: RFC 3926 section 7; RFC 3450 section 5; RFC 3451 sections 7, 8; RFC 3452 section 7; RFC 3738 section 7; RFC 5052 section 11; RFC 5053 section 6; RFC 6330 section 6 · v2: RFC 6726 section 7.3.1 (should) | As the RFC | As the RFC | |
| Receiver without write access to system files | Receiver | v1: RFC 3926 section 7 (should) | As the RFC | As the RFC | |
| Network measures: Reverse Path Forwarding checks, rendezvous point placement | Network | v1: RFC 3926 section 7; RFC 3450 sections 1.3, 5; RFC 3451 section 8; RFC 3452 section 7; RFC 3738 section 7; RFC 5052 section 11; RFC 5053 section 6; RFC 6330 section 6 (should) | As the RFC | As the RFC | |
| Decryption-KEY-URI for protected download files | Sender and receiver | – | TS 26.346 clause 7.2.15 (shall) | – |
Changes by release
| Release | Document | What changes |
|---|---|---|
| 17 | TS 26.346 V17.6.0 and TS 26.517 V17.11.0 | The baseline of the three profiles: the Profiled FDT Schema of annex L.6 (schemaVersion 2) and the Object Distribution Method of TS 26.517 clause 6.2 are both in Release 17 |
| 18 | TS 26.346 V18.2.0 | No change to the clauses on this page |
| 18 | TS 26.517 V18.6.0 and V18.7.0 | Session description: the SDP timing refers to the service schedule descriptions (clause 6.2.2.1). Segment streaming: V18.6.0 lets the DASH MPD be included in the object list; V18.7.0, like V17.11.0, requires the DASH MPD, its ancillary resources and the initialisation segments to be in the object list and retransmitted (clause 6.2.3.5). In-session object repair is for further study (clause 6.2.4.3) |
| 19 | TS 26.346 V19.3.0 | The extended FDT schema goes to schemaVersion 5 (clause 7.2.10.1) and the Profiled FDT Schema to schemaVersion 3 (clause L.6.3). Repair-Start and Repair-Limit-Percentage join the optional FDT data (clause 7.2.9) and the Profiled FDT Schema (clause L.6.1). File@Expires leaves the Profiled FDT Schema, with the sentence that gave it precedence over FDT@Expires (clause L.6.2). In-session unicast file repair is added (clause 9.4B) |
| 19 | TS 26.517 V19.3.0 | In-session object repair is specified (clause 6.2.4.3) |
The IETF documents do not change with the 3GPP releases.
Sources for this page
- IETF: RFC 3926, RFC 3450, RFC 3451, RFC 3452, RFC 3695, RFC 3738, RFC 5052, RFC 5053, RFC 5445, RFC 6330, RFC 6726, RFC 5775 and RFC 5651; every MUST, SHALL, SHOULD, RECOMMENDED, MAY and OPTIONAL sentence outside the conventions, IANA and reference sections.
- 3GPP: TS 26.346 V17.6.0, V18.2.0 and V19.3.0, clauses 7.1 to 7.3, L.4, L.5 and L.6 and annex A (table A.1), and clauses 9.3, 9.4 and 9.4B by title; TS 26.517 V17.11.0, V18.6.0, V18.7.0 and V19.3.0, clause 6.2; every sentence with shall, should or may, or stating that something is mandatory, supported, not used or excluded, and the lists they introduce. Schema listings and table L.4.8-1 are listed by clause.
- Not on this page: rules addressed to the authors of FEC schemes and content delivery protocols (RFC 3452 and RFC 5052, what a scheme specification must define), and the IANA and conventions sections.
Related: Standards: Content Delivery Protocols · Technical Analysis: Content Delivery Protocols · Content Delivery Protocols Reference Tools