Dynamic user equipment identifier assignment

Abstract

Apparatuses, methods, and systems for dynamic user equipment identifier assignment are disclosed. An apparatus (600) includes a transceiver (625) that receives, at a user equipment ("UE") device, an initial identifier for the UE device from a mobile wireless communication network; and a processor (605) that generates a plurality of identifiers for the UE device based on the initial identifier, where each of the plurality of identifiers is generated based on a previous identifier to form a chain of identifiers, assigns a last generated identifier of the chain of identifiers to the UE device, and periodically assigns a different identifier to the UE device from the chain of identifiers, the different identifier including an identifier of the chain of identifiers used to generate an identifier currently assigned to the UE.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 059,829, filed January 31, 2021, entitled “METHOD OF ENABLING PRIVACY FOR UAV BROADCAST IDENTITIES”, which is incorporated herein by reference. Technical Field

[0003] The topics disclosed in this article generally relate to wireless communication, and more specifically to dynamic user equipment identifier assignment. Background Technology

[0004] In some wireless communication systems, user equipment (“UE”) can connect to the fifth-generation (“5G”) core network (i.e., “5GC”) within a public terrestrial mobile network (“PLMN”). In this wireless network, unmanned aerial vehicles (“UAVs”) communicate with each other and transmit broadcast information via a UAV-to-UAV (“U2U”) radio interface. If the sender identifier remains unchanged, a specific UAV can be easily tracked by listening to the broadcast messages using the sender identifier. Summary of the Invention

[0005] A process for assigning dynamic user equipment identifiers is disclosed. This process can be implemented by an apparatus, system, method, and / or computer program product.

[0006] An apparatus includes a transceiver that receives an initial identifier for the UE device from a mobile wireless communication network at a user equipment (“UE”) device; and a processor that generates a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain, the last generated identifier in the identifier chain is assigned to the UE device, and different identifiers are periodically assigned to the UE device from the identifier chain, the different identifiers including identifiers in the identifier chain used to generate the identifier currently assigned to the UE.

[0007] Another device includes a transceiver that transmits an initial identifier for the UE device from a mobile wireless communication network to a user equipment (“UE”) device; and a processor that generates a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain, the last generated identifier in the identifier chain is associated with the UE device, and different identifiers are periodically associated with the UE device from the identifier chain, the different identifiers including identifiers in the identifier chain used to generate the identifier currently associated with the UE. Attached Figure Description

[0008] A more specific description of the embodiments briefly described above will be presented with reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not intended to limit the scope; the embodiments will be described and explained with additional features and details using the drawings, in which:

[0009] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for dynamic user equipment identifier assignment;

[0010] Figure 2 This is a diagram illustrating one embodiment of hash chain generation and use for dynamic user equipment identifier assignment;

[0011] Figure 3 This is a signal flow diagram illustrating one embodiment of the process for generating and using hash chain identifiers for dynamic user equipment identifier assignment.

[0012] Figure 4 This is a signal flow diagram illustrating one embodiment of the process for UAV authentication and authorization via USS / UTM;

[0013] Figure 5 This is a signal flow diagram illustrating one embodiment of the process for initial identifier refresh based on NAS;

[0014] Figure 6 This is a block diagram illustrating one embodiment of a user equipment device that can be used for dynamic user equipment identifier assignment;

[0015] Figure 7 This is a block diagram illustrating one embodiment of a network device that can be used for dynamic user equipment identifier assignment;

[0016] Figure 8 This is a flowchart illustrating one embodiment of a method for dynamic user equipment identifier assignment; and

[0017] Figure 9This is a flowchart illustrating an embodiment of another method for assigning dynamic user equipment identifiers. Detailed Implementation

[0018] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining aspects of both software and hardware.

[0019] For example, the disclosed embodiments can be implemented as hardware circuitry that includes custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0020] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device employs only signals for accessing the code.

[0021] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0022] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0023] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, and C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider ("ISP").

[0024] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0025] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0026] As used herein, a list containing the conjunction “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one or more of…” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one of…” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C and excludes combinations of A, B, and C. As used herein, “selected from the group consisting of A, B, and C” includes one and only one of A, B, or C and excludes combinations of A, B, and C. As used in this article, “selecting members of a group consisting of A, B, and C and their combinations” includes only A, only B, only C, combinations of A and B, combinations of B and C, combinations of A and C, or combinations of A, B, and C.

[0027] The following description of various aspects of the embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that individual blocks in the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0028] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0029] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0030] The flowcharts and / or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0031] It should also be noted that in some alternative implementations, the functions marked in the boxes may not appear in the order shown in the figures. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functionality involved. Other steps and methods that are equivalent in function, logic, or effect to one or more boxes or portions thereof shown in the figures can be contemplated.

[0032] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used only to indicate the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of a depicted embodiment. It will also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0033] The description of the elements in each figure can be referenced to the elements in the preceding figures. In all figures, similar reference numerals refer to similar elements, including alternative embodiments of similar elements.

[0034] Generally, this disclosure describes systems, methods, and apparatuses for assigning dynamic user equipment identifiers. In some embodiments, the method may be performed using computer code embedded in a computer-readable medium. In some embodiments, the apparatus or system may include a computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solution described below.

[0035] In traditional unmanned aerial vehicle (“UAV”) systems, UAVs communicate with each other and broadcast information via UAV-to-UAV (“U2U”) radio interfaces. If the sender identifier remains unchanged, a particular UAV can be easily tracked by listening to broadcast messages using the sender identifier. In some embodiments, if the sender simply randomizes the identifier, for example, as in vehicle-to-everything (“V2X”) broadcast communications, the UAV system (“UAS”) service provider (“USS”) and UAS business management (“UTM”) may at some point be unaware of the true identity of a potentially misbehaving UAV.

[0036] The proposed solution described in this paper generates a hash chain that appears as a pseudo-random number when used in the opposite or reverse direction of the hash chain generation. Because both parties, such as the UAV and the wireless network function or node, traverse the hash chain at the same update interval, the USS, UTM, UAV Flight Enable Subsystem (“UFE”), etc., always know the identifier that the UAV is currently using or assigned.

[0037] Figure 1 A wireless communication system 100 for dynamic user equipment identifier assignment according to embodiments of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a fifth-generation radio access network (“5G-RAN”) 115, a mobile core network 140, and a UAS 101. The 5G-RAN 115 and the mobile core network 140 form a mobile communication network. The 5G-RAN 115 may consist of a 3GPP access network 120 including at least one cellular base station unit 121 and / or a non-3GPP access network 130 including at least one access point 131. The remote unit 105 communicates with the 3GPP access network 120 using a 3GPP communication link 123 and / or communicates with the non-3GPP access network 130 using a non-3GPP communication link 133. Even when Figure 1 The document describes a specific number of remote units 105, 3GPP access network 120, cellular base station unit 121, 3GPP communication link 123, non-3GPP access network 130, access point 131, non-3GPP communication link 133, and mobile core network 140. Those skilled in the art will also recognize that any number of remote units 105, 3GPP access network 120, cellular base station unit 121, 3GPP communication link 123, non-3GPP access network 130, access point 131, non-3GPP communication link 133, and mobile core network 140 can be included in the wireless communication system 100.

