Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 26.848  Word version:  12.0.0

Top   Top   Up   Prev   None
1…   4…

 

4  Enhanced MBMS Operationp. 9

4.1  Introductionp. 9

4.2  Enhancement, Recommended Requirements and Working assumptionsp. 9

4.2.1  Switch from HTTP-based unicast delivery method to MBMS download delivery methodp. 9

4.2.2  Potential FLUTE Enhancementsp. 14

4.2.2.1  Deployment Architecture considerationsp. 14

4.2.2.2  High-Level Design Principlesp. 16

4.2.2.3  Recommended Requirements & Evaluation Criteriap. 17

4.2.2.4  Gap Analysis & Evaluationp. 19

4.2.2.4.1  Type 1: Backward compatible towards Rel-11 and earlier UEsp. 19
4.2.2.4.2  Type 2: Backward compatible towards Rel-11 and earlier Networksp. 20
4.2.2.4.3  Type 3: Backward compatible towards Rel-11 and earlier Networks and UEsp. 20
4.2.2.4.4  Type 4: UEs of Rel-11 and earlier releases ignore content delivered over Rel-12 FLUTE+p. 20
4.2.2.4.5  Considered Strictly backward-compatible extensionsp. 20
4.2.2.4.5.1  Generalp. 20
4.2.2.4.5.2  LCT based on RFC 5651p. 20
4.2.2.4.5.3  File Delivery Table Instance Descriptorp. 21
4.2.2.4.5.4  Extensions to FDT Instancep. 21
4.2.2.4.5.5  Extension Headersp. 23
4.2.2.4.5.6  Code Pointsp. 24
4.2.2.4.5.7  Object expiration mechanism for FLUTE enhancementsp. 25
4.2.2.4.5.8  FLUTE packets of DASH Segments in different orderp. 26
4.2.2.4.6  ALC RFC differences and analysisp. 27

4.2.2.5  Assumptionsp. 29

4.2.2.6  Solutionp. 29

4.2.3  Datacasting Servicesp. 30

4.2.4  File Repair without FDTp. 33

4.2.5  Zapping Portal Servicesp. 36

4.2.6  Joint object protectionp. 40

4.2.7  Multiple FLUTE Sessions for an MBMS User Servicep. 40

4.2.8  Targeted Ad Insertionp. 48

4.2.9  Generic Application Service Delivery over MBMSp. 54

4.2.10  Improve MBMS OTA efficiencyp. 56

4.2.11  Multi-Program Support:p. 58

4.2.12  Robust DASH operation in live servicesp. 59

4.3  Related Change Requestsp. 60

5  Conclusionp. 60

$  Change historyp. 61


Up   Top