Content for TR 26.998 Word version: 18.1.0

0… 4… 4.2… 4.2.2… 4.2.2.2 4.2.2.3 4.2.2.4 4.2.3… 4.3… 4.4… 4.5… 4.6… 4.6.4… 4.6.5… 4.6.8… 5 6… 6.2… 6.2.4… 6.2.4.2 6.2.5… 6.3… 6.3.4… 6.3.4.2 6.3.5… 6.4… 6.4.4 6.4.5… 6.5… 6.5.4 6.5.5 6.5.6… 6.6… 6.6.4 6.6.5… 7… 8… 8.9 9 A… A.2 A.3… A.4 A.5 A.6 A.7…

6.2.4.2 EDGAR-based media streaming
...

6.2.4.2 EDGAR-based media streaming p. 61

Figure 6.2.4.2-1 illustrates the procedure diagram for 5G immersive media downlink streaming using an EDGAR-based UE.

Copy of original 3GPP image for 3GPP TS 26.998, Fig. 6.2.4.2-1: EDGAR-based procedure for 5G downlink streaming

Figure 6.2.4.2-1: EDGAR-based procedure for 5G downlink streaming
(⇒ copy of original 3GPP image)

Prerequisites and assumptions:

Identical to those from the STAR UE case.

Procedures:

Step 1~8.

Identical to steps 1~8 from the STAR UE case (Figure 6.2.4.1-1).

Step 9.

Based on the processed scene description and the device capabilities, the 5GMSd AS/EAS is selected, and edge processes are instantiated using the processes defined in 5GMS_EDGE:

The AR/MR Lightweight Scene Manager sends the scene description and the device capabilities to 5GMS AS. The 5GMS AS derives the EAS KPIs and if needed selects a new AS/EAS (through AF) based on the new KPI. Then the edge processes are started, and a new entry point URL is provided to the AR/MR Lightweight Scene Manager.
The AR/MR Lightweight Scene Manager derives the EAS KPIs from the scene description and device capabilities, requests the AF to provide the list of suitable EAS. Then the AR/MR Lightweight Scene Manager selects the AS/EAS and requests to start the edge processes in the EAS. The edge processes are started, and a new entry point URL is provided to the AR/MR Lightweight Scene Manager.

Step 10.

The AR/MR Lightweight Scene Manager requests the lightweight scene description. The edge processes derive the lightweight scene description from the full scene description and provide it to AR/MR Lightweight Scene Manager.

Step 11.

The simplified entry point (lightweight scene description) is processed.

Step 12~19.

Identical to steps 9~16 from the STAR UE case (Figure 6.2.4.1-1).

Step 20.

The Media Client establishes the transport session(s) to acquire the media content.

Step 21.

The 5GMSd AS initiates and starts a media session. This media session forms a stateful session loop specific to the UE, containing steps 22~25:

Stateful media session loop (steps 22~28):

Step 22.

The latest pose information is acquired by the AR/MR Lightweight Scene Manager and shared to the Media Client.

Step 23.

The Media Client sends the latest pose information to the 5GMSd AS.

Step 24.

The 5GMSd AS performs pre-rendering of the media based on the latest received pose information and possibly any original scene update. Pre-rendering may typically consist of decoding and rendering immersive media, and encoding the rendered (2D) media.

Step 25.

The pre-rendered media is sent by the 5GMSd AS to the Media Client.

Step 26.

The Media Client decodes and processes the media data. For encrypted media data, the Media Client may also perform decryption.

Step 27.

The Media Client passes the media data to the AR/MR Lightweight Scene Manager.

Step 28.

The AR/MR Lightweight Scene Manager renders the media, and passes the rendered media to the AR Runtime, which performs further processing such as registration of the AR content into the real world, composition, and pose correction.