[0038] In one implementation, RAN 120 conforms to the 5G system specified in the 3rd Generation Partnership Project (“3GPP”) specifications. For example, RAN 120 could be an NG-RAN, implementing NR RAT and / or LTE RAT. In another example, RAN 120 could include a non-3GPP RAT (e.g., Or an IEEE 802.11-family compliant WLAN. In another embodiment, RAN 120 conforms to the LTE system specified in the 3GPP specification. However, more generally, the wireless communication system 100 can implement other open or proprietary communication networks, such as Global Microwave Interconnection Access (“WiMAX”) or the IEEE 802.16 family of standards and other networks. This disclosure is not intended to limit itself to any particular wireless communication system architecture or protocol implementation.

[0039] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or other terms used in the art. In various embodiments, remote unit 105 includes a subscriber identification and / or identification module (“SIM”) and a mobile device (“ME”) providing mobile termination functionality (e.g., radio transmission, handover, voice encoding and decoding, error detection and correction, signaling to the SIM, and access). In some embodiments, the remote unit 105 may include a terminal device (“TE”) and / or be embedded in an electrical appliance or device (e.g., a computing device, as described above).

[0040] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected TVs), smart appliances (e.g., internet-connected appliances), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 may include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as a UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit (“WTRU”), device, or other terms used in the art.

[0041] Remote unit 105 can communicate directly with one or more cellular base station units 121 in 3GPP access network 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, UL and DL communication signals can be carried on 3GPP communication link 123. Similarly, remote unit 105 can communicate with one or more access points 131 in non-3GPP access network 130 via UL and DL communication signals carried on non-3GPP communication link 133. Here, access networks 120 and 130 are intermediate networks providing remote unit 105 with access to mobile core network 140.

[0042] In some embodiments, remote unit 105 communicates with a remote host (e.g., in data network 150 or data network 160) via a network connection to mobile core network 140. For example, an application 107 in remote unit 105 (e.g., a web browser, media client, or Voice over Internet Protocol (“VoIP”) application) can trigger remote unit 105 to establish a Protocol Data Unit (“PDU”) session (or other data connection) with mobile core network 140 via 5G-RAN 115 (i.e., via 3GPP access network 120 and / or non-3GPP access network 130). Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and the remote host. The PDU session represents a logical connection between remote unit 105 and user plane function (“UPF”) 141.

[0043] To establish a PDU session (or PDN connection), remote unit 105 must register with mobile core network 140 (also referred to as "attached to mobile core network" in the context of fourth-generation ("4G") systems). Note that remote unit 105 may establish one or more PDU sessions (or other data connections) with mobile core network 140. Thus, remote unit 105 may have at least one PDU session for communicating with packet data network 150. Additionally—or alternatively—remote unit 105 may have at least one PDU session for communicating with packet data network 160. Remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other communication peers.

[0044] In a 5G system (“5GS”) context, the term “PDU session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between remote unit 105 and a specific data network (“DN”) via UPF 131. A PDU session supports one or more Quality of Service (“QoS”) streams. In some embodiments, a one-to-one mapping between QoS streams and QoS profiles may exist, such that all packets belonging to a particular QoS stream have the same 5G QoS identifier (“5QI”).

[0045] In 4G / LTE system environments, Evolved Packet System (“EPS”) and Packet Data Network (“PDN”) connections (also known as EPS sessions) provide end-to-end (E2E) connectivity between the remote unit and the PDN. The PDN connectivity process establishes an EPS bearer, i.e., a tunnel between the remote unit 105 and the packet gateway (“PGW”, not shown) in the mobile core network 130. In some embodiments, a one-to-one mapping exists between the EPS bearer and the QoS profile, such that all packets belonging to a particular EPS bearer have the same QoS class identifier (“QCI”).

[0046] As described in more detail below, remote unit 105 may use a first data connection (e.g., a PDU session) established with the first mobile core network 130 to establish a second data connection (e.g., part of a second PDU session) with the second mobile core network 140. When establishing a data connection (e.g., a PDU session) with the second mobile core network 140, remote unit 105 uses the first data connection to register with the second mobile core network 140.

[0047] Cellular base station unit 121 may be geographically distributed. In some embodiments, cellular base station unit 121 may also be referred to as an access terminal, base station, base station, node B (“NB”), evolved Node B (abbreviated as eNodeB or “eNB”, also known as an evolved universal terrestrial radio access network (“E-UTRAN”) node B), 5G / NR node B (“gNB”), home node B, relay node, device, or any other term used in the art. Cellular base station unit 121 is typically part of a radio access network (“RAN”) such as 3GPP access network 120, which may include one or more controllers communicatively coupled to one or more corresponding cellular base station units 121. These and other elements of the radio access network are not illustrated but are generally well known to those skilled in the art. Cellular base station unit 121 is connected to mobile core network 140 via 3GPP access network 120.

[0048] Cellular base station unit 121 can serve multiple remote units 105 within a service area, such as a cell or cell sector, via 3GPP wireless communication link 123. Cellular base station unit 121 can communicate directly with one or more remote units 105 via communication signals. Typically, cellular base station unit 121 transmits DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Furthermore, DL communication signals can be carried on 3GPP communication link 123. 3GPP communication link 123 can be any suitable carrier in the licensed or unlicensed radio spectrum. 3GPP communication link 123 facilitates communication between one or more remote units 105 and / or one or more cellular base station units 121. Note that during NR operation on unlicensed spectrum (referred to as "NR-U"), base station unit 121 and remote units 105 communicate on unlicensed (i.e., shared) radio spectrum.

[0049] Non-3GPP access networks 130 can be geographically distributed. Each non-3GPP access network 130 can serve multiple remote units 105 with a service area. Access points 131 in non-3GPP access networks 130 can communicate directly with one or more remote units 105 by receiving UL communication signals and transmitting DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Both DL and UL communication signals are carried on non-3GPP communication links 133. 3GPP communication links 123 and non-3GPP communication links 133 can employ different frequencies and / or different communication protocols. In various embodiments, access points 131 can communicate using unlicensed radio spectrum. Mobile core network 140 can provide services to remote units 105 via non-3GPP access networks 130, as described in more detail herein.

[0050] In some embodiments, non-3GPP access network 130 is connected to mobile core network 140 via interoperability entity 135. Interoperability entity 135 provides interoperability between non-3GPP access network 130 and mobile core network 140. Interoperability entity 135 supports connectivity via “N2” and “N3” interfaces. As depicted, both 3GPP access network 120 and interoperability entity 135 use the “N2” interface to communicate with AMF 143. 3GPP access network 120 and interoperability entity 135 also use the “N3” interface to communicate with UPF 141. Although depicted as being outside of mobile core network 140, in other embodiments, interoperability entity 135 may be part of the core network. Although depicted as being outside of non-3GPP RAN 130, in other embodiments, interoperability entity 135 may be part of non-3GPP RAN 130.

