Content for TS 23.437 Word version: 19.0.0
0 Introduction
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
4 Architectural requirements
4.1 General
4.2 Spatial anchors management
4.3 Spatial map management
5 Involved business relationships
6 Functional model deployment options
6.1 General
...
...
0 Introduction p. 9
The term "metaverse" has been used in various ways to refer to the broader implications of AR and VR. It is used to refer to a persistent, shared, perceived set of interactive perceived spaces. "Metaverse" in diverse sectors evokes a number of possible new experiences, products and services that emerges in virtual reality and augmented reality services.
Localized mobile metaverse services are immersive and integrated into a user's ordinary experiences. Such service experiences are location-related and can include presentation of AR, MR media. Localized mobile metaverse services can be associated with specific places (3D locations in the physical world). The association between these places and service information is termed a spatial anchor. Spatial anchors enable mobile metaverse services to be discovered and accessed, if the user is authorized. Users' localization is important in order to discover spatial anchors.
The spatial map is created using processed sensor data. Creation of a spatial map for a location makes localization there possible, as well as assignment of spatial anchors in that location.
This technical specification provides application layer architecture and related procedures for enabling spatial anchors management and spatial mapping management.
1 Scope p. 10
The present document specifies the application layer architecture, procedures and information flows necessary for spatial anchors management and spatial mapping management to support mobile metaverse services. It includes architectural requirements, application layer architecture fulfilling the architecture requirements and procedures to manage spatial anchors and spatial maps.
The normative work in the present document is based on the requirements as defined in TS 22.156 and related use cases in TR 22.856.
2 References p. 10
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.156: "Mobile Metaverse Services; Stage 1".
[3]
TR 22.856: "Feasibility Study on Localized Mobile Metaverse Services".
[4]
TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[5]
TS 23.502: "Procedures for the 5G System; Stage 2".
[6]
TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[7]
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
3 Definitions of terms, symbols and abbreviations p. 10
3.1 Terms p. 10
For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
For the purposes of the present document, the following terms given in TS 22.156 apply:
localization
pose
Spatial anchor
Spatial map
spatial mapping service
spatial localization service
3.2 Symbols p. 11
For the purposes of the present document, the following symbols apply:
3.3 Abbreviations p. 11
4 Architectural requirements p. 11
4.1 General p. 11
This clause provides architectural requirements to consider for Spatial anchors service and Spatial map service.
4.2 Spatial anchors management p. 11
[AR-4.2-a]
The spatial anchors management service shall provide mechanisms to manage (e.g. create, get, update, delete) , discover and subscribe spatial anchors.
[AR-5.2-b]
The spatial anchors management service shall provide spatial anchor usage information to the authorized consumers.
4.3 Spatial map management p. 11
[AR-4.3-a]
The spatial map management service shall provide mechanisms to produce, get, update, delete and subscribe spatial maps.
[AR-4.3-b]
The spatial map management service shall provide mechanisms to expose spatial map information to the authorized third parties.
[AR-4.3-c]
The spatial map management service shall allow multiple spatial maps in a given three-dimensional space for different vertical applications and consumer's usage.
[AR-4.3-d]
The spatial map management service shall be able to interact with other SEAL servers and 5GS to support vertical applications.
[AR-4.3-e]
The spatial map management service shall provide mechanisms to register, update and deregister spatial map data source and allow discovery of spatial map data source by authorized consumers.
[AR-4.3-f]
The spatial map management service shall provide mechanisms to register, update and deregister VAL servers with spatial map capabilities and allow discovery of VAL servers with spatial map capabilities by authorized consumers.
[AR-4.3-g]
The spatial map management service shall provide mechanisms to localize a VAL UE.
[AR-4.3-h]
The spatial map management service shall provide mechanisms for authorized consumers to augment information associated with a spatial map.
5 Involved business relationships p. 12
The business relationship as specified in clause 5 of TS 23.434 is applicable for this specification, where VAL user is metaverse service user, VAL service provider is metaverse service provider and further, VAL service provider and SEAL service provider can be same organization.
6 Functional model deployment options p. 12
6.1 General p. 12
The deployment model as specified in clause 8 of TS 23.434 is applicable for this specification. The SEAL server(s) as specified in clause 8.2.1 of TS 23.434 can be one or more SEAL services (e.g. Spatial anchors service, Spatial map service), providing enablement services to the metaverse application servers. The SEAL-S interface provides multiple service APIs towards Metaverse application server.
