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.1.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… 
4.2.2.3 Type 2: 5G EDGe-Dependent AR (EDGAR) UE 
...

 

4.2.2.3  Type 2: 5G EDGe-Dependent AR (EDGAR) UE  p. 18

Figure 4.2.2.3-1 provides a functional structure for Type 2: 5G EDGe-Dependent AR (EDGAR) UE.
Copy of original 3GPP image for 3GPP TS 26.998, Fig. 4.2.2.3-1: Functional structure for Type 2: 5G EDGe-Dependent AR (EDGAR) UE
Figure 4.2.2.3-1: Functional structure for Type 2: 5G EDGe-Dependent AR (EDGAR) UE
(⇒ copy of original 3GPP image)
Up
Main characteristics of Type 2: 5G EDGe-Dependent AR (EDGAR) UE:
  • The 5G EDGAR UE is a regular 5G UE. 5G connectivity is provided through an embedded 5G modem and 5G System components.
  • The AR Runtime is local and uses data from sensors, audio inputs or video inputs. The AR Runtime, in particular the XR Spatial Compute, may be assisted by the cloud/edge application for example spatial localization and mapping provided by a spatial computing service.
  • Media processing is local, the device needs to embed all media codecs required for decoding pre-rendered 2D view.
  • A Lightweight Scene Manager is local to the AR/MR device, but the main scene management and composition is done on the cloud/edge. A scene description is generated and exchanged to establish the split work flow.
  • The main AR/MR application resides on the cloud/edge, but a basic application functionality is on the UE to support regular UE functionalities and launching services and applications.
  • Power consumption on such glasses must be low enough to fit the form factors. Heat dissipation is essential.
  • Media Access Functions are provided that support the delivery of media content components over the 5G system, in particular cloud and split rendering supporting functions. Media Access Functions are divided in control on M5 (Media Session Handler and Media AF) and user data on M4 (Media Client and Media Application Server). Detailed requirements are for study in this report.
  • While the EDGAR UE may have additional functionalities, for example those available in a STAR UE, generally for media centric or compute heavy use cases processing needs to be supported by the edge, hence referred to as EDGe-Dependent AR (EDGAR) UE.
  • The application may also communicate though the 5G System using a dedicated interface.
Up

Up   Top   ToC