Group identifier privacy for internet of things devices

By encrypting and updating temporary group identifiers based on permanent device IDs, the wireless communication system enhances privacy and security for IoT devices, mitigating the risk of malicious access to their permanent IDs.

WO2026234615A1PCT designated stage Publication Date: 2026-11-12LENOVO UNITED STATES INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/IB2026/054533
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems for Internet of Things (IoT) devices face challenges in protecting the privacy of group identifiers, as defining group IDs based on permanent device IDs can allow malicious devices to read out the permanent IDs of ambient IoT devices, compromising their security.

Method used

A network entity (NE) identifies a bitstring corresponding to permanent device IDs, generates a temporary group ID and security key, encrypts them, and transmits these to IoT devices, allowing them to update their temporary IDs and security keys using a keyed hash function, thereby enhancing privacy.

Benefits of technology

This approach reduces the likelihood of malicious devices accessing permanent device IDs by encrypting and updating temporary group identifiers, ensuring enhanced privacy and security for IoT devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2026054533_12112026_PF_FP_ABST
    Figure IB2026054533_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure relate to group identifier (ID) privacy for Internet- of-Things (IoT) devices. A network equipment (NE) may identify a permanent device identifier (ID) for each IoT device of a set of IoT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of IoT devices. The NE may assign a temporary group ID and a group security key to the set of IoT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of IoT devices. The NE may transmit a command request to each IoT device of the set of IoT devices that includes an encrypted temporary group ID and an encrypted group security key. The NE may transmit a group inventory request with the temporary group ID to the set of IoT devices.
Need to check novelty before this filing date? Find Prior Art

Description

Lenovo Ref. No. SMM920250048-WO-PCT1GROUP IDENTIFIER PRIVACY FOR INTERNET OF THINGS DEVICES RELATED APPLICATION

[0001] This application claims priority to U.S. Application Serial No. 19 / 202,801 filed May 08, 2025 entitled “GROUP IDENTIFIER PRIVACY FOR INTERNET OF THINGS DEVICES,” the disclosure of which is incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to group identifier (ID) privacy.BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0004] As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusiveAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT2list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.” Further, as used herein, including in the claims, a “set” may include one or more elements.

[0005] The device (e.g., NE, UE, Internet-of-Things (loT) device), processors, and methods of the present disclosure each have several innovative aspects, no single of which is solely responsible for the desirable features disclosed herein.

[0006] An NE (e.g., a base station) for wireless communication is described. The NE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the NE may be configured to, capable of, or operable to identify a permanent device ID for each loT device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices; assign a temporary group ID and a group security key to the set of loT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices; transmit a command request to each loT device of the set of loT devices that includes an encrypted temporary group ID and an encrypted group security key; and transmit a group inventory request with the temporary group ID to the set of loT devices.

[0007] A processor (e.g., a standalone processor chipset, or a component of an NE) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to identify a permanent device ID for each loT device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices; assign a temporary group ID and a group security key to the set of loT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices; transmit a command request to each loT device of the set of loT devices that includes an encrypted temporary group ID and an encrypted group security key; and transmit a group inventory request with the temporary group ID to the set of loT devices.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT3

[0008] A method performed or performable by an NE (e.g., a base station) for wireless communication is described. The method may include identifying a permanent device ID for each loT device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices; assigning a temporary group ID and a group security key to the set of loT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices; transmitting a command request to each loT device of the set of loT devices that includes an encrypted temporary group ID and an encrypted group security key; and transmitting a group inventory request with the temporary group ID to the set of loT devices.

[0009] In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to update the temporary group ID assigned to the set of loT devices based on the group inventory request. In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to perform a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices. In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to receive, from the set of loT devices and in response to a global inventory request, a temporary device ID for each loT device of the set of loT devices; and update the temporary device IDs for the set of loT devices based on the group inventory request.

[0010] In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to store a table that includes one or more of the permanent device IDs of the set of loT devices, temporary device IDs of the set of loT devices, expected temporary device IDs of the set of loT devices, the bitstring, temporary group IDs for the set of loT devices, a security key shared by the NE and the set of loT devices, session keys for the set of loT devices, or group security keys for the set of loT devices.

[0011] In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to detect that a response to the group inventory request was not received from at least one loT device of the set of loT devices. In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to retransmit, in response to detecting that the response was not received, the group inventory request to the set of loT devices assigned with the temporary group ID.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT4

[0012] In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to transmit, to the set of loT devices in response to detecting that the response was not received, a first global inventory request that includes a nonce that was included in a second global inventory request transmitted prior to the command request. In some implementations, the NE, the processor, and the method may further be configured to, capable of, or operable to retransmit, in response to detecting that the response was not received, the command request to the at least one loT device.

[0013] An loT device for wireless communication is described. The loT device may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the loT device may be configured to, capable of, or operable to receive a command request that includes an encrypted temporary group ID and an encrypted group security key; decrypt the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device; receive a group inventory request with the temporary group ID; and update the temporary group ID based on the group inventory request.

[0014] A processor (e.g., a standalone processor chipset, or a component of an loT device) for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may be configured to, capable of, or operable to receive a command request that includes an encrypted temporary group ID and an encrypted group security key; decrypt the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device; receive a group inventory request with the temporary group ID; and update the temporary group ID based on the group inventory request.

[0015] A method performed or performable by an loT device for wireless communication is described. The method may include receiving a command request that includes an encrypted temporary group ID and an encrypted group security key; decrypting the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device; receiving a group inventory request with the temporary group ID; and updating the temporary group ID based on the group inventory request.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT5

