Content for TS 23.436 Word version: 19.2.0
0…
5…
6…
8…
8.3…
8.4…
8.5…
8.6…
8.7…
8.8…
8.9…
8.10…
8.11…
8.12…
8.13…
8.14…
8.15…
8.16…
9…
9.3…
9.4…
A…
8.15 Procedure for Location-related UE Group Analytics
8.15.1 General
8.15.2 Procedure
8.15.3 Information flows
...
...
8.15 Procedure for Location-related UE Group Analytics |R19| p. 85
8.15.1 General p. 85
This clause describes two procedures (covering both subscribe-notify and request-response models in clause 8.15.2.1 and 8.15.2.2 respectively) for supporting location-related UE group analytics, where the location-related UE group analytics are performed based on data collected from the Data Producer (e.g. 5GC NFs (e.g. GMLC (via NEF), NWDAF), ADAE Client, LM server) and A-ADRF.
8.15.2 Procedure p. 86
8.15.2.1 Subscribe-notify model p. 86
Pre-conditions:
- The location information about the UEs is available at SEAL LM server.
- The location information of the UEs exposure is allowed at 5GC.
Step 1.
The analytics consumer (i.e. LMS) sends location-related UE group analytics subscription request to ADAE server. The Analytics ID in the request message is set to "UE group route analytics" or "UE group member deviation". For analytics subscription request, the request contains message as defined in Table 8.15.3.2-1.
Step 2.
Upon receiving the event subscription request from the consumer, the ADAE server checks for the relevant authorization for the event subscription. If the authorization is successful, the ADAE server stores the request information. The ADAE server sends a service API event subscription response indicating successful subscription.
Step 3.
The ADAES maps the analytics event ID to a list of data collection event identifiers, and a list of data producer IDs. Such mapping may be preconfigured by OAM or may be determined by ADAES based on the analytics event type/vertical type and/or data producer profile.
Step 4.
The ADAE server sends a data collection subscription request to the Data Producer (e.g. 5GC NFs (e.g. GMLC (via NEF), NWDAF), ADAE Client, LM server) and a data collection request to the Data Producer (e.g. A-ADRF for historical data) with the respective Data Collection Event ID and the requirement for collection location related data/analytics of UEs. Data collection at the UE(s) reuses the mechanism defined in TS 26.531.
Step 5.
The Data Producer sends data collection subscription response as a positive or negative acknowledgement to the ADAE server.
Step 6.
The ADAE server based on data collection subscription receive location related data/analytics of UEs from the Data Producer (e.g. 5GC NFs (e.g. GMLC (via NEF), NWDAF), ADAE Client, LM server).
Step 7.
The ADAE server based on data collection request receive location related historial data of UEs from the Data Producer (e.g. A-ADRF).
Step 8.
The ADAE server performs analytics relevant operations to generate the analytics based on the data received from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data). In detail, the ADAE server may generate analytics in the following ways.
Step 9.
- For UE group route analytics: Inputs include the location information of UE(s) from LM server (e.g. UE's location in clause 9.3.7 of TS 23.434), the analytics from NWDAF (e.g. UE mobility analytics, Movement behaviour analytics, UE communication analytics, and/or Dispersion analytics in TS 23.288). For example, UE's location service from LMS allows ADAES to obtain the UE location, UE mobility analytics provides potential moving direction of the UE(s), Dispersion analytics gives ADAES information on UE data volume dispersion predictions, etc., by combining all the information collected, predictions on UE group route can be generated.
- For UE group member deviation analytics: Inputs include the Ranging/Sidelink Positioning location information of the UE group member from GMLC (via NEF) (e.g. Ranging/Sidelink Positioning location results in clause 6.20 of TS 23.273), location information of the UE group member from LM server (e.g. UE's location in clause 9.3.7 of TS 23.434), and the analytics from NWDAF (e.g. UE mobility analytics, Movement behaviour analytics, Relative Proximity analytics, and/or Abnormal behaviour analytics in TS 23.288) of this UE group member. The ADAE server can aggregate the collected information (e.g. distance between UEs from the Ranging/Sidelink Positioning location information service, predictions on distance between UEs from the Relative Proximity analytics, etc.) and derive which UE group member is deviating (or will deviate) from other group member(s) or target group member (e.g. UE's ranging information with any other UE(s) in a group is larger than a threshold, and such trend shows longer and longer ranging within a time period, or the UE moving direction is different from any other UE(s) in a group or target group member).
The ADAE server sends location-related UE group analytics notifications to the consumer with the required location-related UE group analytics.
8.15.2.2 Request-response model p. 87
Pre-conditions:
- ADAE Server already has the analytics data derived from steps 3-6 in the procedure introduced in clause 8.15.2.1.
Step 1.
The analytics consumer (i.e. LMS) sends a get location-related UE group analytics request message to the ADAE server to receive analytics data for location-related UE group analytics with Analytics ID in the request message setting to "UE group route analytics" or "UE group member deviation". The request contains message as defined in Table 8.15.3.8-1.
Step 2.
Upon receiving the request, the ADAE server authenticates and authorizes the analytics consumer.
Step 3.
If the analytics consumer is authorized, the ADAE server may get the analytics by performing steps 3 to 8 of clause 8.15.2.1.
Step 4.
If the analytics consumer is authorized, the ADAE server sends a get location-related UE group analytics response message including the analytics data (statistical and/or predictive) of the location-related UE group analytics.
8.15.3 Information flows p. 88
8.15.3.1 General p. 88
The following information flows are specified for location-related UE group analytics based on clause 8.15.2.
8.15.3.2 Location-related UE group analytics subscription request p. 88
Table 8.15.3.2-1 describes the information flow from the consumer (LMS) as a request or update request for the location-related UE group analytics.
| Information element | Status | Description |
|---|---|---|
| Requestor ID | M
(NOTE 1) | The identifier of the consumer. |
| Analytics ID | O
(NOTE 1) | The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics". |
| Analytics type | M | The type of analytics for the event, e.g. statistics or predictions. |
| Analytics filter information | M | Filter information for the analytics event. |
| > Application Group ID | O
(NOTE 2) | Application group identifier for which the analytics subscription applies. |
| > Target VAL UE ID(s) | O
(NOTE 2) | The identifier(s) of the VAL UE(s) for which the analytics subscription applies. |
| > Area of Interest | O | The geographical or service area for which the subscription request applies. |
| > Application Group profile(s) | O | Information about the Application Group(s) with common EAS (as defined in TS 23.558 Table 8.15.11-1). |
| > Deviation | O | Deviation information, e.g. different moving direction or moving speed, distance with the target group member UE larger than an threshold. |
| >> Target Group member UE ID | O | The identifier of the target group member UE. |
| >> Deviation criteria | O | The criteria used for detecting deviation of group member UE, e.g. distance, moving direction, moving speed. |
| 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. |
| Preferred confidence level | O | The level of accuracy for the analytics service (in case of prediction). |
| Time validity | O | The time validity of the subscription request. |
|
NOTE 1:
This information element shall not be updated.
NOTE 2:
One of the elements shall be provided.
|
||
8.15.3.3 Location-related UE group analytics subscription response p. 89
Table 8.15.3.3-1 describes the information elements for the location-related UE group analytics subscription response from the ADAE server to the consumer.
| Information element | Status | Description |
|---|---|---|
| Result | M | The result of the analytics subscription request (positive or negative acknowledgement). |
8.15.3.4 Location-related UE group analytics notification p. 89
Table 8.15.3.4-1 describes the information flow from the ADAES to the consumer (LM Server) as a response for the location-related UE group analytics.
| Information element | Status | Description |
|---|---|---|
| Analytics ID | M | The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics". |
| Outputs for UE group route | O
(NOTE 1) | The reported analytics for UE group route analytics apply. |
| > List of EAS ID(s) | M | List of identifiers of EAS. |
| >> EAS ID(s) | O | Identifier(s) of EAS(s). |
| >> Route ID | M | The identifier of the common route for the UE(s) to EAS(s). |
| >> VAL UE ID(s) | M | The identifiers of the VAL UE(s) which with the common route to the EAS(s). |
| Outputs for UE group member deviation | O
(NOTE 1, NOTE 2) | The reported analytics for group member deviation analytics apply. |
| > Application Group ID | M | Application group identifier. |
| >> Target Group member UE ID | O | The identifier of the target group member UE. |
| > List of VAL UE ID(s) | M | The VAL UE(s) which with different behaviour with the majority group members or the target group member. |
| >> VAL UE ID | O | Identifier of the VAL UE. |
| >> Deviation | O | Detail information of deviation for the VAL UE, e.g., different moving direction or moving speed, distance with the target group member. |
| >> Time duration | O | The time duration of this UE deviation. |
| Validity Time | O | The valid time duration of the analytics. |
| Confidence level | O | For predictive analytics, the achieved confidence level can be provided. |
|
NOTE 1:
One of these shall be present based on the analytics event.
NOTE 2:
Statistics on UE deviation including e.g. minimum, maximum, and average UEs moving into area, moving out of area, moving speed, and distance from target group member.
|
||
8.15.3.5 Location information collection subscription request p. 90
Table 8.15.3.5-1 describes information elements for the Ranging/SL positioning data and location information collection subscription request from the ADAE server to the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data.
| Information element | Status | Description |
|---|---|---|
| Requestor ID | M | The identifier of the consumer. |
| Data Collection Event ID | M | The identifier of the data collection event. |
| Data Collection requirements | M | The requirements for data collection, including the format of data, frequency of reporting, level of abstraction of data, level of accuracy of data. |
| Analytics ID | O | The identifier of the analytics event, for which the data collection is needed. This ID can be for example "UE group route analytics" or "UE group member deviation analytics". |
| List of Data Producer IDs | O | In case when this request is performed via A-DCCF, then the list of Data Producer IDs is needed. |
| > Target data producer profile criteria | O | Characteristics of the data producers to be used. |
| > VAL UE IDs | O | The VAL UE(s) identifiers for which the data/analytics apply. |
| Area of Interest | O | The geographical or service area for which the requirement request applies. |
| Time validity | O | The time validity of the request. |
8.15.3.6 Location information collection subscription response p. 91
Table 8.15.3.6-1 describes information elements for the Data collection subscription response from the Data Producer, e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, A-ADRF for historical data.
| Information element | Status | Description |
|---|---|---|
| Result | M | The result of the location information collection subscription request (positive or negative acknowledgement). |
8.15.3.7 Data Notification p. 91
Table 8.15.3.7-1 describes information elements for the Data Notification from the Data Producer to the ADAE server.
| Information element | Status | Description |
|---|---|---|
| Data Collection Event ID | M | The identifier of the data collection event. |
| Data Producer ID | M | The identity of Data Producer. |
| Analytics ID | O | The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics". |
| Data Type | M | The type of reported data samples which can be network data, application data, edge data, or different granularities / abstraction of data (e.g. real time, non-real time). This also indicates whether data are offline (from A-ADRF or not). |
| Data Output | M | The reported data, which can be inform of measurements or offline/historical data on the requested parameter based on subscription. Such data can be location information of UEs (moving devices like UAS devices, V2X devices, robots, and/or people with UE, static devices like infrastructures) for a given time and area of interest, measurement of UE(s) moving in or moving out of the area of interest, UE mobility analytics, Ranging/Sidelink Positioning location information of UEs, Movement behaviour analytics, UE communication analytics, Dispersion analytics, Relative Proximity analytics, and/or Abnormal behaviour analytics. |
8.15.3.8 Get analytics data request p. 91
Table 8.15.3.8-1 describes information elements for the location-related UE group analytics request from the analytics consumer to the ADAE server.
| Information element | Status | Description |
|---|---|---|
| Requestor ID | M | The identifier of the consumer. |
| Analytics ID | M | The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics". |
| Analytics type | M | The type of analytics for the event, e.g. statistics or predictions. |
| Analytics filter information | M | Filter information for the analytics event. |
| > Application Group ID | O
(NOTE) | Application group identifier for which the analytics subscription applies. |
| > Target VAL UE ID(s) | O
(NOTE) | The identifier(s) of the VAL UE(s) for which the analytics subscription applies. |
| > Area of Interest | O | The geographical or service area for which the subscription request applies. |
| > Application Group profile(s) | O | Information about the Application Group(s) with common EAS (as defined in TS 23.558 Table 8.15.11-1). |
| > Deviation | O | Deviation information, e.g. different moving direction or moving speed, distance with the target group member UE larger than a threshold. |
| >> Target Group member UE ID | O | The identifier of the target group member UE. |
| >> Deviation criteria | O | The criteria used for detecting deviation of group member UE, e.g. distance, moving direction, moving speed. |
| Preferred confidence level | O | The level of accuracy for the analytics service (in case of prediction). |
|
NOTE:
One of elements shall be provided.
|
||
8.15.3.9 Get analytics data response p. 92
Table 8.15.3.9-1 describes information elements for the Get location-related UE group analytics response from the ADAE server to the consumer.
| Information element | Status | Description |
|---|---|---|
| Analytics ID | M | The identifier of the analytics event. This ID can be for example "UE group route analytics" or "UE group member deviation analytics". |
| Outputs for UE group route | O
(NOTE 1) | The reported analytics for UE group route analytics apply. |
| > List of EAS ID(s) | M | List of identifiers of EAS. |
| >> EAS ID(s) | O | Identifier(s) of EAS(s). |
| >> Route ID | M | The identifier of the common route for the UE(s) to EAS(s). |
| >> VAL UE ID(s) | M | The identifiers of the VAL UE(s) which with the common route to the EAS(s). |
| > Timestamp | O | Time stamp of the collected analytics data. |
| Outputs for UE group member deviation | O
(NOTE 1, NOTE 2) | The reported analytics for group member deviation analytics apply. |
| > Application Group ID | M | Application group identifier. |
| >> Target Group member UE ID | O | The identifier of the target group member UE. |
| > List of VAL UE ID(s) | M | The VAL UE(s) which with different behaviour with the majority group members or the target group member. |
| >> VAL UE ID | O | Identifier of the VAL UE. |
| >> Deviation | O | Detail information of deviation for the VAL UE, e.g., different moving direction or moving speed, distance with the target group member. |
| >> Time duration | O | The time duration of this UE deviation. |
| > Timestamp | O | Time stamp of the collected analytics data. |
| Validity Time | O | The valid time duration of the analytics. |
| Confidence level | O | For predictive analytics, the achieved confidence level can be provided. |
|
NOTE 1:
One of these shall be present based on the analytics event.
NOTE 2:
Statistics on UE deviation including e.g. minimum, maximum, and average UEs moving into area, moving out of area, moving speed, and distance from target group member.
|
||
