hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.9.3 Notify
|
API operation name: edge_analytics_notify
Description: The consumer is notified by ADAES on the edge load analytics.
Inputs: -
Outputs: See clause 8.8.3.7.
See clause 8.8.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.9.4 Get
|
API operation name: edge_analytics_get
Description: The consumer requests edge analytics data.
Inputs: See clause 8.8.3.8.
Outputs: See clause 8.8.3.9.
See clause 8.8.2.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.10 SS_ ADAE_slice_usage_stats
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.10.1 General
|
API description: This API enables the Consumer to communicate with the ADAE server for requesting and receiving slice usage statistical data.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.10.2 Get
|
API operation name: slice_usage_stats_get
Description: The consumer requests and receives slice usage statistics from ADAE server.
Inputs: See clause 8.7.4.7.
Outputs: See clause 8.7.4.8.
See clause 8.7.3 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.11 SS_ADAE_edge_preparation_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.11.1 General
|
API description: This API enables the analytics consumer (e.g., the VAL server, ECS, EES) to communicate with the ADAE server for requesting or subscribing to edge computing preparation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.11.2 Subscribe
|
API operation name: edge_preparation_analytics_subscribe
Description: The consumer subscribes for edge computing preparation analytics.
Inputs: See clause 8.11.3.2.
Outputs: See clause 8.11.3.3.
See clause 8.11.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.11.3 Notify
|
API operation name: edge_preparation_analytics_notify
Description: The consumer is notified by the ADAE server on the edge computing preparation analytics.
Inputs: -
Outputs: See clause 8.11.3.4.
See clause 8.112.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.11.4 Get
|
API operation name: edge_preparation_analytics_get
Description: The consumer requests edge computing preparation analytics
Inputs: -See clause 8.11.3.7
Outputs: See clause 8.11.3.8.
See clause 8.11.2.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.12 SS_ADAE_server-to-server_performance_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.12.1 General
|
API description: This API enables the analytics consumer (e.g., the VAL server, EES) to communicate with the ADAE server for requesting or subscribing to server-to-server performance analytics.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.12.2 Subscribe
|
API operation name: server-to-server_performance_analytics_subscribe
Description: The consumer subscribes to the ADAE server for Server-to-server performance analytics.
Inputs: See clause 8.13.3.2.
Outputs: See clause 8.13.3.3.
See clause 8.13.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.12.3 Notify
|
API operation name: server-to-server_performance_analytics_notify
Description: The consumer is notified by the ADAE server on the Server-to-server performance analytics.
Inputs: -
Outputs: See clause 8.13.3.4.
See clause 8.13.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.13 SS_ADAE_collision_detection_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.13.1 General
|
API description: This API enables the analytics consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) to communicate with the ADAE server for requesting or subscribing to collision detection analytics.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.13.2 Subscribe
|
API operation name: collision_detection_analytics_subscribe
Description: The consumer subscribes for collision detection analytics.
Inputs: See clause 8.14.3.2.
Outputs: See clause 8.14.3.3.
See clause 8.14.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.13.3 Notify
|
API operation name: collision_detection_analytics_notify
Description: The consumer is notified by the ADAE server on collision detection analytics.
Inputs: -
Outputs: See clause 8.14.3.4.
See clause 8.14.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.13.4 Get
|
API operation name: collision_detection_analytics_get
Description: The consumer requests collision detection analytics.
Inputs: See clause 8.14.3.8.
Outputs: See clause 8.14.3.9.
See clause 8.14.2.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.14 SS_ADAE_location-related_UE_group_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.14.1 General
|
API description: This API enables the analytics consumer (e.g. LMS) to communicate with the ADAE server for requesting or subscribing to location-related UE group analytics.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.14.2 Subscribe
|
API operation name: location-related_UE_group_analytics_subscribe
Description: The consumer subscribes for location-related UE group analytics.
Inputs: See clause 8.15.3.2.
Outputs: See clause 8.15.3.3.2.
See clause 8.15.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.14.3 Notify
|
API operation name: location-related_UE_group_analytics_notify
Description: The consumer is notified by the ADAE server on location-related UE group analytics.
Inputs: -
Outputs: See clause 8.15.3.4.
See clause 8.15.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.14.4 Get
|
API operation name: location-related_UE_group_analytics_get
Description: The consumer requests location-related UE group analytics.
Inputs: -See clause 8.15.3.8
Outputs: See clause 8.15.3.9.
See clause 8.15.2.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.15 SS_ADAE_AIML_member_capability_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.15.1 General
|
API description: This API enables the analytics consumer (e.g. VAL Server, AIMLE Server) to communicate with the ADAE server for requesting or subscribing to application layer AIML member capability analytics.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.15.2 Subscribe
|
API operation name: AIML_member_capability_analytics_subscribe
Description: The consumer subscribes for application layer AIML member capability analytics.
Inputs: See clause 8.16.3.2.
Outputs: See clause 8.16.3.3.
See clause 8.16.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.15.3 Notify
|
API operation name: AIML_member_capability_analytics_notify
Description: The consumer is notified by the ADAE server on application layer AIML member capability analytics.
Inputs: -
Outputs: See clause 8.16.3.4.
See clause 8.16.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.15.4 Get
|
API operation name: AIML_member_capability_analytics_get
Description: The consumer requests application layer AIML member capability analytics.
Inputs: -See clause 8.16.3.8
Outputs: See clause 8.16.3.9.
See clause 8.16.2.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.16 SS_ ADAE_ServiceExp API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.16.1 General
|
API description: This API enables the ADAE client share service experience information to ADAE server.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.16.2 Request
|
API operation name: SS_ ADAE_ServiceExp_Request
Description: The consumer sends application service experience report to the server.
Inputs: See clause 8.9.3.1.
Outputs: See clause 8.9.3.2
See clause 8.9.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.17 SS_ ADAE_DN_energy_analytics API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.17.1 General
|
API description: This API enables the VAL server to communicate with the ADAE server for requesting for DN energy efficiency/consumption analytics.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.2.17.2 Get DN_energy_analytics
|
API operation name: DN_energy_analytics_get
Description: The consumer requests DN energy efficiency/consumption analytics.
Inputs: See clause 8.18.3.2.
Outputs: See clause 8.18.3.3.
See clause 8.18.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3 A-ADRF APIs
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.1 General
|
This clause provides the APIs provided by A-ADRF.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.2 A-ADRF APIs
|
Table 9.3.2-1 illustrates the A-ADRF APIs.
Table 9.3.2-1: List of A-ADRF APIs
API Name
API Operations
Known Consumer(s)
Communication Type
SS_AADRF_Data_Collection
Subscribe
ADAES
Subscribe / Notify
Notify
SS_ AADRF_Historical_ServiceAPI_Logs
Get
ADAES
Request / Response
SS_AADRF_NetworkSlice_Data
Get
ADAES
Request / Response
SS_AADRF_Location_Accuracy_Data
Get
ADAES
Request / Response
SS_AADRF_EdgeData_Collection
Subscribe
ADAES
Subscribe / Notify
Notify
ADAES
SS_AADRF_Edge_Preparation_Data
Get
ADAES
Request / Response
SS_AADRF_Data_Storage
Request Subscription
ADAE server, A-DCCF
Request / Response
Store Data
ADAE server
Request / Response
SS_AADRF_ServerToServer_Analytics
Get
ADAES
Request / Response
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.3 SS_AADRF_Data_Collection API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.3.1 General
|
API description: This API enables the ADAE server to communicate with the A-ADRF for subscribing for offline data collection and for getting notified about the offline data/statistics.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.3.2 Subscribe
|
API operation name: Data_Collection_Subscribe
Description: The consumer subscribes for offline data from A-ADRF.
Inputs: See clause 8.2.4.4.
Outputs: See clause 8.2.4.5.
See clause 8.2.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.3.3 Notify
|
API operation name: Data_Collection_Notify
Description: The consumer is receiving the offline data from A-ADRF as notification, based on subscription.
Inputs: -
Outputs: See clause 8.2.4.6.
See clause 8.2.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.4 SS_ AADRF_Historical_serviceAPI_logs API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.4.1 General
|
API description: This API enables the ADAE server to communicate with the A-ADRF for requesting service API logs and receiving the offline data/statistics on API logs.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.4.2 Get
|
API operation name: Historical_ServiceAPI_Logs_Get
Description: The consumer requests API logs from A-ADRF.
Inputs: See clause 8.6.3.4.
Outputs: See clause 8.6.3.5.
See clause 8.6.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.5 SS_ AADRF_NetworkSlice_data API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.5.1 General
|
API description: This API enables the ADAE server to communicate with the A-ADRF for requesting and receiving network slice data.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.5.2 Get
|
API operation name: NetworkSlice_Data_Get
Description: The consumer requests network slice data from A-ADRF.
Inputs: See clause 8.7.3.5.
Outputs: See clause 8.7.3.6.
See clause 8.7.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.6 SS_AADRF_EdgeData_Collection API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.6.1 General
|
API description: This API enables the ADAE server to communicate with the A-ADRF for subscribing for edge data collection and for getting notified about the offline data/statistics for the EDN and/or EAS/EES.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.6.2 Subscribe
|
API operation name: EdgeData_Collection_Subscribe
Description: The consumer subscribes for offline edge data from A-ADRF.
Inputs: See clause 8.8.3.4.
Outputs: See clause 8.8.3.5.
See clause 8.8.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.6.3 Notify
|
API operation name: EdgeData_Collection_Notify
Description: The consumer is receiving the offline edge data from A-ADRF as notification, based on subscription.
Inputs: -
Outputs: See clause 8.8.3.6.
See clause 8.8.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.7 SS_AADRF_Location_Accuracy API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.7.1 General
|
API description: This API enables the ADAE server to communicate with the A-ADRF to request location analytics/data for VAL UEs or VAL service area.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.7.2 Get
|
API operation name: Location_Accuracy_Data_Get
Description: The consumer is receiving offline location analytics/data from A-ADRF.
Inputs: See clause 8.5.3.4.
Outputs: See clause 8.5.3.5.
See clause 8.5.2 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.8 SS_AADRF_Edge_Preparation_Data API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.8.1 General
|
API description: This API enables the ADAE server to communicate with the A-ADRF to request edge computing preparation data for the EAS, EES, and/or ECS.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.8.2 Get
|
API operation name: edge_preparation_data_get
Description: The consumer is receiving offline edge computing preparation data from the A-ADRF.
Inputs: See clause 8.11.3.5.
Outputs: See clause 8.11.3.6.
See clause 8.11.2.1 for details of usage of this operation.
|
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.9 SS_AADRF_Data_Storage API
| |
20479eb37624e17cc85fa37e0dbf82f7
|
23.436
|
9.3.9.1 General
|
API description: This API enables the ADAE server or the A-DCCF to request the A-ADRF to initiate a subscription for data or analytics. Data or analytics provided in notifications as a result of the subsequent subscription by the A-ADRF are stored in the A-ADRF. This API also enables the consumer to request the A-ADRF to store data or analytics from ADAE server or A-DCCF.
|
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
|
200a67263e13f9f0a665c785e9573ee5
|
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].
|
200a67263e13f9f0a665c785e9573ee5
|
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".
|
200a67263e13f9f0a665c785e9573ee5
|
23.437
|
3 Definitions of terms, symbols and abbreviations
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.