[0016] In some implementations, the loT device, the processor, and the method may further be configured to, capable of, or operable to perform a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices. In some implementations, the loT device, the processor, and the method may further be configured to, capable of, or operable to transmit, in response to a global inventory request, a temporary device ID for the loT device; and update the temporary device ID for the loT device based on the group inventory request. In some implementations, the loT device, the processor, and the method may further be configured to, capable of, or operable to transmit a response to the group inventory request that includes the updated temporary device ID for the loT device.BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0018] Figure 2 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0019] Figure 3 illustrates an example of a process flow in accordance with aspects of the present disclosure.

[0020] Figure 4 illustrates an example of a flowchart of a method performed by an loT device and / or an NE in accordance with aspects of the present disclosure.

[0021] Figure 5 illustrates an example of a UE in accordance with aspects of the present disclosure.

[0022] Figure 6 illustrates an example of a processor in accordance with aspects of the present disclosure.

[0023] Figure 7 illustrates an example of an NE in accordance with aspects of the present disclosure.

[0024] Figure 8 illustrates an example of a flowchart of a method performed by an NE in accordance with aspects of the present disclosure.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT6

[0025] Figure 9 illustrates an example of a flowchart of a method performed by an loT device in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0026] In some examples, a wireless communications system may include multiple ambient loT devices. Ambient loT devices may be described as battery-less or limited energy storage capacity devices whose energy is provided through the harvesting of naturally available energy sources (e.g., radio waves, light, motion, or heat). In some examples, ambient loT devices may be capable of receiving group communications (e.g., a group inventory request). Group communications may include a group ID that specifies the group of ambient loT devices for which the group communication is directed to. In some examples, the group ID may be an example of a bitstring that corresponds to a component of the group of ambient loT devices’ permanent IDs. A permanent ID of an ambient loT device may include identification information that is used to distinguish different ambient loT devices from one another and is considered a private identifier of the ambient loT device. However, defining group communications using this type of group ID may allow a malicious device to read out the permanent IDs of the ambient loT devices. For example, the malicious device may perform a binary search for a permanent ID on multiple group communications and with each group communication, the malicious devices may read out a respective bit of the permanent ID.

[0027] The techniques described herein provide privacy for group IDs of loT devices. In some examples, an NE may be preconfigured with a permanent ID for each loT device of a set of loT devices and obtain a bitstring that corresponds to one or more of the permanent IDs. Further, the NE may perform group management of the loT devices. That is, the NE may determine that a portion of each of the permanent IDs of a subset of the set of loT devices matches the bitstring and, as a result, group the subset of the loT devices together. Moreover, the NE may generate a temporary group ID and group security key for the subset of loT devices. Upon completion of group management, the NE may encrypt the temporary group ID and the group security key and transmit a command request to each of the subset of loT devices that includes the encrypted information. The subset of loT devices may receive the command request and decrypt the command request to obtain the temporary group ID and the group security key.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT7

[0028] Later, the NE may transmit a group inventory request to the subset of loT device with the temporary group ID. Upon transmitting the group inventory request, the NE may update the temporary group ID for a subsequent group communication. The subset of loT device may recognize the group inventory request because the temporary group ID of the group inventory request matches the temporary group ID provided to the subset of loT via the command request. In response to receiving the group inventory request, the subset of loT devices may update the temporary group ID using similar methods that the NE used to update the temporary group ID such that the subset of loT devices may recognize the subsequent group communications from the NE. It should be understood that various terms may be used interchangeably with “communicating,” such as “signaling,” “transmitting,” “receiving,” “outputting,” “forwarding,” “relaying,” “retrieving,” “obtaining,” and so forth.

[0029] By performing the techniques described, the wireless communications system provides privacy for group IDs of loT devices which may decrease the likelihood of a malicious device gaining access to the loT permanent device ID when compared to other methods.

[0030] Aspects of the present disclosure are described in the context of a wireless communications system. Additional aspects of the present disclosure are described in the context of component diagrams, process flows, method flows, etc. Aspects of the present disclosure are further set forth in the accompanying drawings and the description below. The description set forth herein, in connection with the accompanying drawings, describes example implementations and does not represent all the implementations that may be implemented or that are within the scope of the claims. The detailed description includes specific details for the purpose of providing an understanding of the described implementations. These implementations, however, may be practiced without these specific details. Additionally, the description set forth herein, in connection with the accompanying drawings is provided to enable a person having ordinary skill in the art to make or use the present disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and implementations described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT8

[0031] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0032] The one or more NEs 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NEs 102 described herein may be or include or may be referred to as a network node, a base station, an access point (AP), a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0033] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT9

[0034] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an loT device, an Internet-of-Every thing (loE) device, or machine-type communication (MTC) device, among other examples.

[0035] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0036] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N6, or other network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other indirectly (e.g., via the CN 106). In some implementations, one or more NEs 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0037] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT10(e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NEs 102 associated with the CN 106.

[0038] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N6, or other network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0039] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0040] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifthAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT11numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0041] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0042] Additionally, or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, / =l , / r=2, / r=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0043] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT12more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0044] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0045] In some examples, the UEs 104 may be examples of loT devices. A type of loT devices may include ambient loT devices. Ambient loT devices may be described as battery-less or limited energy storage devices whose energy is provided though the harvesting of radio waves, light, motion, heat, or any other suitable power source. An example of an loT device may include a sensor under a bridge configured to measure water. Unlike other full capability devices, ambient loT devices are characterized by their low complexity, low maintenance, long life span (e.g., more than ten years), small size, low capabilities, and low power consumption. Further, ambient loT devices do not typically include a universal subscriber identity module (USIM). Each ambient loT may have a corresponding permanent device ID. The permanent device ID may include three components: ID type, domain information (e.g., public land mobile network (PEMN) ID, network identifier (NID), and third-party ID), and identification information. The domain information and the ID type may be common for all ambient loT devices within a same domain and may be public information. The identification information is used to distinguish different ambient loT devices from one another and may be considered a private ID of the ambient loT device.

