Patent Description:
The subject matter disclosed herein relates generally to wireless communications and more particularly relates to dynamic user equipment identifier assignment. There is described herein a user equipment device, a network apparatus, and a method performed by a user equipment device.

In certain wireless communication systems, a User Equipment device ("UE") is able to connect with a fifth-generation ("<NUM>") core network (i.e., "5GC") in a Public Land Mobile Network ("PLMN") In wireless networks, unmanned aerial vehicles ("UAVs") communicate with each other and send broadcast information over the UAV to UAV ("U2U") radio interface. If the sender identity does not change, it is easy to track a specific UAV by listening to the broadcast messages using the sender identity.

<CIT> describes a a method of operating a node for performing handover between access networks wherein a user has authenticated for network access in a first access network. The method comprises receiving from a home network a first session key and a temporary identifier allocated to the user for the duration of a communication session. The identifier is mapped to a second session key, and the mapped identifier and key are stored at the node. The second session key is sent to an access network, and the identifier to a user terminal. When the user terminal moves to a second access network, the node receives from the user terminal, in connection with a handover request, the identifier. The second session key mapped to the identifier is retrieved, and sent to the second access network. The method may further comprise deriving a plurality of identifiers from the received temporary identifier using a hash chain.

<CIT> describes protecting the confidentiality and/or integrity of NSSAI exchanged during initial registration while minimizing overhead incurred for an AMF relocation procedure.

<CIT> describes a server and a terminal that share a first hash function H and an initial value S(k, <NUM>) unique to each terminal, such that the same temporary ID is calculated at the server and the terminal.

Claim <NUM> defines a user equipment device, claim <NUM> defines a network apparatus, claim <NUM> defines a method performed by a user equipment device. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention.

Disclosed are procedures for dynamic user equipment identifier assignment. Said procedures may be implemented by apparatus, systems, methods, and/or computer program products.

One apparatus includes a transceiver that receives, at a user equipment ("UE") device, an initial identifier for the UE device from a mobile wireless communication network and a processor 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 an identifier that was generated last in 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 comprising an identifier in the chain of identifiers that is used to generate the identifier that is currently assigned to the UE.

Another apparatus includes a transceiver that sends, to a user equipment ("UE") device from a mobile wireless communication network, an initial identifier for the UE device and a processor 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, associates an identifier that was generated last in the chain of identifiers with the UE device, and periodically associates a different identifier with the UE device from the chain of identifiers, the different identifier comprising an identifier in the chain of identifiers that is used to generate the identifier that is currently associated with the UE.

Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN"), wireless LAN ("WLAN"), or a wide area network ("WAN"), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider ("ISP")).

As used herein, "a member selected from the group consisting of A, B, and C and combinations thereof" 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.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.

Generally, the present disclosure describes systems, methods, and apparatus for dynamic user equipment identifier assignment. In certain embodiments, the methods may be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.

In conventional unmanned aerial vehicles ("UAV") systems, UAVs communicate with each other and send broadcast information over the UAV to UAV ("U2U") radio interface. If the sender identity does not change, it is easy to track a specific UAV by listening to the broadcast messages using the sender identity. In certain embodiments, if the sender simply randomizes the identifier, e.g., like in vehicle-to-everything ("V2X") broadcast communication, then an unmanned aerial system ("UAS") service supplier ("USS") and UAS traffic management ("UTM") would not know at a certain point in time the real identity of a potentially misbehaving UAV.

The proposed solutions described herein generate a hash chain, which looks like pseudo-random numbers when used in the opposite or reverse direction of the hash chain generation. Since both parties, e.g., the UAV and the wireless network function or node, go through the hash chain with the same update interval, the USS, UTM, UAV flight enablement subsystem ("UFES"), and/or the like, knows at any time the identity that the UAV is currently using or assigned.

<FIG> depicts a wireless communication system <NUM> for dynamic user equipment identifier assignment, according to embodiments of the disclosure. In one embodiment, the wireless communication system <NUM> includes at least one remote unit <NUM>, a Fifth-Generation Radio Access Network ("<NUM>-RAN") <NUM>, a mobile core network <NUM>, and a UAS <NUM>. The <NUM>-RAN <NUM> and the mobile core network <NUM> form a mobile communication network. The <NUM>-RAN <NUM> may be composed of a 3GPP access network <NUM> containing at least one cellular base unit <NUM> and/or a non-3GPP access network <NUM> containing at least one access point <NUM>. The remote unit <NUM> communicates with the 3GPP access network <NUM> using 3GPP communication links <NUM> and/or communicates with the non-3GPP access network <NUM> using non-3GPP communication links <NUM>. Even though a specific number of remote units <NUM>, 3GPP access networks <NUM>, cellular base units <NUM>, 3GPP communication links <NUM>, non-3GPP access networks <NUM>, access points <NUM>, non-3GPP communication links <NUM>, and mobile core networks <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM>, 3GPP access networks <NUM>, cellular base units <NUM>, 3GPP communication links <NUM>, non-3GPP access networks <NUM>, access points <NUM>, non-3GPP communication links <NUM>, and mobile core networks <NUM> may be included in the wireless communication system <NUM>.

In one implementation, the RAN <NUM> is compliant with the <NUM> system specified in the Third Generation Partnership Project ("3GPP") specifications. For example, the RAN <NUM> may be a NG-RAN, implementing NR RAT and/or LTE RAT. In another example, the RAN <NUM> may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers ("IEEE") <NUM>-family compliant WLAN). In another implementation, the RAN <NUM> is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access ("WiMAX") or IEEE <NUM>-family standards, among other networks.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. Moreover, the remote units <NUM> may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit ("WTRU"), a device, or by other terminology used in the art. In various embodiments, the remote unit <NUM> includes a subscriber identity and/or identification module ("SIM") and the mobile equipment ("ME") providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit <NUM> may include a terminal equipment ("TE") and/or be embedded in an appliance or device (e.g., a computing device, as described above).

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. Moreover, the remote units <NUM> may be referred to as UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit ("WTRU"), a device, or by other terminology used in the art.

The remote units <NUM> may communicate directly with one or more of the cellular base units <NUM> in the 3GPP access network <NUM> via uplink ("UL") and downlink ("DL") communication signals. Furthermore, the UL and DL communication signals may be carried over the 3GPP communication links <NUM>. Similarly, the remote units <NUM> may communicate with one or more access points <NUM> in the non-3GPP access network(s) <NUM> via UL and DL communication signals carried over the non-3GPP communication links <NUM>. Here, the access networks <NUM> and <NUM> are intermediate networks that provide the remote units <NUM> with access to the mobile core network <NUM>.

