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: See clause 8.10.3.3.
See clause 8.10.2 for details of usage of this operation. |
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 operation. |
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 subscription is accepted by the A-DCCF, the consumer (ADAE server) receives from the A-DCCF an identifier (Subscription Correlation ID) allowing it to further manage (modify, delete) the subscription.
NOTE: The definition of delete service operation is within stage 3 scope. |
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 consumer may also request that data be stored in an A-ADRF. When historical data is being obtained, the consumer may specify the A-ADRF ID.
Inputs: See clause 8.12.3.2.
Outputs: See clause 8.12.3.3.
See clause 8.12.2 for details of usage of this operation. |
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 analytics is to be deleted.
Inputs: See clause 8.12.3.4.
Outputs: -.
See clause 8.12.2 for details of usage of this operation. |
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 location and/or particular time and helps the analytics consumer to decide on the actions to improve the service experience over the satellite access. |
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 request to ADAE server for UE RAT connectivity prediction/stats, including an analytics event ID for UE RAT Connectivity analytics. The request may include also the target area, a target VAL service, or a VAL UE, or group of UEs of the VAL service, time validity. If the VAL UEs are provided by the VAL server, this request may also include the expected route or a set of waypoints for the UEs of the VAL application.
2. The ADAE server sends a UE RAT connectivity analytics subscription response as an ACK to the VAL server.
3. The ADAE server subscribes to the SEAL Location management server to get the location information of the VAL UE along with the RAT type. It can set the trigger criteria of receiving the location information of the UE whenever UE RAT type changes as specified in 3GPP TS 23.434 [2] clause 9.3.5.
4. The ADAE server subscribes for NWDAF UE mobility analytics per VAL UE (for all the VAL UEs) and gets notification on the per UE location/mobility analytics based on 3GPP TS 23.288 [4] clause 6.7.2.
5. If the data is collected from multiple sources, the ADAES combines or correlates the data/analytics from steps 3-4 and stores the data into A-ADRF if needed.
6. The ADAE server optionally requests UE RAT connectivity historical analytics/data from A-ADRF for the corresponding VAL UEs.
7. Based on the request, the ADAE server receives UE RAT connectivity historical analytics/data from A-ADRF for the corresponding VAL UEs.
8. The ADAE server abstracts or correlates the data/analytics from steps 5-6 and provides analytics on the UE RAT connectivity for the target VAL application.
9. The ADAE server sends the UE RAT connectivity analytics notification to the consumer. |
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 connectivity analytics event.
VAL UE ID(s) or Group ID
M
The identity of the VAL UE(s) or group of UEs for which the analytics subscription applies
VAL service ID
O
The identifier of the VAL service for which location accuracy analytics is requested.
Preferred confidence level
O
The level of accuracy for the analytics service (in case of prediction).
Area of Interest
O
The geographical or service area for which the subscription request applies.
Time validity
O
The time validity of the subscription request.
UE mobility / route information
O
Information on the target UE or group UE mobility including the expected route/set of waypoints.
Reporting requirements
O
It describes the requirements for analytics reporting. This requirement may include e.g. the type and frequency of reporting (periodic or event triggered), the reporting periodicity in case of periodic, and reporting thresholds. |
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 analytics
List of VAL UE IDs and addresses
M
The VAL UE(s) identifiers and IP address(es) for which the data/analytics apply
VAL service ID
O
The service ID, in case of requesting historical data for a particular VAL service.
Reporting configuration
O
The configuration for data reporting. This requirement may include e.g. the frequency of reporting (periodic), the reporting periodicity in case of periodic, and reporting thresholds, whether data abstraction is needed or not.
Data collection requirements
O
The requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data.
Area of Interest
O
The geographical or service area for which the subscription request applies
Time validity
O
The time validity of the request |
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 address(es) for which the analytics apply
VAL service ID
O
The service ID, in case of requesting historical data for a particular VAL service.
Analytics Output
M
The reported analytics for the UE RAT connectivity, which can be in form of offline stats/historical data for a specific VAL service or for particular UE(s) or group of UEs |
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 the analytics applies.
VAL service ID
O
The identifier of the VAL service for which the analytics applies.
Analytics Output
M
The analytics output which can be predictive or statistical parameter.
> RAT type prediction for given waypoints
O
A predicted or expected RAT type changes for a particular VAL service or UEs for the given waypoints.
>> Applicable area
O
The set of location co-ordinates or waypoints for which the analytics output is applicable.
>> Applicable time period
O
The time period that the analytics applies to.
Confidence level
O
For predictive analytics, the achieved confidence level can be provided.
> RAT type prediction for a given time period
O
A predicted or expected RAT type changes for a particular VAL service or UEs for the given time period.
>> Applicable time period
O
The time period that the analytics applies to.
>> Confidence level
O
For predictive analytics, the achieved confidence level can be provided. |
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 General This clause provides the different deployment models for ADAE services. There could be three deployment options: - ADAES can be deployed at a centralized cloud platform, and collects data from multiple EDNs - ADAES can be deployed at the edge platform - Coordinated ADAES deployment, where multiple ADAE services are deployed in edge or central clouds. Such deployment allows for local-global analytics for system wide optimization A.2 Deployment model #1: Cloud-deployed ADAES In this deployment, as shown in Figure A.2-1, the ADAES is centrally located and can provide analytics services to different consumers including, edge servers, VAL servers, as well as to other SEAL servers (e.g. NSCE). The statistics/predictions that the ADAES provides are applicable to the ADAES service area, which can be provided for the entire PLMN. Figure A.2-1: Cloud deployed ADAES A.3 Deployment model #2 Edge-deployed ADAES In this deployment, as shown in Figure A.3-1, the ADAES is located at the EDN and provides analytics services to the EAS and EES at the edge platform. ADAES can be deployed by the ECSP or the MNO to provide analytics for the application or edge parameters. The statistics/predictions that the edge deployed ADAES are applicable to the ADAES service areas (as shown in the example in Fig A.2-2), which are equivalent to the EES/EAS service areas. Such analytics can be about the edge load or the EAS performance and can be provided to consumers within EDN. In this deployment the interaction between edge deployed ADAES is possible for exchanging edge/application analytics for application mobility scenarios or for cases when ADAES #1 and #2 service areas have overlapping coverage. Figure A.3-1: Edge deployed ADAES A.4 Deployment model #3: Coordinated ADAES deployment In this deployment, multiple ADAESs can be located at different EDNs/DNs and can be deployed by the same ADAE provider. Such coordinated deployments allow the local – global analytics derivation (which may be needed for improving the analytics confidence level). The centrally deployed ADAES can also act as ADAE analytics aggregator entity and configures the edge deployed ADAES to derive analytics on different sub-areas. One example is the use of analytics for the EDN#1 or EDN#2 load which will help predicting the VAL server performance at a centrally located ADAES. Such deployment is also applicable for ML-based analytics methods, like supervised learning, where the centrally located ADAES acts as ML model training entity, and the edge located ADAESs can act as ML model inference entities (using edge data to improve the prediction accuracy). The statistics/predictions that the edge deployed ADAES correspond to the ADAES service areas (as shown in the example in Fig A.4-1), which is equivalent to the EES/EAS service areas. The central ADAE server covers all PLMN area and is used to coordinate or jointly perform analytics with the distributed ADAES. Such analytics services can be provided to consumers at the central DN, like the VAL servers or SEAL services or even at the PLMN side (e.g. NWDAF consuming service experience analytics). Figure A.4-1: Coordinated deployment of ADAES Annex B (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2022-10 SA6#51-e TS skeleton 0.0.0 2022-10 SA6#51-e Implementation of the following pCRs approved by SA6: S6-222940, S6-222941, S6-222942, S6-222943 0.1.0 2022-11 SA6#52 Implementation of the following pCRs approved by SA6: S6-223235, S6-223237, S6-223455, S6-223456, S6-223494 0.2.0 2023-01 SA6#52-bis-e Implementation of the following pCRs approved by SA6: S6-230262, S6-230363, S6-230247 0.3.0 2023-03 SA6#53 Implementation of the following pCRs approved by SA6: S6-230939, S6-230847, S6-230848, S6-230849, S6-230850 0.4.0 2023-03 SA#99 SP-230273 Presentation for information at SA#99 1.0.0 2023-04 SA6#54-e Implementation of the following pCRs approved by SA6: S6-231484, S6-231543, S6-231502, S6-231435, S6-231641, S6-231257, S6-231261, S6-231270. 1.1.0 2023-05 SA6#55 Implementation of the following pCRs approved by SA6: S6-231690, S6-232085, S6-232091. 1.2.0 2023-06 SA#100 SP-230687 Presentation for approval at SA#100 2.0.0 2023-06 SA#100 SP-230687 MCC Editorial update for publication after TSG SA approval (SA#100) 18.0.0 2023-09 SA#101 SP-230996 0001 3 F Updates to Procedure on Service experience 18.1.0 2023-09 SA#101 SP-230996 0002 F Adding missing A-ADRF API 18.1.0 2023-12 SA#102 SP-231544 0004 4 F Extend the edge performance analytics to support transmission quality analytics 18.2.0 2023-12 SA#102 SP-231544 0005 1 F Updates to Procedure on support for application performance analytics 18.2.0 2023-12 SA#102 SP-231544 0006 F Updates to Procedure on support for slice-specific application performance analytics 18.2.0 2023-12 SA#102 SP-231544 0007 2 F Updates to Procedure on support for UE-to-UE application performance analytics 18.2.0 2023-12 SA#102 SP-231544 0008 F Updates to Procedure on support for location accuracy analytics 18.2.0 2023-12 SA#102 SP-231544 0009 F Updates to Procedure for supporting service API analytics 18.2.0 2023-12 SA#102 SP-231544 0010 F Updates to Slice usage pattern analytics 18.2.0 2023-12 SA#102 SP-231544 0011 F Updates to Procedure for supporting edge load analytics 18.2.0 2023-12 SA#102 SP-231544 0012 3 F Clarification on parameter of the analytics request 18.2.0 2023-12 SA#102 SP-231544 0014 1 F Clarification and correction for edge load analytics 18.2.0 2024-03 SA#103 SP-240300 0015 F Correct edge load analytics 18.3.0 2024-03 SA#103 SP-240300 0016 F Correct registration 18.3.0 2024-03 SA#103 SP-240300 0020 1 F Updates to Application Performance Analytics and API 18.3.0 2024-03 SA#103 SP-240300 0021 2 F Updates to Slice-specific Application Performance Analytics and API 18.3.0 2024-03 SA#103 SP-240300 0022 2 F Updates to UE-to-UE Application Performance Analytics and API 18.3.0 2024-03 SA#103 SP-240300 0023 1 F Updates to Location Accuracy Analytics and API 18.3.0 2024-03 SA#103 SP-240300 0024 2 F Updates to Service API Analytics and API 18.3.0 2024-03 SA#103 SP-240300 0025 2 F Updates to Slice Usage Pattern Analytics and API 18.3.0 2024-03 SA#103 SP-240300 0026 1 F Updates to Edge Load Analytics and API 18.3.0 2024-03 SA#103 SP-240320 0019 3 F Fix the inconsistency of the A-ADRF 19.0.0 2024-06 SA#104 SP-240772 0030 2 B Edge computing preparation analytics 19.1.0 2024-06 SA#104 SP-240771 0031 2 B A-ADRF Service for Supporting Data Storage 19.1.0 2024-06 SA#104 SP-240771 0032 1 B A-DCCF Service for Supporting Data Collection 19.1.0 2024-06 SA#104 SP-240754 0033 1 A Addition of functional entities and reference points 19.1.0 2024-06 SA#104 SP-240766 0034 1 A Support for server-to-server performance analytics 19.1.0 2024-09 SA#105 SP-241211 0036 1 A Alignment with SA4 and CT1 19.2.0 2024-09 SA#105 SP-241220 0037 3 B Support of Collision Detection Analytics 19.2.0 2024-09 SA#105 SP-241220 0038 3 B Support of Location-related UE Group Analytics 19.2.0 2024-09 SA#105 SP-241212 0039 3 B Support of Application Layer AI/ML Member capability Analytics 19.2.0 2024-12 SA#106 SP-241717 0040 5 B UE RAT connectivity analytics for non terrestrial access 19.3.0 2024-12 SA#106 SP-241715 0043 1 B Architecture for supporting interactions with AIMLE 19.3.0 2024-12 SA#106 SP-241733 0044 1 B Support for VAL performance analytics for tethered UEs 19.3.0 2024-12 SA#106 SP-241718 0045 1 B Updates to Location Accuracy Analytics 19.3.0 2024-12 SA#106 SP-241715 0047 1 B Push service experience information 19.3.0 2024-12 SA#106 SP-241718 0048 1 B Updates to application performance analytics 19.3.0 2024-12 SA#106 SP-241718 0049 2 B Updates to edge load analytics 19.3.0 2024-12 SA#106 SP-241715 0050 1 B Updates to Application Layer AI/ML Member Capability Analytics 19.3.0 2024-12 SA#106 SP-241720 0051 1 B Resolves ENs for Collision Detection Analytics 19.3.0 2024-12 SA#106 SP-241718 0053 B Updates to Slice-specific Application Performance Analytics 19.3.0 2024-12 SA#106 SP-241718 0054 B Updates to UE-to-UE Application Performance Analytics 19.3.0 2024-12 SA#106 SP-241718 0055 1 B Updates to Service API Analytics 19.3.0 2024-12 SA#106 SP-241718 0056 1 B Updates to Slice Usage Pattern Analytics 19.3.0 2024-12 SA#106 SP-241718 0057 F Updates to Service Experience to Support Application Performance Analytics 19.3.0 2024-12 SA#106 SP-241718 0058 F Updates to A-ADRF Service on Analytics Storage 19.3.0 2024-12 SA#106 SP-241718 0059 D Updates to A-DCCF Service on Data Collection 19.3.0 2024-12 SA#106 SP-241715 0060 2 B Support for DN Energy Analytics 19.3.0 2024-12 SA#106 SP-241715 0061 1 B ML Model Performance Degradation Detection 19.3.0 |
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 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 3GPP TS 22.156 [2] and related use cases in 3GPP TR 22.856 [3].
|
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.
- 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.156: "Mobile Metaverse Services; Stage 1".
[3] 3GPP TR 22.856: "Feasibility Study on Localized Mobile Metaverse Services".
[4] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[5] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[6] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[7] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[8] 3GPP TS 26.119: "Media Capabilities for Augmented Reality".
|
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 with a spatial map. Each layer is uniquely identified by a layer Identifier. A spatial map layer may include layer-specific metadata, information pertaining to real-world objects, information on the area covered by the layer. A spatial map consumer may utilize the information contained within one or more layers associated with a spatial map, in conjunction with the spatial map media, to provide consumer-specific functionalities.
For the purposes of the present document, the following terms given in 3GPP TS 22.156 [2] apply:
Localization
Pose
Spatial Anchor (SAn)
Spatial Map (SM)
Spatial mapping service
Spatial localization service
|
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 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.
|
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 servers. The SEAL-S interface provides multiple service APIs towards Metaverse application server.
|
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 anchor in space (x, y and z coordinates).
Spatial map position (NOTE 1)
O
Position information based on spatial map. It includes the identifier of the Spatial map and the corresponding localization information or object ID.
> Spatial map ID
O
Identifier of the spatial map
>> Spatial map layer ID
O
Identifier of the spatial map layer if Spatial map ID is present
>> Localization (NOTE 2)
O
3D position and pose of the VAL UE
>> Object ID (NOTE 2)
O
Identifier of the object on which the spatial anchor is produced. The object can be stationary or trackable.
Application specific Spatial anchor 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 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.
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 group ID
O
Identifier of spatial anchor group that the spatial anchor associates with
Time period
O
Indicates time period or duration or time windows – comprising a start time and an expiry time. A spatial anchor is active during this time period. After the expiry time, the state of a spatial anchor becomes inactive. The time period may include one or more values (e.g. repeated over time/day).
Expiry handling indication
O
Indicates whether the spatial anchor has to be deleted or its state to be updated as inactive on expiry by the SAn server. Absence of this IE shall be considered that SAn server deletes the spatial anchor on expiry.
Spatial anchor state
O
Indicates the state of the spatial anchor (active or inactive). Spatial anchors in inactive state is not discoverable.Absence of this IE shall be considered as spatial anchor is in active state.
NOTE 1: One of the IEs shall be present.
NOTE 2: If Spatial map ID is present, either one of the IEs shall be present.
|
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 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
Spatial map media format
O
The media format of 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 contains the information as specified in Table 7.3.3.1-2.
Table 7.3.3.1-2 describes object information details for the spatial map information specified in the Table 7.3.3.1-1.
Table 7.3.3.1-2: Spatial map object information
Information element
Status
Description
Object ID
M
The identifier of the corresponding object
Object type
M
The type of object
Associated UE ID
O
Identifier of the UE associated with the object.
Object mobility information
M
Classifies whether the object is stationary or trackable.
> Object position
O
The 3D position of the object in the layer. For stationary object, this IE shall be present. For trackable object, 3D position of it shall be provided while it is being tracked, otherwise no value.
> Direction (NOTE)
O
Direction of the trackable object while it’s being tracked, otherwise no value.
> Velocity (NOTE)
O
Velocity of the trackable object while it’s being tracked, otherwise no value.
Object specific information
O
Object specific attribute information
NOTE: These IEs may be present when object is moving or changes it’s location frequently.
NOTE 1: Capability of SM server to distinguish whether object is stationary or trackable is outside the scope of this specification.
NOTE 2: For the current release, the object specific information is implementation specific and out of scope.
|
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 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.
> Mobility information
O
Indicates the mobility information of the SM data source.e.g., fixed, low or high mobility
NOTE: The definition of SM data types is application specific (e.g., VAL layer) for the current release.
|
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 associated with a UE when they are co-located for at least a certain period of time).
NOTE: The UE-object association information is used by the SEAL SM server to associate a UE with a mobile object such as a human user carrying a UE.
|
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. The Spatial Anchors service offers the capabilities to manage spatial anchors to the vertical application layer. The Spatial Anchors service functional model is based on SEAL layer as specified in 3GPP TS 23.434 [4].
The spatial anchors service 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.
|
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 the SSAn interface of the SAn server. The CAPIF can be used by VAL functions to discover the services of the SAn server.
|
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 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). The requestor may want to associate spatial anchor with the stationary or trackable object in the spatial map. For such cases, the request includes spatial map position with corresponding spatial map ID and object ID. If the request includes application specific spatial anchor information, that information remains opaque to the SAn server and can be stored with the spatial anchor. The request can indicate to create multiple spatial anchors. The requsted message may include one spatial anchor group ID allocated by requestor for each spatial anchor to be created, if the requestor has got an available spatial anchor group ID. If the spatial anchor group ID is not available, then the SAn server may create the spatial anchor group for the spatial anchors and associate the spatial anchor with the group.
NOTE 1: The application specific spatial anchor information is out of scope of standardization. For example, the application specific spatial anchor information can contain specific service information like a URL, a media data, a type, a manufacturing company, a date, a ratings, and customer premise information (e.g. a residence, office or shop) etc. Such information may be stored in key-value pair and is opaque to the SAn server.
NOTE 2: The spatial anchor group ID is available with the requestor through spatial anchor group creation or through mechanism which could be implementation specific.
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). If the request is to create spatial anchor on an object, then the SAn server can create it with spatial map position information included in the request. SAn server 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.
|
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 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 1)
O
The 3D geographic position of the spatial anchor in space (x, y and z coordinates).
>> Spatial map position (NOTE 1)
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) or object ID.
>>> Spatial map ID
O
Identifier of the spatial map
>>>> Spatial map layer ID
O
Identifier of the spatial map layer if Spatial map ID is present
>>>> Reference point
O
Reference point from where the spatial anchor is placed in the spatial map
>>>> Localization (NOTE 2)
O
3D position within spatial map and pose of the VAL UE
>>>> Object ID (NOTE 2)
O
Identifier of the object on which the spatial anchor will be created
> Application specific Spatial anchor 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.
> Associated name
O
Name of the product/service associated with the spatial anchor
> Time period
O
Indicates time period or duration or time windows – comprising a start time and an expiry time. A spatial anchor is active during this time period. After the expiry time, the state of a spatial anchor becomes inactive. The time period may include one or more values (e.g. repeated over time/day).
> Expiry handling indication
O
Indicates whether the spatial anchor has to be deleted or its state to be updated as inactive on expiry by the SAn server. Absence of this IE shall be considered that SAn server deletes the spatial anchor on expiry.
> Spatial anchor resource identifier
M
The identifier to associate the resource information with the created spatial anchors.
> Spatial anchor group ID
O
Identifier of spatial anchor group that the spatial anchor associates with
NOTE 1: One of the IEs shall be present.
NOTE 2: If Spatial map ID is present, either one of the IEs shall be present.
|
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
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.
>> Spatial anchor group ID
O
Identifier of spatial anchor group being associated with this spatial anchor.
Failure response
O
Indicates that the create spatial anchor request has failed.
> Cause
O
The cause for the request failure.
|
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 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.
|
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 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).
Time period
O
Indicates time period or duration or time windows – comprising a start time and an expiry time. A spatial anchor is active during this time period. After the expiry time, the state of a spatial anchor becomes inactive. The time period may include one or more values (e.g. repeated over time/day).
Spatial anchor state
O
Indicates the state of the spatial anchor (active or inactive). Spatial anchors in inactive state is not discoverable. Absence of this IE shall be considered as spatial anchor is in active state.
Expiry handling indication
O
Indicates whether the spatial anchor has to be deleted or its state to be updated as inactive on expiry by the SAn server. Absence of this IE shall be considered that SAn server deletes the spatial anchor on expiry.
> Application specific Spatial anchor 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.
|
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
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.
|
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. 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. If time period is present in the spatial anchor profile, the SAn server and SAn client shall monitor the time period and delete the locally stored spatial anchor information if the expiry handling indication in the profile is set to delete on expiry of the given time period.
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.
|
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.