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.928  Word version:  18.0.0

Top   Top   Up   Prev   Next
0…   4…   4.1.2…   4.2…   4.3…   4.4…   4.5…   4.6…   4.6.7   4.7…   4.9…   5…   6…   7…   8   A…   A.4…   A.7…   A.10…   A.13   A.14   A.15   A.16   A.17   A.18… 
A Collection of XR Use Cases  A.1 Introduction and Template  A.2 Use Case 1: 3D Image Messaging  A.3 Use Case 2: AR Sharing 
...

 

A  Collection of XR Use Cases  p. 81

A.1  Introduction and Template  p. 81

In order to collect relevant service scenario and core use cases in the context of XR, this Annex documents collected individual use cases and the established processes to collect those use cases.
The following procedure was applied for adding to the present document:
  • There is consensus that the use case is understood, relevant and in scope of the Study Item
  • A feasibility study is provided and considered sufficient. Some examples on what is expected on feasibility is provided below.
    • How could the use case be implemented based on technologies available today or expected to be available in a foreseeable timeline, at most within 3 years?
    • What are the technology challenges to make this use case happen?
    • Do you have any implementation information?
      • Demos
      • Proof of concept
      • Existing services
      • References
    • Could a reduced experience of the use case be implemented in an earlier timeframe or is it even available today?
  • Beyond use case description and feasibility, the template includes sufficient information on
    • Categorization: Type, Degrees of Freedom, Delivery Type, Device
    • Preconditions: What is necessary to make this work?
    • QoS Considerations: What network capabilities are needed, e.g. bitrate, latency, etc.?
    • QoE Considerations: What is expected that the user is satisfied with the quality?
    • Potential Standardisation Status and Needs: This may include 3GPP relevant standards or external standards.
For use cases that are moved to the present document, in the course of the study item, is expected that the following aspects are addressed:
  1. The use case is mapped to one or multiple architectures.
  2. For each use case the functions and interfaces are defined, and the requirements are developed to address the use case.
  3. Specific requirements include
    1. Architectural requirements
    2. Network and QoS requirements
    3. Media Processing requirements
    4. More detailed QoE requirements
The template provided in Table A.1-1 is recommended to be used for this collection.
Use Case Name
 
Description
 
Categorization
Type:
AR, VR, XR, MR
Degrees of Freedom:
2D, 3DoF, 3DoF+, OD 6DoF, 6DoF
Delivery:
Download, Streaming, Interactive, Conversational, Split
Device:
Phone, HMD, Glasses, Automotive Heads-up, others
Preconditions
<provides conditions that are necessary to run the use case, for example support for functionalities on the end device or network>
Requirements and QoS/QoE Considerations
<provides a summary on potential requirements as well as considerations on KPIs/QoE as well as QoS requirements>
Feasibility
<How could the use case be implemented based on technologies available today or expected to be available in a foreseeable timeline, at most within 3 years?
  • What are the technology challenges to make this use case happen?
  • Do you have any implementation information?
    • Demos
    • Proof of concept
    • Existing services
    • References
  • Could a reduced experience of the use case be implemented in an earlier timeframe or is it even available today?
>
Potential Standardization Status and Needs
<identifies potential standardization needs>
Table A.1-2 provides an overview of the use cases and their characterization.
No Use Case Type Experience Delivery Device
13D Image MessagingAR3DoF+, 6DoFUpload and DownloadPhone
2AR SharingAR, MR6DoFLocal, Messaging Download and UploadPhone
3Streaming of Immersive 6DoFVR3DoF+, 6DoFStreaming Interactive SplitHMD with a controller
4Emotional Streaming2D, AR and VR2D, 3DoF+, 6DoFStreaming Interactive, SplitPhone and HMD
5Untethered Immersive Online GamingVR6DoFStreaming, Interactive, SplitHMD with a Gaming controller
6Immersive Game Spectator ModeVR6DoFStreaming, Split2D screen or HMD with a controller
7Real-time 3D Communication3D, AR3DoF+ConversationalPhone
8AR guided assistant at remote location (industrial services)2D video with dynamic AR rendering of graphics6DoF (2D + AR)Local, Streaming, Interactive, Conversational5G AR Glasses, 5G touchscreen computer or tablet
9Police Critical Mission with ARAR, VR3DoF to 6DoFLocal, Streaming, Interactive, Conversational, Group Communication5G AR Glasses/Helmet, VR camera/microphone, Audio stereo headset, 5G accurate positioning
10Online shopping from a catalogue - downloadingAR6DoFDownload AR Glasses, Rendering system, Tablet (or smartphone), Capture device
11Real-time communication with the shop assistantAR6DoFInteractive, Conversational AR Glasses, Rendering system, Tablet (or smartphone), Capture device
12360-degree conference meetingAR, MR, VR3DoFConversationalMobile / Laptop
133D shared experienceAR, MR, VR3DoF+ 6DoFConversationalMobile / Laptop
146DOF VR conferencingVR6DoFInteractive, ConversationalVR gear with binaural playback and HMD video playback, Call server
15XR MeetingAR, VR, XR6DoFInteractive ConversationalPhone, HMD, Glasses, headphones
16Convention / Poster SessionAR, VR, MR6DoFInteractive ConversationalPhone, HMD, AR Glasses, VR controller/pointing device, headphones
17AR animated avatar callsAR2D, 3DoFConversationalPhone, HMD, Glasses, headphones
18Online shopping from a catalogue - downloadingAR6DoFDownload AR Glasses, Rendering system, Tablet (or smartphone), Capture device
19Front-facing camera video multi-party callsAR3DoFConversationalSmartphone with front-facing camera, headset
20AR Streaming with Localization RegistryAR, Social AR6DoFStreaming, Interactive, ConversationalAR glasses with binaural audio playback support
21Immersive 6DoF Streaming with Social InteractionVR and Social VR3DoF+, 6DoFStreaming Interactive Conversational SplitHMD with a controller
225G Online Gaming PartyVR6DoFStreaming, Interactive, Split, D2DHMD with a Gaming controller
23Spatial Shared DataAR6DoFStreaming Interactive Conversational SplitHMD, AR Glasses
Up