[0051] In one embodiment, UAS 101 includes components, networks, hardware, software, etc., for unmanned aerial vehicle operation between UAV 106 (e.g., a drone) and UAV controller 108. UAV 106 may refer to an aircraft remotely controlled by UAV controller 108 without a human pilot, crew, or passengers. UAV controller 108 may refer to a device configured to wirelessly transmit commands to UAV 106 for controlling the UAV (e.g., controlling the UAV's speed, direction, orientation, etc.), for example via mobile network 140, access networks 120, 130, etc. UAS operator 102 may be a person operating UAV 106 (e.g., via UAV controller 108) and typically requesting flight authorization. UAV 106 and UAV controller 108 may each be a UE in wireless communication system 100 and / or may include an instance of remote unit 105. Thus, UAV 106 and / or UAV controller 108 may communicate with access network 120 to access services provided by mobile core network 140.

[0052] In some embodiments, UAV 106 and / or UAV-C controller 108 communicate functionally with UFES 155 and / or USS / UTM 157 via a network connection to mobile core network 140. In one embodiment, USS / UTM 157 provides an overlapping set of USSs that assist UAV 106 operator 102 in performing safe and compliant operations. Services may include flight plan demultiplexing, remote identification, etc.

[0053] As described below, UAV 106 and / or UAV controller 108 can establish a PDU session (or similar data connection) with mobile core network 140 using RAN 115. Mobile core network 140 can then use the PDU session to relay services between UAV 106, UAV controller 108, and packet data network 150.

[0054] In some embodiments, the non-3GPP access network 130 may be controlled by the operator of the mobile core network 140 and may be able to directly access the mobile core network 140. This non-3GPP AN deployment is referred to as a “trusted non-3GPP access network.” The non-3GPP access network 130 is considered “trusted” when it is operated by a 3GPP operator or trusted partner and supports certain security features, such as strong air interface encryption. In contrast, a non-3GPP AN deployment that is not controlled by the operator (or trusted partner) of the mobile core network 140, cannot directly access the mobile core network 140, or does not support certain security features is referred to as an “untrusted” non-3GPP access network. The interoperability entity 135 deployed in the trusted non-3GPP access network 130 may be referred to herein as a Trusted Network Gateway Function (“TNGF”). The interoperability entity 135 deployed in the untrusted non-3GPP access network 130 may be referred to herein as a Non-3GPP Interoperability Function (“N3IWF”). Although depicted as part of a non-3GPP access network 130, in some embodiments the N3IWF may be part of a mobile core network 140 or may be located in a data network 150.

[0055] In one embodiment, the mobile core network 140 is a 5G core (“5GC”) or an evolved packet core (“EPC”), which may be coupled to a data network 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account with respect to the mobile core network 140. Each mobile core network 140 belongs to a single Public Land Mobile Network (“PLMN”). This disclosure is not intended to limit the implementation of any particular wireless communication system architecture or protocol.

[0056] The mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF (“UPF”) 141. The mobile core network 140 also includes multiple control plane functions, including but not limited to Access and Mobility Management Function (“AMF”) 143, Session Management Function (“SMF”) 145, Policy Control Function (“PCF”) 146, Authentication Server Function (“AUSF”) 147, Unified Data Management (“UDM”) and Unified Data Repository Function (“UDR”) 149, USS / UTM 157, and UFES 155.

[0057] In the 5G architecture, UPF 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU sessions for interconnecting data networks (“DN”). AMF 143 is responsible for non-access stratum (“NAS”) signaling termination, NAS cryptography and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security environment management. SMF 145 is responsible for session management (i.e., session establishment, modification, and release), remote unit (i.e., UE) IP address allocation and management, DL data notification, and service orientation configuration for appropriate service routing by the UPF.

[0058] PCF 146 is responsible for unifying the policy framework, providing policy rules to the CP function, and accessing subscription information in the UDR used for policy decisions. AUSF 147 acts as the authentication server.

[0059] The UDM is responsible for authentication and Key Agreement (“AKA”) credential generation, user identification and processing, access authorization, and subscription management. The UDR is a repository of subscriber information and can be used to serve many network functions. For example, the UDR can store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third-party applications, and so on. In some embodiments, the UDM and UDR are quasi-co-located and depicted as a combined entity “UDM / UDR”149.

[0060] In various embodiments, the mobile core network 140 may also include a network exposure function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners, for example, via one or more APIs), a network repository (“NRF”) (which provides NF service registration and discovery, enabling NFs to identify appropriate services among themselves and communicate with each other via application programming interfaces (“APIs”), or other NFs defined for 5GC. In some embodiments, the mobile core network 140 may include an authentication, authorization, and charging (“AAA”) server.

[0061] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. Network instances can be identified by S-NSSAI, while the set of network slices authorized for use by the remote unit 105 is identified by NSSAI. In some embodiments, various network slices may include individual instances of network functions, such as SMF and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For ease of illustration, in Figure 1 Different network slices are not shown, but their support is assumed.

[0062] Despite Figure 1 A specific number and type of network functions are described, but those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Furthermore, in the case where the mobile core network 140 includes an EPC, the described network functions can be replaced by appropriate EPC entities such as MME, S-GW, P-GW, HSS, etc.

[0063] Although Figure 1 The components of the 5G RAN and 5G core network are described, but the described embodiments for using pseudonyms for access authentication via non-3GPP access are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfox, etc. For example, in 4G / LTE variants involving EPC, AMF 143 can be mapped to the MME, SMF to the control plane portion of the PGW and / or mapped to the MME, UPF 141 can be mapped to the SGW and the user plane portion of the PGW, UDM / UDR 149 can be mapped to the HSS, etc.

[0064] As depicted, remote unit 105 (e.g., UE) can connect to the mobile core network (e.g., a 5G mobile communication network) via two types of access: (1) via 3GPP access network 120 and (2) via non-3GPP access network 130. The first type of access (e.g., 3GPP access network 120) uses a type of wireless communication defined by 3GPP (e.g., NG-RAN), and the second type of access (e.g., non-3GPP access network 130) uses a type of wireless communication not defined by 3GPP (e.g., WLAN). 5G-RAN 115 refers to any type of 5G access network capable of providing access to the mobile core network 140, including 3GPP access network 120 and non-3GPP access network 130.

[0065] As described above, UAV 106 communicates with each other using broadcast messages, and with UAV controller 108, etc. The problem is that if the UAV identifier is determined, unauthorized and / or other parties can track UAV 106 and receive broadcast messages. In a conventional solution to this problem, the UAV broadcast identifier is randomized to avoid tracking in a manner similar to that in V2X. However, the problem with this solution is that, while the tracking problem is solved, the USS / UTM 157 can no longer associate messages with a specific UAV because it is unaware of the newly randomly generated identifier.

[0066] In another traditional solution, the USS / UTM 157 periodically assigns a broadcast identifier via application layer signaling, making the USS / UTM 157 aware of the broadcast identifier being used. However, this solution has the drawback of significantly increasing signaling, as all active UAVs 106 need to be periodically updated within potentially short time intervals.

[0067] To address the issue of dynamically changing the UAV 106 identifier used for broadcasting and other communications, as described above, this disclosure proposes a solution in which UAV 106 and USS / UTM 157 and / or UFES 155 generate hash chains that appear as pseudo-random numbers when used in relative directions. Because UAV 106 and USS / UTM 157 and / or UFES 155 use the same hash chain with the same update interval, USS / UTM 157 and / or UFES 155 know at all times the identifier currently being used or assigned by UAV 106.

[0068] In such an embodiment, the proposed solution, described in more detail below, sends an initial UAV identifier, update interval, and maximum hash chain length from the USS / UTM 157 to the UAV 106, generates a list of pseudo-random numbers in the UAV 106 and in the USS / UTM 157 that are the same identifiers used by the UAV 106 as the source identifier for its communication, updates the UAV identifier according to the identifiers generated in the hash chain at each update interval until the initial UAV identifier is reached, and sends the initial UAV identifier, update interval, and maximum hash chain with remote identifier and tracking information (“RITI”) information.

[0069] Advantageously, in one embodiment, the identifier assigned to UAV 106 can be dynamically changed in such a way that USS / UTM 157 and / or UFES 155 know the identifier that UAV 106 is currently using or currently assigned, and this may prevent others from tracking a particular UAV based on the UAV identifier.

[0070] In one embodiment, an application-layer identifier supply is provided. In such an embodiment, a hash chain 200 is created to generate and store temporary UAV 106 identifiers used in a relative / reverse generation order, such as Figure 2 As shown in the image.

[0071] In one embodiment, hash chain 200 is generated based on initial identifier 202. Initial identifier 202 is input to a hash function, such as SHA 256, SHA 512, MD5, MD6, etc., and the output of the hash function is the next identifier (ID#1) 204a in chain 200, which is then input again to a hash function, or a different hash function previously agreed upon between UAV 106 and USS / UTM 157, to generate the next identifier (ID#2) 204b, and so on, until a maximum number of identifiers are generated. Although hash functions for generating identifier chains have been described, those skilled in the art will recognize other methods for creating identifier chains at UAV 106 and at USS / UTM 157 and / or UFES 155.

[0072] Identifier 204 can be stored (at UAV 106 and at a location in mobile network 140 where it is accessible to USS / UTM 157) and then used in reverse generation order. Generating the hash of the identifier may be easy and fast, but reversing the operation may be difficult. In one embodiment, the result is a pseudo-random chain of identifiers that can be dynamically and over time assigned to UAV 106 in reverse generation order.

[0073] In one embodiment, the identifier is long enough to avoid conflicts between multiple UAVs 106 using the same identifier at the same time. In some embodiments, various types of identifiers can be used, such as temporary UAV identifiers, CAA-level UAV identifiers, remote identifiers, broadcast remote identifiers, external identifiers, etc.

[0074] Figure 3 An embodiment of the process describing the use of identifiers in a hash chain is described. In the depicted embodiment, it is assumed that UAV 106 has been registered to the mobile network and USS / UTM 157, for example, an application layer connection has been established between UAV 106 and USS / UTM 157.

[0075] In one embodiment, USS / UTM 157 generates (see box 305) an initial UAV identifier as a starting value for the hash chain, along with an update interval and a maximum hash chain length. The update interval, as described above, defines the length of time from when an identifier is assigned to UAV 106 until a new identifier from the identifier chain is assigned to UAV 106. In some embodiments, the update interval multiplied by the hash chain length indirectly indicates the interval at which USS / UTM 157 updates UAV 106 with a new initial UAV identifier.

[0076] In a further embodiment, the USS / UTM 157 provides the UAV 106 with at least one of the following information elements (see message transmission 310): initial UAV identifier, update interval, and / or maximum hash chain length. In some embodiments, the UAV 106 acknowledges receipt of the parameters in its response to the USS / UTM 157.

[0077] In one embodiment, UAV 106 and USS / UTM 157 use the same hash function to generate (see boxes 315 and 320) such as Figure 2 The hash chain described herein, and the generated identifiers are stored in the same order as those generated, for example, using arrays, linked lists and / or other data structures.

[0078] In some embodiments, UAV 106 and USS / UTM 157 update the identifier currently assigned to UAV 106 according to the update interval (see boxes 325 and 330) by moving from the last identifier in the hash chain and then toward the initial UAV identifier with each update interval (USS / UTM 157 generates and sends to UAV 106). Once UAV 106 and USS / UTM 157 reach or approach the initial UAV identifier (e.g., within one, two, five identifiers, etc.), USS / UTM 157 may restart at step 1. Figure 3 The process described herein. In some embodiments, the update interval and / or maximum hash chain length may also be varied, which can be defined according to the USS / UTM 157 configuration. In one embodiment, restarting... Figure 3 The process described in the text may be triggered by either UAV 106 or USS / UTM 157.

[0079] Further embodiments are directed to NAS-based identifier provisioning. In one embodiment, this embodiment is based on 3GPP TR23.754, a portion of which... Figure 4 As illustrated in the diagram. In one embodiment, UAV 106 undergoes a registration and authorization process (see box 402) and requests the establishment of a PDU session (see box 404).

[0080] In some implementations, the steps of the procedure in Clause 6.5.3.1 of TR23.754 are modified as disclosed herein:

[0081] At step 12d, if provided, USS / UTM 157 verifies (see box 406) the PDU establishment request based on the CAA-level UAV identifier, the permanent device identifier (“PEI”), and the flight authorization identifier.

[0082] In one embodiment, USS / UTM 157 determines Remote Identification and Tracking Information (“RITI”) for use by UAV 106. This may include a new initial CAA-level UAV identifier (e.g., a temporary identifier for remote identification) used as a means of remotely identifying UAV 106, an update interval, hash chain length, and authorization data that may include the certified regions and times in which UAV 106 can operate, UAV 106 type, and so on.

[0083] In one embodiment, the USS / UTM 157 generates a hash chain up to the hash chain length starting from the initial CAA-level UAV identifier (see [link to relevant documentation]). Figure 2 And update the identifier in use according to the update interval, by starting from the last identifier in the hash chain and then moving towards the initial UAV identifier with each update interval, so that the USS / UTM 157 always knows the UAV identifier currently assigned to UAV 106.

[0084] In one embodiment, the time when the USS / UTM 157 needs to provide a new initial CAA-level UAV identifier (e.g., the time that triggers a hash chain reset or restart) is determined by multiplying the hash chain length by the update interval. The update interval and hash chain length can be independent parameters of the RITI. The USS / UTM 157 can also determine authorization data containing information about user plane connectivity between UAV 106 and UAV controller 108. Some RITI information, such as the CAA-level UAV identifier, is received and stored by the UFES 155 along with the authorization data.

[0085] As part of step 12e, USS / UTM 157 sends (see message passing 408) a UAV operation acceptance containing authorization data and RITI to UFES 155, which may also include the update interval and hash chain length. The authorization data may include pairing information between the authorized UAV 106 and UAV controller 108, for example, including the identifier of the UAV controller 108 controlling UAV 106 or the identifier of the UAV 106 controlled by UAV controller 108.

[0086] At step 12f, UFES 155 sends (see message 410) a UAV operation acceptance containing authorization data and RITI to USS / UTM 157, which may also include the update interval and hash chain length. UFES 155 can store the mapping between CAA-level UAV identifiers, 3GPP UAV identifiers, authorization data, and RITI. UFES 155 can generate hash chains up to the hash chain length (see...). Figure 2And by starting with the last identifier in the hash chain and then moving toward the initial UAV identifier with each update interval, the UAV identifier being used is updated according to the update interval, so that UFES 155 always knows the UAV identifier currently assigned to UAV 106 at any given time.

[0087] Secondary authorization (see box 412) can be performed during PDU session establishment, which can provide GPSI to USS / UTM 157 for authorizing pairing of UAV 106 and UAV controller 108, and for flight path authorization / registration for flight operations. In one embodiment, USS / UTM 157 can assign RITI information as part of secondary authorization. At step 14, SMF 145 configures (see box 414) user plane connectivity for communication between UAV 106 and UAV controller 108.

[0088] At step 15, the PDU session is successfully established after the UAV operation request from USS / UTM 157 is accepted and / or a secondary authorization is successful. SMF 145 forwards the RITI (see Message Passing 416) to UAV 106 within the Protocol Configuration Options (“PCO”) of the Session Management Message, which may include the update interval and hash chain length. UAV 106 can generate hash chains up to the hash chain length (see [link to relevant documentation]). Figure 2 And the UAV identifier being used can be updated according to the update interval by starting from the last identifier in the hash chain and then moving towards the initial UAV identifier with each update interval, for example, the identifier assigned to UAV 106.

[0089] At step 16, UAV 106 broadcasts (see box 418) remote identification information for remote identification based on RITI information and the current UAV identifier assigned to UAV 106. At step 17, UAV 106 sends (see message 420) remote identification information to USS / UTM 157 based on RITI information and the currently assigned UAV identifier.

[0090] In some embodiments, when USS / UTM 157 assumes that UAV 106 has reached the beginning of the hash chain, for example, when a timer in US / UTM 157 reaches the update interval multiplied by the hash chain length, USS / UTM 157 and / or UFES 155 do not generate a hash chain and simply update UAV 106 with a new initial UAV identifier, update interval, and maximum hash chain length.

[0091] In some embodiments, the USS / UTM 157 and / or UFES 155 generate a (pseudo) random list of identifiers and send the list of identifiers along with the update interval to the UAV 106.

[0092] In a further embodiment, USS / UTM 157 and / or UFES 155, in response to a request from UAV 106, generate at least one of the following information elements: initial UAV identifier, update interval, and / or maximum hash chain length.

[0093] In some embodiments, the initial UAV identifier, update interval, and maximum hash chain length are pre-configured in UAV 106 and USS / UTM 157 and / or UFES 155.

[0094] In some embodiments, when the initial UAV identifier is reached, USS / UTM 157 and / or UFES 155 and UAV 106 do not update, recreate, regenerate, etc., the hash chain, but instead restart with the last entry in the hash chain.

[0095] In various embodiments, USS / UTM 157 and / or UFES 155 and UAV 106 do not follow a static update interval but instead follow a pattern of infrequently updating the UAV identifier to the next identifier in the hash chain. This infrequent pattern can be configured or provisioned on UAV 106.

[0096] In a further embodiment, USS / UTM 157 and / or UFES 155 send at least one of the following information elements to UAV controller 108 in a manner similar to UAV 106: initial UAV identifier, update interval, and / or maximum hash chain length.

[0097] Figure 5 An embodiment for initial identifier refresh based on NAS is described, which can be based on Figure 4 The process described herein can assume that the initial identifier (e.g., CAA-level UAV ID) is already supplied within or with RITI. The process can be triggered by USS / UTM 157, for example, starting from step 3d, but is shown below to be triggered by UAV 106:

[0098] In step 1, in one embodiment, when UAV 106 detects that it is approaching the beginning of the hash chain, for example, the hash chain is reaching or has already reached the initial identifier (e.g., a CAA-level UAV identifier), it sends a NAS request with a UAV operation request to SMF 145 (see message passing 502). The UAV operation request may instruct UAV 106 to be supplied with at least a new initial identifier. UAV 106 may also be supplied with a new update interval and hash chain length. Whether the update interval and hash chain length are changed, adjusted, modified, etc., can be determined based on the configuration of USS / UTM 157.

[0099] At step 2, in one embodiment, SMF 145 selects (see box 504) USS / UTM 157 based on previous registration. At step 3a, in one embodiment, SMF 145 sends (see messaging 506) a UAV operation request to UFES 155. At step 3b, in one embodiment, UFES 155 recognizes that the UAV operation request is to update the initial identifier and selects (see box 508) USS / UTM 157 based on previous registration.

[0100] At step 3c, in one embodiment, UFES 155 sends a UAV operation request to the selected USS / UTM 157 (see Message Passing 510). At step 3d, in one embodiment, USS / UTM 157 verifies the request based on the currently used CAA-level UAV identifier and PEI (see Box 512).

[0101] Based on PEI, in some embodiments, USS / UTM 157 selects the current hash chain and verifies the received CAA-level UAV identifier currently assigned to UAV 106. In various embodiments, USS / UTM 157 determines the RITI for UAV 106, which may include a new initial CAA-level UAV identifier (e.g., a temporary identifier for remote identification) used as a means of remotely identifying UAV 106 and may include a new update interval and hash chain length.

[0102] USS / UTM 157 can generate hash chains up to the hash chain length starting from the initial CAA-level UAV identifier (see [link]). Figure 2The system updates the UAV identifier in use according to the update interval, starting from the last identifier in the hash chain and then moving towards the initial UAV identifier with each update interval. This ensures that the USS / UTM 157 knows at any given time which UAV 106 is currently using or assigned. The hash chain length, multiplied by the update interval, indicates when the USS needs to provide a new initial CAA-level UAV identifier. The update interval and hash chain length can be independent parameters of RITI. Some RITI information, such as the CAA-level UAV identifier, can be received and stored by the UFES 155 along with the authorization data.

[0103] At step 3e, in one embodiment, USS / UTM 157 sends (see message passing 514) a UAV operation acceptance message containing authorization data and RITI to UFES 155, which may include an update interval and hash chain length. At step 3f, in one embodiment, UFES 155 sends (see message passing 516) a UAV operation acceptance message containing authorization data and RITI to USS / UTM 157, which may include an update interval and hash chain length.

[0104] In one embodiment, the UFES 155 can store the mapping between CAA-level UAV identifiers, 3GPP UAV identifiers, authorization data, and RITI. The UFES 155 can generate hash chains up to a hash chain length (see [link to relevant documentation]). Figure 2 Furthermore, the UFES 155 can update the UAV identifier being used or assigned according to the update interval by starting from the last identifier in the hash chain and moving towards the initial UAV identifier with each update interval, so that the UAV 106 knows which UAV identifier is being used or assigned.

[0105] In step 4, in one embodiment, SMF 145 forwards the RITI (see Message Passing 518) to UAV 106 within the PCO of the Session Management message, which may include an update interval and a hash chain length. UAV 106 can generate hash chains up to the hash chain length (see...). Figure 2 ), and can update the UAV identifier being used or assigned to UAV 106 by starting from the last identifier in the hash chain and then moving toward the initial UAV identifier with each update interval.

[0106] In step 5, in one embodiment, UAV 106 broadcasts (see box 520) remote identification information for remote identification based on RITI information and the current UAV identifier. In step 6, in one embodiment, UAV 106 sends (see box 522) remote identification information to USS / UTM 157 based on RITI information and the current UAV identifier. In step 7, UAV 106 communicates with UAV controller 108 (see message passing 524).

[0107] Figure 6 User equipment device 600, which can be used for dynamic user equipment identifier assignment according to embodiments of the present disclosure, is depicted. In various embodiments, user equipment device 600 is used to implement one or more of the solutions described above. User equipment device 600 may be an embodiment of the remote unit 105, UE 205, UAV 106, and / or UAV controller 108 described above. Furthermore, user equipment device 600 may include processor 605, memory 610, input device 615, output device 620, and transceiver 625.

[0108] In some embodiments, input device 615 and output device 620 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 600 may not include any input device 615 and / or output device 620. In various embodiments, user equipment device 600 may include one or more of the following: processor 605, memory 610, and transceiver 625, and may not include input device 615 and / or output device 620.

[0109] As depicted, transceiver 625 includes at least one transmitter 630 and at least one receiver 635. In some embodiments, transceiver 625 communicates with one or more cells (or radio coverage areas) supported by one or more basic units 121. In various embodiments, transceiver 625 may operate on unlicensed spectrum. Furthermore, transceiver 625 may include multiple UE panels supporting one or more beams. Additionally, transceiver 625 may support at least one network interface 640 and / or application interface 645. Application interface 645 may support one or more APIs. Network interface 640 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 640 may be supported, as will be understood by those skilled in the art.

[0110] In one embodiment, processor 605 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 605 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 605 executes instructions stored in memory 610 to perform the methods and routines described herein. Processor 605 is communicatively coupled to memory 610, input device 615, output device 620, and transceiver 625. In some embodiments, processor 605 may include an application processor (also referred to as a “main processor”) that manages application domain and operating system (“OS”) functions, and a baseband processor (also referred to as a “baseband radio processor”) that manages radio functions.

[0111] In various embodiments, transceiver 625 and processor 605 control user equipment device 600 to implement the UE behavior described above. In one embodiment, transceiver 625 receives an initial identifier for the UE device from a mobile wireless communication network at the UE device. In one embodiment, processor 605 generates a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0112] In one embodiment, processor 605 assigns the last generated identifier in the identifier chain to the UE device. In another embodiment, processor 605 periodically assigns different identifiers from the identifier chain to the UE device, including identifiers in the identifier chain used to generate the identifier currently assigned to the UE.

