hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.3.9.2 Request Subscripiton | API operation name: Data_Storage_Subscribe
Description: The consumer requests A-ADRF to subscribe for data or analytics from ADAE server or A-DCCF for store. This service operation provides parameters needed by the A-ADRF to initiate the subscription (to an ADAE server or A-DCCF).
Inputs: See clause 8.10.3.2.
Outputs: ... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.3.9.3 Store Data | API operation name: Data_Storage_Request
Description: The consumer requests A-ADRF to store data or analytics from ADAE server or A-DCCF. Data or analytics are provided to the A-ADRF in the request message.
Inputs: See clause 8.10.3.4.
Outputs: See clause 8.10.3.5.
See clause 8.10.2 for details of usage of this operati... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.3.10 SS_AADRF_ServerToServer_Analytics API | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.3.10.1 General | API description: This API enables the ADAE server to communicate with the A-ADRF to request server-to-server analytics for inter-server communication. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.3.10.2 Get | API operation name: ServerToServer_Analytics_Get
Description: The consumer is receiving offline server-to-server analytics/data from A-ADRF.
Inputs: See clause 8.13.3.7.
Outputs: See clause 8.13.3.8.
See clause 8.13.2 for details of usage of this operation. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4 A-DCCF APIs | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4.1 General | This clause provides the APIs provided by A-DCCF. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4.2 A-DCCF APIs | Table 9.4.2-1 illustrates the A-DCCF APIs.
Table 9.4.2-1: List of A-DCCF APIs
API Name
API Operations
Known Consumer(s)
Communication Type
SS_ADCCF_Data_Collection
Subscribe
ADAE server
Subscribe / Notify
Notify
Get
ADAE server
Request / Response |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4.3 SS_ADCCF_Data_Collection API | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4.3.1 General | API description: This API enables the consumer to subscribe/unsubscribe for data or analytics via the A-DCCF, be notified about data or analytics exposed by the A-DCCF, fetch the subscribed data and have data delivered via the A-DCCF. Historical data, or runtime data may be obtained using this service.
When the subscri... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4.3.2 Subscribe | API operation name: Data_Collection_Subscribe
Description: The consumer subscribes to receive data or analytics, or if the data is already requested from the A-DCCF, then the subscription is updated. The subscription includes service operation specific parameters that identify the data or analytics to be provided. The ... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4.3.3 Notify | API operation name: Data_Collection_Notify
Description: The A-DCCF notifies the consumer of the requested data or analytics according to the request, or notifies of the availability of previously subscribed data or analytics when data delivery is via the A-DCCF. The A-DCCF may also notify the consumer when data or anal... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 9.4.3.4 Request | API operation name: Data_Collection_Request
Description: The consumer retrieves data or analytics from the A-DCCF.
Inputs: See clause 8.12.3.5.
Outputs: See clause 8.12.3.6.
See clause 8.12.2 for details of usage of this operation. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10 Analytics related to satellite access | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.1 General | This clause describes the procedures and information flows for analytics related to satellite access. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2 Support for UE RAT connectivity analytics | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.1 General | This clause describes the procedure for supporting UE RAT connectivity analytics for satellite access. The ADAES service consumer can subscribe and receive notifications about UE RAT connectivity analytics events. This analytics helps to predict the type of satellite RAT that a UE will latch onto on a particular locati... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.2 Procedure | Figure 10.2.2-1 illustrates the procedure for UE RAT connectivity analytics.
Pre-conditions:
1. The ADAES is registered and capable of interacting with 5GS to UE mobility analytics.
Figure 10.2.2-1: Procedure for supporting UE RAT connectivity analytics
1. The analytics consumer (e.g.VAL server) makes a subscription re... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.3 Information flows | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.3.1 UE RAT connectivity analytics subscription request | Table 10.2.3.1-1 describes information elements for the UE RAT connectivity analytics subscription request from the VAL server/Analytics consumer to the ADAE server.
Table 10.2.3.1-1
Information element
Status
Description
VAL server ID
M
The identifier of the VAL server.
Analytics ID
M
The identifier of the UE RAT conn... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.3.2 UE RAT Connectivity analytics subscription response | Table 10.2.3.2-1 describes information elements for the UE RAT connectivity analytics subscription response from the ADAE server to the VAL server/Analytics consumer.
Table 10.2.3.2-1
Information element
Status
Description
Result
M
The result of the analytics subscription request (positive or negative acknowledgement) |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.3.3 UE RAT Connectivity data retrieval request | Table 10.2.3.3-1 describes information elements for the UE RAT connectivity data retrieval request from the ADAE server to the A-ADRF.
Table 10.2.3.3-1
Information element
Status
Description
ADAE server ID
M
The identifier of the ADAE server
Analytics ID
M
The identifier of the analytics event i.e. UE RAT connectivity ... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.3.4 UE RAT Connectivity data retrieval response | Table 10.2.3.4-1 describes information elements for the UE RAT connectivity data retrieval response from the A-ADRF to the ADAE server.
Table 10.2.3.4-1
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event.
List of VAL UE IDs and addresses
M
The VAL UE(s) identifiers and IP addres... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.3.5 UE RAT Connectivity analytics notification | Table 10.2.3.5-1 describes information elements for the UE RAT connectivity analytics notification from the A-ADRF to the ADAE server.
Table 10.2.3.5-1
Information element
Status
Description
Analytics ID
M
The identifier of the analytics event (UE RAT connectivity)
VAL UE ID(s)
O
The identity of the VAL UE(s) for which... |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.4 ADAE server APIs | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.4.1 General | This clause provides the APIs provided by ADAES related to satellite access. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.4.2 ADAE server APIs | Table 10.2.4.2-1 illustrates the ADAE server APIs related to satellite access.
Table 10.2.4.2-1: List of ADAE server APIs
API Name
API Operations
Known Consumer(s)
Communication Type
SS_ADAE_UE_RAT_connectivity_analytics
Subscribe
VAL server
Subscribe/Notify
Notify |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.4.3 SS_ADAE_UE_RAT_connectivity_analytics API | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.4.3.1 General | API description: This API enables the analytics consumer (e.g., the VAL server) to communicate with the ADAE server for requesting or subscribing to UE RAT connectivity analytics. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.4.3.2 Subscribe | API operation name: UE_RAT_connectivity_analytics_subscribe
Description: The consumer subscribes to the ADAE server for UE RAT connectivity analytics.
Inputs: See clause 10.2.3.1.
Outputs: See clause 10.2.3.2.
See clause 10.2.2 for details of usage of this operation. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.4.3.3 Notify | API operation name: UE_RAT_connectivity_analytics_notify
Description: The consumer is notified by the ADAE server on the Server-to-server performance analytics.
Inputs: -
Outputs: See clause 10.2.3.5.
See clause 10.2.2 for details of usage of this operation. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.5 A-ADRF APIs | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.5.1 General | This clause provides the APIs provided by A-ADRF related to satellite access. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.5.2 A-ADRF APIs | Table 10.2.5.2-1 illustrates the A-ADRF APIs related to satellite access.
Table 10.2.5.2-1: List of A-ADRF APIs
API Name
API Operations
Known Consumer(s)
Communication Type
SS_ADRF_UE_RAT_connectivity_analytics
Get
ADAES
Request/Response |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.5.3 SS_AADRF_UE RAT connectivity analytics API | |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.5.3.1 General | API description: This API enables the ADAE server to communicate with the A-ADRF to request UE RAT connectivity analytics of VAL UEs. |
20479eb37624e17cc85fa37e0dbf82f7 | 23.436 | 10.2.5.3.2 Get | API operation name: UE_RAT_connectivity_analytics_Data_Get Description: The consumer is receiving offline UE RAT connectivity analytics/data from A-ADRF. Inputs: See clause 10.2.3.3. Outputs: See clause 10.2.3.4. See clause 10.2.2 for details of usage of this operation. Annex A (informative): Deployment scenarios A.1 G... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 1 Scope
| 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 requirement... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 2 References
| 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.
-... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 3 Definitions of terms, symbols and abbreviations
| |
26e140d21b097a2c000610e4bd7ffb34 | 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].
Spatial map layer: A spatial map layer is a logically grouped set of data associated wit... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>
|
26e140d21b097a2c000610e4bd7ffb34 | 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].
ID identifier
SAn Spatial Anchor
SM Spatial Map
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 4 Architectural requirements
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 4.1 General
| This clause provides architectural requirements to consider for Spatial anchors service and Spatial map service.
|
26e140d21b097a2c000610e4bd7ffb34 | 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-4.2-b] The spatial anchors management service shall provide spatial anchor usage information to the authorized consumers.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 sha... |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 6 Functional model deployment options
| |
26e140d21b097a2c000610e4bd7ffb34 | 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... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7 Identities and commonly used values
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.1 General
| This clause specifies details about the identifiers and common values used for spatial anchors and spatial map services.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.2 Identities
| |
26e140d21b097a2c000610e4bd7ffb34 | 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
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.2.2 Identities related to spatial anchors
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.2.3 Identities related to spatial map
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.3 Common values
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.3.1 General
| This clause specifies common values used in this specification.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.3.2 Common values related to spatial anchors
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 1)
O
The 3D geographic position of the spatial ... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.3.3 Common values related to spatial map
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 ... |
26e140d21b097a2c000610e4bd7ffb34 | 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 elemen... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 7.3.3.3 UE-object association information
| Table 7.3.3.31 describes information elements for the UE-object association information.
Table 7.3.3.3-1: UE-object association information
Information element
Status
Description
List of association conditions
M
The conditions to specify when the object can be associated with a UE (e.g., the object can be assoc... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8 Spatial Anchors (SAn) Service
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.1 General
| Spatial anchors service is a SEAL service that offers spatial anchors related capabilities to one or more vertical applications.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.2 Functional model for spatial anchors service
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 service functional model
The Spatial Anchors service functional entities are grouped into the vertical application layer and the Service Enabler Architecture Layer (SEAL) layer. Th... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.2.2.1 Functional Elements
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.2.2.1.1 Spatial anchors (SAn) server
| The SAn server acts as a SEAL server 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.2.2.1.2 Spatial anchors (SAn) client
| The SAn client acts as a SEAL client for SAn 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.2.2.2 Reference Points
| |
26e140d21b097a2c000610e4bd7ffb34 | 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).
|
26e140d21b097a2c000610e4bd7ffb34 | 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).
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 service
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 ... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.3 Spatial anchors management procedures
| |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.3.1 Spatial anchor creation
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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 S... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.3.1.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 an... |
26e140d21b097a2c000610e4bd7ffb34 | 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
... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.3.2 Spatial anchor update
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.3.2.3 Information flows
| |
26e140d21b097a2c000610e4bd7ffb34 | 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 an... |
26e140d21b097a2c000610e4bd7ffb34 | 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... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.3.3 Spatial anchor deletion
| |
26e140d21b097a2c000610e4bd7ffb34 | 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.
|
26e140d21b097a2c000610e4bd7ffb34 | 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. F... |
26e140d21b097a2c000610e4bd7ffb34 | 23.437 | 8.3.3.3 Information flows
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.