Content for TS 23.256 Word version: 19.0.0

1… 4… 4.2… 4.2.3… 4.3… 4.4… 4.5… 5… 5.2.3… 5.2.4… 5.2.5… 5.2.5.3… 5.2.5.4… 5.2.7 5.2.8… 5.2.9… 5.3… 5.4… 5.5… 5.12… 5.13… 5.14… 6… 6.2… 6.3… 6.3.4… A…

5.12 Pre-flight Planning and In-flight Monitoring for UAVs 5.12.1 General 5.12.2 Procedure for NEF Assisted Pre-flight Planning 5.12.3 Procedure for NEF Assisted In-flight Monitoring
...

5.12 Pre-flight Planning and In-flight Monitoring for UAVs |R19| p. 72

5.12.1 General p. 72

5G network may support pre-flight planning and in-flight monitoring for UAVs via the NEF service exposure. The USS/UTM may request assistance information to NEF of pre-flight planning and in-flight monitoring for UAV, after the UAV establishes user plane connection with the USS/UTM.

In the case of pre-flight planning, USS/UTM may request assistance information to NEF for the following cases:

Determine the most suitable flight path among several candidate flight paths:
USS/UTM provides multiple planned flight paths to the network, and network leverages the network analytics e.g. Movement Behaviour Analytics and/or QoS Sustainability Analytics, to determine the most suitable planned flight path among the candidates.
Plan a flight path based on starting and ending point of the flight:
USS/UTM provides location information of the starting and ending points for the flight to the network, and network leverages the network analytics e.g. Movement Behaviour Analytics and/or QoS Sustainability Analytics, to determine a detailed flight path. NEF responds the USS/UTM about the detailed flight path to assist the pre-flight planning.
Output QoS information along the flight path:
USS/UTM provides multiple planned flight paths to the network, and network leverages QoS Sustainability Analytics to output QoS information for each flight path provided.

In the case of in-flight monitoring, in addition to QoS Sustainability Analytics request, USS/UTM can provide the UAV flight path and corresponding (arriving) time to the network, in order for the network to verify whether the UAV's exact location matches the scheduled location represented by the waypoint.

5.12.2 Procedure for NEF Assisted Pre-flight Planning p. 74

Reproduction of 3GPP TS 23.256, Fig. 5.12.2-1: Procedure for NEF Assisted Pre-flight Planning

Figure 5.12.2-1: Procedure for NEF Assisted Pre-flight Planning

Step 1.

The UAV establishes a PDU Session for communication with the USS/UTM as described in clause 5.2.3.

Step 2.

(via application layer) The UAV requests pre-flight planning service from USS/UTM.

Step 3.

The USS/UTM derives information for the pre-flight planning request and decides to request assistance information from NEF.

Step 4.

The USS/UTM sends pre-flight planning assist request to NEF. The request message includes identifier of the UAV (e.g. GPSI), information of the starting and ending points for the flight, requirements on the flight route (e.g. on time), candidate flight route(s) (received from the UAV or local derived at the USS/UTM), and accuracy level of predictions relevant to the flight planning.

Step 5.

The NEF maps parameters included in the request from the USS/UTM to information used by the 3GPP system (e.g. map the geographical area into an area of interest that is represented by a list of Cell IDs, gNB IDs or TAIs). The NEF determines services needed for the request and relevant NFs, e.g. NEF service on UAV tracking and mode (UAV location reporting mode, UAV presence monitoring mode, List of Aerial UEs in a geographic area), NWDAF analytics service (Movement Behaviour analytics, and/or QoS Sustainability Analytics), GMLC service (e.g. Ranging/Sidelink Positioning location).

Step 6.

If the NEF cannot satisfy the requirements on flight planning (e.g. cannot get predictions relevant to the flight planning from NWDAF with the required accuracy level), the NEF responses to the USS/UTM to reject the pre-flight planning assist request, and may include the detail reason.

Step 7.

If being rejected in step 6, the USS/UTM may response to the UAV to reject the pre-flight planning request, may include the detail reason if available.

Step 8.

The NEF performs steps 2-5 in clause 5.3.4, and filter list of UAVs in the areas of interest.

Step 9.

The NEF subscribes/requests for notification on Movement Behaviour analytics provided by NWDAF as defined in clause 6.21.4 of TS 23.288. The subscribe request message include identifier of the UAV (e.g. GPSI) obtained in step 4 and height information of UAV. The other parameters included in the request are described in clause 6.21.4 of TS 23.288. The list of UAVs in the areas of interest output from step 8 can be used as inputs for the NEF to request the NWDAF on Movement Behaviour analytics.

Step 10.