[0113] In one embodiment, transceiver 625 receives from a mobile wireless communication network at least one of the following: the maximum number of identifiers generated for the identifier chain, and the periodic interval for periodically assigning different identifiers from the identifier chain to the UE device.

[0114] In one embodiment, processor 605 regenerates multiple identifiers in the identifier chain in response to the assigned identifier being within a threshold number of identifiers of the initial identifiers in the identifier chain. In one embodiment, transceiver 625 sends a Non-Access Stratum (“NAS”) message to the mobile wireless communication network to request the regeneration of the identifier chain in response to the assigned identifier being within a threshold number of identifiers of the initial identifiers in the identifier chain and before regenerating multiple identifiers in the identifier chain.

[0115] In one embodiment, memory 610 is a computer-readable storage medium. In some embodiments, memory 610 includes volatile computer storage media. For example, memory 610 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 610 includes non-volatile computer storage media. For example, memory 610 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 610 includes both volatile and non-volatile computer storage media.

[0116] In some embodiments, memory 610 stores data related to dynamic user equipment identifier assignment. For example, memory 610 may store various parameters, panel / beam configurations, resource assignments, policies, identifiers, etc., as described above. In some embodiments, memory 610 also stores program code and related data, such as an operating system or other controller algorithms running on user equipment device 600.

