# US 2022/0277657 A1 · Methods and Apparatus for Enhancing Unmanned Aerial Vehicle Management Using a Wireless Network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2022/0277657 A1 - Document ID: US20220277657A1 - Status: Published application - Kind: A1 - Application number: 17/662,300 - Filed: 2022-05-06 - Published: 2022-09-01 - Earliest claimed: 2019-11-08 - Assignees: Huawei Technologies Co., Ltd. - Applicants: Huawei Technologies Co., Ltd. - Inventors: Zhixian Xiang - Web page: https://patentgrep.com/patent/US20220277657A1 ## CPC - G08G 5/55: for a single aircraft - H04W 4/44: for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H] - G08G 5/22: located on the ground - G08G 5/26: Transmission of traffic-related information between aircraft and ground stations - G08G 5/53: for cruising - G08G 5/56: for two or more aircraft - G08G 5/57: for unmanned aircraft - H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks - H04W 12/069: using certificates or pre-shared keys - H04W 12/50: Secure pairing of devices - H04W 12/61: Time-dependent - H04W 12/63: Location-dependent; Proximity-dependent - H04W 12/68: Gesture-dependent or behaviour-dependent - H04W 48/08: Access restriction or access information delivery, e.g. discovery data delivery (signalling during connection H04W76/00) - H04W 48/16: Discovering, processing access restriction or access information - H04W 72/51: based on terminal or device properties - G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93}) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method includes receiving, by an unmanned aerial system (UAS) traffic management (UTM) from a mobile network function providing UAS management support functionality, an authentication-authorization request including additional UAS management information associated with an unmanned aerial vehicle (UAV); validating, by the UTM, the authentication-authorization request thereby producing authorization data associated with the UAV; determining, by the UTM, information for UAV management including remoted identification and tracking information (RITI); and transmitting, by the UTM to the mobile network function, an authentication-authorization response including the authorization data associated with the UAV and the information for UAV management. ## Claims ### Claim 1 A method comprising: receiving, by an unmanned aerial system (UAS) traffic management (UTM) from a mobile network function providing UAS management support functionality, an authentication-authorization request including additional UAS management information associated with an unmanned aerial vehicle (UAV); validating, by the UTM, the authentication-authorization request thereby producing authorization data associated with the UAV; determining, by the UTM, information for UAV management including remoted identification and tracking information (RITI); and transmitting, by the UTM to the mobile network function, an authentication-authorization response including the authorization data associated with the UAV and the information for UAV management. ### Claim 2 (depends on 1) The method of claim 1, the mobile network function being implemented in one of an existing mobile network function, or a new mobile network function, to provide management support for the UAS. ### Claim 3 (depends on 2) The method of claim 2, the existing mobile network function comprising one of an access management function (AMF), or a session management function (SMF). ### Claim 4 (depends on 2) The method of claim 2, the new mobile network function comprising a UAV flight enablement subsystem (UFES). ### Claim 5 (depends on 1) The method of claim 1, the information for the UAV management comprising at least one of location information associated with the UAV, or other information related to the UAV in accordance with information defined in a subscription of the UAV or requested by the UTM. ### Claim 6 (depends on 5) The method of claim 5, the other information related to the UAV being provided by a mobile network. ### Claim 7 (depends on 5) The method of claim 5, the other information related to the UAV comprising at least one of authorization status information, policy information, pairing information associated with the UAV and associated UAV controllers (UAV-Cs), restriction information, connectivity restrictions, or connectivity requirements. ### Claim 8 (depends on 6) The method of claim 6, the authorization data associated with the UAV comprising at least one of a result of the validating of the authentication-authorization request, operation policy related to a connection associated with the UAV management, UAV connection operation information in case the validating of the authentication-authorization request fails, an authorized area associated with the UAV, an authorized time associated with the UAV, communication capability and quality of service (QoS) requirements associated with the UAV, an indication if a user equipment (UE) associated with the authentication-authorization request is allowed to be used with certain UAVs, UAV connectivity behaviors usable by the mobile network, or UAV-C connectivity behaviors usable by the mobile network. ### Claim 9 (depends on 1) The method of claim 1, the information for the UAV management further compromising at least one of an assigned identity of the UAV and a UAV-C associated with the UAV, pairing information associated with the UAV and the UAV-C associated with the UAV. ### Claim 10 (depends on 9) The method of claim 9, the pairing information comprising identifiers of the UAV and the UAV-C associated with the UAV or Internet protocol (IP) addresses of the UAV and the UAV-C associated with the UAV. ### Claim 11 (depends on 6) The method of claim 6, the authorization data associated with the UAV and the information for the UAV management being provided to the mobile network during UAV authentication and authorization, or provisioned for the UAV during UAV operation. ### Claim 12 A method comprising: receiving, by a mobile network function, identification and tracking information associated with an unmanned aerial vehicle (UAV); updating, by the mobile network function, a record associated with the UAV in accordance with identification information of the identification and tracking information; and providing, by the mobile network function to an unmanned aerial system (UAS) traffic management (UTM) function, the identification and tracking information in accordance with a request received from the UTM. ### Claim 13 (depends on 12) The method of claim 12, the mobile network function being implemented in one of an existing mobile network function, or a first new mobile network function, to provide support for a UAS. ### Claim 14 (depends on 12) The method of claim 12, the record associated with the UAV being stored in a unified data management (UDM) or a second new mobile network function. ### Claim 15 (depends on 12) The method of claim 12, the identification information comprising a UAV identifier. ### Claim 16 (depends on 12) The method of claim 12, the identification information comprising a mobile network identifier associated with the UAV. ### Claim 17 (depends on 12) The method of claim 12, updating the record associated with the UAV comprising updating a mapping between identifiers associated with the UAV. ### Claim 18 (depends on 12) The method of claim 12, the mobile network function comprising a UAS network publishing function (UNPF). ### Claim 19 (depends on 18) The method of claim 18, the UNPF being implemented as a UAV flight enablement subsystem (UFES). ### Claim 20 (depends on 12) The method of claim 12, the identification and tracking information associated with the UAV being received a dedicated UTM container containing UAV information being transferred between the UAV and the mobile network function and the UTM using a 3GPP defined protocol. ### Claim 21 (depends on 20) The method of claim 20, the 3GPP defined protocol comprising a network access stratum (NAS) message. ### Claim 22 (depends on 12) The method of claim 12, the identification and tracking information comprising location information of the UAV. ### Claim 23 (depends on 12) The method of claim 12, the identification and tracking information associated with the UAV being received from a second mobile network function in accordance with a request made by the mobile network function. ### Claim 24 (depends on 23) The method of claim 23, the second mobile network function comprising a location base function or an access management function (AMF). ### Claim 25 An unmanned aerial system (UAS) traffic management (UTM), the UTM comprising: one or more processors; and a non-transitory memory storage comprising instructions that, when executed by the one or more processors, cause the UTM to: receive, from a mobile network function providing UAS management support functionality, an authentication-authorization request including additional UAS management information associated with an unmanned aerial vehicle (UAV); validate the authentication-authorization request thereby producing authorization data associated with the UAV; determine information for UAV management including remoted identification and tracking information (RITI); and transmit, to the mobile network function, an authentication-authorization response including the authorization data associated with the UAV and the information for the UAV management. ### Claim 26 (depends on 25) The UTM of claim 25, the information for the UAV management comprising at least one of location information associated with the UAV, or other information related to the UAV in accordance with information defined in a subscription of the UAV or requested by the UTM. ### Claim 27 (depends on 26) The UTM of claim 26, the other information related to the UAV comprising at least one of authorization status information, policy information, pairing information associated with the UAV and associated UAV controllers (UAV-Cs), restriction information, connectivity restrictions, or connectivity requirements. ### Claim 28 (depends on 25) The UTM of claim 25, the authorization data associated with the UAV comprising at least one of a result of authentication-authorization request validation, operation policy related to a connection associated with the UAV management, UAV connection operation information in case the authentication-authorization request validation fails, an authorized area associated with the UAV, an authorized time associated with the UAV, communication capability and quality of service (QoS) requirements associated with the UAV, an indication if a user equipment (UE) associated with the authentication-authorization request is allowed to be used with certain UAVs, UAV connectivity behaviors usable by a mobile network, or UAV-C connectivity behaviors usable by the mobile network. ### Claim 29 (depends on 25) The UTM of claim 25, the information for the UAV management further compromising at least one of an assigned identity of the UAV and a UAV-C associated with the UAV, pairing information associated with the UAV and the UAV-C associated with the UAV. ### Claim 30 (depends on 28) The UTM of claim 28, the authorization data associated with the UAV and the information for the UAV management being provided to the mobile network during UAV authentication and authorization, or provisioned for the UAV during UAV operation. ### Claim 31 A mobile network function comprising: one or more processors; and a non-transitory memory storage comprising instructions that, when executed by the one or more processors, cause the mobile network function to: receive identification and tracking information associated with an unmanned aerial vehicle (UAV); update a record associated with the UAV in accordance with identification information of the identification and tracking information; and provide, to an unmanned aerial system (UAS) traffic management (UTM) function, the identification and tracking information in accordance with a request received from the UTM. ### Claim 32 (depends on 31) The mobile network function of claim 31, the mobile network function being implemented in one of an existing mobile network function, or a first new mobile network function, to provide support for a UAS. ### Claim 33 (depends on 31) The mobile network function of claim 31, the record associated with the UAV being stored in a unified data management (UDM) or a second new mobile network function. ### Claim 34 (depends on 31) The mobile network function of claim 31, the identification information comprising a UAV identifier or a mobile network identifier associated with the UAV. ### Claim 35 (depends on 31) The mobile network function of claim 31, the identification and tracking information associated with the UAV being received a dedicated UTM container containing UAV information being transferred between the UAV and the mobile network function and the UTM using a 3GPP defined protocol.