Content for TR 22.856 Word version: 19.2.0

1… 5… 5.2… 5.3… 5.4… 5.5… 5.6… 5.7… 5.8… 5.9… 5.10… 5.11… 5.12… 5.13… 5.14… 5.15… 5.16… 5.17… 5.18… 5.19… 5.20… 5.21… 5.22… 5.23… 5.24… 5.25… 5.26… 5.27… 5.28… 6 7… 7.2 8 A B C…

5.4 Use Case on Spatial Anchor Enabler 5.4.1 Description 5.4.2 Pre-conditions 5.4.3 Service Flows 5.4.4 Post-conditions 5.4.5 Existing feature partly or fully covering use case functionality 5.4.6 Potential New Requirements needed to support the use case
...

5.4 Use Case on Spatial Anchor Enabler p. 26

5.4.1 Description p. 26

In use case 5.1 "Localized Mobile Metaverse Service Use Case," we introduced the term spatial anchor to describe an association between space and service information. This use case elaborates the concept of the spatial anchor to enable diverse mobile metaverse services, including those described in use case 5.1. This use case focuses on the creation, management and use of spatial anchors.

The overall purpose of this enabler is to make it possible to create AR content and share it with others. The 'spatial anchor producer' determines what to share and its location, and any constraints (e.g. who to share the spatial anchor with) and additional information, most importantly the 'resource' associated with the anchor (e.g. AR media, mobile metaverse service to access, etc.).

The 'spatial anchor consumer' is able to recognize anchors associated with locations, and use the spatial anchor to obtain the associated information.

Functionally, a spatial anchor has the following model:

Spatial Anchor: information that can be provided by a content producer to a content consumer. How this is done is out of scope of this use case.
Precise spatial location information: where the produced content is located, including the content's extent, orientation, etc.
Service information: this information is out of scope of standardization but could contain, e.g. a URL, media data, media access information, etc. This information is used by an application to access a service.

The spatial anchor enabler will benefit retail environments. Here, a cheese seller has extensive information about her wares that she will share with customers.

Copy of original 3GPP image for 3GPP TS 22.856, Fig. 5.4.1: Spatial Anchors - created by a user to share with other users

Figure 5.4.1: Spatial Anchors - created by a user to share with other users
(⇒ copy of original 3GPP image)

In this use case there are several actors that are relevant.

Leka the cheese seller is the content producer. She creates content and also anchors them to her wares. (She is very adept at putting the cheese back in the same places, and moving the anchors when this is not possible.)
I am the customer.
Warez is the mobile metaverse service provider stores that updates Leka's content, generates its presentation (that is, the AR content that is presented to customers), supports any interactive features, etc.
FineNet is the network operator that enables anchored services for any content producer, customer and mobile metaverse service provider.

5.4.2 Pre-conditions p. 27

Leka makes use of a UE that has a subscription with FineNet. She has a sensor that can be used in combination with the UE to indicate precise locations. In Figure 5.4.1, the sensor can identify the location of the tip of the cheese fork she holds.

Leka obtains services from Warez, where she stores information related to her inventory. She also has arranged in advance what information to display to customers and in what format.

I wear glasses that provide AR experience and communicate by means of my UE. I have a mobile subscription with FineNet also.

5.4.3 Service Flows p. 27

Leka places wares on display. She indicates the location of wares that are associated with inventory information so that the association of location (listed below as 'pose' including position in 3 dimensional space, orientation and possibly more spatial data) and service information are captured by the 5GS. This inventory information is captured also by the mobile network operator as spatial anchors. This is shown on the top half of Figure 5.4.3-1.

Copy of original 3GPP image for 3GPP TS 22.856, Fig. 5.4.3-1: Spatial Anchor Enabler Service Flow

Figure 5.4.3-1: Spatial Anchor Enabler Service Flow
(⇒ copy of original 3GPP image)

Creating, modifying, removing spatial anchors