In some embodiments, the remote units <NUM> communicate with a remote host (e.g., in the data network <NUM> or in the data network <NUM>) via a network connection with the mobile core network <NUM>. For example, an application <NUM> (e.g., web browser, media client, telephone and/or Voice-over-Internet-Protocol ("VoIP") application) in a remote unit <NUM> may trigger the remote unit <NUM> to establish a protocol data unit ("PDU") session (or other data connection) with the mobile core network <NUM> via the <NUM>-RAN <NUM> (i.e., via the 3GPP access network <NUM> and/or non-3GPP network <NUM>). The mobile core network <NUM> then relays traffic between the remote unit <NUM> and the remote host using the PDU session. The PDU session represents a logical connection between the remote unit <NUM> and a User Plane Function ("UPF") <NUM>.

In order to establish the PDU session (or PDN connection), the remote unit <NUM> must be registered with the mobile core network <NUM> (also referred to as "attached to the mobile core network" in the context of a Fourth Generation ("<NUM>") system). Note that the remote unit <NUM> may establish one or more PDU sessions (or other data connections) with the mobile core network <NUM>. As such, the remote unit <NUM> may have at least one PDU session for communicating with the packet data network <NUM>. Additionally - or alternatively - the remote unit <NUM> may have at least one PDU session for communicating with the packet data network <NUM>. The remote unit <NUM> may establish additional PDU sessions for communicating with other data networks and/or other communication peers.

In the context of a <NUM> system ("5GS"), the term "PDU Session" refers to a data connection that provides end-to-end ("E2E") user plane ("UP") connectivity between the remote unit <NUM> and a specific Data Network ("DN") through the UPF <NUM>. A PDU Session supports one or more Quality of Service ("QoS") Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same <NUM> QoS Identifier ("5QI").

In the context of a <NUM>/LTE system, such as the Evolved Packet System ("EPS"), a Packet Data Network ("PDN") connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, i.e., a tunnel between the remote unit <NUM> and a Packet Gateway ("PGW", not shown) in the mobile core network <NUM>. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier ("QCI").

As described in greater detail below, the remote unit <NUM> may use a first data connection (e.g., PDU Session) established with the first mobile core network <NUM> to establish a second data connection (e.g., part of a second PDU session) with the second mobile core network <NUM>. When establishing a data connection (e.g., PDU session) with the second mobile core network <NUM>, the remote unit <NUM> uses the first data connection to register with the second mobile core network <NUM>.

The cellular base units <NUM> may be distributed over a geographic region. In certain embodiments, a cellular base unit <NUM> may also be referred to as an access terminal, a base, a base station, a Node-B ("NB"), an Evolved Node B (abbreviated as eNodeB or "eNB," also known as Evolved Universal Terrestrial Radio Access Network ("E-UTRAN") Node B), a <NUM>/NR Node B ("gNB"), a Home Node-B, a Home Node-B, a relay node, a device, or by any other terminology used in the art. The cellular base units <NUM> are generally part of a radio access network ("RAN"), such as the 3GPP access network <NUM>, that may include one or more controllers communicably coupled to one or more corresponding cellular base units <NUM>. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The cellular base units <NUM> connect to the mobile core network <NUM> via the 3GPP access network <NUM>.

The cellular base units <NUM> may serve a number of remote units <NUM> within a serving area, for example, a cell or a cell sector, via a 3GPP wireless communication link <NUM>. The cellular base units <NUM> may communicate directly with one or more of the remote units <NUM> via communication signals. Generally, the cellular base units <NUM> transmit DL communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the 3GPP communication links <NUM>. The 3GPP communication links <NUM> may be any suitable carrier in licensed or unlicensed radio spectrum. The 3GPP communication links <NUM> facilitate communication between one or more of the remote units <NUM> and/or one or more of the cellular base units <NUM>. Note that during NR operation on unlicensed spectrum (referred to as "NR-U"), the base unit <NUM> and the remote unit <NUM> communicate over unlicensed (i.e., shared) radio spectrum.

The non-3GPP access networks <NUM> may be distributed over a geographic region. Each non-3GPP access network <NUM> may serve a number of remote units <NUM> with a serving area. An access point <NUM> in a non-3GPP access network <NUM> may communicate directly with one or more remote units <NUM> by receiving UL communication signals and transmitting DL communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain. Both DL and UL communication signals are carried over the non-3GPP communication links <NUM>. The 3GPP communication links <NUM> and non-3GPP communication links <NUM> may employ different frequencies and/or different communication protocols. In various embodiments, an access point <NUM> may communicate using unlicensed radio spectrum. The mobile core network <NUM> may provide services to a remote unit <NUM> via the non-3GPP access networks <NUM>, as described in greater detail herein.

In some embodiments, a non-3GPP access network <NUM> connects to the mobile core network <NUM> via an interworking entity <NUM>. The interworking entity <NUM> provides an interworking between the non-3GPP access network <NUM> and the mobile core network <NUM>. The interworking entity <NUM> supports connectivity via the "N2" and "N3" interfaces. As depicted, both the 3GPP access network <NUM> and the interworking entity <NUM> communicate with the AMF <NUM> using a "N2" interface. The 3GPP access network <NUM> and interworking entity <NUM> also communicate with the UPF <NUM> using a "N3" interface. While depicted as outside the mobile core network <NUM>, in other embodiments the interworking entity <NUM> may be a part of the core network. While depicted as outside the non-3GPP RAN <NUM>, in other embodiments the interworking entity <NUM> may be a part of the non-3GPP RAN <NUM>.

In one embodiment, the UAS <NUM> comprises a components, networks, hardware, software, and/or the like for conducting unmanned aircraft operations between a UAV <NUM>, e.g., a drone, and a UAV controller <NUM>. The UAV <NUM> may refer to an aircraft without a human pilot, crew, or passengers that is remotely controlled using a UAV controller <NUM>. A UAV controller <NUM> may refer to device that is configured to wirelessly send instructions to the UAV <NUM> for controlling the UAV, e.g., for controlling the speed, direction, orientation, and/or the like of the UAV, e.g., via the mobile network <NUM>, an access network <NUM>, <NUM>, and/or the like. The UAS operator <NUM> may be the person who operates the UAV <NUM> (e.g., via the UAV controller <NUM>) and who, typically, requests flight authorizations. The UAV <NUM> and UAV controller <NUM> may each be UEs in the wireless communication system <NUM> and/or may include an instance of a remote unit <NUM>. As such, the UAV <NUM> and/or the UAV controller <NUM> may communicate with an access network <NUM> to access services provided by a mobile core network <NUM>.

