hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
For the purposes of the present document, the following terms given in 3GPP TS 22.156 [2] apply:
localization
pose
Spatial anchor
Spatial map
spatial mapping service
spatial localization service
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
<ABBREVIATION> <Expansion>
SAn Spatial Anchor
SM Spatial Map
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
4 Architectural requirements
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
4.1 General
|
This clause provides architectural requirements to consider for Spatial anchors service and Spatial map service.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
4.2 Spatial anchors management
|
[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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
4.3 Spatial map management
|
[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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
5 Involved business relationships
|
The business relationship as specified in clause 5 of 3GPP TS 23.434 [4] 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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
6 Functional model deployment options
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
6.1 General
|
The deployment model as specified in clause 8 of 3GPP TS 23.434 [4] is applicable for this specification. The SEAL server(s) as specified in clause 8.2.1 of 3GPP TS 23.434 [4] 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.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7 Identities and commonly used values
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.1 General
|
This clause specifies details about the identifiers and common values used for spatial anchors and spatial map services.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.2 Identities
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.2.1 General
|
Following identifies as defined in clause 7 of 3GPP TS 23.434 [4] are applicable for this specification too.
User ID
VAL user ID
VAL UE ID
VAL service ID
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.2.2 Identities related to spatial anchors
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.2.2.1 Spatial anchor ID
|
A unique identifier to identify spatial anchor. It is assigned by SEAL SAn server. The identity is unique within service provider's domain.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.2.3 Identities related to spatial map
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.2.3.1 Spatial map ID
|
A unique identifier to identify spatial map. It is assigned by SEAL SM server. The identity is unique within service provider's domain.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.2.3.2 Spatial map layer ID
|
A unique identifier to identify a layer within a spatial map. It is assigned by SEAL SM server. The identity is unique within a spatial map.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.3 Common values
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.3.1 General
|
This clause specifics common values used in this specification.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.3.2 Common values related to spatial anchors
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.3.2.1 Spatial anchor profile
|
Table 7.3.2.1-1 describes information elements for the spatial anchor profile stored in the SAn server.
Table 7.3.2.1-1: Spatial anchor profile
Information element
Status
Description
Spatial anchor ID
M
Identifier of the discovered spatial anchor.
Position (NOTE)
O
The 3D geographic position of the spatial anchor in space (x, y and z coordinates).
Spatial map position (NOTE)
O
Position information based on spatial map. It includes the identifier of the Spatial map and the corresponding localization information.
Spatial anchor specific information
O
A container to contain application specific information.
VAL service information
M
Information about the application service associated with the spatial anchor.
> VAL Service ID
M
The identifier of the application service.
Service area
O
The service area where the spatial anchor is accessible.
Allowed entities list
O
Identity of entities (e.g. VAL client, VAL server or VAL service identity) which are permitted to discover the spatial anchor.
NOTE: One of the IEs shall be present.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.3.3 Common values related to spatial map
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.3.3.1 Spatial map information
|
Table 7.3.3.1-1 describes information elements for the spatial map information stored in the SM server.
Table 7.3.3.1-1: Spatial map information
Information element
Status
Description
Spatial map ID
M
The identifier of the spatial map
Spatial map coverage
M
The three-dimensional space coordinates information of the spatial map
Allowed entities list
O
Identity of entities (e.g. VAL client, VAL server or VAL service identity) which are permitted to discover and access the spatial map
List of spatial map layers
M
The list of spatial map layer information. At least one or more spatial map layers should be included. Each element includes the information described below.
> Spatial map layer ID
M
The identifier of the corresponding spatial map layer.
> Spatial map layer information
O
A container to carry the corresponding spatial map layer specific information
>> area
O
The area covered by this layer. This area can be the same or a subset of the Spatial map coverage space.
>> associated spatial map
O
The details about a spatial map associated with this layer. For example, if the layer is for a particular floor of the building, the detailed spatial map of that particular floor can be associated with this layer.
> List of objects
O
List of object information. Each element includes the information below.
>> Object ID
M
The identifier of the corresponding object
>> Object type
M
The type of object
>> Object position
O
The 3D position of the object in the layer
>> Object specific information
O
Object specific attribute information
NOTE: For the current release, the object specific information is implementation specific and out of scope.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
7.3.3.2 SM data source profile
|
Table 7.3.3.2-1 describes information elements in the SM data source profile.
Table 7.3.3.2-1: SM data source profile
Information element
Status
Description
SM data source ID
M
The identifier of the SM data source
SM information details
M
The SM information details available at the SM data source; each element includes the information described below.
> SM data identifier
M
The identifier of SM information
> SM data type (NOTE)
M
The type of SM information (e.g., LiDAR camera, RGB-D camera, high-resolution cameras, etc.) that is provided by the application layer.
> SM data format
O
The format of a SM information (e.g., raw, processed, etc.)
> SM data area
M
The spatial coverage area of the SM data.
> Position information
O
Indicates the Three dimensional area of interest or location information of the SM data source
> Availability State information
O
Indicates the time period availability information of the SM data source.
> Data source update interval information
O
Indicates the rate at which data source updates or generates the data. It describes how often the new data is captured or collected. e.g., every x milliseconds generates data.
NOTE: The definition of SM data types is application specific (e.g., VAL client) for the current release.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8 Spatial Anchors (SAn) Server
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.1 General
|
Spatial anchors server is a SEAL service that offers spatial anchors related capabilities to one or more vertical applications.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2 Functional model for spatial anchors server
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.1 General
|
This clause provides architecture for spatial anchors (SAn) service. The on-network functional model is specified in clause 8.2.2, and service based architecture is specified in clause 8.2.3.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2 On-network functional model description
|
Figure 8.2.2-1 illustrates an on-network functional model for Spatial Anchors (SAn) service.
Figure 8.2.2-1: On-network Spatial Anchors functional model
The Spatial Anchors server functional entities are grouped into the vertical application layer and the Service Enabler Architecture Layer (SEAL) layer. The Spatial Anchors server offers the capabilities to manage spatial anchors to the vertical application layer. The Spatial Anchors server functional model is based on SEAL layer as specified in 3GPP TS 23.434 [4].
The spatial anchors server functional entities on the UE and in the network are respectively the spatial anchors (SAn) client and spatial anchors (SAn) server. The VAL client and VAL server are application client and server respectively to provide an application service to the user. The SAn client and SAn server provides client and server side functionalities respectively for managing spatial anchors for the application. The SAn client is a SEAL client providing spatial anchors service to VAL client. The SAn server is a SEAL server providing spatial anchors service to VAL server and UE. The interface between SAn Client and SAn Server is SAn-UU. The SAn client interacts with the VAL client using a SAn-C interface. The SAn server interacts with the VAL server using a SAn-S. The SAn server communicates with the underlying 3GPP network system (either directly or via NEF) using network interfaces specified by the 3GPP network system (e.g. T8, N33). When SAn server is deployed by PLMN operator, the SAn server communicates with 3GPP network system by directly invoking the APIs from exposed by 3GPP core network functions.
Figure 8.2.2-2: Spatial Anchors server interaction with Spatial Map Server
Figure 8.2.2-2 illustrates the functional model for interconnection between SAn server and Spatial Map server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.1 Functional Elements
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.1.1 Spatial anchors (SAn) server
|
The SAn server acts as a SEAL client and it is used to provide services to create/update/delete/discover spatial anchors for the VAL application (i.e. metaverse application). It can communicate with other SAn server in the distributed SEAL deployments.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.1.2 Spatial anchors (SAn) client
|
The SAn client acts as a SEAL client for spatial anchors server. It supports client side functionalities for creating/updating/deleting/discovering/retrieving spatial anchors for VAL application (i.e. metaverse application). The SAn client receives the request from VAL client to perform specific functionality.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.1.3 VAL server
|
The VAL server is specified in clause 6.4.2.3 of 3GPP TS 23.434 [4]. The VAL server provides the server side functionalities corresponding to the vertical applications (i.e. metaverse applications) to the client of a VAL user based on a service contract.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.1.4 VAL client
|
The VAL client is specified in clause 6.4.2.2 of 3GPP TS 23.434 [4]. The VAL client provides a metaverse services to the user. It uses the SAn client to manage spatial anchors for the application.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.2 Reference Points
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.2.1 SAn-UU
|
SAn-UU reference point enables interactions between a SAn client and SAn server. It is used to create/update/delete/discover/retrieve spatial anchors for the VAL applications (i.e. metaverse applications).
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.2.2 SAn-S
|
SAn-S reference point enables interactions between a SAn server and VAL servers (i.e. metaverse application servers). It can be used to create/update/delete/get/retrieve spatial anchors for the VAL applications (i.e. metaverse applications).
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.2.3 SAn-C
|
SAn-C reference point enables interactions between a SAn client and VAL clients (i.e. metaverse application clients). It is used by the VAL client to share information regarding spatial anchors related information to the SAn client and also to get spatial anchors related information from the SAn client.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.2.2.4 SEAL-X (AnM) (between the SAn server and the SM server)
|
The SEAL-X (AnM) reference point, which exists between the Spatial anchors server and the Spatial map server, provides a means for the both servers to exchange information related to anchors and maps to each other.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.2.3 Service based architecture
|
Figure 8.2.3-1 illustrates the service-based SEAL architecture to support spatial anchors services.
Figure 8.2.3-1: service based architecture for spatial anchors server
The SAn server exposes the APIs over the SSAn interface to the VAL server and SAn client. The VAL servers consume the services by interacting on the SSAn interface of the SAn server. The CAPIF can be used by VAL functions to discover the services of the SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3 Spatial anchors management procedures
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.1 Spatial anchor creation
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.1.1 General
|
Spatial anchor creation enables a SAn client or VAL server to create spatial anchor(s) with the SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.1.2 Procedure
|
Figure 8.3.1.2-1 illustrates the spatial anchor creation procedure.
Pre-conditions:
1. The SAn client or VAL server has received information (e.g. URI, IP address) related to the SAn server;
2. The SAn client or VAL server has received security credentials authorizing it to communicate with the SAn server.
3. For SAn client to trigger this procedure, the SAn client has received the required information from the VAL client over SAn-C interface.
Figure 8.3.1.2-1: Spatial anchor creation
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor create request to the SAn server. The request includes a requestor identifier, security credentials, and list of spatial anchors to be created as described in clause 8.3.1.3.1. The request includes a position, allowed entities list defining which entities are permitted to discover and access the spatial anchor, and discoverability information (e.g., indicating whether the spatial anchor is discoverable by any user). If the request includes spatial anchor specific information, that information remains transparent to the SAn server and can be stored with the spatial anchor. The request can indicate to create multiple spatial anchors.
NOTE: The spatial anchor specific information is out of scope of standardization. For example, the spatial anchor specific information may contain application specific service information like a name, a URL, a media data, a type, a manufacturing company, a date, an expiry date, a ratings, and customer premise information (e.g. a residence, office or shop), a service schedule defining times when the spatial anchor(s) are active and inactive, etc. Such information may be stored in key-value pair and is transparent to the SAn server.
2. Upon receiving the request, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized, the SAn server creates the spatial anchor(s), assigns spatial anchor identifier to the newly created spatial anchor(s) and stores the spatial anchor information.
3. The SAn server sends a spatial anchor create response to the requestor. If the SAn server created spatial anchors, the response includes an indication of success and spatial anchor identifier(s) of newly created spatial anchor(s). Otherwise, the response includes an indication of failure and can include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.1.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.1.3.1 Spatial anchor create request
|
Table 8.3.1.3.1-1 describes information elements for the spatial anchor create request from the SAn client or VAL server to the SAn server.
Table 8.3.1.3.1-1: Spatial anchor create request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
The security credentials of the requestor.
VAL service information
M
Information about the application service associated with the spatial anchor.
> Service ID
M
The identifier of the application service.
> Service endpoint
M
Endpoint information (e.g., URI, FQDN, IP address) used to communicate with the application service.
> Service connection information
O
The connection information (e.g., DNN, DNAI(s)) for establishing connectivity to the application service.
List of spatial anchors
M
List of spatial anchors to be created.
> Position information
M
Position information of the spatial anchor
>> Position (NOTE)
O
The 3D geographic position of the spatial anchor in space (x, y and z coordinates).
>> Spatial map position (NOTE)
O
Position information of the spatial anchor within the spatial map. It includes the identifier of the Spatial map, identifier of spatial map layer(s) and the corresponding localization information (The localization information is specific to spatial map format).
> Spatial anchor specific information
O
A container to contain application specific information.
> Service area
O
The service area where the spatial anchor is accessible.
> Allowed entities list
O
Identity of entities (e.g. VAL client, VAL server or VAL service identity) which are permitted to discover the spatial anchor.
> Spatial anchor resource identifer
M
The identifier to associate the resource information with the created spatial anchors.
NOTE: One of the IEs shall be present.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.1.3.2 Spatial anchor create response
|
Table 8.3.1.3.2-1 describes information elements for the spatial anchor create response from the SAn service.
Table 8.3.1.3.2-1: Spatial anchor create response
Information element
Status
Description
Successful response
O
Indicates that the spatial anchor create request was successful.
> List of spatial anchors
O
The list of created spatial anchors.
>> Spatial anchor ID
O
The identifier of the spatial anchor
>> Spatial anchor resource identifier
O
The identifier provided by the SAn client in order to associate the created spatial anchor with the resource information used for creating the spatial anchor.
Failure response
O
Indicates that the create spatial anchor request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.2 Spatial anchor update
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.2.1 General
|
Spatial anchor update enables a SAn client or VAL server to update spatial anchor(s) with the SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.2.2 Procedure
|
Figure 8.3.2.2-1 illustrates the spatial anchor update procedure.
Pre-conditions:
1. The SAn client or VAL server has received information (e.g. URI, IP address) related to the SAn server; and
2. The SAn client or VAL server has received security credentials authorizing it to communicate with the SAn server.
3. For SAn client to trigger this procedure, the SAn client has received the required information from the VAL client over SAn-C interface.
Figure 8.3.2.2-1: Spatial anchor update
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor update request to the SAn server. The request includes a requestor identifier, security credentials, the identifier of spatial anchors, and spatial anchor information to update as described in clause 8.3.2.3.1. The request may include information to update multiple spatial anchors.
2. Upon receiving the request, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized and the spatial anchor identifier provided in the request is found, the SAn server updates the spatial anchor information based on information provided in the request.
3. The SAn server sends a spatial anchor update response to the requestor. If the SAn server updated the spatial anchor, the response includes an indication of success and the identifier of updated spatial anchor(s). Otherwise, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.2.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.2.3.1 Spatial anchor update request
|
Table 8.3.2.3.1-1 describes information elements for the spatial anchor update request from the SAn client or VAL server to the SAn server.
Table 8.3.2.3.1-1: Spatial anchor update request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
The security credentials of the requestor.
> VAL service information
O
Information about the application service associated with the spatial anchor.
>> Service ID
O
The identifier of the application service.
>> Service endpoint
O
Endpoint information (e.g., URI, FQDN, IP address) used to communicate with the application service.
>> Service connection information
O
The connection information (e.g., DNN, DNAI(s)) for establishing connectivity to the application service.
List of spatial anchors
M
List of spatial anchors to be updated.
> Spatial anchor ID
M
Identifier of the spatial anchor to be updated.
> Position information
O
Position information of the spatial anchor
>> Position (NOTE)
O
The 3D geographic position of the spatial anchor in space (x, y and z coordinates).
>> Spatial map position (NOTE)
O
Position information of the spatial anchor within the spatial map. It includes the identifier of the Spatial map, identifier of spatial map layer(s) and the corresponding localization information (The localization information is specific to spatial map format).
> Spatial anchor specific information
O
A container to contain application specific information.
> Service area
O
The service area where the spatial anchor is accessible.
> Allowed entities list
O
Identity of entities (e.g. VAL client, VAL server or VAL service identity) which are permitted to discover the spatial anchor.
NOTE: If Position information is included, at least one of the IEs shall be present.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.2.3.2 Spatial anchor update response
|
Table 8.3.2.3.2-1 describes information elements for the spatial anchor update response from the SAn server.
Table 8.3.2.3.2-1: Spatial anchor update response
Information element
Status
Description
Successful response
O
Indicates that the update spatial anchor request was successful.
> List of spatial anchor ID
O
List of identifiers of the updated spatial anchors.
Failure response
O
Indicates that the update spatial anchor request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.3 Spatial anchor deletion
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.3.1 General
|
Spatial anchor deletion enables a SAn client or VAL server to delete spatial anchor(s) with the SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.3.2 Procedure
|
Figure 8.3.3.2-1 illustrates the spatial anchor deletion procedure.
Pre-conditions:
1. The SAn client or VAL server has received information (e.g. URI, IP address) related to the SAn server; and
2. The SAn client or VAL server has received security credentials authorizing it to communicate with the SAn server.
3. For SAn client to trigger this procedure, the SAn client has received the required information from the VAL client over SAn-C interface.
Figure 8.3.3.2-1: Spatial anchor deletion
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor delete request to the SAn server. The request includes a requestor identifier, security credentials, the identifier of spatial anchors to delete as described in clause 8.3.3.3.1. The request may include information to delete multiple spatial anchors.
2. Upon receiving the request, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized and the spatial anchor identifier provided in the request is found, the SAn server deletes the spatial anchor information.
3. The SAn server sends a spatial anchor delete response to the requestor. If the SAn server deleted the spatial anchor(s), the response includes an indication of success and the identifier of deleted spatial anchor(s). Otherwise, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.3.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.3.3.1 Spatial anchor delete request
|
Table 8.3.3.3.1-1 describes information elements for the spatial anchor delete request from the SAn client or VAL server to the SAn server.
Table 8.3.3.3.1-1: Spatial anchor delete request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
The security credentials of the requestor.
List of spatial anchors ID
M
List of identifiers of the spatial anchors to be deleted.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.3.3.2 Spatial anchor delete response
|
Table 8.3.3.3.2-1 describes information elements for the delete spatial anchor response from the SAn server to the SAn client or VAL server.
Table 8.3.3.3.2-1: Delete spatial anchor response
Information element
Status
Description
Successful response
O
Indicates that the delete spatial anchor request was successful.
> List of spatial anchor ID
O
List of identifiers of the deleted spatial anchors.
Failure response
O
Indicates that the delete spatial anchor request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.4 Spatial anchor discovery
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.4.1 General
|
Spatial anchor discovery enables a SAn client or VAL server to discover spatial anchor(s) with the SAn server. The discovery of spatial anchor(s) is based on matching spatial anchor discovery filters provided in the request.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.4.2 Procedure
|
Figure 8.3.4.2-1 illustrates the procedure for spatial anchor discovery following the request-response model.
Pre-conditions:
1. The SAn client or VAL server has received information (e.g. URI, IP address) related to the SAn server; and
2. The SAn client or VAL server has received security credentials authorizing it to communicate with the SAn server.
3. For SAn client to trigger this procedure, the SAn client has received the required information from the VAL client over SAn-C interface.
Figure 8.3.4.2-1: Spatial anchor discovery
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor discovery request message to the SAn server to obtain information about spatial anchors of interest. The request includes a requestor identifier, security credentials, and can include spatial anchor discovery filters as described in clause 8.3.4.3.1. If the discovery request was triggered by a VAL client on a UE, the spatial anchor discovery request can additionally include a VAL client identifier.
2. Upon receiving the request, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized, the SAn server identifies spatial anchor(s) that satisfies the spatial anchor discovery filters.
NOTE 1: User preferences in the spatial anchor discovery filters can be compared with spatial anchor specific information.
For each matching spatial anchor, the SAn server checks whether the requestor is authorized to obtain the spatial anchor based on the identity and location of the requestor, and based on the allowed entities list. To determine the location of interest of the requestor, the SAn server may use location information provided in the request. If location information is not provided in the request, the SAn server may obtain location information by invoking the 3GPP Core Network Location Services as described in 3GPP TS 23.273 [6] and 3GPP TS 23.502 [5] directly or via the NEF, or by invoking the SEAL Location Management APIs as described in 3GPP TS 23.434 [4].
3. The SAn server sends a spatial anchor discovery response to the requestor. If the SAn server has identified spatial anchor(s), the response includes an indication of success and the identified spatial anchors and may includes the recommended list of spatial anchors. Otherwise, the response includes an indication of failure and may include a reason for failure.
NOTE 2: The logic to generate a recommended list of spatial anchors is out of scope and implementation specific.
4. Upon receiving the spatial anchor discovery response, if the response indicates success, the requestor can store the spatial anchor information in a spatial anchor cache. The requestor evaluates the validity conditions associated with the discovered spatial anchors prior to using the spatial anchor. If the requestor is the SAn client, the SAn client can provide spatial anchor information to the VAL client(s). Upon receiving valid spatial anchor information, VAL client(s) can access the service(s) associated with each spatial anchor.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.4.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.4.3.1 Spatial anchor discovery request
|
Table 8.3.4.3.1-1 describes information elements for the spatial anchor discovery request from the SAn client or VAL server to the SAn server.
Table 8.3.4.3.1-1: Spatial anchor discovery request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
The security credentials of the requestor.
VAL client ID
O
The identifier of the VAL client when the requestor is a SAn client.
Discovery filters
O
The filters used for determining the spatial anchors.
> List of spatial anchor ID
O
The list of spatial anchor identifiers to discover.
> Area of interest
O
The area of interest (e.g., topological area and/or geographical area).
> Service ID
O
The identifier of a VAL service.
> Spatial anchor specific information
O
A container to contain application specific information.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.4.3.2 Spatial anchor discovery response
|
Table 8.3.4.3.2-1 describes information elements for the spatial anchor discovery response from the SAn server.
Table 8.3.4.3.2-1: Spatial anchor discovery response
Information element
Status
Description
Successful response
O
Indicates that the spatial anchor discovery request was successful.
List of spatial anchors
O
List of discovered spatial anchors.
> Spatial anchor ID
M
Identifier of the discovered spatial anchor.
> Position
M
The 3D position of the spatial anchor in space (x, y and z coordinates).
> Spatial anchor specific information
O
A container to contain application specific information.
> VAL service information
M
Information about the application service associated with the spatial anchor.
>> Service ID
M
The identifier of the application service.
>> Service endpoint
M
Endpoint information (e.g., URI, FQDN, IP address) used to communicate with the application service.
>> Service connection information
O
The connection information (e.g., DNN, DNAI(s)) for establishing connectivity to the application service.
Failure response
O
Indicates that the spatial anchor discovery request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5 Spatial anchor subscription
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.1 General
|
Spatial anchor subscription enables a SAn client or VAL server to subscribe with the SAn server to receive notifications related to spatial anchors.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.2 Procedures
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.2.1 Subscribe
|
Figure 8.3.5.2.1-1 illustrates the spatial anchor subscription procedure.
Pre-conditions:
1. The SAn client or VAL server has received information (e.g. URI, IP address) related to the SAn server; and
2. The SAn client or VAL server has received security credentials authorizing it to communicate with the SAn server.
Figure 8.3.5.2.1-1: Spatial anchor subscription
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor subscribe request to the SAn server. The request includes a requestor identifier, security credentials, a notification endpoint, and event information for which the requestor is subscribing. The request may include an expiration time.
a. The requestor may include the "discovery" event type to indicate the SAn server to notify the requestor when the SAn server detects events related to the management of spatial anchors (e.g., creation, update, deletion) according to discovery event filters and spatial anchor filters provided in the request. If the requestor is a SAn client, the request includes a VAL client identifier.
b. The VAL server may include the "UE with spatial anchor interest" event type to indicate the SAn server to notify the VAL server when the SAn server detects UE(s) with interest in specific spatial anchors according to the spatial anchor of interest event filters and spatial anchor filters provided in the request.
c. The requestor may include the "spatial anchor in range" event type to indicate the SAn server to notify the requestor when the SAn server detects that spatial anchors become in range or out of range of the subscriber according to range event filters provided in the request. Range event filters can include a range for detecting spatial anchors, an indication to enable persistent search, the pose of the subscriber. If the requestor is a SAn client, the spatial anchor subscribe request includes a VAL client identifier.
2. Upon receiving the request from the requestor, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized, the SAn server creates the subscription and stores the subscription information.
a. If the subscribed event is for "discovery", the SAn server starts monitoring spatial anchors management events according to the discovery event filters and spatial anchor filters.
b. If the subscribed event is for "UE with spatial anchor interest", the SAn server starts monitoring spatial anchors of interest according to the UE with spatial anchor interest event filters and spatial anchor filters. If the spatial anchors of interest have been discovered by a UE, the SAn server can obtain the UE location information from the 5GS or the SEAL Location Management service. Additionally, the SAn server can consider data analytics, such as UE mobility prediction. The SAn server may monitor the distance between UEs and the spatial anchor of interest to determine whether the UEs enters, exits or is within range of the spatial anchors of interest.
c. If the subscribed event is for "spatial anchor in range" and the requestor is a SAn client, the SAn server starts monitoring the corresponding UE location and direction corresponding to the pose information according to the range event filters and spatial anchor filters. The UE location information can be obtained by using capabilities of the 5GS or the SEAL Location Management service. Additionally, the SAn server can consider data analytics, such as UE mobility prediction. The SAn server monitors the distance between UEs and the spatial anchor of interest to determine whether the spatial anchors becomes in-range or out-of-range of the UE. If persistent search is enabled, the SAn server monitors location of the user (or UE) and pose of the user, along with a direction of movement, and discovers a list of spatial anchors which becomes in-range or out of range of the user device based on the location of the user device, the pose of the user and in the user's field of view.
3. The SAn server sends a spatial anchor subscribe response to the requestor. If the SAn server has created the subscription, the response includes an indication of success, the subscription identifier and may include an expiration time; to maintain the subscription, the requestor shall send a subscription update request before the expiration time, otherwise the spatial anchor subscription expires. If the SAn server has not created the subscription, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.2.2 Notify
|
Figure 8.3.5.2.2-1 illustrates the spatial anchor notify operation between the SAn server and a SAn client or VAL server.
Pre-conditions:
1. The SAn client or VAL server has subscribed for spatial anchor notifications with the SAn server;
Figure 8.3.5.2.2-1: Spatial anchor notification
1. An event occurs at the SAn server that satisfies trigger conditions for notifying a subscriber (e.g., SAn client or VAL server) according to subscribed events and discovery filters provided for the events.
2. The SAn server sends a spatial anchor notification to the requestor indicating the event. The notification includes a subscription identity and includes event-specific information.
a. If the subscribed event is for "discovery", the notification includes the list of determined spatial anchors
b. If the subscribed event is for "UE with spatial anchor interest", the notification includes information about UE with spatial anchor interest (e.g., UE identifier, spatial anchor identifier(s), range from the spatial anchor(s), entering or exiting the range, etc.).
c. If the subscribed event is for "spatial anchor in range", the notification includes the list of determined spatial anchors that become in range, out of range of the subscriber.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.2.3 Subscription update
|
Figure 8.3.5.2.3-1 illustrates the procedure for a SAn client or VAL server to update a subscription with the SAn server.
Pre-conditions:
1. The SAn client or VAL server has subscribed for spatial anchor notifications with the SAn server;
Figure 8.3.5.2.3-1: Spatial anchor subscription update
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor subscription update request to the SAn server. The request includes the requestor identifier, security credentials and the subscription identifier and may include subscribed event information and expiration time.
2. Upon receiving the request from the requestor, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized, the SAn server updates the subscription information.
3. The SAn server sends a spatial anchor subscription update response to the requestor. If the SAn server has updated the subscription, the response includes an indication of success and may include an expiration time. To maintain the subscription, the requestor shall send a subscription update request before the expiration time, otherwise the spatial anchor subscription expires. If the SAn server has not updated the subscription, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.2.4 Unsubscribe
|
Figure 8.3.5.2.4-1 illustrates the procedure for a SAn client or VAL server to unsubscribe with the SAn server.
Pre-conditions:
1. The SAn client or VAL server has subscribed for spatial anchor notifications with the SAn server;
Figure 8.3.5.2.4-1: Spatial anchor unsubscribe
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor unsubscribe request to the SAn server. The request includes the requestor identifier, security credentials and the subscription identifier.
2. Upon receiving the request from the requestor, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized, the SAn server cancels the subscription associated with the subscription identifier.
3. The SAn server sends a spatial anchor unsubscribe response to the requestor. If the SAn server has canceled the subscription, the response includes an indication of success. If the SAn server has not canceled the subscription, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3.1 Spatial anchor subscribe request
|
Table 8.3.5.3.1-1 describes information elements for the spatial anchor subscribe request from the SAn client or VAL server to the SAn server.
Table 8.3.5.3.1-1: Spatial anchor subscribe request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
The security credentials of the requestor.
VAL client ID
O
The identifier of the VAL client when the requestor is a SAn client.
Notification Target Address
M
Notification target address (e.g. URL) where the notifications should be sent.
Proposed expiration time
O
Proposed expiration time for the subscription.
Event type
M
The type of event for which the requestor is subscribing. Supported event types include:
- "discovery"
- "UE with spatial anchor interest"
- "spatial anchor in range"
Persistent Search (NOTE)
O
Indicates to enable persistent search.
Event detection filters
O
Event type specific detection filters.
> Discovery event filters
O
Event filters applicable to the "discovery" event type. The event filter is considered by the SAn server for triggering the notification and can include management events (e.g., creation, update, deletion).
> UE with spatial anchor interest event filters
O
Event filters applicable to “UE with spatial anchor interest” event type. The event filter is considered by the SAn server for triggering the notification and can include an indication for detecting UEs that have discovered spatial anchors, that are within range or become out of range of spatial anchors, or that enter or leave the range of a spatial anchor, and a value for the range.
> Range event filters
O
Event filters applicable to “spatial anchor in range” event type. The event filter is considered by the SAn server for triggering the notification and can include an indication for spatial anchors becoming in range of the UE, out of range of the UE, or both and a value for the range.
>> current location
O
Current location of the user and direction.
>> pose
O
Current pose of the user
>> application specific range
M
Specifies range within which the spatial anchors are monitored to be in range or out of range of the subscriber's field of view.
>> Spatial anchor specific information
O
A container to contain application specific information.
Spatial anchor filters
O
The characteristics of spatial anchors that the SAn server considers for triggering a notification.
> Spatial anchor ID list
O
Identifiers of the spatial anchors of interest.
> Service ID list
O
Identifiers of the associated application services of interest.
> Area of interest
O
The area of interest (e.g., topological and/or geographical).
NOTE: This IE can be included with "spatial anchor in range" event.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3.2 Spatial anchor subscribe response
|
Table 8.3.5.3.2-1 describes information elements for the spatial anchor subscribe response sent by the SAn server.
Table 8.3.5.3.2-1: Spatial anchor subscribe response
Information element
Status
Description
Successful response
O
Indicates that the subscription request was successful.
> Subscription ID
M
Subscription identifier corresponding to the subscription.
> Expiration time
O
Indicates the expiration time of the subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure response
O
Indicates that the subscription request failed.
> Cause
O
Indicates the cause of subscription request failure
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3.3 Spatial anchor notification
|
Table 8.3.5.3.3-1 describes information elements for the spatial anchor notification sent by the SAn server.
Table 8.3.5.3.3-1: Spatial anchor notification
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
Event type
M
The type of event notification. Supported event types include:
- "discovery"
- "UE with spatial anchor interest"
- "spatial anchor in range"
Detected event
O
Identifier of the event that was detected and that triggered the server to send a notification (e.g., spatial anchors becoming in range of the UE or out of range of the UE; or, UE entering the range of a spatial anchor or leaving the range of a spatial anchor).
Spatial anchor list
O
List of discovered spatial anchors (as detailed in spatial anchor discovery response).
Applicable for "discovery" and "spatial anchor in range" events.
UE with spatial anchor interest list
O
List of UE with spatial anchor interest.
Applicable for "UE with spatial anchor interest" and "spatial anchor in range" events.
> UE ID
O
Identifier of the UE with spatial anchor interest.
> Spatial anchor ID
O
Identifier of the spatial anchor of interest.
> Spatial anchor range
O
The spatial anchor range.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3.4 Spatial anchor subscription update request
|
Table 8.3.5.3.4-1 describes information elements for the spatial anchor subscription update request from the SAn client or VAL server to the SAn server.
Table 8.3.5.3.4-1: Spatial anchor subscription update request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
Security credentials of the requestor.
Subscription ID
M
Subscription identifier corresponding to the subscription to be updated.
Notification Target Address
O
Notification target address (e.g. URL) where the notifications should be sent.
Proposed expiration time
O
Proposed expiration time for the subscription.
Event detection filters
O
Event type specific detection filters that the SAn server considers for triggering a notification, as detailed in Table 8.3.5.3.1-1.
Spatial anchor filters
O
The characteristics of spatial anchors that the SAn server considers for triggering a notification, as detailed in Table 8.3.5.3.1-1.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3.5 Spatial anchor subscription update response
|
Table 8.3.5.3.5-1 describes information elements for the spatial anchor subscription update response sent by the SAn server.
Table 8.3.5.3.5-1: Spatial anchor subscription update response
Information element
Status
Description
Successful response
O
Indicates that the subscription update request was successful.
> Expiration time
O
Indicates the expiration time of the updated subscription. To maintain an active subscription, a subscription update is required before the expiration time.
Failure response
O
Indicates that the subscription update request failed.
> Cause
O
Indicates the cause of subscription update request failure
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3.6 Spatial anchor unsubscribe request
|
Table 8.3.5.3.6-1 describes information elements for the spatial anchor unsubscribe request from the SAn client or VAL server to the SAn server.
Table 8.3.5.3.6-1: Spatial anchor unsubscribe request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
Security credentials of the EEC
Subscription ID
M
Subscription identifier corresponding to the subscription to be unsubscribed
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.5.3.7 Spatial anchor unsubscribe response
|
Table 8.3.5.3.7-1 describes information elements for the spatial anchor unsubscribe response sent by the SAn server.
Table 8.3.5.3.7-1: Spatial anchor unsubscribe response
Information element
Status
Description
Successful response
O
Indicates that the unsubscribe request was successful.
Failure response
O
Indicates that the unsubscribe request failed.
> Cause
O
Indicates the cause of unsubscribe request failure
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.6 Spatial anchor retrieve
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.6.1 General
|
Spatial anchor get operation enables a SAn client or VAL server to get details about the specific spatial anchor from the SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.6.2 Procedure
|
Figure 8.3.6.2-1 illustrates the procedure for spatial anchor retrieve operation following the request-response model.
Pre-conditions:
1. The SAn client or VAL server has received information (e.g. URI, IP address) related to the SAn server;
2. The SAn client or VAL server has received security credentials authorizing it to communicate with the SAn server;
3. The SAn client or VAL server has discovered the list of spatial anchors as per the procedure defined in clause 8.3.4.
Figure 8.3.6.2-1: Spatial anchor retrieve
1. The requestor (e.g., SAn client or VAL server) sends a spatial anchor retrieve request message to the SAn server to get information about specific spatial anchors of interest. The request includes a requestor identifier, security credentials, identity of the spatial anchor.
2. Upon receiving the request, the SAn server validates if the requestor is authorized for the request. If the requestor is authorized, the SAn server identifies whether spatial anchor exists or not based on identity of the spatial anchor.
3. The SAn server sends a spatial anchor retrieve response to the requestor. If the SAn server has identified spatial anchor, the response includes an indication of success and the details about the spatial anchor. Otherwise, the response includes an indication of failure and may include a reason for failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.6.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.6.3.1 Spatial anchor retrieve request
|
Table 8.3.6.3.1-1 describes information elements for the spatial anchor retrieve request from the SAn client or VAL server to the SAn server.
Table 8.3.6.3.1-1: Spatial anchor retrieve request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server or VAL UE and VAL user).
Security credentials
M
The security credentials of the requestor.
> Spatial anchor ID
M
Identifier of the spatial anchor.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.3.6.3.2 Spatial anchor retrieve response
|
Table 8.3.6.3.2-1 describes information elements for the spatial anchor retrieve response from the SAn server.
Table 8.3.6.3.2-1: Spatial anchor retrieve response
Information element
Status
Description
Successful response
O
Indicates that the spatial anchor retrieve request was successful.
> Spatial anchor profile
M
Spatial anchor profile as specified in Table 7.3.2.1-1
Failure response
O
Indicates that the spatial anchor retrieve request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4 Spatial anchor usage information
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.1 General
|
The spatial anchor usage information procedure allows consumer (i.e. VAL server) to get usage information about the spatial anchor. The spatial anchor usage information procedure enables the VAL server to request or subscribe with the SAn server to receive spatial anchor usage information.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.2 Spatial anchor usage information (Sub-Notify)
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.2.1 General
|
This clause enables VAL server to subscribe spatial anchor usage information from the SEAL SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.2.2 Procedure
|
Figure 8.4.2.2-1 depicts the procedure for subscribing to receive information related to spatial anchor usage for metaverse applications. The service is provided by SAn server.
Figure 8.4.2.2-1: Spatial anchor usage information subscription
1. A consumer (e.g. VAL server) sends a spatial anchor usage information subscription request to the SAn server). The request can include the VAL server identifier, security credentials, a notification endpoint (e.g., IP address, FQDN, URI), and spatial anchor filters like spatial anchor identifiers, spatial anchor location information, position of the user, proximity distance, and application service identifier. It may also include the periodicity for reporting notification and sampling interval.
2. Upon receiving the request, the SAn server authorizes the VAL server subscription request and sends a spatial anchor usage subscription response to the consumer.
3. The SAn server samples the information related to spatial anchor usage based on the obtained data and the stored spatial anchor data as per the sampling interval. It provides notification to the consumer as per the reporting interval. The notification message includes spatial anchor ID, number of times spatial anchor discovered and accessed, spatial anchor density per location, user density per spatial anchor, spatial anchor services accessed information.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.2.3 Information flows
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.2.3.1 Spatial anchor usage information subscription request
|
Table 8.4.2.3.1-1 describes information elements for the spatial anchor usage information subscription request from the consumer to the SAn server.
Table 8.4.2.3.1-1: Spatial anchor usage information subscription request
Information element
Status
Description
Requestor identifier
M
The identifier of the requestor (e.g., VAL server).
Security credentials
M
The security credentials of the requestor.
Spatial anchor analytics filters
M
Indicates the spatial anchor filter for the analytics information
> Spatial anchor identifiers
O
Indicates the spatial anchor identities
> Spatial anchor location information
O
Indicates the spatial anchor location information
> Area information
O
Indicates the area information (e.g., location information)
> Application service information
O
Indicates the application service information(e.g., application identifier)
Analytics sampling interval
O
Indicates the interval to sample the spatial anchor(s) related information to generate analytics
Reporting interval
O
Indicates the periodic reporting interval of analytics information
notification endpoint
O
Indicates the endpoint(e.g., IP address, FQDN, URI) to send the analytics information notification
NOTE: Spatial anchor analytics filters IE must include at least one optional IE.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.2.3.2 Spatial anchor usage information subscription response
|
Table 8.4.2.3.2-1 describes information elements for the spatial anchor usage information subscription response from the SAn server to the consumer.
Table 8.4.2.3.2-1: Spatial anchor usage information subscription response
Information element
Status
Description
Successful response
O
Indicates that the subscription request was successful.
> Spatial anchor Analytics subscription ID
M
Identity for the spatial anchor analytics subscription
Failure response
O
Indicates that the subscription request has failed.
> Cause
O
The cause for the request failure.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.2.3.3 Spatial anchor usage information notification
|
Table 8.4.2.3.3-1 describes information elements for the spatial anchor usage information notification from the SAn server to the consumer.
Table 8.4.2.3.3-1: Spatial anchor usage information notification
Information element
Status
Description
Spatial anchor Analytics subscription ID
M
Identity for the spatial anchor analytics subscription
Spatial anchor identifiers
M
Indicates the spatial anchor identities
> Spatial anchor usage information
M
Indicates spatial anchor usage information. It includes number of times spatial anchor discovered and accessed, spatial anchor services accessed information.
> Spatial anchor density per location
M
Indicates the density of the spatial anchor in the given area.
> User density per spatial anchor
M
Indicates the density of users within proximity to a specific spatial anchor.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.3 Spatial anchor usage information (Request-Response)
| |
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.3.1 General
|
This clause enables VAL server to request spatial anchor usage information from the SEAL SAn server.
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
8.4.3.2 Procedure
|
Figure 8.4.3.2-1 depicts the procedure to receive information related to spatial anchor usage for metaverse applications. The service is provided by SAn server.
Figure 8.4.3.2-1 Spatial anchor usage information
1) The consumer (e.g. VAL server) sends a request message to the SAn server to get the spatial anchor usage information as per Table 8.4.3.3.1-1.
2) The SAn server authorizes the consumer. If the requestor is authorized, then the SAn server provides the spatial anchor usage information. The response message includes spatial anchor ID, number of times spatial anchor discovered and accessed, spatial anchor density per location, user density per spatial anchor, spatial anchor services accessed information.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.