The NEF subscribes/requests for notification on QoS Sustainability analytics provided by NWDAF as defined in clause 6.9.1 of TS 23.288. The subscribe/request message include identifier of the UAV (e.g. GPSI) obtained in step 4 and the UAV flight path information defined as 3D location waypoints. The other parameters included in the request are described in clause 6.9.1 of TS 23.288. The list of UAVs in the areas of interest output from step 8 can be used as inputs for the NEF to request the NWDAF on QoS Sustainability analytics.

Step 11.

The NEF may request GMLC service(s), e.g. Ranging/Sidelink positioning location as defined in clause 6.20.3 of TS 23.273. The list of UAVs in the areas of interest output from step 8 can be used as inputs for the NEF to request the GLMC service on Ranging/Sidelink Positioning location.

Step 12.

The NEF generates assistance information for pre-flight planning based on the information and analytics from steps 8-10. The assistance information may be the best matched route among the ones provided from the USS/UTM in step 4, or potential flight route(s) if candidate flight route(s) is not provided in step 4.

Step 13.

The NEF responses to the USS/UTM with the assistance information.

Step 14.

The USS/UTM decides flight planning by using the assistance information and flight planning mechanism which is out of scope.

Step 15.

The USS/UTM sends response to the UAV with the planned flight route.

5.12.3 Procedure for NEF Assisted In-flight Monitoring p. 76

Reproduction of 3GPP TS 23.256, Fig. 5.12.3-1: Procedure for NEF Assisted In-flight Monitoring

Figure 5.12.3-1: Procedure for NEF Assisted In-flight Monitoring

Step 1.

The USS/UTM sends in-flight monitoring assist subscribe message to NEF. The message includes identifier of the UAV (e.g. GPSI) and information of the flight route, monitoring mode (e.g. UAV location monitoring, fight route monitoring, flight environment monitoring, Ranging/Sidelink positioning location monitoring, QoS Sustainability analytics), report requirements (e.g. report format (event triggered or periodically), assistance information (e.g. the monitoring results, information generated from the monitoring results)), and may include planned fight route if fight route monitoring, list of UAVs in the areas of interest if flight environment monitoring, preset value for distance if Ranging/Sidelink positioning location monitoring.

Step 2.

NEF maps the parameters in the message from the USS/UTM to information used by the 3GPP system. The NEF determines services needed for the message and relevant NFs, e.g. NEF service on UAV tracking (UAV location reporting mode, UAV presence monitoring mode, List of Aerial UEs in a geographic area), GMLC service (Ranging/Sidelink Positioning location), NWDAF analytics service (QoS Sustainability Analytics).

Step 3.

If the NEF cannot provide the requested assistance information for in-flight monitoring, the NEF responses to the USS/UTM to reject the in-flight monitoring assistance subscribe message, may include the detail reason if available.

Step 4.

For UAV location monitoring, the NEF executes steps 2-5 in clause 5.3.2 to obtain the location of the target UAV.

Step 5.

For fight route monitoring, the NEF executes steps 2-4 in clause 5.3.3. Upon to the subscribe message in step 1 for reporting, the NEF may compare the monitored flight route with the planned fight route (if provided in step 1) and generate assistance information on whether the UAV is flight in right route.

Step 6.

For flight environment monitoring, the NEF executes steps 2-5 in clause 5.3.4 to obtain the information of aerial UEs in the same geographic area of the target UAV.

Step 7.

For QoS Sustainability analytics, the NEF requests NWDAF service for QoS results as described in clause 6.9.1 of TS 23.288. The subscribe/request message include identifier of the UAV (e.g. GPSI) obtained in step 4 and the UAV flight path information defined as 3D location waypoints. The other parameters included in the request are described in clause 6.9.1 of TS 23.288. The list of UAVs in the areas of interest output from step 8 can be used as inputs for the NEF to request the NWDAF on QoS Sustainability analytics.

Step 8.

For Ranging/Sidelink positioning location monitoring, the NEF requests GLMC service for Ranging/Sidelink Positioning location results as described in clause 6.20.4 of TS 23.273, the procedure of SL-MT-LR for periodic, triggered Location Events (steps 1-20 for initiation the monitoring, steps 21-31 for monitoring periodic). The list of UAVs in the areas of interest output from step 6 can be used as inputs to step 7 for NEF to request GLMC service for Ranging/Sidelink Positioning location, if the UAVs is unknown in the areas of interest.

Step 9.

The NEF notifies the USS/UTM the monitoring results (e.g. the location of the target UAV, indication on whether the UAV is flight in right route, the target UAV presence in areas of interest, the information of aerial UEs in the same geographic area of the target UAV, the distance of other UAVs and the target UAV and whether the distance is smaller than a preset value).

Steps 4-9 may be repeated for report monitoring results periodically.