Section: 7 Consolidated potential requirements 7.1 General
Content: The UTM shall be able to associate the UAV and UAV controller, identify them as a UAS, and authorise a UAS to operate. The UTM shall be able to refuse authorisation for a UAS to operate. The 3GPP system shall enable a UAS to send the following UAV data to a UTM: unique identity (this may be unique 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status. The 3GPP system shall enable a UAS to send the following UAV controller data to a UTM: unique identity, UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, the identity of the UAV operator who operate the UAV controller, UAV operator license and certification. The 3GPP system shall enable a UAS to send different UAS data to UTM based on the different authentication and authorizations level which are applied to the UAS. The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future. The 3GPP system shall enable a UE in a UAS to send the following identifiers to a UTM: IMSI, IMEI, MSISDN. The 3GPP system may enable an MNO to augment the data sent to a UTM with the following: network-based positioning information, preconfigured pairing data. NOTE: this augmentation may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information. A UAS may optimise subsequent messages sent to an UTM by omitting unchanged static or semi-static data (e.g. owner identity, owner address, owner contact details, owner certification). The UTM shall be able to inform an MNO of the outcome of an authorisation to operate. The 3GPP system shall enable an MNO to allow a UAS authorisation request only if appropriate subscription information is present. An MNO shall be able to enforce the authorisation for a UAS to operate (e.g. by enabling or disabling communication between the UAV and UAV controller). The 3GPP system shall enable a UTM to be aware of the identity/identities of a UAS. The 3GPP system shall enable a UAS to update a UTM with the live location information of a UAV and its UAV controller. The 3GPP system may enable an MNO to supplement location information sent to a UTM. NOTE: this supplement may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information. The 3GPP system shall support a UTM to consume Location Service provided by the network. The 3GPP system shall enable a UAS to send the location of the UAV and UAV controller towards UTM with at least a periodicity of 1 update per second. The 3GPP system shall enable an authorised official to query a UTM for information, location, and identities of an active UAS when an authorised official provides a subset of UAS data (e.g. an IMSI, general location, or IMEI). An MNO shall be able to enforce the authorisation for assisting a UAS to operate, e.g. by establishing a reliable route within 3GPP network to deliver the commands/control messages between the UAV and UAV controller. The 3GPP network shall be able to support roaming when providing network assisted UAS operation. The 3GPP system shall provide the capability for an MNO to receive the UAS information regarding its 3GPP communication capabilities. The 3GPP system shall support the UAS identification data which can differentiate the UAS with UAS-capable UE and the UAS with non-UAS-capable UE. NOTE: UAS-capable UE refers to the UE which support interaction capability with UTM and certain 3GPP communication features which 3GPP provides for UAS. The 3GPP system shall support identification and reporting unauthorized UAVs to a UTM.