[0046] loT devices may receive two types of communications from the NE 102. The two types of communications may include inventory requests and command requests. An inventory request may be directed to an individual loT device or a group of loT devices and all loT devices receiving the inventory request may respond to the inventory request (e.g., with an inventory response). A Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT13command request may be directed to an individual loT device and may require a preceding inventory procedure. A group request (e.g., a group inventory request) may include a group ID that is recognizable to a group of loT devices. In some examples, the group ID may be defined using a bit sequence of dynamic length of the identification information of the group of loT devices.However, defining the group ID in such a way may allow malicious devices to obtain an loT device’s permanent ID.

[0047] In some examples, the NE 102 may identify filtering information associated with the loT devices. Filtering information may be defined as a bitstring that corresponds to one component of the loT permanent device ID and may be used to form groups of loT devices. For example, the NE 102 may identify loT devices whose permanent device ID matches the filtering information and group these loT devices together. In some examples, the group ID included in the group request (e.g., the group inventory request) may include the filtering information. However, defining the group ID in such a way may still allow malicious devices to obtain an loT device’s permanent ID.

[0048] The methods described herein provide protection and security for group communications for loT devices. In some examples, the NE 102 (or an loT device controller) may be preconfigured with a permanent ID for each loT device of a set of loT devices and obtain filtering information. Further, the NE 102 may perform group management of the loT devices. That is, the NE 102 may determine that a portion of each of the permanent IDs of a subset of the set of loT devices matches the filtering information and, as a result, group the subset of the loT devices together. Moreover, the NE 102 may generate a temporary group ID and a group security key for the subset of loT devices. Upon completion of group management, the NE 102 may encrypt the temporary group ID and the group security key and transmit a command request to each of the subset of loT devices that includes the encrypted information. The subset of loT devices may receive the command request and decrypt the command request to obtain the temporary group ID and the group security key.

[0049] Later, the NE 102 may transmit a group inventory request to the subset of loT device with the temporary group ID. Upon transmitting the group inventory request, the NE 102 may update the temporary group ID for a subsequent group communication. The subset of loT device may recognize the group inventory request because the temporary group ID of the group inventory request matches the temporary group ID provided to the subset of loT via the command request. In response to receiving the group inventory request, the subset of loT devices may update the Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT14temporary group ID using similar methods that the NE 102 used to update the temporary group ID such that the subset of loT devices may recognize the subsequent group communication from the NE 102. Reference is made herein to communicating data or information, such as signaling communication resources and / or communications that are transmitted or received between devices. It is to be appreciated that other terms may be used interchangeably with communicating, such as signaling, transmitting, receiving, outputting, forwarding, retrieving, obtaining, and so forth.

[0050] Figure 2 illustrates an example of a wireless communications system 200 in accordance with aspects of the present disclosure. In some examples, the wireless communications system 200 may support aspects of the wireless communications system 100. For example, the wireless communications system 200 may include loT devices 204 which may be examples of the UEs 104 as described with reference to Figure 1. Further, the wireless communications system 200 may include an NE 202 which may be an example of the NE 102 as described with reference to Figure 2.

[0051] In some examples, the wireless communications system 200 may include multiple loT devices 204. For example, the wireless communications system 200 may include, at least, an loT device 204-a, an loT device 204-b, an loT device 204-c, an loT device 204-d, and an loT device 205 -e. Each loT device 204 of the multiple loT devices 204 may be preconfigured with a respective permanent device ID and a shared security key. Similarly, the NE 102 may be preconfigured with the permanent device IDs of the multiple loT devices 204 and the shared security key.

[0052] In some examples, the multiple loT device 204 may onboard (or connect) with the NE 202 and each loT device 204 may derive a respective temporary device ID as well as a respective session key. The temporary device ID may be specific to the loT device 204 and may allow the loT devices 204 to recognize individual communications (e.g., individual command requests or individual inventory requests).

[0053] After this, the NE 202 may perform group management. As part of group management, the NE 202 identifies a group of loT devices 204. To identify the group of loT devices 204, the NE 202 compares filtering information to the permanent device IDs of the multiple loT devices 204. The filtering information may include a bit sequence that corresponds to one or more of the permanent device IDs of the multiple loT devices 204. For example, the bit sequence may include a portion of at least one of the loT device’s permanent device IDs. The filtering information may beAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT15preconfigured to the NE 202 or the NE 202 may obtain the filtering information from a storage device (e.g., a separate server or a data management device). The NE 202 may group loT devices 204 whose corresponding permanent device ID (or at least a portion of the permanent device ID) matches the filtering information. In one example, the NE 202 may group the loT device 204-a, the loT device 204-b, and the loT device 204-c together. Further, the NE 202 may generate a temporary group ID and a group security key and assign the temporary group ID and the group security key to the group of loT devices 204.

[0054] Next, the NE 202 may perform group configuration. As part of group configuration, the NE 202 may generate an individual command request 206 for each of the loT devices 204 of the group of the loT devices 204. Each individual command request 206 may include a respective temporary device ID, an encoded temporary group ID, an encoded group security key, a first freshness parameter (e.g., a nonce), and a payload. In some examples, the NE 202 may encode (or encrypt) the temporary group ID and the group security key using the session keys (e.g., devicespecific session keys). Each loT device 204 of the group may receive the respective individual command request 206 and decode (or decrypt) the individual command request 206 (e.g., using their session key) to obtain the temporary group ID and the group security key.

