Content for TR 26.849 Word version: 12.1.0
4 MBMS operation on Demand (MooD)
4.1 Introduction
4.2 Use Cases, Recommended Requirements, Gap Analysis and Working Assumptions
4.3 Architecture
4.4 Message Flows
$ Change history
4 MBMS operation on Demand (MooD) p. 7
4.1 Introduction p. 7
4.2 Use Cases, Recommended Requirements, Gap Analysis and Working Assumptions p. 8
4.2.1 Use Cases p. 8
4.2.1.1 Use Case #1: Demand-based eMBMS for Real-Time (RT) Content p. 8
4.2.1.2 Use Case #2: Demand-based eMBMS for Non-Real-Time (NRT) Content p. 8
4.2.1.3 Use Case #3: Demand-based deactivation of eMBMS service p. 8
4.2.1.4 Use Case #4: Operator Control of eMBMS operation on Demand, Live Streaming Service Support p. 8
4.2.1.5 Use Case #5: Content Aggregation p. 9
4.2.2 Recommended Requirements & Evaluation Criteria p. 9
4.2.3 Gap Analysis & Evaluation p. 10
4.2.3.1 General p. 10
4.2.3.1.1 Dynamic and Demand-based MBMS User Service Establishment p. 10
4.2.3.1.2 Dynamic and Demand-based MBMS User Service Termination p. 10
4.2.3.1.3 Dynamic Conversion from Unicast to Broadcast Delivery p. 10
4.2.3.2 UE-Supported Operation p. 11
4.2.4 Assumptions p. 11
4.3 Architecture p. 11
4.4 Message Flows p. 12
4.4.1 High-Level Call Flow for UE-Supported MooD Operation p. 12
4.4.2 Call Flow (From BC to UC) p. 14
4.4.3 Switching from non-eMBMS UC to eMBMS BC p. 16
4.4.4 MBMS User Service UC to BC MooD Example Flows p. 18
4.4.4.1 Flow 1 - Consumption Reporting enabled on unicast p. 18
4.4.4.1.1 Assumptions and pre-conditions p. 18
4.4.4.1.2 Flow 1 Sequence p. 19
4.4.4.1.3 Flow 1 Description p. 19
4.4.4.2 Flow 2 - Mobility (SAI change) p. 20
4.4.4.2.1 Assumptions and pre-conditions p. 20
4.4.4.2.2 Flow 2 Sequence p. 21
4.4.4.2.3 Flow 2 Description p. 22
4.4.4.3 Applicability to non-DASH services p. 22
4.4.4.4 Location in ADPD r12:consumptionReport p. 22
4.4.5 Solution p. 23
$ Change history p. 34