In some embodiments, the UAV <NUM> and/or the UAV-C controller <NUM> communicates with a UFES <NUM> and/or a USS/UTM <NUM> function via a network connection with the mobile core network <NUM>. The USS/UTM <NUM>, in one embodiment, provides a set of overlapping USSs that assist UAV <NUM> operators <NUM> in conducting safe and compliant operations. The services may include de confliction of flight plans, remote identification, and/or the like.

As described below, the UAV <NUM> and/or UAV controller <NUM> may establish a PDU session (or similar data connection) with the mobile core network <NUM> using the RAN <NUM>. The mobile core network <NUM> may then relay traffic between the UAV <NUM> and the UAV controller <NUM> and the packet data network <NUM> using the PDU session.

In certain embodiments, a non-3GPP access network <NUM> may be controlled by an operator of the mobile core network <NUM> and may have direct access to the mobile core network <NUM>. Such a non-3GPP AN deployment is referred to as a "trusted non-3GPP access network. " A non-3GPP access network <NUM> is considered as "trusted" when it is operated by the 3GPP operator, or a 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 an operator (or trusted partner) of the mobile core network <NUM>, does not have direct access to the mobile core network <NUM>, or does not support the certain security features is referred to as a "non-trusted" non-3GPP access network. An interworking entity <NUM> deployed in a trusted non-3GPP access network <NUM> may be referred to herein as a Trusted Network Gateway Function ("TNGF"). An interworking entity <NUM> deployed in a non-trusted non-3GPP access network <NUM> may be referred to herein as a non-3GPP interworking function ("N3IWF"). While depicted as a part of the non-3GPP access network <NUM>, in some embodiments the N3IWF may be a part of the mobile core network <NUM> or may be located in the data network <NUM>.

In one embodiment, the mobile core network <NUM> is a <NUM> core ("5GC") or the evolved packet core ("EPC"), which may be coupled to a data network <NUM>, like the Internet and private data networks, among other data networks. A remote unit <NUM> may have a subscription or other account with the mobile core network <NUM>. Each mobile core network <NUM> belongs to a single public land mobile network ("PLMN").

The mobile core network <NUM> includes several network functions ("NFs"). As depicted, the mobile core network <NUM> includes at least one UPF ("UPF") <NUM>. The mobile core network <NUM> also includes multiple control plane functions including, but not limited to, an Access and Mobility Management Function ("AMF") <NUM> that serves the <NUM>-RAN <NUM>, a Session Management Function ("SMF") <NUM>, a Policy Control Function ("PCF") <NUM>, an Authentication Server Function ("AUSF") <NUM>, a Unified Data Management ("UDM")/Unified Data Repository function ("UDR") <NUM>, a USS/UTM <NUM>, and a UFES <NUM>.

The UPF(s) <NUM> is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network ("DN"), in the <NUM> architecture. The AMF <NUM> is responsible for termination of non-access stratum ("NAS") signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF <NUM> is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) IP address allocation & management, DL data notification, and traffic steering configuration for UPF for proper traffic routing.

The PCF <NUM> is responsible for unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR. The AUSF <NUM> acts as an authentication server.

The UDM is responsible for generation of Authentication and Key Agreement ("AKA") credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and can be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber-related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as combined entity "UDM/UDR" <NUM>.

In various embodiments, the mobile core network <NUM> may also include an Network Exposure Function ("NEF") (which is responsible for making network data and resources easily accessible to customers and network partners, e.g., via one or more APIs), a Network Repository Function ("NRF") (which provides NF service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces ("APIs")), or other NFs defined for the 5GC. In certain embodiments, the mobile core network <NUM> may include an authentication, authorization, and accounting ("AAA") server.

In various embodiments, the mobile core network <NUM> 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 <NUM> optimized for a certain traffic type or communication service. A network instance may be identified by a S-NSSAI, while a set of network slices for which the remote unit <NUM> is authorized to use is identified by NSSAI. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF and UPF <NUM>. In some embodiments, the different network slices may share some common network functions, such as the AMF <NUM>. The different network slices are not shown in <FIG> for ease of illustration, but their support is assumed.

Although specific numbers and types of network functions are depicted in <FIG>, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network <NUM>. Moreover, where the mobile core network <NUM> comprises an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as an MME, S-GW, P-GW, HSS, and the like.

While <FIG> depicts components of a <NUM> RAN and a <NUM> core network, the described embodiments for using a pseudonym for access authentication over non-3GPP access apply to other types of communication networks and RATs, including IEEE <NUM> variants, GSM, GPRS, UMTS, LTE variants, CDMA <NUM>, Bluetooth, ZigBee, Sigfoxx, and the like. For example, in an <NUM>/LTE variant involving an EPC, the AMF <NUM> may be mapped to an MME, the SMF mapped to a control plane portion of a PGW and/or to an MME, the UPF <NUM> may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR <NUM> may be mapped to an HSS, etc..

As depicted, a remote unit <NUM> (e.g., a UE) may connect to the mobile core network (e.g., to a <NUM> mobile communication network) via two types of accesses: (<NUM>) via 3GPP access network <NUM> and (<NUM>) via a non-3GPP access network <NUM>. The first type of access (e.g., 3GPP access network <NUM>) uses a 3GPP-defined type of wireless communication (e.g., NG-RAN) and the second type of access (e.g., non-3GPP access network <NUM>) uses a non-3GPP-defined type of wireless communication (e.g., WLAN). The <NUM>-RAN <NUM> refers to any type of <NUM> access network that can provide access to the mobile core network <NUM>, including the 3GPP access network <NUM> and the non-3GPP access network <NUM>.

As described above, UAVs <NUM> communicate with one another, with a UAV controller <NUM>, and/or the like, using broadcast messages. An issue is that if the UAV identifier is determined, unauthorized and/or other parties can track the UAV <NUM> and receive the broadcast messages. In one conventional solution to this problem, the UAV broadcast identifier is randomized to avoid tracking in a similar manner as in V2X. However, the problem with this solution is that, on the one hand, the tracking issue is resolved, but the USS/UTM <NUM> cannot relate the messages to a specific UAV anymore because it does not know the new randomly-generated identifier.