[0055] After this, the NE 202 may perform group inventory. As a part of group inventory, the NE 202 may generate a group inventory request 208 and transmit the group inventory request 208 to the group of loT devices 204. The group inventory request 208 may include the temporary group ID as well as a second freshness parameter (e.g., a nonce). Further, the NE 202 may update the temporary group ID upon generating the group inventory request 208. In some examples, the NE 202 may update the temporary group ID by performing a key hash function (e.g., hash-based message authentication code (HMAC)) with the group security key over the second freshness parameters and the temporary group ID.

[0056] The group of loT devices 204 may recognize and receive the group inventory request 208 based on the temporary group ID included in the group inventory request 208. In response to receiving the group inventory request 208, the group of loT devices 204 may independently update their respective temporary device ID and the temporary group ID. In some examples, the group of loT devices 204 may update the temporary group ID in a similar way as the NE 202. That is, the loT devices 204 may perform a key hash function (e.g., HMAC) with the group security key over Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT16the second freshness parameters and the temporary group ID. In some examples, the group of loT devices 204 may transmit a response (e.g., a group inventory response 210) to the group inventory request 208. The group inventory response 210 may include the updated temporary device ID and the second freshness parameter. Upon receiving the group inventory response 210, the NE 202 may update the temporary device IDs of the group of loT device 204 with the updated temporary device IDs provided in the group inventory response 210.

[0057] Figure 3 illustrates an example of a process flow 300 in accordance with aspects of the present disclosure. In some examples, the process flow 300 may be implemented by aspects of the wireless communications system 100 and the wireless communications system 200. For example, the process flow 300 may be implemented by the UE 104, the NE 102, the loT device 204, or the NE 202 as described with reference to Figures 1 and 2.

[0058] At 308, a set of loT devices 304, an NE 302 (or an loT function of the NE 302), and a data manager 306 may undergo preconfiguration. During preconfiguration, the set of loT devices 304, the NE 302, and the data manager 306 may identify a permanent device ID for each loT device 304 of the set of loT devices and a shared security key. Additionally, the NE 302 may identify filtering information for the set of loT devices 304. The filtering information may include a bitstring that corresponds to one or more of the permanent device IDs of the set of loT devices 304.

[0059] From 310 to 318, a global inventory procedure is performed to onboard the set of the loT devices 304.

[0060] At 310, the NE 302 may generate a global inventory request. In some examples, the global inventory request may include domain information associated with the set of loT devices 304 such that all loT devices 304 of the set of loT devices 304 respond to the global inventory request. For example, the global inventory request may include global paging information. In addition, the global inventory may also include a first freshness parameter (e.g., a nonce) generated by the NE 302. Further, at 310, the NE 302 may precompute, for all loT devices 304 of the set of loT devices 304, a respective temporary device ID. In some examples, the NE 302 may precompute the temporary device IDs by performing a keyed hash function (e.g., HMAC) with the shared security key over the first freshness parameter and a respective permanent device ID. Additionally, the NEAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT17302 may derive a session key from the shared security key for each loT device 304 of the set of loT devices 304 for protection of command messages.

[0061] Additionally, at 310, the NE 302 may create and store a table with parameters that include one or more of permanent device IDs for the set of loT devices 304, temporary device IDs for the set of loT devices 304, precomputed temporary device IDs for the set of loT devices 304, the filtering information, temporary group ID for the set of loT devices 304, the shared security key, the session keys, and group security keys. Table 1 illustrates an example of the table created by the NE 302. Different loT devices 304 of the set of loT devices 304 may be associated with a different permanent device ID and a different temporary device ID. However, different devices may be associated with the same filtering information and may belong to a same temporary group ID. Further, all loT devices 304 of the same group may share a same group security key.Permanent Temporary Precomputed Filtering Temporary Shared Session Group Device ID Device ID Temporary Information Group ID Security Key Security Device ID Key KeyTable 1

[0062] At 312, the NE 302 may page all loT devices 304 within an area of the NE 302 (e.g., the set of loT devices 304) using the global inventory request. That is, the NE 302 may transmit the global inventory request to the set of loT devices 304.

[0063] At 314, the set of loT devices 304 may recognize the global inventory request (e.g., based on the domain information included in the global inventory request) and each loT device 304 of the set of loT devices 304 may generate a respective temporary device ID in a similar way as the NE 302. Additionally, at 314, each loT device 304 may derive a respective session key from the shared security key for protection of command messages. The session keys may match the session keys generated by the NE 302 at 310.

[0064] At 316, each loT device 304 of the set of loT devices 304 may respond to the global inventory request. That is, each loT device 304 may transmit, to the NE 302, a respective global inventory response that includes the respective temporary device ID generated by the loT device 304 as well as the first freshness parameter.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT18

[0065] At 318, the NE 302 receives all of the responses from the set of loT devices 304 and compares the received temporary device IDs with the precomputed temporary device IDs.Additionally, at 318, the NE 302 performs group management and may group at least some loT devices 304 of the set of loT device 304 together. For example, the NE 302 may group together loT devices 304 with filtering information that matches the permanent device IDs of the loT devices 304. Additionally, the NE 302 may assign a same temporary group ID to the group of loT devices 304. Further, the NE 302 may derive a group security key for the temporary group ID. In some examples, the NE 302 may store the temporary group ID and the group security key in a table (e.g., Table 1).

[0066] At 320, the NE 302 may select a specific group of loT devices 304 for group configuration and generate a second freshness parameter (e.g., a nonce). Additionally, at 320, the NE 302 may generate an individual command request for each loT device 304 of the selected group. Each command request may include a respective temporary device ID, the second freshness parameter, an encoded version of the temporary group ID, an encoded version of the group security key, and a payload. In some examples, the NE 302 may encode the temporary group ID and the group security key using the device-specific session keys. In some examples, the second freshness parameter and the payload may also be encoded. Additionally, at 320, the NE 302 may precompute a new temporary device ID for each loT device 304 of the selected group and update the table with the precomputed new temporary device IDs.