To add new wares to display, Leka captures the location of the item with her cheese for (which includes sensors.) She associates a new spatial anchor with this location and product information (e.g. by scanning the bar code on the cheese). The Warez inventory management system also generates AR content on demand (mobile metaverse media): this application is external to 3GPP standards. Leka's UE accesses the mobile metaverse service that establishes the association that comprises the spatial anchor, the physical location and the service information.

When Leka moves wares, Leka can adjust the spatial location of items or remove them entirely (e.g. when the cheese has been sold) by registering the new location or removal with the Warez inventory management system. The 'location' and 'service information' can be updated over time.

Leka can also update the information that will be displayed as AR (mobile metaverse media) to the customer by the mobile metaverse server offered by the Warez inventory management system, for example the description of the cheese, its price, etc. This interaction is out of scope of 3GPP standards.

Accessing and using Spatial Anchors

I enter the store and examine what is on display. I capture the scene with sensors and share this information with the Spatial Mapping and Localization Service Enabler (5.5). This allows me to identify my localization information, including orientation, precisely.

I put on (activating) my AR glasses. By means of my UE with access over FineNet, share the location and orientation information (the area of interest) with the 5G system.

The 5G system uses the localization information to identify all applicable spatial anchors in the area of interest. These are returned to the UE and the AR glasses. This function is illustrated in the lower half of Figure 5.4.3-1.

The service information suffices to access the media server offered by Warez. The location information indicates the location of each spatial anchor.

I now perceive the spatial anchors as shown in Figure 5.4.1.

As Leka indicates the Halloumi in her counter, and my gaze focuses on that location (known to a very high degree of precision), the AR glasses use the service information associated with the spatial anchor to activate the Halloumi cheese media.

I now perceive the AR information panel associated with the Halloumi cheese.

5.4.4 Post-conditions p. 28

I am able to observe the AR content (mobile metaverse media) associated with the wares on display, as shown in Figure 5.4.1. As wares are moved or removed from the display, the content shifts as well. The display of AR content is the result of the service information (i.e. how to access the media) and the localization information (i.e. where the media is placed, oriented, etc.)

At any time Leka can add new wares and associated AR content, update the content that is displayed, etc.

I perceive AR content associated with the items in the shop and happily buy the cheese that meets my needs.

5.4.5 Existing feature partly or fully covering use case functionality p. 28

None

5.4.6 Potential New Requirements needed to support the use case p. 28

[PR 5.4.6-1]

Subject to operator policy, the 5G system shall enable an authorized third party to establish an association between a physical location (in three dimensional space, an orientation, etc.) and service information, where the service information is provided to the 5G system and the spatial anchor is either provided or determined by the 5G system.

[PR 5.4.6-2]

Subject to operator policy, the 5G system shall be able to establish an association between a physical location (in three dimensional space, an orientation, etc.) and service information, where the service information is provided to the 5G system and the spatial anchor is either provided or determined by the 5G system.

[PR 5.4.6-3]

Subject to operator policy, the 5G system shall enable an authorized third party to obtain all of the spatial anchors located in a given three dimensional area.

[PR 5.4.6-4]

Subject to operator policy, the 5G system shall enable a third party to request the service information associated with the precise location of a specific spatial anchor. Making use of this service and location information, the third party can access a mobile metaverse server to obtain AR media.

[PR 5.4.6-5]

Subject to operator policy, the 5G system shall provide an authorized third party a means to manage the spatial anchor(s), e.g. add, remove or modify spatial anchors, determine privacy and security aspects, and specifically to enable the third party to define which spatial anchors they manage have restricted access conditions.

[PR 5.4.6-6]

The 5G system shall be able to collect charging information for the establishment or management of an association between a physical location and service information, where a third party creates, deletes or changes a spatial anchor or associated service information.

[PR 5.4.6-7]

The 5G system shall be able to collect charging information associated with the network operator exposure of spatial anchors to authorized third parties, and of service information associated with spatial anchors.