This solution addresses Key issue #4: Location Information veracity.
The solution proposes to use the currently supported location service to provide network-based location information to the USS/UTM.
Step 1-3 shows the procedure for the UTM/USS to obtain a network-based location for the UAV.
The USS/UTM sends the location request to UFES to request the UAV location from network. The USS/UTM includes the relevant identity of the UAV when the USS/UTM is requesting location information about an individual UE or a geographic area when trying to find the information of all UAVs in an area.
UFES uses the provided identity to obtain the identities needed to request location from the rest of the network. UFES gets the relevant UAV(s) location from AMF or GMLC by the current location services supported by AMF or GMLC.
UFES checks that the USS/UTM is authorized to receive the location information for a UAV.
USS/UTM is authorized to receive the location information of a group of UAVs in a particular geographic area or of an individual UAV if it has authorized the UAV(s) for service.
Furthermore, a USS/UTM can be authorized to receive the data about all UAV's in a particular geographic area (e.g. such an authorization is pre-provisioned in the UFES based on regulatory requirements). The details of providing such an authorization are left to implementation/deployments.
The UFES provides the authorized UAV(s) location information to USS/UTM for the relevant UAV. USS/UTM can use the output received at step 3 to verify the location reported by the UAV.
A similar solution is possible when the UAV is connected to EPS.
This solution provides a mitigation against UAV location spoofing as it ensures that network-based location information about a UAV is available to the USS/UTM.
The solution also supports the authorization of USS/UTMs to receive only the UAV location information about either UAVs under the USS/UTM control or if all the UAVs in a geographic if specifically authorized to receive this information.