In another conventional solution, the USS/UTM <NUM> periodically assigns broadcast identities via application layer signaling, so that the USS/UTM <NUM> is aware of the broadcast identities that are in use. However, this solution has the drawback that signaling is heavily increased since all active UAVs <NUM> need to be periodically updated within a potentially short time interval.

To solve the problem of dynamically changing a UAVs <NUM> identity for broadcast and other communications, described above, the present disclosure proposes solutions where the UAV <NUM> and the USS/UTM <NUM> and/or the UFES <NUM> generate a hash chain, which looks like pseudo-random numbers when used in the opposite direction. Because the UAV <NUM> and the USS/UTM <NUM> and/or the UFES <NUM> use the same hash chain with the same update interval, the USS/UTM <NUM> and/or the UFES <NUM> knows at any time the identity that the UAV <NUM> is currently using or assigned.

In such an embodiment, the proposed solutions, described in more detail below, send an initial UAV identifier, update interval, and max hash-chain length from the USS/UTM <NUM> to the UAV <NUM>, generate the same pseudo-random number list of identities in the UAV <NUM> and in the USS/UTM <NUM>, which are used by the UAV <NUM> as source identity for its communication, update the UAV identifier according to the identities generated in the hash-chain at each update interval until the Initial UAV identifier is reached, and send the initial UAV identifier, update interval, and max hash chain with remote identification and tracking information ("RITI") information.

Beneficially, in one embodiment, the identifier assigned to the UAV <NUM> can be dynamically changed in such a way that the USS/UTM <NUM> and/or the UFES <NUM> knows the identifier that the UAV <NUM> is currently using or is currently assigned, and which may prevent others from tracking specific UAVs based on the UAVs identity.

In one embodiment, application layer identifier provisioning is provided. In such an embodiment, a hash-chain <NUM> is created to generate and store temporary UAV <NUM> identities that are used in the opposite/reverse order of generation, as shown in the <FIG>.