[0117] In one embodiment, input device 615 may include any known computer input device, including a touch panel, button, keyboard, stylus, microphone, etc. In some embodiments, input device 615 may be integrated with output device 620, such as a touchscreen or similar touch-sensitive display. In some embodiments, input device 615 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 615 includes two or more different devices, such as a keyboard and a touch panel.

[0118] In one embodiment, output device 620 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 620 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 620 may include a wearable display, such as a smartwatch, smart glasses, head-up display, etc., that is separate from but communicatively coupled to the rest of user equipment device 600. Furthermore, output device 620 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0119] In some embodiments, output device 620 includes one or more speakers for generating sound. For example, output device 620 may generate an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 620 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 620 may be integrated with input device 615. For example, input device 615 and output device 620 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 620 may be located near input device 615.

[0120] Transceiver 625 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 625 operates under the control of processor 605 to transmit and receive messages, data, and other signals. For example, processor 605 may selectively activate transceiver 625 (or a portion thereof) at specific times to transmit and receive messages.

[0121] Transceiver 625 includes at least a transmitter 630 and at least one receiver 635. One or more transmitters 630 can be used to provide UL communication signals to base unit 121, such as the UL transmissions described herein. Similarly, one or more receivers 635 can be used to receive DL communication signals from base unit 121, as described herein. Although only one transmitter 630 and one receiver 635 are illustrated, user equipment device 600 can have any suitable number of transmitters 630 and receivers 635. Furthermore, transmitters 630 and receivers 635 can be of any suitable type. In one embodiment, transceiver 625 includes a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum.