A.2  Use Case 1: 3D Image Messaging  p. 84

Use Case Description:
3D Image Messaging
Alice uses her phone that is equipped with a depth camera to capture an image of a statue in 3D. The phone captures a set of images and builds a 3D model of the object. After a few seconds the 3D image is ready to share and Alice sends the image to Bob as an MMS message.
Categorization
Type:
AR
Degrees of Freedom:
3DoF+ or 6DoF
Delivery:
Upload and Download
Device:
Phone, AR glasses
Preconditions
  • Phone is equipped with 3D capture capabilities, such as depth camera or a stereo camera on the back of the phone, possibly supported by an app for processing multiple images.
  • Phone is equipped with a 3D image viewer
Requirements and QoS/QoE Considerations
  • QoS: Reliable delivery of a File of a few MByte distributed over MMS
  • QoE: Quality of the 3D object representation, level of details
Feasibility
Some new smartphone releases are equipped with a Time of Flight (ToF) depth camera (see for example https://en.wikipedia.org/wiki/Time-of-flight_camera) that can be used to build accurate 3D models of objects of interest. Compared to structured light cameras, ToF do not require a large baseline to achieve good depth accuracy.
Applications such as 3D Photo are using the stereo camera on the back of some phone models to generate a 3D model using a set of pictures taken consecutively. To compensate for the small baseline, complex processing (e.g. deep model to reconstruct the depth map) may be required.
The 3D image can be stored as a point cloud, a mesh, or a layered image. The content maybe compressed to reduce the message size. The content is identified through its mime type and can be embedded with other content such as text.
Potential Standardization Status and Needs
The following aspects may require standardization work:
  • Standardized formats for 3D images, e.g. meshes, point clouds, and/or depth-layered images
  • Extensions to MMS to support 3D images
Up

A.3  Use Case 2: AR Sharing  p. 85

Use Case Description:
AR Sharing
Alice is shopping for a new couch at the furniture store close to her. Alice finds a couch that she likes and wants to check Bob's opinion who sits back home. Alice scans a QR code with her phone to download a 3D model of the couch and sends it to Bob via MMS. Bob places the virtual model of the couch on a plane surface in the living room. Bob likes how the couch fits in their living room and captures a 3D picture of the room with the couch and shares it with Alice.
Categorization
Type:
AR, MR
Degrees of Freedom:
6DoF
Delivery:
Local, Messaging Download and Upload
Device:
Phone, AR glasses
Requirements and QoS/QoE Considerations
  • QoS: Reliable Delivery (Upload and Download) of a File of a few or several MByte
  • QoE: Quality of the 3D object representation, level of details
Preconditions
  • Bob's smartphone has support for AR technology
Feasibility
Modeling of sale items in 3D will be increasing. This will facilitate purchase decisions for millions of customers. Texture of the 3D models may vary to reflect available choices for the item.
A user can use ARCore [4] or ARKit [5] to detect flat surfaces and place the 3D model on it. The AR scene can be captured with the real scene in the background and the 3D object in the foreground.
To achieve physically-based rendering (PBR), additional characteristics of the 3D object's texture are stored. These may include properties such as specular, diffuse, transparency, reflectivity, etc.
Potential Standardization Status and Needs
The following aspects may require standardization work:
  • Standardized format for 3D objects is needed
  • Standardized format for mixed reality 3D scenes is needed
  • Extensions to MMS to support sharing of 3D objects and scenes
Up

Up   Top   ToC