Section: 5.1.2 Scenario
Content: A UAS is made up of a UAV and a UAV controller which is a physical device used by a UAV operator. One UAV controller may command and control one UAV or a fleet of UAVs. The UAV and the UAV controller both have certain credentials and identities which are factory set, related to the status of the UAS or UAV operator, or related to the operating scenario. This includes unique 3GPP credentials and identities. The communication between the UAV controller and UAV is done via 3GPP communication service offered by MNO. Detection of UAS communication is possible in an MNO network and if UE subscription does not allow such communication it is rejected. Permission for a UE to function as an aerial UE in the 3GPP network can be identified via subscription information. The network may use this information to perform the necessary control and apply relevant functions. Based on this subscription information uplink power adjustment and frequency band alteration can be applied in order UAS communication not to have impact on other types of communication. In addition to UAS subscription information UE can indicate a radio capability to the network which may be used to identify a UE with relevant functions for UAS communication in a 3GPP network. In this scenario, the UAS has been switched on in order for the UAV operator to fly the UAV using the UAV controller. The UAV operator pairs the UAV and the UAV controller for UAS operation through some mechanism. The UAV passes UAV data to onboard 3GPP UE. The UE authenticates with MNO. In parallel to the attach request, the UE sends the UAV data & 3GPP identifiers to the Unmanned Aerial System Traffic Management (UTM), requesting initial permission to attach to the network to fly and using certain services provided by UTM. Subject to national regulatory UTM requirements, a UAS may need to go through several authentication and authorization processes before a UAS can be fully operated, e.g. after finishing the initial authentication for establish connection with the UTM, a UAV may need to go through additional application level authentication to activate some UTM services, such as flight monitoring or collision avoidance service. Therefore, a UAS may need to provide different UAS identity data according to the level of the authorization and authentication process required by the UAS. If the request towards UTM is coming from UE without subscription information for drone communication, then the request shall be rejected. The same operation is done by the UAV controller using its own credentials and identifiers. During the initial authorization procedures, the MNO and UTM need to be able to associate the UAV and the UAV controller as a UAS. If the UTM rejects a request for some reasons, e.g. incorrect identities or credentials, or UAS element(s) are operating in the area which is prohibited, the MNO rejects the attach request of the UAV and/or UAV controller of the UAS. If both registration requests are accepted for the UAS, the UAV operator can use the UAV controller to fly the UAV by transmitting commands from the UAV controller to the UAV via 3GPP network.