[0122] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 625, transmitters 630, and receivers 635 may be implemented as physically separate components accessing shared hardware resources and / or software resources (such as, for example, network interface 640).

[0123] In various embodiments, one or more transmitters 630 and / or one or more receivers 635 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an ASIC, or other type of hardware component. In some embodiments, one or more transmitters 630 and / or one or more receivers 635 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components, such as a network interface 640 or other hardware components / circuit, may be integrated with any number of transmitters 630 and / or receivers 635 into a single chip. In such embodiments, transmitters 630 and receivers 635 may be logically configured as transceivers 625 using a plurality of common control signals, or configured as modular transmitters 630 and receivers 635 implemented in the same hardware chip or multi-chip module.

[0124] Figure 7 A network device 700, which can be used for dynamic user equipment identifier assignment according to embodiments of the present disclosure, is depicted. In one embodiment, the network device 700 may be an implementation of a RAN node, such as the basic unit 121, RAN node 210, or gNB described above. Furthermore, the basic network device 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725.

[0125] In some embodiments, input device 715 and output device 720 are combined into a single device, such as a touchscreen. In some embodiments, network device 700 may not include any input device 715 and / or output device 720. In various embodiments, network device 700 may include one or more of the following: processor 705, memory 710, and transceiver 725, and may not include input device 715 and / or output device 720.

[0126] As depicted, transceiver 725 includes at least one transmitter 730 and at least one receiver 735. Here, transceiver 725 communicates with one or more remote units 105. Furthermore, transceiver 725 may support at least one network interface 740 and / or application interface 745. Application interface 745 may support one or more APIs. Network interface 740 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 740 may be supported, as will be understood by those skilled in the art.

[0127] In one embodiment, processor 705 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 705 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. In some embodiments, processor 705 executes instructions stored in memory 710 to perform the methods and routines described herein. Processor 705 is communicatively coupled to memory 710, input device 715, output device 720, and transceiver 725. In some embodiments, processor 705 may include an application processor (also referred to as a "main processor") that manages application domain and operating system ("OS") functions, and a baseband processor (also referred to as a "baseband radio processor") that manages radio functions.

[0128] In various embodiments, network device 700 is the USS / UTM 157 and / or UFES 155 as described above. In such embodiments, transceiver 725 transmits an initial identifier for the UE device from a mobile wireless communication network, such as the USS / UTM 157, to a user equipment (“UE”) device. In one embodiment, processor 705 generates a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0129] In one embodiment, the processor 705 associates the last generated identifier in the identifier chain with the UE device. In another embodiment, the processor 705 periodically associates different identifiers with the UE device from the identifier chain, including identifiers in the identifier chain used to generate the identifier currently associated with the UE.

[0130] In one embodiment, transceiver 725 sends to the UE device at least one of the following: the maximum number of identifiers generated for the identifier chain, and an update interval for periodically associating different identifiers from the identifier chain with the UE device.

[0131] In one embodiment, processor 705 regenerates multiple identifiers in the identifier chain in response to an associated identifier being within a threshold number of identifiers in the initial identifier chain. In one embodiment, transceiver 725 receives a non-access stratum (“NAS”) message from the UE device to request the regeneration of the identifier chain in response to an associated identifier being within a threshold number of identifiers in the initial identifier chain.

[0132] In one embodiment, memory 710 is a computer-readable storage medium. In some embodiments, memory 710 includes volatile computer storage media. For example, memory 710 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 710 includes non-volatile computer storage media. For example, memory 710 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 710 includes both volatile and non-volatile computer storage media.

[0133] In some embodiments, memory 710 stores data related to dynamic user equipment identifier assignment. For example, memory 710 may store parameters, configurations, resource assignments, policies, identifiers, etc., as described above. In some embodiments, memory 710 also stores program code and related data, such as an operating system or other controller algorithms running on network device 700.

