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  TR 26.998  Word version:  18.0.0

Top   Top   Up   Prev   Next
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 Procedures and call flows  6.2.4.1 STAR-based media streaming 
...

 

6.2.4  Procedures and call flows  p. 57

6.2.4.1  STAR-based media streaming  p. 57

Figure 6.2.4.1-1 illustrates the procedure diagram for 5G immersive media downlink streaming using a STAR-based UE when all essential AR/MR functions in a UE are available without an assist by an edge.
Copy of original 3GPP image for 3GPP TS 26.998, Fig. 6.2.4.1-1: STAR-based procedure for 5G downlink streaming
Figure 6.2.4.1-1: STAR-based procedure for 5G downlink streaming
(⇒ copy of original 3GPP image)
Up
Prerequisites and assumptions:
  • The AR/MR Scene Manager includes immersive media rendering and scene graph handling functionalities.
  • The Media Player includes immersive content delivery and immersive media decoding functionalities.
  • The AR/MR Application in the UE is run by the user.
  • The STAR UE initialises AR registration (starts analysing the surroundings where a user/UE is located), it namely:
    1. captures its surroundings via camera(s)
    2. analyses where the device is located
    3. registers the device into the analysed surroundings.
  • AR/MR Application and AR/MR Application Provider have exchanged some information, such as device capability or content configuration, for content rendering. The exchange procedures for device capability and content configuration are FFS.
  • AR/MR Application Provider has established a Provisioning Session and its detailed configurations has been exchanged.
  • AR/MR Application Provider has completed to set up ingesting immersive contents.
Procedures:
Step 1.
The scene content is ingested by the 5GMSd AS.
Step 2.
Service Announcement is triggered by AR/MR Application. Service Access Information including Media Client entry or a reference to the Service Access Information is provided through the M8d interface.
Step 3.
Desired media content is selected.
Step 4.
Optionally, the Service Access information is acquired or updated.
Step 5.
The AR/MR Application initializes the Scene Manager with the entry point (full scene description) URL.
Step 6.
The Media Client establishes the transport session for receiving the entry point (scene description).
Step 7.
The Media Client requests and receives the full scene description.
Step 8.
The entry point (scene description) is processed.
Step 9.
The AR/MR Scene Manager requests the creation of a new AR/MR session from the AR Runtime.
Step 10.
The AR Runtime creates a new AR/MR session.
AR Media Delivery Pipeline, steps 11~23 requests, receives and renders scenes and scene updates:
Step 11.
The Media Client and/or AR/MR Scene Manager notifies the necessary QoS information required to the Media Session Handler.
Step 12.
The Media Session Handler shares the information with the 5GMSd AF, in some cases including desired QoS information. Based on existing provisioning by the AR/MR Application Provider, the 5GMSd AF may request QoS modifications to the PDU sessions.
Steps 13~15 establish the transport sessions, receives, and process the delivery manifests:
Step 13.
For the required media content, the Media Client establishes the transport session(s) to acquire delivery manifest(s) information.
Step 14.
The Media Client requests and receives the delivery manifest(s) from the 5GMSd AS.
Step 15.
The Media Client processes the delivery manifest(s). It determines for example the number of needed transport sessions for media acquisition. The Media Client is expected to be able to use the delivery manifest(s) information to initialize the media pipelines for each media stream.
Step 16.
The AR/MR Scene Manager and Media Client configures the rendering and delivery media pipelines.
Step 17.
The Media Client establishes the transport session(s) to acquire the media content.
Media session loop, steps 18~23 provide the latest pose information, request, receive and render the media objects of the immersive scene:
Step 18.
The latest pose information is acquired by the AR/MR Scene Manager and shared to the Media Client.
Step 19.
The Media Client requests the immersive media data according to the delivery manifest processed, possibly taking into account pose information (e.g., viewport dependent streaming).
Step 20.
The Media Client receives the immersive media data and triggers the media rendering pipeline(s), including the registration of AR content into the real world accordingly.
Step 21.
The Media Client decodes and processes the media data. For encrypted media data, the Media Client may also perform decryption.
Step 22.
The Media Client passes the media data to the AR/MR Scene Manager.
Step 23.
The AR/MR 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, and pose correction.
Up

Up   Top   ToC