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…

9.1 Baseline procedure
...

9 Procedures for Service URL handling |R18| p. 191

9.1 Baseline procedure p. 191

The launch of a 5GMS session using a 3GPP Service URL (see clause 4.10) is shown in Figure 9.1-1. In this procedure, the Application is not assumed to be a 5GMS-Aware Application.

Copy of original 3GPP image for 3GPP TS 26.501, Fig. 9.1-1: Baseline procedure for 3GPP Service URL Handling

Figure 9.1-1: Baseline procedure for 3GPP Service URL Handling
(⇒ copy of original 3GPP image)

The call flow is as follows:

Step 1.

The 5GMS Application Provider provisions media streaming services at reference point M1 and provides one or more External service identifiers to the 5GMS AF as part of the Provisioning Session.

Step 2.

The 5GMS Application Provider generates a unique 3GPP Service URL that includes one of the provisioned External service identifiers. Additional service announcement parameters, including a Media Entry Point URL, may also be embedded in this 3GPP Service URL.

Step 3.

The Application discovers the set of currently available media services at reference point M8.

Step 4.

The user selects a media service in the Application that is offered as a 3GPP Service URL.

Step 5.

The Application requests the 3GPP Service URL corresponding to the media service. If the Media Session Handler is available, it handles and resolves the URL.

Step 6.

The Media Session Handler may collect additional service parameters from the 5GMS AF. In particular, Service Access Information may be retrieved from the 5GMS AF using the External service identifier extracted from the 3GPP Service URL to identify the Provisioning Session of interest.

Step 7.

If the 3GPP Service URL requested in step 4 contains an embedded Media Entry Point URL, or if a Media Entry Point URL was obtained in step 5 or 6 the Media Session Handler launches the Media Stream Handler.

Alternatively, the Application may launch the Media Stream Handler directly itself using any Media Entry Point it obtained in preceding steps that is supported by the 5GMS Client.

Step 8.

Inter-Process Communication is established between the Media Stream Handler and the Media Session Handler.

Step 9.

Media streaming occurs between the Media Player, 5GMS AS and the 5GMS Application Provider.