[0134] In one embodiment, input device 715 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 715 may be integrated with output device 720, such as a touchscreen or similar touch-sensitive display. In some embodiments, input device 715 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 715 includes two or more different devices, such as a keyboard and a touch panel.

[0135] In one embodiment, output device 720 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 720 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 720 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 720 may include a wearable display, such as a smartwatch, smart glasses, head-up display, etc., that is separate from but communicatively coupled to the rest of network device 700. Furthermore, output device 720 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0136] In some embodiments, output device 720 includes one or more speakers for generating sound. For example, output device 720 may generate an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 720 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 720 may be integrated with input device 715. For example, input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 720 may be located near input device 715.

[0137] Transceiver 725 includes at least a transmitter 730 and at least one receiver 735. One or more transmitters 730 can be used to communicate with a UE, as described herein. Similarly, one or more receivers 735 can be used to communicate with network functions in a PLMN and / or RAN, as described herein. Although only one transmitter 730 and one receiver 735 are shown, the network device 700 can have any suitable number of transmitters 730 and receivers 735. Furthermore, the transmitters 730 and receivers 735 can be of any suitable type.

[0138] Figure 8 This is a flowchart of a method 800 for dynamic user equipment identifier assignment. Method 800 can be executed by a UE as described herein, such as remote unit 105, UE 205, UAV 106, UAV controller 108, and / or user equipment device 600. In some embodiments, method 800 can be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0139] In one embodiment, method 800 includes receiving 805 an initial identifier for the UE device from a mobile wireless communication network at a user equipment (“UE”) device. In another embodiment, method 800 includes generating 810 plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0140] In one embodiment, method 800 includes assigning the last generated identifier in an identifier chain to the UE device. In another embodiment, method 800 includes periodically assigning 820 different identifiers from the identifier chain to the UE device, wherein the different identifiers include identifiers in the identifier chain used to generate the identifier currently assigned to the UE. Method 800 ends.

[0141] Figure 9This is a flowchart of a method 900 for dynamic user equipment identifier assignment. Method 900 can be performed by a network function and / or network device device 900, such as a USS / UTM 157, UFES 155, etc. In some embodiments, method 900 can be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0142] In one embodiment, method 900 includes sending 905 an initial identifier for the UE device from a mobile wireless communication network to a user equipment (“UE”) device. In another embodiment, method 900 includes generating 910 plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0143] In one embodiment, method 900 includes associating the last generated identifier in the identifier chain with the UE device 915. In another embodiment, method 900 includes periodically associating different identifiers with the UE device from the identifier chain, wherein the different identifiers include identifiers in the identifier chain used to generate the identifier currently associated with the UE. Method 900 ends.

[0144] A first means for dynamic user equipment identifier assignment is disclosed. The first means may include a UE as described herein, such as remote unit 105, UE 205, UAV 106, UAV controller 108, and / or user equipment device 600. In some embodiments, the first means includes a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0145] In one embodiment, the first device includes a transceiver that receives an initial identifier for the UE device from a mobile wireless communication network at a user equipment (“UE”) device. In another embodiment, the first device includes a processor that generates a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0146] In one embodiment, the processor assigns the last generated identifier in the identifier chain to the UE device. In another embodiment, the processor periodically assigns different identifiers from the identifier chain to the UE device, including identifiers in the identifier chain used to generate the identifier currently assigned to the UE.

[0147] In one embodiment, the transceiver receives from the mobile wireless communication network at least one of the following: the maximum number of identifiers generated for the identifier chain, and the update interval for periodically assigning different identifiers from the identifier chain to the UE device.

[0148] In one embodiment, the processor regenerates multiple identifiers in the identifier chain in response to the assigned identifier being within a threshold number of identifiers in the initial identifier chain. In another embodiment, the transceiver sends a Non-Access Stratum (“NAS”) message to the mobile wireless communication network to request the regeneration of the identifier chain in response to the assigned identifier being within a threshold number of identifiers in the initial identifier chain and before regenerating multiple identifiers in the identifier chain.

[0149] In one embodiment, an initial identifier for the UE is received from the mobile wireless communication network in a Non-Access Stratum (“NAS”) message. In one embodiment, the UE device includes an unmanned aerial vehicle (“UAV”), and the identifier includes at least one of the following: a temporary UAV identifier, a Civil Aviation Administration (“CAA”) level UAV identifier, a remote identifier, a broadcast remote identifier, and an external identifier. In one embodiment, each of the plurality of identifiers is generated using at least one hash function, said at least one hash function being the same between the UE device and the mobile wireless communication network.

[0150] A first method for dynamic user equipment identifier assignment is disclosed. The first method can be performed by a UE as described herein, such as remote unit 105, UE 205, UAV 106, UAV controller 108, and / or user equipment device 600. In some embodiments, the first method can be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0151] In one embodiment, the first method includes receiving an initial identifier for the UE device from a mobile wireless communication network at the user equipment (“UE”) device. In another embodiment, the first method includes generating a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0152] In one embodiment, the first method includes assigning the last generated identifier in the identifier chain to the UE device. In another embodiment, the first method includes periodically assigning different identifiers from the identifier chain to the UE device, wherein the different identifiers include identifiers in the identifier chain used to generate the identifier currently assigned to the UE.

[0153] In one embodiment, the first method includes receiving from a mobile wireless communication network a maximum number of identifiers generated for an identifier chain. In another embodiment, the first method includes receiving from the mobile wireless communication network an update interval for periodically assigning different identifiers from the identifier chain to a UE device.

[0154] In one embodiment, the first method includes regenerating a plurality of identifiers in the identifier chain in response to the assigned identifier being within a threshold number of identifiers of the initial identifiers in the identifier chain. In another embodiment, the first method includes sending a non-access stratum (“NAS”) message to the mobile wireless communication network to request the regeneration of the identifier chain in response to the assigned identifier being within a threshold number of identifiers of the initial identifiers in the identifier chain and before regenerating the plurality of identifiers in the identifier chain.

[0155] In one embodiment, an initial identifier for the UE is received from the mobile wireless communication network in a Non-Access Stratum (“NAS”) message. In one embodiment, the UE device includes an unmanned aerial vehicle (“UAV”) and the identifier includes at least one of the following: a temporary UAV identifier, a Civil Aviation Administration (“CAA”) level UAV identifier, a remote identifier, a broadcast remote identifier, and an external identifier. In one embodiment, each of the plurality of identifiers is generated using at least one hash function, wherein the at least one hash function is the same between the UE device and the mobile wireless communication network.

[0156] A second means for assigning dynamic user equipment identifiers is disclosed. The second means may include network functions such as USS / UTM 157, UFES 155, etc., and / or network device means 900. In some embodiments, method 900 may be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0157] In one embodiment, the second device includes a transceiver that transmits an initial identifier for the UE device from a mobile wireless communication network to a user equipment (“UE”) device. In another embodiment, the second device includes a processor that generates a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0158] In one embodiment, the processor associates the last generated identifier in the identifier chain with the UE device. In another embodiment, the processor periodically associates different identifiers with the UE device from the identifier chain, including identifiers in the identifier chain used to generate the identifier currently associated with the UE.

[0159] In one embodiment, the transceiver sends to the UE device at least one of the following: the maximum number of identifiers generated for the identifier chain, and the update interval for periodically associating different identifiers from the identifier chain with the UE device.

