Content for TS 23.255 Word version: 19.3.0
7.5 Real-Time UAV Connection Status Monitoring and Location reporting
7.5.1 General
7.5.2 Procedures
7.5.2.1 Procedure for real-time UAV network connection status monitoring and location update
7.5.2.2 Subscription for real-time UAV status information
7.5.2.3 Notification of real-time UAV status information
7.5.2.4 Unsubscription for real-time UAV status information
7.5.3 Information flows
7.5.3.1 Information flows between UAE server and SEAL servers
7.5.3.2 Subscribe real-time UAV status information request
7.5.3.3 Subscribe real-time UAV status information response
7.5.3.4 Notify real-time UAV status information
7.5.3.5 Unsubscribe real-time UAV status information request
7.5.3.6 Unsubscribe real-time UAV status information response
...
...
7.5 Real-Time UAV Connection Status Monitoring and Location reporting p. 48
7.5.1 General p. 48
This clause enables the UAE server to provide a real-time view of UAV network status and location reporting based on current network connection status, in particular with the supporting of following use cases:
- Support of real-time monitor the 3GPP network connection with UAVs.
- Support of reporting of loss of communication with UAVs.
- Support of location reporting such as last known location after loss of communication.
7.5.2 Procedures p. 48
7.5.2.1 Procedure for real-time UAV network connection status monitoring and location update p. 48
Figure 7.5.2.1-1 illustrates the real-time network monitoring and location update support for UAV operations.
Pre-conditions:
- UAE server has subscribed to the monitoring event API for connection monitoring by the NRM server for both UAV and/or UAV client as specified in clause 14.3.6.2.2 of TS 23.434.
- UAE server has subscribed for the location information and location deviation monitoring events of UAV from LM server as per the clause 9.3.7 and clause 9.3.11.2 specified in TS 23.434.
- Subscription for real-time UAV status information is performed as specified in clause 7.5.2.2.
Step 1.
The UAE server receives location report and location deviation monitoring event notifications from LM server as specified in clause 9.3.8 and clause 9.3.11.2 of TS 23.434. UAE server shall record the current location reporting timestamp as specified in clause 9.3.2.2 of TS 23.434.
Step 2.
The UAE server receives monitoring events notification as specified in clause 14.3.6.3.2 of TS 23.434. If events are regarding loss of UE reachability such as when received "Loss_of_connectivity_notification", the UAE server shall record such event with current timestamp.
Step 3.
NRM server sends notification when UE re-connected status is detected as specified in clause 14.3.6.3.2 of TS 23.434.
Step 4.
The UAE server shall record such event with current timestamp, plus with last known location information and timestamp as specified in clause 9.3.2.7 of TS 23.434 and trigger location update as specified in clause 9.3.4 of TS 23.434.
7.5.2.2 Subscription for real-time UAV status information p. 49
Figure 7.5.2.2-1 describes the procedure for subscription for real-time UAV status information.
Pre-condition:
- UAS application specific server has been provisioned with UAE server information.
Step 1.
The UAE application specific server sends subscribe real-time UAV status information request to the UAE server. The request includes one or more UAV ID(s).
Step 2.
The UAE server stores the subscription information.
Step 3.
The UAE server sends subscription response to the UAS application specific server.
7.5.2.3 Notification of real-time UAV status information p. 49
Pre-conditions:
- UAS application specific server has performed subscription as per procedure in clause 7.5.2.2 with UAE server and the procedure for processing real-time UAV status as specified in clause 7.5.2.1 has performed.
Step 1.
When real-time UAV status information is available at the UAE as per the subscription then, the UAE server sends notification of one or more real-time UAV(s) status information to the UAS application specific server.
7.5.2.4 Unsubscription for real-time UAV status information p. 50
Figure 7.5.2.4-1 describes the procedure for unsubscription for real-time UAV status information.
Pre-condition:
- UAS application specific server has performed the subscription procedure as specified in clause 7.5.2.2.
Step 1.
The UAE application specific server sends unsubscribe real-time UAV status information request to the UAE server. The request includes the subscription ID.
Step 2.
The UAE server cancels the subscription information.
Step 3.
The UAE server sends unsubscription response to the UAS application specific server.
7.5.3 Information flows p. 50
7.5.3.1 Information flows between UAE server and SEAL servers p. 50
The usage of information flows between UAE server and SEAL's Location Management Server is specified in clause 7.1.3.2.
The usage of information flows between UAE server and SEAL's Network Resource Management Server is specified in clause 7.1.4.2.
7.5.3.2 Subscribe real-time UAV status information request p. 50
Table 7.5.3.2-1 describes the information flow for a UAS application specific server to subscribe to real-time UAV status information at the UAE server.
| Information element | Status | Description |
|---|---|---|
| UASS ID | M | The identifier of the UAS application specific server which initiated this request. |
| UAV ID (s) | M | The identifier of one or more UAV(s) (e.g. 3GPP UE ID or CAA level UAV ID) for which the real-time UAV status is requested. |
| Area of Interest | M | Geographic area location information where the UASS server wishes to monitor the UAS's location adherence. |
| Notification Target URI | M | Target URI where the UAS application specific server wishes to receive the notifications about real-time UAV status information. |
7.5.3.3 Subscribe real-time UAV status information response p. 51
Table 7.5.3.3-1 describes the information flow for UAE server to respond for real-time UAV status subscription request from the UAS application specific server.
| Information element | Status | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Result | M | Result from the UAE server in response to subscription request indicating success or failure | |||||||
| Subscription ID (NOTE) | O | Identifier of a successful subscription. | |||||||
|
NOTE:
This IE is included when the Result indicates success
|
|||||||||
7.5.3.4 Notify real-time UAV status information p. 51
Table 7.5.3.4-1 describes the information flow for a UAS application specific server to receive notification about real-time UAV status information from the UAE server.
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Identifier of the subscription for this notification. |
| Real-time UAV(s) status information | M | One or more real-time UAV(s) status information |
| >UAV ID | M | The identifier of the UAV (e.g. 3GPP UE ID or CAA level UAV ID) for which the real-time UAV status information is notified. |
| >UAV status information | M | The UAV status information includes the UAV network connection status information, location information and timestamp. |
7.5.3.5 Unsubscribe real-time UAV status information request p. 51
Table 7.5.3.5-1 describes the information flow for a UAS application specific server to unsubscribe to real-time UAV status information at the UAE server.
| Information element | Status | Description |
|---|---|---|
| Subscription ID | M | Identifier of the subscription for this notification. |
7.5.3.6 Unsubscribe real-time UAV status information response p. 51
Table 7.5.3.6-1 describes the information flow for UAE server to respond for real-time UAV status unsubscription request from the UAS application specific server.
| Information element | Status | Description |
|---|---|---|
| Result | M | Result from the UAE server in response to unsubscription request indicating success or failure |
