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.14 Procedure for Collision Detection Analytics
8.14.1 General
8.14.2 Procedure
8.14.3 Information flows
...
...
8.14 Procedure for Collision Detection Analytics |R19| p. 79
8.14.1 General p. 79
This clause describes two procedures (covering both subscribe-notify and request-response models in clause 8.14.2.1 and 8.14.2.2 respectively) for supporting collision detection analytics, where the collision detection analytics are performed based on data collected from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server) and A-ADRF.
8.14.2 Procedure p. 80
8.14.2.1 Subscribe-notify model p. 80
Pre-conditions:
- Information about environment, e.g. static devices, are available from the 3rd party LM server.
- The location information about the UEs is available at SEAL LM server and/or LM client.
- The Ranging/Sidelink Positioning information exposure of the UEs is allowed at 5GC.
Step 1.
The analytics consumer (e.g. VAL Server, LM server, UAE server, UAS application specific server) sends collision detection analytics subscription request to ADAE server. The Analytics ID in the request message is set to "Collision detection analytics for target UE(s)" or "Collision detection analytics for any UEs". For analytics subscription request, the request contains message as defined in Table 8.14.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 data collection subscription request to the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party 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 of ranging and/or sidelink positioning related data or analytics of UEs, and location information of UEs. Data collection at the UE(s) reuses 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 ranging and/or sidelink positioning related data/analytics of UEs and location information of UEs from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server).
Step 7.
The ADAE server based on data collection request receive ranging and/or sidelink positioning related historical data of UEs from Data Producer (e.g. A-ADRF).
Step 8.
The ADAE server performs analytics relevant operations to generate the analytics for the collision detection between any target VAL UEs, collision detection between any UEs and target VAL UEs, or collision detection between any UE within the Area of Interest and based on the request provided in step 1 and the data/analytics received from the Data Producer (e.g. 5GC NFs (e.g. GMLC, NWDAF), ADAE Client, LM server, LM client, 3rd party LM server, A-ADRF for historical data).
Step 9.
The ADAE server sends collision detection analytics notifications to the consumer with the required collision detection analytics.
8.14.2.2 Request-response model p. 81
Pre-conditions:
- ADAE Server already have the analytics data derived from steps 3-6 in the procedure introduced in clause 8.14.2.1.
Step 1.
The analytics consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) sends a get collision detection analytics request message to the ADAE server to receive analytics data for collision detection analytics with Analytics ID in the request message setting to "Collision detection analytics for target UE(s)". The request contains message as defined in Table 8.14.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.14.2.1.
Step 4.
If the analytics consumer is authorized, the ADAE server sends a get collision detection analytics response message including the analytics data (statistical and/or predictive) of the collision detection analytics.
8.14.3 Information flows p. 82
8.14.3.1 General p. 82
The following information flows are specified for collision detection analytics based on clause 8.14.2.
8.14.3.2 Collision detection analytics subscription request p. 82
Table 8.14.3.2-1 describes the information flow from the consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) as a request or update request for the collision detection 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 "Collision Detection analytics for target UE(s)", "Collision Detection analytics for any UEs". |
| 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. |
| > Filter for Collision between any UE(s) and target UE(s) | O
(NOTE 2) | The filter informaiton for the Collision Detection analytics for target UE(s). |
| >> Target UE(s) | O | The UE(s) for which the analytics subscription applies. |
| >> Any UE(s) | O | The list of any UE(s) collision with that shall be analysed. |
| >> Target VAL server ID | O | If consumer is different from the VAL server, this identifier shows the target VAL server for which the analytics subscription applies. |
| >> Area of Interest | O | The geographical or service area for which the subscription request applies. |
| > Filter for Collision detection between any UE(s) | O
(NOTE 2) | The filter information for the Collision Detection analytics for any UE(s) in an area. |
| >> Target VAL server ID | O | If consumer is different from the VAL server, this identifier shows the target VAL server for which the analytics subscription applies. |
| >> Area of Interest | O | The geographical or service area for which the subscription request applies. |
| Collision detection creteria | O | The parameters for collision detection analytics apply. |
| > Distance | O | The allowed minimum distance between UEs. The collision is detected if the distance between the UEs is less than the provided value. |
| 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.14.3.3 Collision detection analytics subscription response p. 83
Table 8.14.3.3-1 describes the information elements for the collision detection 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.14.3.4 Collision detection analytics notification p. 83
Table 8.14.3.4-1 describes the information flow from the ADAES to the consumer (e.g. VAL Server, LM Server, UAE server, UAS application specific server) as a response for the collision detection analytics.
| Information element | Status | Description |
|---|---|---|
| Analytics ID | M | The identifier of the analytics event. This ID can be for example "Collision Detection analytics for target UE(s)", "Collision Detection analytics for any UEs". |
| Outputs | O | The reported analytics for the collision detection analytics. |
| > VAL UE IDs | M | The VAL UE identifiers for which the analytics outputs apply. |
| >> Time of potential collisions | M | Time of the potential collisions between the UEs. |
| >> Location of potential collisions | M | Location of the potential collisions between the UEs. |
| >> Direction of moving | O | Direction of the UEs moving. |
| >> Velocity of moving | O | Velocity of the UEs moving. |
| Confidence level | O | For predictive analytics, the achieved confidence level can be provided. |
8.14.3.5 Ranging/SL positioning data and location information collection subscription request p. 83
Table 8.14.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, LM client, 3rd party 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. |
| 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.14.3.6 Ranging/SL positioning data and location information collection subscription response p. 84
Table 8.14.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, LM client, 3rd party LM server, A-ADRF for historical data.
| Information element | Status | Description |
|---|---|---|
| Result | M | The result of the Ranging/SL positioning data and location information collection subscription request (positive or negative acknowledgement). |
8.14.3.7 Data Notification p. 84
Table 8.14.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. |
| 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 ranging/sidelink positioning information of UEs, location information of UEs (moving devices like UAS devices, V2X devices, robots, and/or people with UE), and the location information about environment (static devices like infrastructures) for a given time and area of interest, Relative Proximity analytics. |
8.14.3.8 Get analytics data request p. 84
Table 8.14.3.8-1 describes information elements for the collision detection analytics request from the analytics consumer to the ADAE server.
| Information element | Status | Description |
|---|---|---|
| Requestor ID | M | The identifier of the consumer. |
| Analytics ID | O | The identifier of the analytics event. This ID can be for example "Collision Detection analytics for target UE(s)". |
| 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. |
| > Target VAL UE ID(s) | O | The VAL UE(s) for which the analytics subscription applies. |
| > Target VAL server ID | O | If consumer is different from the VAL server, this identifier shows the target VAL server for which the analytics subscription applies. |
| > Area of Interest | O | The geographical or service area for which the subscription request applies. |
| Collision detection criteria | O | The parameters for collision detection analytics apply. |
| > Distance | O | The allowed minimum distance between UEs. |
| Preferred confidence level | O | The level of accuracy for the analytics service (in case of prediction). |
8.14.3.9 Get analytics data response p. 85
Table 8.14.3.9-1 describes information elements for the Get collision detection analytics response from the ADAE server to the consumer.
| Information element | Status | Description |
|---|---|---|
| Analytics ID | O | The identifier of the analytics event. This ID can be for example "Collision Detection analytics". |
| Outputs | O | The reported analytics for the collision detection analytics. |
| > VAL UE IDs | M | The VAL UE identifiers for which the analytics outputs apply. |
| >> Time of potential collisions | M | Time of the potential collisions between the UEs. |
| >> Location of potential collisions | M | Location of the potential collisions between the UEs. |
| >> Direction of moving | O | Direction of the UEs moving. |
| >> Velocity of moving | O | Velocity of the UEs moving. |
| >> Timestamp | O | Time stamp of the collected analytics data. |
| Confidence level | O | For predictive analytics, the achieved confidence level can be provided. |
