# US 12,764,535 B2 · Revocation of UAS-related authorization and security information > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,764,535 B2 - Document ID: US12764535B2 - Status: Granted - Kind: B2 - Application number: 18/260,930 - Filed: 2022-01-10 - Published: 2024-03-21 - Granted: 2026-10-13 - Earliest claimed: 2021-01-08 - Assignees: Lenovo (Singapore) Pte. Ltd. - Applicants: Lenovo (Singapore) Pte. Ltd. - Inventors: Sheeba Backia Mary Baskaran; Andreas Kunz; Dimitrios Karampatsis - Web page: https://patentgrep.com/patent/US12764535B2 ## CPC - H04W 12/082: using revocation of authorisation - G08G 5/22: located on the ground - H04W 12/50: Secure pairing of devices - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - 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}) ## Abstract Apparatuses, methods, and systems are disclosed for handling security aspects for UAS in a 3GPP network. One apparatus contains a transceiver that receives a revocation indication message from a mobile communication network and a processor that deletes UAS-related authorization and security information corresponding to a UAV ID. The transceiver further transmits a revocation acknowledgement message to the mobile communication network. ## Claims ### Claim 1 A user equipment (“UE”) for wireless communication, the UE comprising: at least one memory; and at least one processor coupled with the at least memory and configured to cause the UE to: receive a revocation indication message from a mobile communication network; delete uncrewed aerial system (“UAS”)-related authorization and security information corresponding to an uncrewed aerial vehicle (“UAV”) identifier (“ID”), wherein the UAS-related authorization and security information comprises at least a UAV and UAS service supplier authentication and authorization (“UUAA”) context comprising authorization information and a security context received after a successful UUAA, wherein the security context comprises a security key, a token, a lifetime, pairing information, or a combination thereof; and transmit a revocation acknowledgement message to the mobile communication network. ### Claim 2 (depends on 1) The UE of claim 1, wherein the UAV ID comprises a civil aviation authority (“CAA”)-level UAV ID, wherein the UAS-related authorization and security information comprises one or more of: a UUAA result; a Command and Control (“C2”) authorization result; UUAA authorization information; a pairing authorization result; C2 association information; a C2 association authorization result; UAS security information; session security key material; a session security token; or a combination thereof. ### Claim 3 (depends on 1) The UE of claim 1, wherein the revocation indication message revokes the UUAA for the UAV ID. ### Claim 4 (depends on 1) The UE of claim 1, wherein the revocation indication message revokes a UAS pairing corresponding to the UAV ID, wherein the at least one processor is configured to cause the UE to perform a UAS pairing procedure between a UAV and a UAV controller (“UAV-C”) and to receive pairing authorization information or session security information based on a successful completion of the UAS pairing procedure, and wherein the UAS-related authorization and security information further comprises the pairing authorization information or the session security information. ### Claim 5 (depends on 4) The UE of claim 4, wherein to perform the UAS pairing procedure, the at least one processor is configured to cause the UE to: transmit a pairing authorization request comprising: a first ID that belongs to the UAV, and a second ID belonging to the UAV-C; and receive a pairing success indication comprising the session security information. ### Claim 6 A processor for wireless communication, the processor comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive a revocation indication message from a mobile communication network; delete uncrewed aerial system (“UAS”)-related authorization and security information corresponding to an uncrewed aerial vehicle (“UAV”) identifier (“ID”), wherein the UAS-related authorization and security information comprises at least a UAV and UAS service supplier authentication and authorization (“UUAA”) context comprising authorization information and a security context received after a successful UUAA, wherein the security context comprises a security key, a token, a lifetime, pairing information, or a combination thereof; and transmit a revocation acknowledgement message to the mobile communication network. ### Claim 7 (depends on 6) The processor of claim 6, wherein the UAV ID comprises a civil aviation authority (“CAA”)-level UAV ID, wherein the UAS-related authorization and security information comprises one or more of: a UUAA result; a Command and Control (“C2”) authorization result; UUAA authorization information; a pairing authorization result; C2 association information; a C2 association authorization result; UAS security information; session security key material; a session security token; or a combination thereof. ### Claim 8 (depends on 6) The processor of claim 6, wherein the revocation indication message revokes a UUAA for the UAV ID. ### Claim 9 (depends on 6) The processor of claim 6, wherein the revocation indication message revokes a UAS pairing corresponding to the UAV ID, wherein the at least one controller is configured to cause the processor to perform a UAS pairing procedure between a UAV and a UAV controller (“UAV-C”) and to receive pairing authorization information or session security information based on a successful completion of the UAS pairing procedure, and wherein the UAS-related authorization and security information further comprises at least the pairing authorization information or the session security information. ### Claim 10 (depends on 9) The processor of claim 9, wherein to perform the UAS pairing procedure, the at least one controller is configured to cause the processor to: transmit a pairing authorization request comprising: a first ID that belongs to the UAV, and a second ID belonging to the UAV-C; and receive a pairing success indication comprising the session security information. ### Claim 11 A network apparatus for wireless communication, the network apparatus comprising: at least one memory; and at least one processor coupled with the at least memory and configured to cause the network apparatus to: receive a revocation message comprising an uncrewed aerial vehicle (“UAV”) identifier (“ID”); transmit a revocation indication to a user equipment (“UE”) in response to the revocation message; delete an uncrewed aerial system (“UAS”) context corresponding to the revocation message, wherein the UAS context comprises authorization information and security context that was received after a successful UAV and UAS service supplier Authentication and Authorization (“UUAA”) procedure, wherein the security context comprises a security key, a token, a lifetime, pairing information, or a combination thereof; and receive a revocation acknowledgement from the UE. ### Claim 12 (depends on 11) The network apparatus of claim 11, wherein the revocation message revokes a UUAA for the UAV ID, wherein to transmit the revocation indication, the at least one processor is configured to cause the network apparatus to transmit a UE configuration update (“UCU”) command to the UE. ### Claim 13 (depends on 11) The network apparatus of claim 11, wherein the UAV ID comprises one or more of: generic public subscription identifier (“GPSI”) and a civil aviation authority (“CAA”)-level UAV ID. ### Claim 14 (depends on 11) The network apparatus of claim 11, wherein the at least one processor is further configured to cause the network apparatus to: determine whether an active data connection corresponds to the revocation message; and release the active data connection, in response to determining that the active data connection corresponds to the revocation request. ### Claim 15 (depends on 11) The network apparatus of claim 11, wherein the revocation message revokes a UAS pairing corresponding to the UAV ID, wherein to transmit the revocation indication, the at least one processor is configured to cause the network apparatus to transmit a PDU session release command. ### Claim 16 (depends on 11) The network apparatus of claim 11, wherein the at least one processor is configured to cause the network apparatus to perform a UAS pairing procedure between a UAV and a UAV controller (“UAV-C”) and to receive pairing authorization information or session security information, based on a successful completion of the UAS pairing procedure, and wherein the UAS context comprises the pairing authorization information or the session security information. ### Claim 17 (depends on 11) The network apparatus of claim 11, wherein the revocation message comprises a pairing update message for the UAV ID, wherein the pairing update message comprises new pairing authorization information, and one or more of: a UAV controller (“UAV-C”) ID and cause value ‘UAV-C replacement’, wherein to transmit the revocation indication to the UE, the at least one processor is configured to cause the network apparatus to transmit a protocol data unit (“PDU”) session modification command, and wherein the at least one processor is further configured to cause the network apparatus to update a UAS pairing corresponding to the UAV ID based on the new pairing authorization information. ### Claim 18 (depends on 11) The network apparatus of claim 11, wherein the UAS context comprises one or more of: UUAA result; a Command and Control (“C2”) authorization result; UUAA authorization information; a pairing authorization result; C2 association information; a C2 association authorization result; UAS security information; session security key material; a session security token; or a combination thereof. ### Claim 19 (depends on 11) The network apparatus of claim 11, wherein the at least one processor is further configured to cause the network apparatus to: receive a reauthentication request message from a UAS network function (“UAS-NF”), the reauthentication request message containing: a network-level UAV ID, a civil aviation authority (“CAA”)-level UAV ID, and a cause value that indicates reauthentication of the UE; and transmit a non-access stratum (“NAS”) message to the UE, the NAS message containing: a UAV ID request, and an indication that reauthentication of the UE is required. ### Claim 20 A method performed by a network function, the method comprising: receiving a revocation message comprising an uncrewed aerial vehicle (“UAV”) identifier (“ID”); transmitting a revocation indication to a user equipment (“UE”) in response to the revocation message; deleting an uncrewed aerial system (“UAS”) context corresponding to the revocation message, wherein the UAS context comprises authorization information and security context that was received after a successful UAV and UAS service supplier authentication and authorization (“UUAA”) procedure, wherein the security context comprises a security key, a token, a lifetime, pairing information, or a combination thereof; and receiving a revocation acknowledgement from the UE.