Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 26.501  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   4.1…   4.2…   4.3…   4.4   4.5…   4.6…   4.7…   4.8   4.9…   4.10…   4.11…   5…   5.2…   5.2.4   5.2.5…   5.3…   5.3.2…   5.4…   5.5…   5.6…   5.7…   5.7.4…   5.7.8   5.7.9…   5.8…   5.10…   5.10.3   5.10.4   5.10.5…   5.10.6…   5.10.7   5.11…   5.12…   5.12.3   5.12.4…   5.12.5…   5.13…   5.14…   6…   6.2…   6.2.2.2…   6.2.3…   6.3…   6.4…   6.8…   6.9…   6.9.5…   6.9.7   6.9.8…   7…   8…   8.2   9…   A…   A.4…   A.8…   A.11…   A.13…   A.15…   A.16…   B…   C…   D…   E…   F…   G…   G.2…   G.3…   H… 
5.10 5GMS via eMBMS  5.10.1 General  5.10.2 Procedures for 5GMS content delivered exclusively via eMBMS 
...

 

5.10  5GMS via eMBMS |R17|  p. 144

5.10.1  General  p. 144

This clause defines procedures for different use cases and scenarios when 5GMS is using eMBMS for delivery as introduced in clause 4.6.

5.10.2  Procedures for 5GMS content delivered exclusively via eMBMS  p. 145

In this case, 5GMS media data is exclusively delivered via eMBMS, i.e. media content is not delivered via reference point M4d, but only via MBMS User Services. The 5GMSd Client acts as an MBMS-Aware Application.
The call flow in Figure 5.10.2-1 extends the call flow defined in clause 5.3.2 to address the delivery of 5GMS media data exclusively via eMBMS. Aspects specific to this use-case are indicated in bold.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.10.2-1: High-level procedure for DASH content delivery via eMBMS
Figure 5.10.2-1: High-level procedure for DASH content delivery via eMBMS
(⇒ copy of original 3GPP image)
Up
Prerequisites (step 0):
  • The 5GMSd Application Provider has provisioned the 5G Media Streaming System, including content ingest and the authorization to distribute 5GMS content via eMBMS.
  • The 5GMS AF has informed the BM-SC about the availability of 5GMS content by provisioning an MBMS service and has obtained relevant information from the eMBMS Service Announcement (such as the MBMS service identifier).
  • The BM-SC is ingesting content from the 5GMS AS, using either pull mode or push mode.
  • The BM-SC has broadcast the MBMS Service Announcement, including an indication that the content is 5GMS content.
Steps:
Step 1.
The 5GMSd-Aware Application triggers the Service Announcement procedure and the 5GMS Service and Content Discovery procedure at reference point M8.
Step 2.
A media content item is selected.
Step 3.
The 5GMSd-Aware Application triggers the 5GMSd Client to start media playback. The Media Player Entry is provided to the 5GMSd Client.
Step 4.
If the 5GMS-Aware Application has received only a reference to the Service Access Information (see step 1), the Media Session Handler interacts with the 5GMSd AF to acquire the whole Service Access Information. This includes relevant information from the eMBMS Service Announcement (such as the MBMS service identifier) in order to bootstrap reception of the MBMS service.
Step 5-11.
The Media Session Handler acts as an MBMS-Aware Application and initiates service acquisition. For details, see TS 26.347. This establishes a transport session for the MPD and the Content.
Step 12.
The Media SessionHandler provides the MPD URL to the Media Player either directly or through the 5GMSd-Aware Application.
Step 13.
The Media Player is invoked to start media access and playback.
Step 14.
The Media Player retrieves the Media Player Entry resource (an MPD) from the proxy Media Server.
Step 15.
The Media Player processes the retrieved MPD. It determines, for example, the number of transport sessions needed for media acquisition. The Media Player should be able to use the MPD information to initialize the media pipelines for each media stream (see step 18). When DRM is used (see step 17) the MPD should also contain sufficient information to initialize the DRM client.
Step 16.
The Media Player notifies the Media Session Handler about the start of a new downlink media streaming session. The notification may include parameters from the MPD.
Step 17.
Optional: The Media Player acquires any necessary DRM information, for example a DRM License.
Step 18.
The Media Player configures the media playback pipeline.
Step 19.
The Media Player retrieves initialization segment(s) referenced by the MPD.
Step 20-25.
Content is delivered using DASH-over-MBMS. Session Announcement updates are provided to the MBMS Client as necessary. MPD updates and Segments are pushed to the media server. The Media Player retrieves media segments from the proxy Media Server according to the MPD and forwards them to the appropriate media rendering pipeline.
Up

Up   Top   ToC