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.
Figure 10.2.2-1 illustrates the procedure for UE RAT connectivity analytics.
Pre-conditions:
-
The ADAES is registered and capable of interacting with 5GS to UE mobility analytics.
Step 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.
Step 2.
The ADAE server sends a UE RAT connectivity analytics subscription response as an ACK to the VAL server.
Step 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
clause 9.3.5 of TS 23.434.
Step 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
clause 6.7.2 of TS 23.288.
Step 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.
Step 6.
The ADAE server optionally requests UE RAT connectivity historical analytics/data from A-ADRF for the corresponding VAL UEs.
Step 7.
Based on the request, the ADAE server receives UE RAT connectivity historical analytics/data from A-ADRF for the corresponding VAL UEs.
Step 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.
Step 9.
The ADAE server sends the UE RAT connectivity analytics notification to the consumer.
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.
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. |
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.
Information element |
Status |
Description |
Result | M | The result of the analytics subscription request (positive or negative acknowledgement). |
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.
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. |
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.
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. |
Table 10.2.3.5-1 describes information elements for the UE RAT connectivity analytics notification from the A-ADRF to the ADAE server.
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. |