In one embodiment, the hash-chain <NUM> is generated based on an initial identity <NUM>. The initial identity <NUM> is input to a hash function, e.g., SHA256, SHA512, MD5, MD6, and/or the like, and the output of the hash function is the next identity (ID#<NUM>) 204a in the chain <NUM>, which is then input again to the hash function, or different hash function that has been previously agreed to between the UAV <NUM> and the USS/UTM <NUM>, to generate the next identity (ID#<NUM>) 204b, and so, until the maximum number of identities is generated. Even though a hash function is described to generate the chain of identifiers, one of skill in the art will recognize other methods for creating a chain of identifiers at the UAV <NUM> and at the USS/UTM <NUM> and/or the UFES <NUM>.

The identities <NUM> may be stored (at the UAV <NUM> and at a location in the mobile network <NUM> that is accessible to the USS/UTM <NUM>), and then used in the reverse order of generation. It may be easy and fast to generate a hash of an identity, but it may be difficult to reverse the operation. In one embodiment, the result is a pseudo-random chain of identifiers that may be assigned to the UAV <NUM>, dynamically and over-time, in the reverse order of generation.

In one embodiment, the length of the identities is sufficiently long to avoid conflicts between multiple UAVs <NUM> using the same identity at the same time. In certain embodiments, various types of identifiers may be used, e.g., a temporary UAV identifier, a CAA-Level UAV identifier, a remote identifier, a broadcast remote identifier, an external identifier, and/or the like.

<FIG> depicts one embodiment of a procedure that describes the usage of the identities in the hash-chain. In the depicted embodiment, it is assumed that the UAV <NUM> is already registered to the mobile network and the USS/UTM <NUM>, e.g., there is an application layer connection already established between the UAV <NUM> and USS/UTM <NUM>.

In one embodiment, the USS/UTM <NUM> generates (see block <NUM>) an initial UAV identifier as a start value for the hash-chain, as well as the update interval and the maximum hash-chain length. The update interval, as described above, defines the length of time that an identifier is assigned to a UAV <NUM> until a new identifier from the chain of identifiers is assigned to the UAV <NUM>. In certain embodiments, the update interval multiplied by the hash-chain length indirectly indicates the interval that the USS/UTM <NUM> updates the UAV <NUM> with a new initial UAV identifier.

In further embodiments, the USS/UTM <NUM> provides (see messaging <NUM>) at least one of the following information elements to the UAV <NUM>: the initial UAV identifier, the update interval, and/or the maximum hash-chain length. The UAV <NUM>, in certain embodiments, acknowledges the receipt of the parameters in a response to the USS/UTM <NUM>.

In one embodiment, the UAV <NUM> and the USS/UTM <NUM> generate (see block <NUM> and <NUM>), using the same hash function(s), the hash-chain as described in <FIG>, and stores the generated identifiers in the same order in which the identifiers were generated, e.g., using an array, a linked list, and/or some other data structure.

In some embodiments, the UAV <NUM> and the USS/UTM <NUM> update (see blocks <NUM> and <NUM>) the identifier that is currently assigned to the UAV <NUM> according to the update interval by starting with the last identifier in the hash-chain and then moving with each update interval towards the initial UAV identifier (that the USS/UTM <NUM> generates and sends to the UAV <NUM>). Once the UAV <NUM> and the USS/UTM <NUM> reach the initial UAV identifier or are close to the initial UAV identifier (e.g., one, two, five identifiers away, or the like), the USS/UTM <NUM> may restart the procedure depicted in <FIG> at Step <NUM>. In certain embodiments, the update interval and/or the maximum hash-chain length may also be changed, which may be defined according to a configuration of the USS/UTM <NUM>. In one embodiment, restarting the procedure depicted in <FIG> may be triggered by either the UAV <NUM> or the USS/UTM <NUM>.

A further embodiment is directed to NAS-based identifier provisioning. In one embodiment, this embodiment is based on 3GPP TR <NUM>, a portion of which is illustrated in <FIG>. In one embodiment, the UAV <NUM> goes through a registration and authorization procedure (see block <NUM>) and requests to establish a PDU session (see block <NUM>).

In certain embodiments, the following steps of the procedure of clause <NUM>. <NUM> of TR <NUM> are modified as disclosed herein:.

At step 12d, the USS/UTM <NUM> validates (see block <NUM>) the PDU establishment request based on a CAA-Level UAV identifier, a permanent equipment identifier ("PEI"), and a flight authorization identifier, if one is provided.

In one embodiment, the USS/UTM <NUM> determines remote identification and tracking information ("RITI") for the UAV <NUM> to use. This may include a new initial CAA-level UAV identifier (e.g., a temporary identifier for remote identification) that is used as a means to remotely identify the UAV <NUM>, an update interval, a hash chain length, and authorization data that may include the authorized area and time where the UAV <NUM> can operate, the UAV <NUM> type, and/or the like.

The USS/UTM <NUM>, in one embodiment, generates a hash chain up to the hash chain length (see <FIG>), starting with the initial CAA-level UAV identifier and updates the identifier in use according to the update interval by starting with the last identifier in the hash chain and then moving with each update interval towards the initial UAV identifier so that the USS/UTM <NUM> knows at any time which UAV identifier is currently assigned to the UAV <NUM> at the moment.

In one embodiment, the time when the USS/UTM <NUM> needs to provide a new initial CAA-level UAV identifier (e.g., the time to trigger a reset or restart of the hash chain) is determined by multiplying the hash chain length with the update interval. The update interval and the hash chain length may be independent parameters of the RITI. The USS/UTM <NUM> may also determine authorization data containing information about the user plane connectivity between the UAV <NUM> and the UAV controller <NUM>. Some of the RITI information, e.g., the CAA-level UAV identifier, are received and stored by the UFES <NUM>, together with the authorization data.

As step 12e, the USS/UTM <NUM> sends (see messaging <NUM>) a UAV operation accept to the UFES <NUM> containing the authorization data and RITI, which may also include the update interval and hash chain length. The authorization data may include the authorized UAV <NUM> and UAV controller <NUM> pairing information, e.g., including the identifier of the UAV controller <NUM> that controls the UAV <NUM> or the identifier of the UAV <NUM> that the UAV controller <NUM> controls.

At step 12f, the UFES <NUM> sends (see messaging <NUM>) a UAV operation accept to the USS/UTM <NUM> containing the authorization data and RITI, which also may include the update interval and hash chain length. The UFES <NUM> may store the correspondence between the CAA-Level UAV identifier, the 3GPP UAV identifier, the authorization data, and the RITI. The UFES <NUM> may generate the hash chain up to the hash chain length (see <FIG>) and may update the UAV identifier in use according to the update interval by starting with the last identifier in the hash-chain and then moving with each update interval towards the Initial UAV identifier, so that the UFES <NUM> knows at any time which UAV identifier is currently assigned to the UAV <NUM> at any moment.

A secondary authorization may be performed (see block <NUM>) during the PDU session establishment, which may provide GPSI to the USS/UTM <NUM> for authorization of UAV <NUM> and UAV controller <NUM> pairing, and for flight path authorization/registration for flight operation. In one embodiment, as part of the secondary authorization, the USS/UTM <NUM> may assign RITI information. At step <NUM>, the SMF <NUM> configures (see block <NUM>) the user plane connectivity for communications between the UAV <NUM> and the UAV controller <NUM>.

At step <NUM>, the PDU session establishment succeeds upon indication from the USS/UTM <NUM> that the UAV operation request is accepted and/or that the secondary authorization succeeded. The SMF <NUM> forwards (see messaging <NUM>) the RITI, which may include the update interval and hash chain length to the UAV <NUM> within the protocol configuration options ("PCO") of the session management message. The UAV <NUM> may generate the hash chain up to the hash chain length (see <FIG>) and may update the UAV identifier in use, e.g., the identifier that is assigned to the UAV <NUM>, according to the update interval by starting with the last identifier in the hash chain and then moving with each update interval towards the initial UAV identifier.

At step <NUM>, the UAV <NUM> broadcasts (see block <NUM>) remote identification information for remote identification based on the RITI information and the current UAV identifier that is assigned to the UAV <NUM>. At step <NUM>, the UAV <NUM> sends (see messaging <NUM>) remote identification information to the USS/UTM <NUM> based on the RITI information and the currently assigned UAV identifier.

In certain embodiments, the USS/UTM <NUM> and/or the UFES <NUM> does not generate a hash chain and just updates the UAV <NUM> with a new initial UAV identifier, update interval, and maximum hash chain length, when the USS/UTM <NUM> assumes that the UAV <NUM> has reached the beginning of the hash chain, e.g., a timer in the USS/UTM <NUM> reaches the value of the update interval multiplied with the hash chain length.

In some embodiments, the USS/UTM <NUM> and/or the UFES <NUM> generates a list of (pseudo) random identities and sends the list of the identities to the UAV <NUM> together with the update interval.

In further embodiments, the USS/UTM <NUM> and/or the UFES <NUM> generates at least one of the following information elements - an initial UAV identifier, an update interval, and/or a maximum hash chain length in response to a request from the UAV <NUM>.

In certain embodiments, the initial UAV identifier, the update interval, and the maximum hash-chain length are preconfigured in the UAV <NUM> and the USS/UTM <NUM> and/or the UFES <NUM>.

In some embodiments, the USS/UTM <NUM> and/or the UFES <NUM> and the UAV <NUM> do not update, recreate, regenerate, or the like the hash chain when the initial UAV identifier is reached, but instead restart again with the last entry in the hash chain.

In various embodiments, the USS/UTM <NUM> and/or the UFES <NUM> and the UAV <NUM> do not follow a static update interval but follow a pattern that infrequently updates the UAV identifier to the next identifier in the hash chain. The infrequent pattern may be configured or provisioned on the UAV <NUM>.

In further embodiments, the USS/UTM <NUM> and/or the UFES <NUM> sends at least one of the following information elements - the initial UAV identifier, the update interval, and/or the maximum hash chain length to the UAV controller <NUM> in a similar manner as to the UAV <NUM>.

<FIG> depicts an embodiment for NAS-based initial identifier refresh, which may be based on the procedure depicted in <FIG> and may assume that an initial identifier (e.g., CAA-level UAV ID) has been provisioned inside or together with the RITI already. The procedure may be triggered by the USS/UTM <NUM>, e.g., starting with step 3d, but it is shown triggered by the UAV <NUM> in the following:.

At step <NUM>, in one embodiment, when the UAV <NUM> recognizes it is close to the beginning of the hash chain, e.g., that the hash chain is reaching the initial identifier (e.g., CAA-level UAV identifier) or has already reached the initial identifier, then it sends (see messaging <NUM>) a NAS request with the UAV operation request to the SMF <NUM>. The UAV operation request may indicate that the UAV <NUM> needs to be provisioned at least with a new initial identifier. The UAV <NUM> may also be provisioned with a new update interval and hash chain length. Whether the update interval and hash chain length are changed, adjusted, modified, or the like, may be determined based on the configuration of the USS/UTM <NUM>.

At step <NUM>, in one embodiment, the SMF <NUM> selects (see block <NUM>) the USS/UTM <NUM> based on a previous registration. At step 3a, in one embodiment, the SMF <NUM> sends (see messaging <NUM>) the UAV operation request to the UFES <NUM>. At step 3b, in one embodiment, the UFES <NUM> recognizes that the UAV operation request is to update the initial identifier and selects (see block <NUM>) the USS/UTM <NUM> according to the previous registration.

At step 3c, in one embodiment, the UFES <NUM> sends (see messaging <NUM>) the UAV operation request to the selected USS/UTM <NUM>. At step 3d, in one embodiment, the USS/UTM <NUM> validates (see block <NUM>) the request based on the currently used CAA-Level UAV identifier and the PEI.

Based on the PEI, in certain embodiments, the USS/UTM <NUM> selects the current hash chain and validates the received CAA-Level UAV identifier that is currently assigned to the UAV <NUM>. The USS/UTM <NUM>, in various embodiments, determines RITI for the UAV <NUM>, which may include a new initial CAA-level UAV identifier (e.g., a temporary identifier for remote identification) that is used as a means to remotely identify the UAV <NUM> and may include a new update interval and hash chain length.

The USS/UTM <NUM> may generate a hash chain up to the hash chain length (see <FIG>), starting with the initial CAA-level UAV identifier and updates the UAV identifier in use according to the update interval by starting with the last identifier in the hash-chain and then moving with each update interval towards the initial UAV identifier so that the USS/UTM <NUM> knows at any time which UAV identifier the UAV <NUM> is using or assigned at the moment. The hash chain length multiplied with the update interval may indicate the time when the USS needs to provide a new initial CAA-level UAV identifier. The update interval and hash chain length may be independent parameters of the RITI. Some of the RITI information, e.g., the CAA-level UAV identifier, may be received and stored by the UFES <NUM>, together with the authorization data.

At step 3e, in one embodiment, the USS/UTM <NUM> sends (see messaging <NUM>) a UAV operation accept message to the UFES <NUM> containing the authorization data and the RITI, which may include the update interval and hash chain length. At step 3f, in one embodiment, the UFES <NUM> sends (see messaging <NUM>) a UAV operation accept to the USS/UTM <NUM> containing the authorization data and the RITI, which may include the update interval and hash chain length.

In one embodiment, the UFES <NUM> may store the correspondence between the CAA-Level UAV identifier, the 3GPP UAV identifier, the authorization data, and the RITI. The UFES <NUM> may generate the hash chain up to the hash chain length (see <FIG>) and may update the UAV identifier that is in use or assigned according to the update interval by starting with the last identifier in the hash chain and moving with each update interval towards the initial UAV identifier, so that the UFES <NUM> knows which UAV identifier the UAV <NUM> is using or assigned.

At step <NUM>, in one embodiment, the SMF <NUM> forwards (see messaging <NUM>) the RITI, which may include the update interval and hash chain length, to the UAV <NUM> within the PCO of the session management message. The UAV <NUM> may generate the hash chain up to the hash chain length (see <FIG>) and may update the UAV identifier that is in use or assigned to the UAV <NUM> according to the update interval by starting with the last identifier in the hash-chain and then moving with each update interval towards the initial UAV identifier.

At step <NUM>, in one embodiment, the UAV <NUM> broadcasts (see block <NUM>) remote identification information for remote identification based on the RITI information and current UAV identifier. At step <NUM>, in one embodiment, the UAV <NUM> sends (see block <NUM>) remote identification information to the USS/UTM <NUM> based on RITI information and current UAV identifier. At step <NUM>, the UAV <NUM> communicates (see messaging <NUM>) with the UAV controller <NUM>.

<FIG> depicts a user equipment apparatus <NUM> that may be used for dynamic user equipment identifier assignment, according to embodiments of the disclosure. In various embodiments, the user equipment apparatus <NUM> is used to implement one or more of the solutions described above. The user equipment apparatus <NUM> may be one embodiment of the remote unit <NUM>, the UE <NUM>, the UAV <NUM>, and/or the UAV controller <NUM>, described above. Furthermore, the user equipment apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, and a transceiver <NUM>.

In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus <NUM> may not include any input device <NUM> and/or output device <NUM>. In various embodiments, the user equipment apparatus <NUM> may include one or more of: the processor <NUM>, the memory <NUM>, and the transceiver <NUM>, and may not include the input device <NUM> and/or the output device <NUM>.

As depicted, the transceiver <NUM> includes at least one transmitter <NUM> and at least one receiver <NUM>. In some embodiments, the transceiver <NUM> communicates with one or more cells (or wireless coverage areas) supported by one or more base units <NUM>. In various embodiments, the transceiver <NUM> is operable on unlicensed spectrum. Moreover, the transceiver <NUM> may include multiple UE panel supporting one or more beams. Additionally, the transceiver <NUM> may support at least one network interface <NUM> and/or application interface <NUM>. The application interface(s) <NUM> may support one or more APIs. The network interface(s) <NUM> may support 3GPP reference points, such as Uu, N1, PC5, etc. Other network interfaces <NUM> may be supported, as understood by one of ordinary skill in the art.

In certain embodiments, the processor <NUM> may include an application processor (also known as "main processor") which manages application-domain and operating system ("OS") functions and a baseband processor (also known as "baseband radio processor") which manages radio functions.

In various embodiments, the transceiver <NUM> and processor <NUM> control the user equipment apparatus <NUM> to implement the above described UE behaviors. In one embodiment, the transceiver <NUM> receives, at a UE device, an initial identifier for the UE device from a mobile wireless communication network. In one embodiment, the processor <NUM> 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.

In one embodiment, the processor <NUM> assigns an identifier that was generated last in the chain of identifiers to the UE device. In one embodiment, the processor <NUM> periodically assigns a different identifier to the UE device from the chain of identifiers, the different identifier comprises an identifier in the chain of identifiers that is used to generate the identifier that is currently assigned to the UE.

In one embodiment, the transceiver <NUM> receives, from the mobile wireless communication network, at least one of a maximum number of identifiers that are generated for the chain of identifiers and an update interval for periodically assigning the different identifier from the chain of identifiers to the UE device.

In one embodiment, the processor <NUM> regenerates the plurality of identifiers in the chain of identifiers in response to the assigned identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers. In one embodiment, the transceiver <NUM> sends a non-access stratum ("NAS") message to the mobile wireless communication network to request regeneration of the chain of identifiers in response to the assigned identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers and prior to regenerating the plurality of identifiers in the chain of identifiers.

In some embodiments, the memory <NUM> stores data related to dynamic user equipment identifier assignment. For example, the memory <NUM> may store various parameters, panel/beam configurations, resource assignments, policies, identifiers, and the like, as described above. In certain embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus <NUM>.

In some embodiments, all, or portions of the output device <NUM> may be integrated with the input device <NUM>.

The transceiver <NUM> communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver <NUM> operates under the control of the processor <NUM> to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor <NUM> may selectively activate the transceiver <NUM> (or portions thereof) at particular times in order to send and receive messages.

The transceiver <NUM> includes at least transmitter <NUM> and at least one receiver <NUM>. One or more transmitters <NUM> may be used to provide UL communication signals to a base unit <NUM>, such as the UL transmissions described herein. Similarly, one or more receivers <NUM> may be used to receive DL communication signals from the base unit <NUM>, as described herein. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the user equipment apparatus <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. Further, the transmitter(s) <NUM> and the receiver(s) <NUM> may be any suitable type of transmitters and receivers. In one embodiment, the transceiver <NUM> includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

In various embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> 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 certain embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface <NUM> or other hardware components/circuits may be integrated with any number of transmitters <NUM> and/or receivers <NUM> into a single chip. In such embodiment, the transmitters <NUM> and receivers <NUM> may be logically configured as a transceiver <NUM> that uses one more common control signals or as modular transmitters <NUM> and receivers <NUM> implemented in the same hardware chip or in a multi-chip module.

<FIG> depicts a network apparatus <NUM> that may be used for dynamic user equipment identifier assignment, according to embodiments of the disclosure. In one embodiment, network apparatus <NUM> may be one implementation of a RAN node, such as the base unit <NUM>, the RAN node <NUM>, or gNB, described above. Furthermore, the base network apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, and a transceiver <NUM>.

In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the network apparatus <NUM> may not include any input device <NUM> and/or output device <NUM>. In various embodiments, the network apparatus <NUM> may include one or more of: the processor <NUM>, the memory <NUM>, and the transceiver <NUM>, and may not include the input device <NUM> and/or the output device <NUM>.

As depicted, the transceiver <NUM> includes at least one transmitter <NUM> and at least one receiver <NUM>. Here, the transceiver <NUM> communicates with one or more remote units <NUM>. Additionally, the transceiver <NUM> may support at least one network interface <NUM> and/or application interface <NUM>. The application interface(s) <NUM> may support one or more APIs. The network interface(s) <NUM> may support 3GPP reference points, such as Uu, N1, N2 and N3. Other network interfaces <NUM> may be supported, as understood by one of ordinary skill in the art.

For example, the processor <NUM> may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. In certain embodiments, the processor <NUM> may include an application processor (also known as "main processor") which manages application-domain and operating system ("OS") functions and a baseband processor (also known as "baseband radio processor") which manages radio function.

In various embodiments, the network apparatus <NUM> is a USS/UTM <NUM> and/or a UFES <NUM>, described above. In such embodiments, the transceiver <NUM> sends, to a user equipment ("UE") device from a mobile wireless communication network, e.g., the USS/UTM <NUM>, an initial identifier for the UE device. In one embodiment, the processor <NUM> 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.

In one embodiment, the processor <NUM> associates an identifier that was generated last in the chain of identifiers with the UE device. In one embodiment, the processor <NUM> periodically associates a different identifier with the UE device from the chain of identifiers, the different identifier comprising an identifier in the chain of identifiers that is used to generate the identifier that is currently associated with the UE.

In one embodiment, the transceiver <NUM> sends, to the UE device, at least one of a maximum number of identifiers that are generated for the chain of identifiers and an update interval for periodically associating the different identifier from the chain of identifiers with the UE device.

In one embodiment, the processor <NUM> regenerates the plurality of identifiers in the chain of identifiers in response to the associated identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers. In one embodiment, the transceiver <NUM> receives a non-access stratum ("NAS") message from the UE device to request regeneration of the chain of identifiers in response to the associated identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers.

In some embodiments, the memory <NUM> stores data related to dynamic user equipment identifier assignment. For example, the memory <NUM> may store parameters, configurations, resource assignments, policies, identifiers, and the like, as described above. In certain embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on the network apparatus <NUM>.

As another, non-limiting, example, the output device <NUM> may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus <NUM>, such as a smart watch, smart glasses, a heads-up display, or the like.

The transceiver <NUM> includes at least transmitter <NUM> and at least one receiver <NUM>. One or more transmitters <NUM> may be used to communicate with the UE, as described herein. Similarly, one or more receivers <NUM> may be used to communicate with network functions in the NPN, PLMN and/or RAN, as described herein. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the network apparatus <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. Further, the transmitter(s) <NUM> and the receiver(s) <NUM> may be any suitable type of transmitters and receivers.

<FIG> is a flowchart diagram of a method <NUM> for dynamic user equipment identifier assignment. The method <NUM> may be performed by a UE as described herein, for example, the remote unit <NUM>, the UE <NUM>, the UAV <NUM>, the UAV controller <NUM>, and/or the user equipment apparatus <NUM>. In some embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM>, in one embodiment, includes receiving <NUM>, at a user equipment ("UE") device, an initial identifier for the UE device from a mobile wireless communication network. The method <NUM>, in one embodiment, includes generating <NUM> 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.

The method <NUM>, in one embodiment, includes assigning <NUM> an identifier that is generated last in the chain of identifiers to the UE device. The method <NUM>, in one embodiment, includes periodically assigning <NUM> a different identifier to the UE device from the chain of identifiers where the different identifier comprises an identifier in the chain of identifiers that is used to generate the identifier that is currently assigned to the UE. The method <NUM> ends.

<FIG> is a flowchart diagram of a method <NUM> for dynamic user equipment identifier assignment. The method <NUM> may be performed by a network function such as the USS/UTM <NUM>, the UFES <NUM>, and/or the like, and/or a network equipment apparatus <NUM>. In some embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM>, in one embodiment, includes sending <NUM>, to a user equipment ("UE") device from a mobile wireless communication network, an initial identifier for the UE device. The method <NUM>, in one embodiment, includes generating <NUM> a plurality of identifiers for the UE device based on the initial identifier where each of the plurality of identifiers generated based on a previous identifier to form a chain of identifiers.

The method <NUM>, in one embodiment, includes associating <NUM> an identifier that is generated last in the chain of identifiers with the UE device. The method <NUM>, in one embodiment, includes periodically associating <NUM> a different identifier with the UE device from the chain of identifiers where the different identifier comprises an identifier in the chain of identifiers that is used to generate the identifier that is currently associated with the UE. The method <NUM> ends.

A first apparatus is disclosed for dynamic user equipment identifier assignment. The first apparatus may include a UE as described herein, for example, the remote unit <NUM>, the UE <NUM>, the UAV <NUM>, the UAV controller <NUM>, and/or the user equipment apparatus <NUM>. In some embodiments, the first apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

In one embodiment, the first apparatus includes a transceiver that receives, at a user equipment ("UE") device, an initial identifier for the UE device from a mobile wireless communication network. In one embodiment, the first apparatus includes a processor 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.

In one embodiment, the processor assigns an identifier that was generated last in the chain of identifiers to the UE device. In one embodiment, the processor periodically assigns a different identifier to the UE device from the chain of identifiers, the different identifier comprises an identifier in the chain of identifiers that is used to generate the identifier that is currently assigned to the UE.

In one embodiment, the transceiver receives, from the mobile wireless communication network, at least one of a maximum number of identifiers that are generated for the chain of identifiers and an update interval for periodically assigning the different identifier from the chain of identifiers to the UE device.

In one embodiment, the processor regenerates the plurality of identifiers in the chain of identifiers in response to the assigned identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers. In one embodiment, the transceiver sends a non-access stratum ("NAS") message to the mobile wireless communication network to request regeneration of the chain of identifiers in response to the assigned identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers and prior to regenerating the plurality of identifiers in the chain of identifiers.

In one embodiment, the initial identifier for the UE is received in a non-access stratum ("NAS") message from the mobile wireless communication network. In one embodiment, the UE device comprises an unmanned aerial vehicle ("UAV") and the identifier comprises at least one of a temporary UAV identifier, a civil aviation authority ("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, the at least one hash function being same between the UE device and the mobile wireless communication network.

A first method is disclosed for dynamic user equipment identifier assignment The first method may be performed by a UE as described herein, for example, the remote unit <NUM>, the UE <NUM>, the UAV <NUM>, the UAV controller <NUM>, and/or the user equipment apparatus <NUM>. In some embodiments, the first method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

In one embodiment, the first method includes receiving, at a user equipment ("UE") device, an initial identifier for the UE device from a mobile wireless communication network. In one embodiment, the first method includes generating 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.

In one embodiment, the first method includes assigning an identifier that is generated last in the chain of identifiers to the UE device. In one embodiment, the first method includes periodically assigning a different identifier to the UE device from the chain of identifiers where the different identifier comprises an identifier in the chain of identifiers that is used to generate the identifier that is currently assigned to the UE.

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

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

A second apparatus is disclosed for dynamic user equipment identifier assignment. The second apparatus may include a network function such as the USS/UTM <NUM>, the UFES <NUM>, and/or the like, and/or a network equipment apparatus <NUM>. In some embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

In one embodiment, the second apparatus includes a transceiver that sends, to a user equipment ("UE") device from a mobile wireless communication network, an initial identifier for the UE device. In one embodiment, the second apparatus includes a processor 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.

In one embodiment, the processor associates an identifier that was generated last in the chain of identifiers with the UE device. In one embodiment, the processor periodically associates a different identifier with the UE device from the chain of identifiers, the different identifier comprising an identifier in the chain of identifiers that is used to generate the identifier that is currently associated with the UE.

In one embodiment, the transceiver sends, to the UE device, at least one of a maximum number of identifiers that are generated for the chain of identifiers and an update interval for periodically associating the different identifier from the chain of identifiers with the UE device.

In one embodiment, the processor regenerates the plurality of identifiers in the chain of identifiers in response to the associated identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers. In one embodiment, the transceiver receives a non-access stratum ("NAS") message from the UE device to request regeneration of the chain of identifiers in response to the associated identifier being within a threshold number of identifiers of the initial identifier in the chain of identifiers.

In one embodiment, the initial identifier for the UE is sent in a non-access stratum ("NAS") message from the mobile wireless communication network. In one embodiment, the UE device comprises an unmanned aerial vehicle ("UAV") and the identifier comprises at least one of a temporary UAV identifier, a civil aviation authority ("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, the at least one hash function being same between the UE device and the mobile wireless communication network.

A second method is disclosed for dynamic user equipment identifier assignment. The second method may be performed by a network function such as the USS/UTM <NUM>, the UFES <NUM>, and/or the like, and/or a network equipment apparatus <NUM>. In some embodiments, the second method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

In one embodiment, the second method includes sending, to a user equipment ("UE") device from a mobile wireless communication network, an initial identifier for the UE device. In one embodiment, the second method includes generating 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.

In one embodiment, the second method includes associating an identifier that is generated last in the chain of identifiers with the UE device. In one embodiment, the second method includes periodically associating a different identifier with the UE device from the chain of identifiers where the different identifier comprises an identifier in the chain of identifiers that is used to generate the identifier that is currently associated with the UE.

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

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

Claim 1:
A user equipment, UE, device (<NUM>) comprising:
a transceiver (<NUM>) arranged to receive an initial identifier for the UE device (<NUM>) from a mobile wireless communication network; and
a processor (<NUM>) arranged to:
generate a plurality of identifiers for the UE device based on the initial identifier, each of the plurality of identifiers generated based on a previous identifier to form a chain of identifiers;
the UE device being characterized in that the processor (<NUM>) is further arranged to:
assign an identifier that was generated last in the chain of identifiers to the UE device; and
periodically assign a different identifier to the UE device from the chain of identifiers, the different identifier comprising an identifier in the chain of identifiers that is used to generate the identifier that is currently assigned to the UE.