[0160] In one embodiment, the processor regenerates multiple identifiers in the identifier chain in response to an associated identifier being within a threshold number of identifiers in the initial identifier chain. In another embodiment, the transceiver receives a Non-Access Stratum (“NAS”) message from the UE device to request the regeneration of the identifier chain in response to an associated identifier being within a threshold number of identifiers in the initial identifier chain.

[0161] In one embodiment, an initial identifier for the UE is sent from the mobile wireless communication network in a Non-Access Stratum (“NAS”) message. In one embodiment, the UE device includes an unmanned aerial vehicle (“UAV”), and the identifier includes at least one of the following: a temporary UAV identifier, a Civil Aviation Administration (“CAA”) level UAV identifier, a remote identifier, a broadcast remote identifier, and an external identifier. In one embodiment, each of the plurality of identifiers is generated using at least one hash function, wherein the at least one hash function is the same between the UE device and the mobile wireless communication network.

[0162] A second method for dynamic user equipment identifier assignment is disclosed. This second method can be performed by a network function and / or network device device 900, such as a USS / UTM157, UFES155, etc. In some embodiments, the second method can be performed by a processor executing program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0163] In one embodiment, the second method includes sending an initial identifier for the UE device from a mobile wireless communication network to a user equipment (“UE”) device. In another embodiment, the second method includes generating a plurality of identifiers for the UE device based on the initial identifier, wherein each of the plurality of identifiers is generated based on a previous identifier to form an identifier chain.

[0164] In one embodiment, the second method includes associating the last generated identifier in the identifier chain with the UE device. In another embodiment, the second method includes periodically associating different identifiers with the UE device from the identifier chain, wherein the different identifiers include identifiers in the identifier chain used to generate the identifier currently associated with the UE.

[0165] In one embodiment, the second method includes sending the maximum number of identifiers generated for the identifier chain to the UE device. In another embodiment, the second method includes sending the UE device an update interval for periodically associating different identifiers from the identifier chain with the UE device.

[0166] In one embodiment, the second method includes regenerating a plurality of identifiers in the identifier chain in response to an associated identifier being within a threshold number of identifiers of the initial identifiers in the identifier chain. In one embodiment, the second method includes receiving a non-access stratum (“NAS”) message from a UE device to request the regeneration of the identifier chain in response to an associated identifier being within a threshold number of identifiers of the initial identifiers in the identifier chain.

[0167] In one embodiment, an initial identifier for the UE is sent from the mobile wireless communication network in a Non-Access Stratum (“NAS”) message. In one embodiment, the UE device includes an unmanned aerial vehicle (“UAV”), and the identifier includes at least one of the following: a temporary UAV identifier, a Civil Aviation Administration (“CAA”) level UAV identifier, a remote identifier, a broadcast remote identifier, and an external identifier. In one embodiment, each of the plurality of identifiers is generated using at least one hash function, said at least one hash function being the same between the UE device and the mobile wireless communication network.

[0168] The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations within the equivalent meaning and scope of the claims should be covered within their scope.

Claims

1. A User Equipment (UE) device, comprising: A transceiver that receives an initial identifier for the UE device from a mobile wireless communication network; as well as Processor, the processor: At least one hash function is used to generate a plurality of identifiers for the UE device based on the initial identifier, each of the plurality of identifiers being generated based on a previous identifier to form an identifier chain, wherein the initial identifier and the at least one hash function are identical between the UE device and the mobile wireless communication network; The last generated identifier in the identifier chain is assigned to the UE device; and Different identifiers are periodically assigned from the identifier chain to the UE device, the different identifiers including identifiers in the identifier chain used to generate the identifier currently assigned to the UE device, wherein the update interval of the different identifiers is the same as the update interval at which the mobile wireless communication network associates different identifiers with the UE device.

2. The UE device according to claim 1, wherein, The transceiver receives from the mobile wireless communication network at least one of the following: a maximum number of identifiers generated for the identifier chain, and an update interval for periodically assigning the different identifiers from the identifier chain to the UE device.

3. The UE device according to claim 1, wherein, The processor, in response to the assigned identifier within a threshold number of the initial identifiers in the identifier chain, regenerates the plurality of identifiers in the identifier chain.

4. The UE device according to claim 3, wherein, The transceiver, in response to the assigned identifier being within a threshold number of the initial identifiers in the identifier chain and before regenerating the plurality of identifiers in the identifier chain, sends a Non-Access Stratum (NAS) message to the mobile wireless communication network to request the regeneration of the identifier chain.

5. The UE device according to claim 1, wherein, The initial identifier for the UE is received from the mobile wireless communication network in a Non-Access Stratum (NAS) message.

6. The UE device according to claim 1, wherein, The UE device includes an unmanned aerial vehicle (UAV), and the identifier includes at least one of the following: a temporary UAV identifier, a Civil Aviation Administration of China (CAA) level UAV identifier, a remote identifier, a broadcast remote identifier, and an external identifier.

7. A mobile wireless communication network device, comprising: A transceiver that sends an initial identifier for the user equipment (UE) device to the UE device; as well as Processor, the processor: At least one hash function is used to generate a plurality of identifiers for the UE device based on the initial identifier, each of the plurality of identifiers being generated based on a previous identifier to form an identifier chain, wherein the initial identifier and the at least one hash function are identical between the UE device and the mobile wireless communication network; Associate the last generated identifier in the identifier chain with the UE device; as well as Different identifiers are periodically associated with the UE device from the identifier chain, the different identifiers including identifiers in the identifier chain used to generate the identifier currently associated with the UE device, wherein the update interval of the different identifiers is equal to the update interval of the identifier assigned to the UE device.

8. The mobile wireless communication network apparatus according to claim 7, wherein, The transceiver sends to the UE device at least one of the following: the maximum number of identifiers generated for the identifier chain, and an update interval for periodically associating the different identifiers from the identifier chain with the UE device.

9. The mobile wireless communication network apparatus according to claim 7, wherein, The processor, in response to an associated identifier, regenerates the plurality of identifiers in the identifier chain within a threshold number of the initial identifiers in the identifier chain.

10. The mobile wireless communication network apparatus according to claim 9, wherein, The transceiver receives a Non-Access Stratum (NAS) message from the UE device in response to an associated identifier within a threshold number of identifiers of the initial identifier in the identifier chain, requesting the regeneration of the identifier chain.

11. The mobile wireless communication network apparatus according to claim 7, wherein, The initial identifier for the UE is sent from the mobile wireless communication network in a Non-Access Stratum (NAS) message.

12. The mobile wireless communication network apparatus according to claim 7, wherein, The UE device includes an unmanned aerial vehicle (UAV), and the identifier includes at least one of the following: a temporary UAV identifier, a Civil Aviation Administration of China (CAA) level UAV identifier, a remote identifier, a broadcast remote identifier, and an external identifier.

13. A method performed by a user equipment (UE) device, comprising: Receive an initial identifier for the UE device from the mobile wireless communication network; At least one hash function is used to generate a plurality of identifiers for the UE device based on the initial identifier, each of the plurality of identifiers being generated based on a previous identifier to form an identifier chain, wherein the initial identifier and the at least one hash function are identical between the UE device and the mobile wireless communication network; Assign the last generated identifier in the identifier chain to the UE device; as well as Different identifiers are periodically assigned from the identifier chain to the UE device, the different identifiers including identifiers in the identifier chain used to generate the identifier currently assigned to the UE device, wherein the update interval of the different identifiers is the same as the update interval at which the mobile wireless communication network associates different identifiers with the UE device.

Images