Content for TR 26.848 Word version: 12.0.0
4 Enhanced MBMS Operation
4.1 Introduction
4.2 Enhancement, Recommended Requirements and Working assumptions
4.3 Related Change Requests
5 Conclusion
$ Change history
4 Enhanced MBMS Operation p. 9
4.1 Introduction p. 9
4.2 Enhancement, Recommended Requirements and Working assumptions p. 9
4.2.1 Switch from HTTP-based unicast delivery method to MBMS download delivery method p. 9
4.2.1.1 Description p. 9
4.2.1.2 Recommended Requirements & Evaluation Criteria p. 9
4.2.1.3 Gap Analysis & Evaluation p. 10
4.2.1.4 Assumptions p. 10
4.2.1.5 Solution p. 10
4.2.2 Potential FLUTE Enhancements p. 14
4.2.2.1 Deployment Architecture considerations p. 14
4.2.2.1.1 Introduction p. 14
4.2.2.1.2 Scenario 1: Managed Live DASH p. 15
4.2.2.1.3 Scenario 2: Unmanaged Live DASH p. 16
4.2.2.2 High-Level Design Principles p. 16
4.2.2.2.1 Error Resilience p. 16
4.2.2.2.2 Self-containment p. 16
4.2.2.2.3 Optimization for Real-time Services p. 17
4.2.2.2.4 Static and Dynamic Information p. 17
4.2.2.2.5 Modular, Generic, Extensible and Efficient Design p. 17
4.2.2.3 Recommended Requirements & Evaluation Criteria p. 17
4.2.2.4 Gap Analysis & Evaluation p. 19
4.2.2.4.1 Type 1: Backward compatible towards Rel-11 and earlier UEs p. 19
4.2.2.4.2 Type 2: Backward compatible towards Rel-11 and earlier Networks p. 20
4.2.2.4.3 Type 3: Backward compatible towards Rel-11 and earlier Networks and UEs p. 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 extensions p. 20
4.2.2.4.5.1 General p. 20
4.2.2.4.5.2 LCT based on RFC 5651 p. 20
4.2.2.4.5.3 File Delivery Table Instance Descriptor p. 21
4.2.2.4.5.4 Extensions to FDT Instance p. 21
4.2.2.4.5.5 Extension Headers p. 23
4.2.2.4.5.6 Code Points p. 24
4.2.2.4.5.7 Object expiration mechanism for FLUTE enhancements p. 25
4.2.2.4.5.8 FLUTE packets of DASH Segments in different order p. 26
4.2.2.4.6 ALC RFC differences and analysis p. 27
4.2.2.5 Assumptions p. 29
4.2.2.6 Solution p. 29
4.2.3 Datacasting Services p. 30
4.2.3.1 Description p. 30
4.2.3.1.1 Use Case #1 - Sports Scores and Statistics p. 30
4.2.3.1.2 Use Case #2 -USD Delivery p. 30
4.2.3.2 Recommended Requirements & Evaluation Criteria p. 30
4.2.3.3 Gap Analysis & Evaluation p. 31
4.2.3.4 Assumptions p. 31
4.2.3.5 Solution p. 32
4.2.4 File Repair without FDT p. 33
4.2.4.1 Description p. 33
4.2.4.1.1 Use Case #1 - Device is tuned to another frequency p. 33
4.2.4.1.2 Use Case #2 -Device is powered-off p. 33
4.2.4.1.3 Use Case #3 -Device is out of MBMS coverage but in good unicast coverage p. 33
4.2.4.2 Recommended Requirements & Evaluation Criteria p. 34
4.2.4.3 Gap Analysis & Evaluation p. 34
4.2.4.3.1 Existing Technologies p. 34
4.2.4.3.2 Consequences of Existing Technologies p. 34
4.2.4.3.3 Summary of Gap Analysis p. 35
4.2.4.4 Assumptions p. 35
4.2.4.5 Solution p. 35
4.2.5 Zapping Portal Services p. 36
4.2.5.1 Description p. 36
4.2.5.2 Recommended Requirements & Evaluation Criteria p. 37
4.2.5.2.1 Fast Zap Video p. 37
4.2.5.2.2 Mosaic Service p. 38
4.2.5.3 Gap Analysis & Evaluation p. 39
4.2.5.3.1 Fast Zap Video p. 39
4.2.5.3.2 Mosaic Service p. 39
4.2.5.4 Assumptions p. 40
4.2.5.5 Solution p. 40
4.2.6 Joint object protection p. 40
4.2.6.1 Description p. 40
4.2.6.1.1 Use Case p. 40
4.2.6.2 Recommended Requirements & Evaluation Criteria p. 40
4.2.6.3 Gap Analysis & Evaluation p. 40
4.2.6.4 Assumptions p. 40
4.2.6.5 Solution p. 40
4.2.7 Multiple FLUTE Sessions for an MBMS User Service p. 40
4.2.7.1 Use Case Descriptions p. 40
4.2.7.1.1 Multiple Media Streams of a DASH-over-MBMS service p. 40
4.2.7.1.2 Hybrid Service Comprising Streaming and Auxiliary File Contents p. 41
4.2.7.2 Recommended Requirements & Evaluation Criteria p. 41
4.2.7.3 Gap Analysis & Evaluation p. 41
4.2.7.3.1 Application Identification p. 41
4.2.7.3.2 Schedule to Session Mapping p. 41
4.2.7.3.3 Service Area Specific Availability of Media Components p. 42
4.2.7.3.4 Inband USD Metadata Fragment Delivery p. 42
4.2.7.3.5 Unambiguous Identification of FLUTE Session Associated with Reception Report p. 43
4.2.7.3.6 Multiple MBMS Bearers Consideration p. 43
4.2.7.4 Assumptions p. 43
4.2.7.5 Solution p. 44
4.2.8 Targeted Ad Insertion p. 48
4.2.8.1 Description p. 48
4.2.8.2 Recommended Requirements & Evaluation Criteria p. 48
4.2.8.3 Gap Analysis & Evaluation p. 49
4.2.8.4 Assumptions p. 49
4.2.8.5 Solution p. 49
4.2.9 Generic Application Service Delivery over MBMS p. 54
4.2.9.1 Description p. 54
4.2.9.1.1 Example 1: Broadcast of MPEG-DASH p. 54
4.2.9.1.2 Example 2: Combined Unicast/Broadcast DASH p. 54
4.2.9.1.3 Example 3: Combined Unicast/Broadcast DASH with Transport Awareness in DASH client p. 55
4.2.9.1.4 Example 4: Apple HLS p. 55
4.2.9.1.5 Example 5: Web Page p. 56
4.2.9.2 Recommended Requirements & Evaluation Criteria p. 56
4.2.9.3 Gap Analysis & Evaluation p. 56
4.2.9.4 Assumptions p. 56
4.2.9.5 Solution p. 56
4.2.10 Improve MBMS OTA efficiency p. 56
4.2.10.1 Description p. 56
4.2.10.2 Recommended Requirements & Evaluation Criteria p. 56
4.2.10.3 Gap Analysis & Evaluation p. 57
4.2.10.4 Assumption p. 57
4.2.10.5 Solution p. 57
4.2.11 Multi-Program Support: p. 58
4.2.11.1 Description p. 58
4.2.11.1.1 Use Case #1 -Portal and Association p. 58
4.2.11.1.2 Use Case #2 -Fast Start-up and Rapid Channel Change p. 58
4.2.11.2 Recommended Requirements & Evaluation Criteria p. 58
4.2.11.3 Gap Analysis & Evaluation p. 58
4.2.11.4 Assumptions p. 58
4.2.11.5 Solution p. 58
4.2.12 Robust DASH operation in live services p. 59
4.3 Related Change Requests p. 60
5 Conclusion p. 60
$ Change history p. 61