[0067] At 322, the NE 302 may transmit the individual command requests to the group of loT devices 304.

[0068] At 324, the group of loT devices 304 may decode the individual command requests to obtain the temporary group ID and the group security key and store the temporary group ID and group security key for future use. In some examples, the group loT devices 304 may utilize their respective session key to decode the individual command requests. Additionally, at 324, the group of loT devices 304 may generate a new temporary device ID. Additionally, in some examples, the group of loT devices 304 may update their respective session keys upon decoding the individual command requests. The NE 302 and the data manager 306 may also update the session keys for the group of loT devices 304 in a similar way.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT19

[0069] At 326, each loT device 304 of the group may transmit an individual command response to the NE 302. Each command response may include the respective new temporary device ID and the second freshness parameter.

[0070] At 328, the NE 302 may receive the individual command responses and may update the table with the new temporary device IDs included in the individual command responses, and potentially, new session keys.

[0071] At 330, the NE 302 may generate a group inventory request. The group inventory request may include the temporary group ID and a third freshness parameter. Further, upon generating the group inventory request, the NE 302 may precompute a new temporary device ID for each loT device 304 belonging to the temporary group ID and update the temporary group ID.

[0072] At 332, the NE 302 may transmit the group inventory request to the group of loT devices 304.

[0073] At 334, the group of loT devices 304 may recognize and receive the group inventory request. Further, at 334, the group of loT devices 304 may generate a new temporary group ID using the third freshness parameter. For example, the group of loT device 304 may perform a keyed hash function with the group security key over the freshness parameter and the temporary group ID. The temporary group ID is secret because it is transmitted protected to each of the loT devices 304.

[0074] At 336, the group of loT devices 304 may transmit responses to the group inventory request to the NE 302. That is, each loT device 304 may transmit a respective group inventory response. Each group inventory response may include the respective new temporary device ID and the third freshness parameter.

[0075] At 338, the NE 302 may receive the group inventory responses and may update the table accordingly. That is, the NE 302 may update the table with the new temporary device ID included in the group inventory responses.

[0076] In some examples, the NE 302 may not receive a group inventory response from at least one of the loT devices 304 of the group of loT devices 304. The NE 302 may detect that the NE 302 has failed to receive a response from the at least one loT device 304 if the NE 302 does not receive the new temporary device ID for the at least one loT device 304 at 336. This may indicate that the atAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT20least one loT device 304 never received the group inventory request and therefore, did not update the temporary group ID.

[0077] To address this issue, the NE 302 may transmit another global inventory request upon detecting the failure to receive the response from the at least one loT device 304. The global inventory request may include the same freshness parameter included in the global inventory request transmitted at 312 (e.g., the first freshness parameter) to avoid high precomputation loads. If the loT device 304 is still within range of the NE 302, the global inventory request prompts the loT device 304 to respond with a new temporary device ID. If the loT device 304 does not respond, the NE 302 may assume that the loT device 304 has moved out of the paging area and the NE 302 may drop the loT device 304 from the group of loT devices.

[0078] Additionally, or alternatively, the NE 302 may retransmit the group inventory request to the group of loT devices 304 upon detecting the failure to receive the response from the at least one loT device 304. The group inventory request may include the same temporary group ID that was included in the group inventory request transmitted at 332. Only loT devices 304 that did not respond to the initial group inventory request may respond to the retransmission of the group inventory request because these loT devices 304 did not update their temporary group ID. If the loT device 304 does not respond, the NE 302 may assume that the loT device 304 has moved out of the paging area and the NE 302 may drop the loT device 304 from the group of loT devices.

[0079] Additionally, or alternatively, the NE 302 may send an individual command request to the at least one loT device 304 in response to detecting the failure to receive the response from the at least one loT device 304. The individual command request may include the temporary device ID associated with the at least one loT device 304 that was included in the command response transmitted at 326. Further, the individual command request may include an encoded version of the new temporary group ID and the group security key such that the at least one loT device 304 can obtain the new temporary group ID. If the loT device 304 does not respond to the command request, the NE 302 may assume that the loT device 304 has moved out of the paging area and the NE 302 may drop the loT device 304 from the group of loT devices.

[0080] Figure 4 illustrates an example of a flowchart of a method 400 in accordance with aspects of the present disclosure. The operations of the method may be implemented by an loTAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT21device or an NE as described herein. In some implementations, the loT device or the NE may execute a set of instructions to control the function elements of the loT device or the NE to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0081] As shown in Figure 4, steps 402 and 404 may include an initialization procedure, steps 406 through 412 may include a group configuration procedure, steps 414 through 420 include a group inventory procedure, and step 422 includes a desynchronization handling procedure.

[0082] At 402, the loT device may receive a global inventory request with a first freshness parameter from the NE and generate a temporary device ID with the first freshness parameter and a shared security key.

[0083] At 404, the loT device may transmit a response to the global inventory request to the NE that includes the temporary device ID.

[0084] At 406, the NE may perform group management. During group management, the NE may map filtering information to a temporary group ID and generate a group security key for the temporary group ID. Additionally, group management may include the NE maintaining and storing mapping information in a table. The mapping information may include a mapping between permanent device IDs of loT devices and temporary device IDs of the loT devices. The mapping information may additionally, e or alternatively include a mapping between the filtering information and the temporary group ID. The NE may update the table each time the mapping information changes (e.g., after inventory or command dialog).

[0085] At 408, the NE may transmit individual command requests with an encrypted version of the temporary group ID, an encrypted version of the group security key, and a second freshness parameter. Additionally, or alternatively, the NE may precompute a new temporary device ID for all loT devices that belong to the temporary group ID.

