Content for TS 26.501 Word version: 18.6.0

1… 4… 4.0.6… 4.1… 4.2… 4.2.2… 4.3… 4.4 4.5… 4.6… 4.7… 4.7.4… 4.8 4.9… 4.10… 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.8… 5.10… 5.10.5… 5.10.6… 5.11… 5.12… 5.12.4… 5.12.5… 6… 6.2… 6.2.2.2… 6.2.3… 6.3… 6.4… 6.8… 6.9… 6.9.5… 6.9.7 7… 8… 9… A… A.4… A.8 A.9 A.10 A.11 A.12 A.13 A.14 A.15… A.15.3… B… B.3 C… C.3 C.4 C.5 D… E…

5.2.4 Procedures for downlink streaming to Media Players with different presentation manifests
...

5.2.4 Procedures for downlink streaming to Media Players with different presentation manifests |R18| p. 81

Figure 5.2.4-1 illustrates a high-level procedure for downlink streaming to Media Players with different presentation manifests. The extensions compared to the DASH streaming in clause 5.2.3 are indicated in bold.

The procedure makes the following assumptions:

Common media segments (e.g. based on CMAF [27]) are shared between multiple Media Players requiring different presentation formats (see clause 4.8).
Key information to initialize the media decoding and rendering pipeline is present in the Media Player Entries (or referenced by the Media Player Entries).

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.2.4-1: High-level procedure for CMAF content shared by different Media Players

Figure 5.2.4-1: High-level procedure for CMAF content shared by different Media Players
(⇒ copy of original 3GPP image)

Steps:

Step 1.

The 5GMSd Application Provider provisions the 5G Media Streaming System, including content hosting.

Step 2.

The 5GMSd-Aware Application triggers the Service Announcement and Service and Content Discovery procedure with the 5GMSd Application Provider. The Service Announcement includes either the whole Service Access Information (i.e. details for Media Session Handling (M5d) and for Media Streaming access (M4d) which may include a Media Entry Point URL for each of the different available presentation manifests, or a reference to the Service Access Information.

Step 3.

A media content item is selected.

Step 4.

The 5GMSd-Aware Application triggers the 5GMSd Client to initiate the 5G Media Streaming Service.

When the 5GMS-Aware Application has received only a reference to the Service Access Information (see step 1):

Step 5.

The Media Session Handler interacts with the 5GMSd AF to acquire the whole Service Access Information. The Service Access Information may include a Media Entry Point URL for each of the different available presentation manifests.

Step 6.

The Media Session Handler provides the Media Entry Points to the 5GMS-Aware Application. The information may indicate a precedence order for these Media Entry Points.

Then:

Step 7.

The 5GMSd-Aware Application queries the Media Player capabilities for different manifests. If multiple streaming formats are supported, a preferred one may be indicated in the response.

Step 8.

The 5GMSd-Aware Application selects one of the Media Entry Points based on the information provided in steps 5 and 6 above.

Step 9.

The 5GMSd-Aware Application informs the Media Session Handler about the streaming format of the chosen Media Entry Point, for example for Consumption Reporting purposes.

Step 10.

In parallel, the Media Player is invoked with the selected Media Entry Point to start media access and playback.

Steps 11 to 24 are identical to steps 6 to 19, respectively, in clause 5.2.3.