5.10.6 Procedures for dynamic provisioning of 5GMS content delivery via eMBMS

26.5013GPP5G Media Streaming (5GMS)General description and architectureRelease 18TS

5.10.6.1 General

In this scenario the same content is distributed via eMBMS (for example using a broadcast network in receive-only mode) and via a 5GMS System. The resources of the broadcast system are statically configured. eMBMS-based distribution may, for example, be used only for services in high demand, and the resources and quality of the service distributed through broadcast may be adjusted according to demand. Demand may be identified through 5GMS Consumption Reporting.

The call flow in Figures 5.10.6 1 and 5.10.6 2 extends that defined in clause 5.6.1 to address generic use cases for broadcast-on-demand. Specific additional use cases are presented in the remainder of clause 5.10.6.

Figure 5.10.6.1-1: High-level procedure for DASH content delivered via eMBMS broadcast-on-demand

Steps:

1: The 5GMS Application Provider provisions one or more MBMS services and permits broadcast distribution of the media content.

2: As a consequence, the 5GMSd AF provisions MBMS delivery and the BM SC informs the 5GMS AF about the resources it will use to ingest media content.

NOTE: This step may happen later, up to (and possibly as part of) step 15, for example only when demand is identified.

3: The media content is announced to the 5GMSd-Aware Application and the application request the entry points for the service.

4: The 5GMSd AS starts to ingest content from the 5GMSd Application Provider.

5: Consumption Reporting is applied for the 5GMSd session.

Media playback initially uses unicast 5G Media Streaming:

6: The media content is selected by the 5GMSd-Aware Application.

7: The 5GMSd-Aware Application triggers the start of media playback by the Media Player.

8: The media presentation manifest (e.g. DASH MPD) is requested by the Media Player from the 5GMSd AS.

9: The Media Player processes the media presentation manifest and identifies that the media content is available on the 5GMS AS

10: The Media Player, under the control of the application, selects the media content and different content options.

11: Media content is received from the 5GMSd AS via reference point M4d.

12: The Media Player informs the Media Session Handler about the consumed media content.

13: The Media Session Handler sends consumption reports to the 5GMSd AF.

Subsequently, media playback switches to eMBMS:

14: By analysing the consumption reports submitted to it in the previous step, the 5GMSd AF identifies a high level of demand for the service.

15: Additional MBMS delivery sessions are provisioned to add delivery of the service via eMBMS.

16: The BM SC starts ingesting media content from the 5GMSd AS.

17: MBMS delivery starts.

18: The 5GMSd AF informs the Media Session Handler that MBMS delivery is initiated and provides the Service Success Information.

19: MBMS content reception is initiated by the Media Session Handler.

20: Once the service is ready, the content delivered on MBMS is used by the Media Player. Consumption reporting continues. Specific cases may use different policies, similar to the hybrid case in clause 5.10.5.

Figure 5.10.6.1-2: High-level procedure for DASH content delivered via eMBMS broadcast-on-demand (continued)

5.10.6.2 Operation modes

At least the following operation modes are supported based on the general procedures in clause 5.10.6.1:

1. Every 5GMS media service is mapped to exactly one MBMS User Service. Whether the MBMS User Service is announced and delivered or not depends on service demand. The MBMS Delivery Session is adjusted dynamically – for example the Delivery Session is disabled, or the bit rate is changed – depending on service demand and/or content requirements.

2. A set of MBMS User Services and MBMS Delivery Sessions is defined in the initial provisioning. 5GMS media services are dynamically mapped to statically configured MBMS User Services based on demand and content requirements.

3. Components of the 5GMS User Service, for example audio service components for different languages, are assigned dynamically to MBMS delivery depending on demand.