[0086] At 410, the loT device may receive the individual command request and decrypt the individual command request to obtain the temporary group ID and the group security key.Additionally, or alternatively, the loT device may update the temporary device ID for the loT device with the second freshness parameter and the shared security key.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT22

[0087] At 412, the loT device may transmit a response to the command request to the NE that includes the updated temporary device ID.

[0088] At 414, the NE may generate a group inventory request for the temporary group ID and precompute a new expected temporary device ID and a new temporary group ID for the group of loT devices belonging to the temporary group ID.

[0089] At 416, the loT device may receive the group inventory request and update the temporary device ID as well as the temporary group ID.

[0090] At 418, the loT device may transmit a response to the group inventory response with the updated temporary device ID.

[0091] At 420, the NE may verify, based on the updated temporary device ID included in the group inventory response, which loT devices of the group replied to the group inventory response.

[0092] At 422, the NE may optionally perform mitigation of de-synchronization. In some examples, the NE may perform a de-synchronization handling procedure if the NE detects that the loT device did not respond to the group inventory request. As part of de-synchronization handling, the NE may send a global inventory request with a same freshness parameter that was included in the global inventory request at 402. Additionally, or alternatively, the NE may transmit retransmit the group inventory request to the group of loT devices. Additionally, or alternatively, the NE may transmit an individual command request to the loT device with the same temporary device ID included in the response transmitted at 412. The individual command request may include an encrypted version of the updated temporary group ID and the group security key.

[0093] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. In some examples, the UE 500 may be an example of an loT device as described with reference to Figures 1 through 4. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT23

[0094] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0095] The processor 502 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, a field-programmable gate-array (FPGA), or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.

[0096] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the UE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 504 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0097] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein. The UE 500 may be configured to or operable to support a means for receiving a command request that includes an encrypted temporary group ID and an encrypted group security key; decrypting the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device; receiving a group inventoryAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT24request with the temporary group ID; and updating the temporary group ID based on the group inventory request.

[0098] Additionally, or alternatively, the UE 500 may support at least one memory (e.g., the memory 504) and at least one processor (e.g., the processor 502) coupled with the at least one memory and configured to cause the UE to receive a command request that includes an encrypted temporary group ID and an encrypted group security key; decrypt the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device; receive a group inventory request with the temporary group ID; and update the temporary group ID based on the group inventory request.

[0099] Additionally, the UE 500 may be configured to support any one or combination of the at least one processor configured to cause the UE 500 to perform a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices.Additionally, the UE 500 may be configured to support any one or combination of the at least one processor configured to cause the UE 500 to transmit, in response to a global inventory request, a temporary device ID for the loT device; and update the temporary device ID for the loT device based on the group inventory request. Additionally, the UE 500 may be configured to support any one or combination of the at least one processor configured to cause the UE 500 to transmit a response to the group inventory request that includes the updated temporary device ID for the loT device.

[0100] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0101] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT25

[0102] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 510 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0103] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature AM (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0104] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0105] The processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT26may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0106] The controller 602 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0107] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory addresses of instructions associated with the memory 604. The controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 602 may be configured to manage flow of data within the processor 600. The controller 602 may be configured to control transfer of data between registers, ALUs 606, and other functional units of the processor 600.

[0108] The memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600). In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600).Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT27

[0109] The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 602 and / or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions. For example, the processor 600 and / or the controller 602 may be coupled with or to the memory 604, the processor 600, and the controller 602, and may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors and the memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0110] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 606 may be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.

[0111] The processor 600 may support wireless communication in accordance with examples as disclosed herein. The processor 600 may be configured to or operable to support at least one controller (e.g., the controller 602) coupled with at least one memory (e.g., the memory 604) and configured to cause the processor to identify a permanent device ID for each loT device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices; assign a temporary group ID and a group security key to the set of loT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of loTAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT28devices; transmit a command request to each loT device of the set of loT devices that includes an encrypted temporary group ID and an encrypted group security key; and transmit a group inventory request with the temporary group ID to the set of loT devices.

[0112] Additionally, the processor 600 may be configured to or operable to support any one or combination of updating the temporary group ID assigned to the set of loT devices based on the group inventory request. Additionally, the processor 600 may be configured to or operable to support any one or combination of performing a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices.

[0113] Additionally, the processor 600 may be configured to or operable to support any one or combination of receiving, from the set of loT devices and in response to a global inventory request, a temporary device ID for each loT device of the set of loT devices; and updating the temporary device IDs for the set of loT devices based on the group inventory request.

[0114] Additionally, the processor 600 may be configured to or operable to support any one or combination of storing a table that includes one or more of the permanent device IDs of the set of loT devices, temporary device IDs of the set of loT devices, expected temporary device IDs of the set of loT devices, the bitstring, temporary group IDs for the set of loT devices, a security key shared by the NE and the set of loT devices, session keys for the set of loT devices, or group security keys for the set of loT devices.

[0115] Additionally, the processor 600 may be configured to or operable to support any one or combination of detecting that a response to the group inventory request was not received from at least one loT device of the set of loT devices. Additionally, the processor 600 may be configured to or operable to support any one or combination of retransmitting, in response to detecting that the response was not received, the group inventory request to the set of loT devices assigned with the temporary group ID.

[0116] Additionally, the processor 600 may be configured to or operable to support any one or combination of transmitting, to the set of loT devices in response to detecting that the response was not received, a first global inventory request that includes a nonce that was included in a second global inventory request transmitted prior to the command request. Additionally, the processor 600Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT29may be configured to or operable to support any one or combination of retransmitting, in response to detecting that the response was not received, the command request to the at least one loT device.

