Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑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…

 

4.2.2  Generic reference device functional structure device typesp. 17

4.2.2.1  Overviewp. 17

In clause 4.8 of TR 26.928, different AR and VR device types had been introduced. This clause provides an update and refinement in particular for AR devices. The focus in this clause mostly on functional components and not on physical implementation of the glass/HMD. Also, in this context the device is viewed as a UE, i.e. which functions are included in the UE.
A summary of the different device types is provided in Table 4.2.2.1-1. The Table also covers:
  • how the devices are connected to get access to information,
  • where the 5G Uu modem is expected to be placed,
  • where the AR Runtime (as specified in clause 4.2.1) is placed,
  • where the Scene Manager (as specified in clause 4.2.1) is placed,
  • where the AR/MR application is running,
  • where the power supply/battery is placed.
Examples for current AR devices with assigned properties are for example provided in [49]. For all glass device types, it is assumed that sensors, cameras and microphones are on the device.
The definition for Split AR/MR in Table 4.2.2.1-1 is as follows:
  • Split: the tethered device (phone/puck) or external entity (cloud/edge) does some power-intense processing (e.g., a pre-rendering of the viewport based on sensor and pose information), and the AR/MR device and/or tethered device performs post-processing considering the latest sensor information (e.g. warping to apply pose correction). Different degrees of split workflow exist, between different devices and entities. Similarly, vision engine functionalities and other AR/MR functions (such as AR/MR media reconstruction, encoding and decoding) may be subject to split computation.
Device Type Name Reference Tethering 5G Uu Modem AR Runtime Scene Manager AR/MR Application Power Supply
5G Standalone AR UE1: STARN/AGlassGlassGlass/Split (1)GlassGlass
5G EDGe-Dependent AR UE2: EDGARN/AGlassGlass/Split (1)Split (1)SplitGlass
5G WireLess Tethered AR UE3: WLAR802.11ad, 5G sidelink, etc.Tethered deviceGlassSplit (2)Tethered deviceGlass
5G Wired Tethered AR UE (3)4: WTARUSB-CTethered deviceTethered deviceSplit (2)Tethered deviceTethered device
NOTE 1:
Cloud/Edge
NOTE 2:
Phone/Puck and/or Cloud/Edge
NOTE 3:
Not considered in this document
The Wired Tethered AR UE device type is for reference purposes only and not considered in this document as it is not included as part of the study item objectives.
Generally, the STAR and WLAR device according to Table 4.2.2.1-1 are expected to have similar functionalities from a 5G System perspective.
Based on this, the focus is on three main different device types in the remainder of this document following the rows 1 to 3 in Table 4.2.2.1-1.
Up

Up   Top   ToC