[0117] Moreover, the processor 600 may be configured to or operable to support at least one controller (e.g., the controller 602) coupled with at least one memory (e.g., the memory 604) and configured to cause the processor to receive a command request that includes an encrypted temporary group ID and an encrypted group security key; decrypt the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device; receive a group inventory request with the temporary group ID; and update the temporary group ID based on the group inventory request.

[0118] Additionally, the processor 600 may be configured to or operable to support any one or combination of performing a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices. Additionally, the processor 600 may be configured to or operable to support any one or combination of transmitting, in response to a global inventory request, a temporary device ID for the loT device; and updating the temporary device ID for the loT device based on the group inventory request. Additionally, the processor 600 may be configured to or operable to support any one or combination of transmitting a response to the group inventory request that includes the updated temporary device ID for the loT device.

[0119] Figure 7 illustrates an example of an NE 700 in accordance with aspects of the present disclosure. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0120] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a DSP, an ASIC, or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT30

[0121] The processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the NE 700 to perform various functions of the present disclosure.

[0122] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the NE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as the memory 704 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0123] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein. The NE 700 may be configured to or operable to support a means for identifying a permanent device ID for each loT device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices; assigning a temporary group ID and a group security key to the set of loT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices; transmitting a command request to each loT device of the set of loT devices that includes an encrypted temporary group ID and an encrypted group security key; and transmitting a group inventory request with the temporary group ID to the set of loT devices.

[0124] Additionally, the NE 700 may be configured to or operable to support a means for updating the temporary group ID assigned to the set of loT devices based on the group inventory request. Additionally, the NE 700 may be configured to or operable to support a means for receiving, from the set of loT devices and in response to a global inventory request, a temporary Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT31device ID for each loT device of the set of loT devices; and updating the temporary device IDs for the set of loT devices based on the group inventory request.

[0125] Additionally, the NE 700 may be configured to or operable to support a means for storing a table that includes one or more of the permanent device IDs of the set of loT devices, temporary device IDs of the set of loT devices, expected temporary device IDs of the set of loT devices, the bitstring, temporary group IDs for the set of loT devices, a security key shared by the NE and the set of loT devices, session keys for the set of loT devices, or group security keys for the set of loT devices.

[0126] Additionally, the NE 700 may be configured to or operable to support a means for detecting that a response to the group inventory request was not received from at least one loT device of the set of loT devices. Additionally, the NE 700 may be configured to or operable to support a means for retransmitting, in response to detecting that the response was not received, the group inventory request to the set of loT devices assigned with the temporary group ID.

[0127] Additionally, or alternatively, the NE 700 may support at least one memory (e.g., the memory 704) and at least one processor (e.g., the processor 702) coupled with the at least one memory and configured to cause the NE to identify a permanent device ID for each loT device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices; assign a temporary group ID and a group security key to the set of loT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices; transmit a command request to each loT device of the set of loT devices that includes an encrypted temporary group ID and an encrypted group security key; and transmit a group inventory request with the temporary group ID to the set of loT devices.

[0128] Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to update the temporary group ID assigned to the set of loT devices based on the group inventory request. Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to perform a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT32

[0129] Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to receive, from the set of loT devices and in response to a global inventory request, a temporary device ID for each loT device of the set of loT devices; and update the temporary device IDs for the set of loT devices based on the group inventory request.

[0130] Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to store a table that includes one or more of the permanent device IDs of the set of loT devices, temporary device IDs of the set of loT devices, expected temporary device IDs of the set of loT devices, the bitstring, temporary group IDs for the set of loT devices, a security key shared by the NE and the set of loT devices, session keys for the set of loT devices, or group security keys for the set of loT devices.

[0131] Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to detect that a response to the group inventory request was not received from at least one loT device of the set of loT devices. Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to retransmit, in response to detecting that the response was not received, the group inventory request to the set of loT devices assigned with the temporary group ID.

[0132] Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to transmit, to the set of loT devices in response to detecting that the response was not received, a first global inventory request that includes a nonce that was included in a second global inventory request transmitted prior to the command request. Additionally, the NE 700 may be configured to support any one or combination of the at least one processor configured to cause the NE 700 to retransmit, in response to detecting that the response was not received, the command request to the at least one loT device.

[0133] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT33

[0134] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0135] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas to receive a signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a LNA) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0136] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as AM, FM, or digital modulation schemes like PSK or QAM. The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0137] Figure 8 illustrates a flowchart of a method 800 in accordance with aspects of the present disclosure. The operations of the method may be implemented by an loT device as described herein. In some implementations, the loT device may execute a set of instructions to control the function elements of the loT device to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0138] At 802, the method may include receiving a command request that includes an encrypted temporary group ID and an encrypted group security key. The operations of 802 may be performedAttorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT34in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by the UE 500 as described with reference to Figure 5.

[0139] At 804, the method may include decrypting the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by the UE 500 as described with reference to Figure 5.

[0140] At 806, the method may include receiving a group inventory request with the temporary group ID. The operations of 806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 806 may be performed the UE 500 as described with reference to Figure 5.

[0141] At 808, the method may include updating the temporary group ID based on the group inventory request. The operations of 808 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 808 may be performed the UE 500 as described with reference to Figure 5.

[0142] Figure 9 illustrates a flowchart of a method 900 in accordance with aspects of the present disclosure. The operations of the method may be implemented by an NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions. It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0143] At 902, the method may include identifying a permanent device ID for each loT device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by the NE 700 as described with reference to Figure 7.

[0144] At 904, the method may include assigning a temporary group ID and a group security key to the set of loT devices based on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices. The operations of 904 may be performed in Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT35accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by the NE 700 as described with reference to Figure 7.

[0145] At 906, the method may include transmitting a command request to each loT device of the set of loT devices that includes an encrypted temporary group ID and an encrypted group security key. The operations of 906 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 906 may be performed by the NE 700 as described with reference to Figure 7.

[0146] At 908, the method may include transmitting a group inventory request with the temporary group ID to the set of loT devices. The operations of 908 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 908 may be performed by the NE 700 as described with reference to Figure 7.

[0147] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Attorney Ref. No. SMM920250048-WO-PCT

Claims

Lenovo Ref. No. SMM920250048-WO-PCT36CLAIMSWhat is claimed is:

1. A network equipment (NE) for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and operable to cause the NE to:identify a permanent device identifier (ID) for each Internet-of-Things (loT) device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices;assign a temporary group ID and a group security key to the set of loT devices based at least in part on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices;transmit a command request to each loT device of the set of loT devices that comprises an encrypted temporary group ID and an encrypted group security key; and transmit a group inventory request with the temporary group ID to the set of loT devices.

2. The NE of claim 1 , wherein the at least one processor is further operable to cause the NE to update the temporary group ID assigned to the set of loT devices based at least in part on the group inventory request.

3. The NE of claim 2, wherein, to update the temporary group ID assigned to the set of loT devices, the at least one processor is operable to cause the NE to perform a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices.

4. The NE of any one of claims 1 to 3, wherein the at least one processor is further operable to cause the NE to:receive, from the set of loT devices and in response to a global inventory request, a temporary device ID for each loT device of the set of loT devices; andupdate the temporary device IDs for the set of loT devices based at least in part on the group inventory request.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT375. The NE of any one of claims 1 to 4, wherein the at least one processor is further operable to cause the NE to store a table that comprises one or more of the permanent device IDs of the set of loT devices, temporary device IDs of the set of loT devices, expected temporary device IDs of the set of loT devices, the bitstring, temporary group IDs for the set of loT devices, a security key shared by the NE and the set of loT devices, session keys for the set of loT devices, or group security keys for the set of loT devices.

6. The NE of any one of claims 1 to 5, wherein the at least one processor is further operable to cause the NE to detect that a response to the group inventory request was not received from at least one loT device of the set of loT devices.

7. The NE of claim 6, wherein the at least one processor is further operable to cause the NE to retransmit, in response to detecting that the response was not received, the group inventory request to the set of loT devices assigned with the temporary group ID.

8. The NE of claim 6 or claim 7, wherein the at least one processor is further operable to cause the NE to transmit, to the set of loT devices in response to detecting that the response was not received, a first global inventory request that comprises a nonce that was included in a second global inventory request transmitted prior to the command request.

9. The NE of any one of claims 6 to 8, wherein the at least one processor is further operable to cause the NE to retransmit, in response to detecting that the response was not received, the command request to the at least one loT device.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT3810. A method performed by a network equipment (NE), comprising:identifying a permanent device identifier (ID) for each Internet-of-Things (loT) device of a set of loT devices and a bitstring corresponding to one or more of the permanent device IDs of the set of loT devices;assigning a temporary group ID and a group security key to the set of loT devices based at least in part on the bitstring matching at least a portion of each of the permanent device IDs of the set of loT devices;transmitting a command request to each loT device of the set of loT devices that comprises an encrypted temporary group ID and an encrypted group security key; andtransmitting a group inventory request with the temporary group ID to the set of loT devices.

11. The method of claim 10, further comprising:updating the temporary group ID assigned to the set of loT devices based at least in part on the group inventory request.

12. The method of claim 10 or claim 11, further comprising:receiving, from the set of loT devices and in response to a global inventory request, a temporary device ID for each loT device of the set of loT devices; andupdating the temporary device IDs for the set of loT devices based at least in part on the group inventory request.

13. The method of any one of claims 10 to 12, further comprising:storing a table that comprises one or more of the permanent device IDs of the set of loT devices, temporary device IDs of the set of loT devices, expected temporary device IDs of the set of loT devices, the bitstring, temporary group IDs for the set of loT devices, a security key shared by the NE and the set of loT devices, session keys for the set of loT devices, or group security keys for the set of loT devices.

14. The method of any one of claims 10 to 13, further comprising:detecting that a response to the group inventory request was not received from at least one loT device of the set of loT devices.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT3915. The method of claim 14, further comprising:retransmitting, in response to detecting that the response was not received, the group inventory request to the set of loT devices assigned with the temporary group ID.

16. An Internet-of-Things (loT) device for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and operable to cause the loT device to:receive a command request that comprises an encrypted temporary group identifier (ID) and an encrypted group security key;decrypt the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device;receive a group inventory request with the temporary group ID; andupdate the temporary group ID based at least in part on the group inventory request.

17. The loT device of claim 16, wherein, to update the temporary group ID, the at least one processor is operable to cause the loT device to perform a keyed hash function with the group security key over a nonce and the temporary group ID assigned to the set of loT devices.

18. The loT device of claim 16 or claim 17, wherein the at least one processor is further operable to cause the loT device to:transmit, in response to a global inventory request, a temporary device ID for the loT device; andupdate the temporary device ID for the loT device based at least in part on the group inventory request.

19. The loT device of claim 18, wherein the at least one processor is further operable to cause the loT device to:transmit a response to the group inventory request that comprises the updated temporary device ID for the loT device.Attorney Ref. No. SMM920250048-WO-PCTLenovo Ref. No. SMM920250048-WO-PCT4020. A method performed by an Internet-of-Things (loT) device, comprising: receiving a command request that comprises an encrypted temporary group identifier (ID) and an encrypted group security key;decrypting the command request to obtain a temporary group ID and a group security key for a set of loT devices that includes the loT device;receiving a group inventory request with the temporary group ID; andupdating the temporary group ID based at least in part on the group inventory request.Attorney Ref. No. SMM920250048-WO-PCT