Method and device for a-iot device id reporting

Abstract

Various aspects of the present disclosure relate to methods and apparatuses for ambient Internet of Things (A-IOT) device identifier (ID) reporting. According to embodiments of the present disclosure, a network equipment (NE) can include at least one memory; and at least one processor coupled with the at least one memory and configured to cause the NE to: send, to a core network (CN) entity, an A-IOT device identifier (ID) for verification, wherein the A-IOT device ID is received from a UE during a random access procedure associated with an A-IOT device inventory for the UE; and receive, from the CN entity, a first indication indicating that the A-IOT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after the A-IOT device inventory, or indicating that the A-IOT device ID is invalid.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to methods and apparatus for reporting device identifiers (IDs) for environmental Internet of Things (A-IoT) devices. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as a base station (BS), which can support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.). Furthermore, the wireless communication system can support wireless communication across various wireless access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable wireless access technologies beyond 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a” preceding an element is unrestricted and is understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, the “or” used in a list of items contained in the claims (e.g., a list of items beginning with phrases such as “at least one of,” “one or more of,” or “one or both of”) indicates a list of inclusion, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, a “set” may contain one or more elements as included in the claims.

[0004] Some embodiments of the methods and apparatus described herein may include a network equipment (NE) for wireless communication. The NE may include: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the NE to: send an A-IoT device ID to a core network (CN) entity for verification, wherein the A-IoT device ID is received from the UE during a random access procedure associated with an A-IoT device inventory for the UE; and receive a first indication from the CN entity, the first indication indicating that the A-IoT device ID is valid, or indicating whether at least one subsequent command message for the UE exists after the A-IoT device inventory, or indicating that the A-IoT device ID is invalid.

[0005] In some embodiments of the NE described herein, the first indication indicates that the A-IOT device ID is valid, or that there are no subsequent commands for the UE after the A-IOT device inventory, and the at least one processor is configured to cause the NE to: send to the UE an acknowledgment (ACK) that the A-IOT device ID has been successfully identified and an indication that communication for the A-IOT device inventory for the UE is complete.

[0006] In some embodiments of the NE described herein, the first indication indicates that the A-IOT device ID is valid, and the at least one processor is configured to cause the NE to receive a second indication indicating that there are no subsequent commands for the UE after the A-IOT device inventory, and the at least one processor is configured to cause the NE to: send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and an indication that communication regarding the A-IOT device inventory for the UE is complete.

[0007] In some implementations of the NE described herein, the first indication indicates that the A-IOT device ID is valid, or indicates that there are no subsequent commands for the UE after the A-IOT device inventory, and the at least one processor is configured to cause the NE to: send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and a downlink (DL) signal for triggering another random access procedure associated with an A-IOT device inventory for another UE.

[0008] In some embodiments of the NE described herein, the first indication indicates that the A-IOT device ID is valid, and the at least one processor is configured to cause the NE to receive a second indication indicating that there are no subsequent commands for the UE after the A-IOT device inventory, and the at least one processor is configured to cause the NE to: send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with the A-IOT device inventory for another UE.

[0009] In some embodiments of the NE described herein, wherein the first indication indicates that the A-IOT device ID is valid or that at least one subsequent command message for the UE exists after the A-IOT device inventory, and the at least one processor is configured to cause the NE to: send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and an indication that at least one subsequent command message for the UE exists after the A-IOT device inventory.

[0010] In some embodiments of the NE described herein, the first indication indicates that the A-IoT device ID is valid, and the at least one processor is configured to cause the NE to receive a second indication, the second indication indicating that at least one subsequent command message for the UE exists after the A-IoT device inventory, and the at least one processor is configured to cause the NE to: send to the UE an acknowledgment that the A-IoT device ID has been successfully identified and an indication that at least one subsequent command message for the UE exists after the A-IoT device inventory.

[0011] In some embodiments of the NE described herein, the at least one processor is configured to cause the NE to: receive a third indication from the CN entity, the third indication indicating termination of communication with the UE along with a final command message for the UE or termination of communication with the UE after the final command message for the UE.

[0012] In some embodiments of the NE described herein, the first indication is a negative acknowledgment (NACK) message indicating that the A-IOT device ID is invalid, and the at least one processor is configured to cause the NE to send an indication to the UE indicating a retransmission of the A-IOT device ID.

[0013] Some embodiments of the methods and apparatus described herein may include a CN entity. The CN entity may include: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the CN entity to: receive an A-IoT device ID of a UE from an NE for verification; verify whether the A-IoT device ID is valid; and send a first indication to the NE, the first indication indicating that the A-IoT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after an A-IoT device inventory for the UE, or indicating that the A-IoT device ID is invalid.

[0014] In some implementations of the CN entity described herein, in response to the A-IoT device ID being valid and no subsequent command messages for the UE following the A-IoT device inventory for the UE, the first indication indicates that the A-IoT device ID is valid, or indicates that no subsequent command messages for the UE following the A-IoT device inventory for the UE; or the first indication indicates that the A-IoT device ID is valid, and the at least one processor is configured to cause the CN entity to send a second indication, the second indication indicating that no subsequent commands for the UE following the A-IoT device inventory.

[0015] In some implementations of the CN entity described herein, in response to the A-IoT device ID being valid and at least one subsequent command message for the UE existing after the A-IoT device inventory for the UE, the first indication indicates that the A-IoT device ID is valid or that at least one subsequent command message for the UE exists after the A-IoT device inventory for the UE; or the first indication indicates that the A-IoT device ID is valid, and the at least one processor is configured to cause the CN entity to send a second indication, the second indication indicating that at least one subsequent command message for the UE exists after the A-IoT device inventory.

[0016] In some embodiments of the CN entity described herein, the at least one processor is configured to cause the CN entity to: send a third indication to the NE, the third indication indicating termination of communication with the UE along with a final command message for the UE or termination of communication with the UE after the final command message for the UE.

[0017] In some implementations of the CN entity described herein, in response to verifying that the A-IOT device ID is invalid, the first indication is a NACK message indicating that the A-IOT device ID is invalid.

[0018] In some implementations of the CN entity described herein, the at least one processor is configured to cause the CN entity to: determine, in response to the validity of the A-IOT device ID, whether there is at least one subsequent command for the UE after the A-IOT device inventory for the UE.

[0019] Some embodiments of the methods and apparatus described herein may include a UE. The UE may include: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the NE to: transmit the A-IoT device ID of the UE to the NE during a random access procedure associated with an A-IoT device inventory for the UE; and in response to transmitting the A-IoT device ID, receive from the NE one of the following: an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating completion of communication for the A-IoT device inventory; an acknowledgment that the A-IoT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an inventory for another UE; an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating the existence of at least one subsequent command message after the inventory; or an indication indicating retransmission of the A-IoT device ID.

[0020] In some implementations of the UE described herein, in response to receiving the instruction indicating a retransmission of the A-IOT device ID, the at least one processor is configured to cause the UE to: retransmit the A-IOT device ID to the NE.

[0021] Some embodiments of the methods and apparatus described herein may include a processor for wireless communication. The processor may include: at least one controller coupled to at least one memory and configured to cause the processor to: send an A-IoT device ID to a CN entity for verification, wherein the A-IoT device ID is received from the UE during a random access procedure associated with an A-IoT device inventory for the UE; and receive a first indication from the CN entity, the first indication indicating that the A-IoT device ID is valid, or indicating whether at least one subsequent command message for the UE exists after the A-IoT device inventory, or indicating that the A-IoT device ID is invalid.

[0022] Some embodiments of the methods and apparatus described herein may include a processor. The processor may include: at least one controller coupled to at least one memory and configured to cause the processor to: receive an A-IoT device ID of a UE from a NE for verification; verify whether the A-IoT device ID is valid; and send a first indication to the NE, the first indication indicating that the A-IoT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after an A-IoT device inventory for the UE, or indicating that the A-IoT device ID is invalid.

[0023] Some embodiments of the methods and apparatus described herein may include a processor. The processor may include: at least one controller coupled to at least one memory and configured to cause the processor to: transmit the A-IoT device ID of the UE to a NE during a random access procedure associated with an A-IoT device inventory for the UE; and, in response to transmitting the A-IoT device ID, receive from the NE one of the following: an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating completion of communication for the A-IoT device inventory; an acknowledgment that the A-IoT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an inventory for another UE; an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating the existence of at least one subsequent command message after the inventory; or an indication indicating retransmission of the A-IoT device ID.

[0024] Some embodiments of the methods and apparatus described herein may include a method performed by the NE. The method may include: sending an A-IOT device ID to a CN entity for verification, wherein the A-IOT device ID is received from the UE during a random access procedure associated with an A-IOT device inventory for the UE; and receiving a first indication from the CN entity, the first indication indicating that the A-IOT device ID is valid, or indicating whether at least one subsequent command message for the UE exists after the A-IOT device inventory, or indicating that the A-IOT device ID is invalid.

[0025] Some implementations of the methods and apparatus described herein may include a method performed by a CN entity. The method may include: receiving an A-IoT device ID of a UE from an NE for verification; verifying whether the A-IoT device ID is valid; and sending a first indication to the NE, the first indication indicating that the A-IoT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after an A-IoT device inventory for the UE, or indicating that the A-IoT device ID is invalid.

[0026] Some embodiments of the methods and apparatus described herein may include a method performed by a UE. The method may include: sending the UE's A-IoT device ID to a NE during a random access procedure associated with an A-IoT device inventory for the UE; and in response to sending the A-IoT device ID, receiving from the NE one of the following: an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating completion of communication for the A-IoT device inventory; an acknowledgment that the A-IoT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an inventory for another UE; an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating the existence of at least one subsequent command message after the inventory; or an indication indicating retransmission of the A-IoT device ID. Attached Figure Description

[0027] To describe how the advantages and features of this application can be obtained, the description of this application is presented with reference to specific embodiments of the application shown in the accompanying drawings. These drawings depict only exemplary embodiments of the application and should therefore not be considered as limiting the scope of the application.

[0028] Figure 1 Examples of wireless communication systems according to various aspects of this disclosure are shown.

[0029] Figure 2 This demonstrates a sample query process as defined in the RFID specification.

[0030] Figure 3 An exemplary random access procedure for an A-IoT device is shown according to various aspects of this disclosure.

[0031] Figure 4 An exemplary process for indicating the state of an A-IoT device using signals, according to various aspects of this disclosure, is shown.

[0032] Figure 5 A flowchart is shown illustrating an exemplary method performed by an NE according to various aspects of this disclosure.

[0033] Figure 6 A flowchart illustrating an exemplary method performed by a CN entity according to various aspects of this disclosure is shown.

[0034] Figure 7 A flowchart illustrating an exemplary method performed by a UE according to various aspects of this disclosure is shown.

[0035] Figure 8 Examples of NEs according to various aspects of this disclosure are shown.

[0036] Figure 9Examples of CN entities are shown according to various aspects of this disclosure.

[0037] Figure 10 Examples of UEs according to various aspects of this disclosure are shown.

[0038] Figure 11 Examples of processors according to various aspects of this disclosure are shown. Detailed Implementation

[0039] The detailed description of the accompanying drawings is intended as a description of preferred embodiments of the present application and is not intended to represent the only forms in which the present application may be practiced. It should be understood that the same or equivalent functionality may be accomplished by different embodiments intended to be covered within the spirit and scope of the present application.

[0040] Although the accompanying drawings depict operations in a specific order, those skilled in the art will readily recognize that these operations need not be performed in the specific order or sequence shown, or that one or more operations may sometimes be skipped to achieve the desired result among all the illustrated operations to be performed. Furthermore, the drawings may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between the illustrated operations. In some cases, multitasking and parallel processing may be advantageous.

[0041] Reference will now be made in detail to some embodiments of this disclosure, examples of which are illustrated in the accompanying drawings. For ease of understanding, embodiments are provided for specific network architectures and new service scenarios, such as 3GPP Long Term Evolution (LTE) and LTE Advanced, 3GPP 5G New Radio (NR), 5G Advanced, 6G, etc. It is understood that all embodiments in this disclosure are applicable to similar technical problems as network architectures and new service scenarios evolve; furthermore, the terminology described in this disclosure may change without affecting the principles of this disclosure.

[0042] Various aspects of this disclosure are described in the context of wireless communication systems.

[0043] Figure 1Examples of a wireless communication system 100 according to various aspects of this disclosure are shown. The wireless communication system 100 may include one or more NEs (e.g., BSs) 102, one or more UEs 104, and CNs 106. The wireless communication system 100 may support various wireless access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable wireless access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support wireless access technologies beyond 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0044] One or more NEs 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receiving signaling, sending signaling) via a Uu interface.

[0045] NE 102 can provide a geographic coverage area, wherein NE 102 can support the services of one or more UE 104s within the geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some embodiments, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas associated with the same or different radio access technologies may overlap, but these different geographic coverage areas may be associated with different NE 102s.

[0046] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or any other suitable term. In some embodiments, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples.

[0047] UE 104 can support direct wireless communication with other UE 104 via a communication link. For example, UE 104 can support direct wireless communication with another UE 104 via 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, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0048] NE 102 may support communication with CN 106, or with another NE 102, or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate indirectly with each other (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0049] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)), and user plane entities that route packets or interconnect to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions of one or more UE 104 served by one or more NE102s associated with CN 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).

[0050] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session, etc.) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session can be an example of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0051] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 can support different resource structures. For example, NE 102 and UE 104 can support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 can support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 can support various frame structures (e.g., multiple frame structures). NE 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0052] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. The first parameter set (e.g., This can be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first set of parameters associated with the first subcarrier spacing (e.g., 15 kHz) is... One time slot can be used per subframe. The second parameter set (e.g., This can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third parameter set (e.g., This can be associated with the third subcarrier spacing (e.g., 60 kHz) and the normal cyclic prefix or extended cyclic prefix. The fourth parameter set (e.g., This can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., This can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0053] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame may have a duration, such as 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, such as 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0054] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more sets of parameters supported in the wireless communication system 100. For example, a first, second, third, fourth, and fifth set of parameters (e.g., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. , , , , The subframe can utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot can contain a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the parameter set. For a normal cyclic prefix, a time slot can contain 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can contain 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for normal and extended cyclic prefixes can depend on the parameter set. It should be understood that for a first parameter set (e.g., quantity) associated with a first subcarrier spacing (e.g., 15 kHz), The references to ) can be used interchangeably between subframes and time slots.

[0055] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency ranges specified as 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 embodiments, NE 102 and UE 104 may perform wireless communication on one or more of the operating frequency bands. In some embodiments, FR1 may be used by NE 102 and UE 104, as well as other equipment or devices for cellular communication services (e.g., control information, data). In some implementations, FR2 may be used by NE 102 and UE104, as well as other equipment or devices for short-range high data rate capability.

[0056] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the following: the first parameter set (e.g., ), which includes a 15 kHz subcarrier spacing; the second parameter set (e.g., ), which includes a 30 kHz subcarrier spacing; and a third parameter set (e.g., ), which includes a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with the following: a third parameter set (e.g., ), which includes a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., It contains a 120 kHz subcarrier spacing.

[0057] The Internet of Things (IoT) has attracted a lot of attention in the world of wireless communications, where IoT devices typically have a smaller size, lower complexity, lower power consumption, and a larger number (e.g., hundreds or even hundreds of billions of IoT devices) than existing UEs.

[0058] IoT devices are typically battery-free devices without energy storage capabilities, or devices with energy storage that do not require manual replacement or recharging. For such devices, energy can be provided by harvesting radio waves, light, motion, heat, or any other suitable power source. For simplicity, such IoT devices may be referred to as A-IoT devices. In other words, an A-IoT device can be an IoT device with limited energy storage capabilities and powered by energy harvesting.

[0059] At the RAN1#116 meeting, a consensus was reached that the time-slot-based ALOHA protocol can serve as a baseline for designing random access procedures for A-IoT devices.

[0060] As an application of the slotted ALOHA protocol, RFID readers (or RFID readers / writers) can use the query process defined in the RFID specification to obtain dedicated tag information for subsequent unicast communication. For example, the tag information may include at least one of the following: Protocol Control / Extended Protocol Control (PC / XPC), Electronic Product Code (EPC), or Packet Cyclic Redundancy Check (CRC).

[0061] Figure 2 This demonstrates a sample query process as defined in the RFID specification.

[0062] refer to Figure 2 At the beginning, the reader can send a Select command to a set of tags (e.g., via multicast) so that the reader can select the desired subset of tags to perform the query.

[0063] Next, the reader can send a Query command to the tag subset (e.g., via multicast). The Query command can contain a value (e.g., represented as "Q"). For example, Q can be an integer in the range (0, 15). Once the Query command is received, each tag in the tag subset can randomly select 0 or 2. Q-1 The time slot number (e.g., denoted as j) is preloaded into its time slot counter.

[0064] For any tag, if j=0, the tag may send (e.g., via backscatter) a 16-bit random number (e.g., denoted as RN16) to the reader; otherwise, the tag may not perform a UL transmission. The tag may decrement j by one each time it receives a QueryRep command, and send RN16 to the reader when j reaches 0.

[0065] exist Figure 2 In the example, under short-range coverage, if a single tag responds with an RN16 in a given round of the query process, the reader can successfully decode the RN16 and return an "ACK" response to the tag, triggering tag information reporting. However, in high-density use cases, multiple tags may choose the same time slot to send RN16, which can lead to collisions and detection failures at the reader. If a collision occurs, the tag can wait for the next round of the query process to report its dedicated tag information.

[0066] refer to Figure 2 In response to a Query command, a single tag can randomly select a timeslot number equal to 0, and then the tag can send an RN16 to the reader. The reader can successfully decode the RN16 and return an "ACK" response to the tag to trigger a tag information report. For example, the tag information can contain at least one of the following: PC / XPC, EPC, or packet CRC. The process from sending the Query command to receiving the tag information can be called a single-tag response.

[0067] In some cases, the tag's EPC can be valid (e.g., the tag's EPC can be successfully identified), and then the reader can send a QueryRep command to trigger the next round of the query process, or send other commands for the tag.

[0068] In some cases, the tag's EPC may be invalid (e.g., the tag's EPC cannot be successfully recognized), and the reader may then return a "NACK" response to the tag.

[0069] According to some embodiments of this disclosure, a random access procedure for an A-IoT device can be designed based on the query procedure defined in the RFID specification.

[0070] Figure 3 An exemplary random access procedure for an A-IoT device is shown according to various aspects of this disclosure.

[0071] refer to Figure 3 The random access process for A-IoT devices may begin at step 300. Step 300 may include steps 300-1 and 300-2.

[0072] In step 300-1, the reader (e.g., NE) may send a SELECT command to a set of A-IoT devices, enabling the reader to select a desired subset of A-IoT devices to perform access. SELECT may contain a value (e.g., denoted as "Q"). For example, Q may be an integer in the range (0, 15).

[0073] In response to receiving a SELECT command, each A-IoT device in a subset of A-IoT devices can randomly select a time slot number between 0 and N (e.g., denoted as j) (where N = fun.(Q)). For example, N = 2 Q-1 .

[0074] In step 300-2, the reader may send a DL signal to trigger a subset of A-IoT devices to perform access. For example, the DL signal may resemble a Query command or QueryRep command in the RFID specification. In some examples, the DL signal may also contain scheduling information indicating corresponding UL transmission parameters. For example, corresponding UL transmission parameters may include at least one of the following: time and / or frequency resources, modulation scheme, coding rate, and / or payload size. In some examples, considering that the A-IoT device can perform uplink (UI) amplification, the scheduling information may also indicate power control related parameters.

[0075] In response to receiving the DL signal, each A-IOT device in the subset of A-IOT devices can subtract one from j.

[0076] In some cases, for a specific A-IoT device, if j=0, the A-IoT device may perform a UL transfer based on the scheduling information indicated by the reader in step 300-2. The UL transfer may contain at least a random number (RN), such as RN16.

[0077] In some other cases, for a specific A-IoT device, if j ≠ 0, the A-IoT device may not send any content and wait for the next DL signal. The A-IoT device may decrement j by one each time it receives a DL signal, and send a random number, such as RN16, when j reaches 0.

[0078] refer to Figure 3 For A-IoT devices in a subset of A-IoT devices, j=0. Next, in step 301, the A-IoT device may send a UL transmission to the reader based on the scheduling information indicated by the reader in step 300-2, wherein the UL transmission may contain at least a random number, such as RN16. In the following steps, RN16 is used as an example of a random number for illustration.

[0079] In step 302, in response to receiving RN16 sent by the A-IoT device, the reader may send an ACK message to the A-IoT device to confirm the successful reception of the UL transmission in step 301. The ACK message may contain the same RN16 as the RN16 included in step 301 and scheduling information for sending the next UL transmission.

[0080] In step 303, in response to receiving an ACK message, the A-IOT device may send its A-IOT device ID (e.g., at least one of PC / XPC, EPC, or packet CRC) to the reader based on the scheduling information in step 302.

[0081] In step 304, in response to receiving the A-IoT device ID, the reader may send an ACK message to the A-IoT device to confirm successful reception of the A-IoT device ID. The ACK message in this document may contain at least the same RN16 as the RN16 included in step 301, indicating successful reception of the A-IoT device ID.

[0082] Following a random access procedure for inventorying A-IoT devices, there may or may not be one or more command operations targeting the A-IoT devices. If one or more command operations target the A-IoT devices after the random access procedure, the reader (e.g., NE) should maintain communication with the A-IoT devices. If no one or more command operations target the A-IoT devices after the random access procedure, the reader may send a DL signal to trigger a random access procedure for another A-IoT device. Therefore, the reader should be aware of whether subsequent communication is required after the random access procedure for the A-IoT devices so that it can perform the corresponding operation. In this document, inventory is used to identify individual A-IoT devices. A command or command operation is defined as communicating with the identified A-IoT device to perform an operation on the A-IoT device, such as reading (reading data from the A-IoT device), writing (writing data to the A-IoT device), or deactivating (temporarily or permanently deactivating the A-IoT device).

[0083] Therefore, how the NE knows whether further communication is needed is a technical problem that needs to be solved.

[0084] Embodiments of this disclosure provide a solution for A-IoT device ID reporting, particularly for using signals to indicate the status of A-IoT devices during A-IoT device ID reporting, so that the NE will know whether subsequent communication is needed after the random access process for inventory of A-IoT devices and perform the corresponding operation. Further details will be described in the following text in conjunction with the accompanying drawings.

[0085] Figure 4An exemplary process for A-IoT device ID reporting is shown according to various aspects of this disclosure.

[0086] Figure 4 The method in the example can be performed by a CN entity (e.g., AIOTF or AMF), an NE (e.g., BS), and multiple UEs (e.g., including UE#1). Each of the multiple UEs can be an A-IOT device or a device with characteristics similar to an A-IOT device.

[0087] Although for illustrative purposes Figure 4 A user interface (UE) was depicted, but after consideration, Figure 4 The process shown can involve any number of UEs. Furthermore, although the method is shown at the system level by the CN entity, NE, and UE, those skilled in the art will understand that the operations implemented in the CN entity, NE, and UE can be implemented independently and incorporated by other devices with similar functionality.

[0088] exist Figure 4 In the example, the CN entity can trigger an A-IoT communication task for inventory. Inventory can be used to identify individual A-IoT devices, and therefore can also be referred to as A-IoT device inventory.

[0089] In step 400, the CN entity may send inventory information to the NE. Therefore, in step 401, the NE can receive inventory information from the CN entity. The inventory information may include a value (e.g., denoted as Q) associated with a time slot counter related to the inventory task. For example, Q may be an integer in the range (0, 15).

[0090] In some examples, the information used for inventory may be included in the paging message used for inventory.

[0091] In step 401, the NE may send a SELECT command to a group of UEs to select a desired subset of UEs (e.g., including UE#1) to perform access for inventory. In some examples, the SELECT command may be included in a paging message for inventory. In some examples, the SELECT command may include a value Q, which is included in the information for inventory.

[0092] In response to receiving a SELECT command, each UE in a subset of UEs can randomly select a time slot number between 0 and N (e.g., denoted as j) (where N = fun.(Q)). For example, N = 2 Q-1 .

[0093] The NE can perform the inventory process by triggering a random access procedure for a subset of the UEs.

[0094] For example, in step 402, the NE may send a DL signal to trigger a subset of UEs (e.g., including UE#1) to perform access. For example, the DL signal may resemble a Query command or QueryRep command in an RFID specification.

[0095] In some examples, the DL signal may also include scheduling information indicating corresponding UL transmission parameters. For example, corresponding UL transmission parameters may include at least one of the following: time and / or frequency resources, modulation scheme, coding rate, and / or payload size. In some examples, the scheduling information may also indicate power control related parameters.

[0096] In response to receiving the DL signal, each UE in the subset of UEs can subtract one from j.

[0097] In some cases, if j=0, the UE can perform a UL transmission based on scheduling information. The UL transmission can contain at least a random number, such as RN16.

[0098] In some other cases, if j≠0, the UE may not send any content and wait for the next DL signal. The UE may decrement j by one each time it receives a DL signal, and send a random number, such as RN16, when j reaches 0.

[0099] exist Figure 4 In the embodiment, after subtracting one from j, the value j of UE#1 can reach 0. In step 403, since j=0, UE#1 can send a UL transmission based on the scheduling information in step 402. The UL transmission can contain at least a random number, such as RN16. In the following steps, RN16 is used as an example of a random number for illustration. The UL transmission in step 403 can also be referred to as Msg.1 in the random access procedure associated with the A-IOT device inventory for UE#1.

[0100] In step 404, in response to receiving RN16 sent by UE#1 in step 403, NE may send a message (e.g., an ACK message) to UE#1 to confirm the successful reception of the UL transmission in step 403. The message may contain the same RN16 as the one included in step 403 and scheduling information for sending the next UL transmission. The message in step 404 may also be referred to as Msg.2 in the random access procedure associated with the A-IOT device inventory for UE#1.

[0101] In step 405, in response to receiving the message, UE#1 may send its A-IoT device ID to the NE based on the scheduling information in step 404. For example, the A-IoT device ID may contain at least one of PC / XPC, EPC, or CRC. As another example, the A-IoT device ID may contain at least one of the following: information that can be used to identify the UE and verification information (e.g., CRC) used to identify the UE. The message in step 405 may also be referred to as Msg.3 in the random access procedure associated with the A-IoT device inventory for UE#1.

[0102] In step 406, in response to receiving the A-IOT device ID from UE#1, the NE may send the A-IOT device ID of UE#1 to the CN entity for verification.

[0103] In step 407, in response to receiving the A-IoT device ID of UE#1, the CN may verify whether the A-IoT device ID is valid. In some examples, the CN may also determine whether there is at least one subsequent command for UE#1 after the A-IoT device inventory for UE#1. As an example, in response to the A-IoT device ID being valid, the CN may also determine whether there is at least one subsequent command for UE#1 after the A-IoT device inventory for UE#1. As another example, the CN may determine whether there is at least one subsequent command for UE#1 after the A-IoT device inventory for UE#1, regardless of whether the A-IoT device ID of UE#1 is valid.

[0104] Considering the different results regarding whether the A-IOT device ID is valid and whether there is at least one subsequent command for UE#1 after the A-IOT device inventory for UE#1, subsequent signaling and operations can generally be divided into three cases, such as case 1, case 2 and case 3.

[0105] Case 1

[0106] In Case 1, the A-IOT device ID is verified as valid, and there are no subsequent command messages for UE#1 after the A-IOT device inventory for UE#1. Case 1 may further include Case 1-1 and Case 1-2.

[0107] Case 1-1

[0108] In case 1-1, in step 408, in response to the A-IOT device ID being verified as valid and no subsequent command message for UE#1 being sent after the A-IOT device inventory for UE#1, CN may send a first instruction to NE.

[0109] In some examples, the first indication can indicate that the A-IOT device ID is valid. The first indication can also suggest that there are no subsequent command messages for UE#1 after the A-IOT device inventory for UE#1.

[0110] In some other examples, the first indication may indicate that no subsequent command messages for UE#1 exist after an A-IOT device inventory for UE#1. For example, the first indication may be a query completion indication that instructs the NE to trigger an A-IOT device inventory for another UE. As another example, the first indication may be a no-follow-command indication. The first indication may also imply that the A-IOT device ID is valid.

[0111] In response to receiving the first indication in step 408, the NE knows that the A-IOT device ID is valid and that there are no subsequent command messages for UE#1 after the A-IOT device inventory for UE#1.

[0112] According to some embodiments of this application, in response to receiving the first indication in step 408, the NE may send to the UE#1 an acknowledgment that the A-IoT device ID has been successfully identified (e.g., an acknowledgment that the A-IoT device ID is valid) and an indication that communication for the A-IoT device inventory of the UE#1 has been completed (e.g., a completion indication). For example, the acknowledgment may be an indication that the A-IoT device ID has been successfully identified (e.g., the A-IoT device ID is valid).

[0113] In some examples, acknowledgment and indication may be contained in a single message, and the NE may send the message to UE#1 in step 409. The message in this document may also be referred to as Msg.4 in the random access procedure associated with an A-IOT device inventory for UE#1.

[0114] In some other examples, acknowledgment may be included in one message, and indication may be included in another message. In step 409, the NE may send a message containing acknowledgment, and also send another message containing indication. The message containing acknowledgment may also be referred to as Msg.4 in the random access procedure associated with the A-IOT device inventory for UE#1.

[0115] According to some embodiments of this application, in response to receiving the first indication in step 408, the NE may send to UE#1 an acknowledgment that the A-IoT device ID has been successfully identified (e.g., an acknowledgment that the A-IoT device ID is valid) and a DL signal for triggering another random access procedure associated with an A-IoT device inventory for another UE. For example, the acknowledgment may be an indication that the A-IoT device ID has been successfully identified (e.g., the A-IoT device ID is valid).

[0116] For example, in step 409, the NE may send a message containing an acknowledgment to UE#1. This message in step 409 may also be referred to as Msg.4 in the random access procedure associated with an A-IoT device inventory for UE#1. In step 410, the NE may send a DL signal to a subset of the UEs. If UE#1 receives the DL signal in step 410, UE#1 may terminate communication.

[0117] Case 1-2

[0118] In cases 1-2, in step 408, in response to the A-IOT device ID being verified as valid and no subsequent command messages for UE#1 being sent after the A-IOT device inventory for UE#1, CN may send a first instruction and a second instruction to NE.

[0119] The first indication may indicate that the A-IoT device ID is valid. The second indication may suggest that there are no subsequent command messages for UE#1 after the A-IoT device inventory for UE#1. For example, the second indication may be a query completion indication that instructs the NE to trigger an A-IoT device inventory for another UE. As another example, the second indication may be a no-follow-command indication.

[0120] The first instruction and the second instruction may be contained in a single message sent from the CN to the NE, or they may be contained in separate messages sent from the CN to the NE.

[0121] In response to receiving the first instruction and the second instruction in step 408, the NE knows that the A-IOT device ID is valid and that there are no subsequent command messages for UE#1 after the A-IOT device inventory for UE#1.

[0122] Next, NE and UE#1 can perform step 409, or steps 409 and 410. All operations related to steps 409 and 410 in case 1-1 can also be applied here. Therefore, for simplicity, details are omitted.

[0123] Case 2

[0124] In scenario 2, the A-IOT device ID is verified as valid, and at least one subsequent command message for UE#1 exists after the A-IOT device inventory for UE#1. Scenario 2 may further include scenarios 2-1 and 2-2.

[0125] Case 2-1

[0126] In case 2-1, in step 411, in response to the A-IOT device ID being verified as valid and at least one subsequent command message for UE#1 existing after the A-IOT device inventory for UE#1, CN may send a first instruction to NE.

[0127] In some examples, the first indication may indicate that the A-IOT device ID is valid. The first indication may suggest that at least one subsequent command message for UE#1 exists after an A-IOT device inventory for UE#1.

[0128] In some other examples, the first indication may indicate that at least one subsequent command message for UE#1 exists after an A-IOT device inventory for UE#1. For example, the first indication may be a subsequent command indication. The first indication may imply that the A-IOT device ID is valid.

[0129] In response to receiving the first indication in step 411, the NE knows that the A-IOT device ID is valid and that there is at least one follow-up command message for UE#1 after the A-IOT device inventory for UE#1.

[0130] Therefore, the NE can maintain communication with UE#1 to receive subsequent command messages for UE#1. The NE can send to UE#1 an acknowledgment that the A-IoT device ID has been successfully identified (e.g., an acknowledgment that the A-IoT device ID is valid) and an indication that at least one subsequent command message for UE#1 exists after the A-IoT device inventory for UE#1 (e.g., a subsequent command indication). For example, the acknowledgment could be an indication that the A-IoT device ID has been successfully identified (e.g., the A-IoT device ID is valid).

[0131] In some examples, acknowledgment and indication may be contained in a single message, and the NE may send the message to UE#1 in step 412. The message in this document may also be referred to as Msg.4 in the random access procedure associated with an A-IOT device inventory for UE#1.

[0132] In some other examples, acknowledgment may be included in one message, and indication may be included in another message. In step 412, the NE may send a message containing acknowledgment, and also send another message containing indication. The message containing acknowledgment may also be referred to as Msg.4 in the random access procedure associated with the A-IOT device inventory for UE#1.

[0133] In step 413, the CN entity may, for example, send at least a command message for UE#1 via the NE. For instance, the command message may instruct the UE to perform at least one of reading, writing, deactivation, etc. UE#1 may perform the corresponding operation and / or, for example, send information required by the CN entity to the CN entity via the NE.

[0134] In some embodiments of scenario 2, when all subsequent command messages for UE#1 have been sent, the CN entity may send an indication to the NE to terminate communication with UE#1 (e.g., a query end indication). As an example, the indication may be sent along with the last command message for UE#1. As another example, the indication may be sent after the last command message for UE#1 has been sent (e.g., successfully sent).

[0135] In some cases, after receiving the instruction, the NE may send an instruction to UE#1 indicating the completion of communication for the A-IOT device inventory for UE#1 (e.g., a completion instruction), or the NE may send a DL signal to trigger the A-IOT device inventory for another UE.

[0136] Case 2-2

[0137] In case 2-2, in step 412, in response to the A-IOT device ID being verified as valid and at least one subsequent command message for UE#1 existing after the A-IOT device inventory for UE#1, CN may send a first instruction and a second instruction to NE.

[0138] The first indication may indicate that the A-IoT device ID is valid. The second indication may indicate that at least one subsequent command message exists for UE#1 after the A-IoT device inventory for UE#1. For example, the second indication may be a subsequent command indication.

[0139] The first instruction and the second instruction may be contained in a single message sent from the CN to the NE, or they may be contained in separate messages sent from the CN to the NE.

[0140] In response to receiving the first instruction and the second instruction in step 411, the NE knows that the A-IOT device ID is valid and that there is at least one follow-up command message for UE#1 after the A-IOT device inventory for UE#1.

[0141] Subsequently, all operations related to steps 412 and 413, as well as the subsequent operations in case 2-1, can also be applied here. Therefore, for simplicity, details are omitted.

[0142] Case 3

[0143] In case 3, the A-IOT device ID is verified as invalid.

[0144] In step 414, in response to the A-IoT device ID being verified as invalid, CN may send a first indication to NE. The first indication may be a NACK message indicating that the A-IoT device ID is invalid.

[0145] In step 415, in response to receiving the first indication, the NE may send an indication to UE#1 indicating a retransmission of the A-IoT device ID of UE#1 (e.g., an A-IoT device ID request indication). This indication may be included in a message, which may also be referred to as Msg.4 in the random access procedure associated with an A-IoT device inventory for UE#1.

[0146] In step 416, in response to receiving an instruction to retransmit the A-IoT device ID, UE#1 may retransmit its A-IoT device ID to the NE. For example, the A-IoT device ID of UE#1 may be included in a message identical to the aforementioned Msg.3 in the random access procedure associated with the inventory of A-IoT devices for UE#1. That is, UE#1 may retransmit the aforementioned Msg.3.

[0147] In step 417, in response to receiving the A-IOT device ID of UE#1, the NE may send the A-IOT device ID to the CN entity for verification. Depending on whether the A-IOT device ID is valid, subsequent operations may be any of those described above.

[0148] Figure 5 A flowchart illustrating exemplary methods according to various aspects of this disclosure is shown. Figure 5 The operation of the method shown can be performed by the NE described herein (e.g., Figure 1 This can be performed by the NE (102) or other devices with similar functions. In some embodiments, the NE can execute a set of instructions to control the functional elements of the NE to perform the described operations or functions.

[0149] like Figure 5 As shown, in step 502, the NE may send the A-IOT device ID to the CN entity for verification, wherein the A-IOT device ID is received from the UE during a random access procedure associated with an A-IOT device inventory for the UE.

[0150] In step 504, the NE may receive a first indication from the CN entity, the first indication indicating that the A-IOT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after the A-IOT device inventory, or indicating that the A-IOT device ID is invalid.

[0151] According to some embodiments of this disclosure, the first indication indicates that the A-IoT device ID is valid, or that there are no subsequent commands for the UE after the A-IoT device inventory, and the NE can send to the UE an acknowledgment that the A-IoT device ID has been successfully identified and an indication that the communication for the A-IoT device inventory for the UE is complete.

[0152] According to some embodiments of this disclosure, the first indication indicates that the A-IoT device ID is valid, or the UE can receive a second indication, the second indication indicating that there are no subsequent commands for the UE after the A-IoT device inventory, and the UE can: send to the UE an acknowledgment that the A-IoT device ID has been successfully identified and an indication that the communication for the A-IoT device inventory for the UE is completed.

[0153] According to some embodiments of this disclosure, the first indication indicates that the A-IOT device ID is valid, or indicates that there are no subsequent commands for the UE after the A-IOT device inventory, and the UE may: send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an A-IOT device inventory for another UE.

[0154] According to some embodiments of this disclosure, the first indication indicates that the A-IOT device ID is valid, or the UE can receive a second indication indicating that there are no subsequent commands for the UE after the A-IOT device inventory, and the UE can: send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an A-IOT device inventory for another UE.

[0155] According to some embodiments of this disclosure, the first indication indicates that the A-IoT device ID is valid or that at least one subsequent command message for the UE exists after the A-IoT device inventory, and the UE may: send to the UE an acknowledgment that the A-IoT device ID has been successfully identified and an indication that at least one subsequent command message for the UE exists after the A-IoT device inventory.

[0156] According to some embodiments of this disclosure, the first indication indicates that the A-IoT device ID is valid, or the UE can receive a second indication, the second indication indicating that there is at least one subsequent command message for the UE after the A-IoT device inventory, and the UE can: send to the UE an acknowledgment that the A-IoT device ID has been successfully identified and an indication that there is at least one subsequent command message for the UE after the A-IoT device inventory.

[0157] In some embodiments, the NE may: receive a third indication from the CN entity, the third indication indicating termination of communication with the UE together with or after a final command message for the UE.

[0158] According to some embodiments of this disclosure, the first indication is a NACK message indicating that the A-IoT device ID is invalid, and the UE may: send an indication to the UE to retransmit the A-IoT device ID.

[0159] Figure 6 A flowchart illustrating exemplary methods according to various aspects of this disclosure is shown. Figure 6 The operation of the method shown can be performed by the CN entity described herein (e.g., Figure 1 The CN entity (CN 106) or other devices with similar functions may execute this. In some implementations, the CN entity may execute a set of instructions to control the functional elements of the CN entity to perform the described operations or functions.

[0160] like Figure 6 As shown in the diagram, in step 602, the CN entity can receive the UE's A-IOT device ID from the NE for verification.

[0161] In step 604, the CN entity may verify whether the A-IoT device ID is valid. In some cases, the CN may determine whether there is at least one subsequent command for the UE after the A-IoT device inventory for the UE, in response to the validity of the A-IoT device ID.

[0162] In step 606, the CN entity may send a first indication to the NE, the first indication indicating that the A-IOT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after the A-IOT device inventory for the UE, or indicating that the A-IOT device ID is invalid.

[0163] According to some embodiments of this disclosure, in response to the A-IoT device ID being valid and no subsequent command messages for the UE following the A-IoT device inventory for the UE, the first indication indicates that the A-IoT device ID is valid, or indicates that no subsequent command messages for the UE following the A-IoT device inventory for the UE; or the first indication indicates that the A-IoT device ID is valid, and the CN entity can send a second indication, the second indication indicating that no subsequent commands for the UE following the A-IoT device inventory.

[0164] According to some embodiments of this disclosure, in response to an A-IoT device ID being valid and at least one subsequent command for the UE existing after an A-IoT device inventory for the UE, the first indication indicates that the A-IoT device ID is valid or that at least one subsequent command message for the UE exists after an A-IoT device inventory for the UE; or the first indication indicates that the A-IoT device ID is valid, and the CN entity can send a second indication, the second indication indicating that at least one subsequent command message for the UE exists after an A-IoT device inventory.

[0165] In some embodiments, the CN entity may send a third indication to the NE, the third indication indicating termination of communication with the UE together with or after the last command message to the UE.

[0166] According to some embodiments of this disclosure, in response to verifying that the A-IoT device ID is invalid, the first indication is a NACK message indicating that the A-IoT device ID is invalid.

[0167] Figure 7 A flowchart illustrating exemplary methods according to various aspects of this disclosure is shown. Figure 7 The operation of the method shown can be performed by the UE described herein (e.g., Figure 1 This can be performed by the UE (104) or other devices with similar functions. In some implementations, the UE can execute a set of instructions to control the functional elements of the UE to perform the described operations or functions.

[0168] like Figure 7 As shown, in step 702, the UE may send its A-IoT device ID to the network entity (NE) during a random access procedure associated with an A-IoT device inventory for the UE.

[0169] In step 704, in response to sending the A-IOT device ID, the UE may receive from the NE one of the following: an acknowledgment that the A-IOT device ID has been successfully identified and an indication that communication for the A-IOT device inventory has been completed; an acknowledgment that the A-IOT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an inventory for another UE; an acknowledgment that the A-IOT device ID has been successfully identified and an indication that at least one subsequent command message exists after the inventory; or an indication for retransmission of the A-IOT device ID.

[0170] According to some embodiments of this disclosure, in response to receiving an instruction to retransmit the A-IoT device ID, the UE may retransmit the A-IoT device ID to the NE.

[0171] Figure 8Examples of an NE 800 according to various aspects of this disclosure are shown. The NE 800 may include at least one processor 802 and at least one memory 804. Additionally, the NE 800 may also include one or more of at least one controller 806 or at least one transceiver 808. The processor 802, memory 804, controller 806, or transceiver 808, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, or electrically).

[0172] Processor 802, memory 804, controller 806, or transceiver 808, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure.

[0173] Processor 802 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 802 may be configured to operate memory 804. In some other embodiments, memory 804 may be integrated into processor 802. Processor 802 may be configured to execute computer-readable instructions stored in memory 804 to cause NE 800 to perform various functions of this disclosure.

[0174] Memory 804 may comprise volatile or non-volatile memory. Memory 804 may store computer-readable, computer-executable code containing instructions that, when executed by processor 802, cause NE 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium (e.g., memory 804 or another type of memory). Computer-readable media includes both non-transitory computer storage media and communication media containing any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0175] In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to cause NE 800 to perform one or more of the functions described herein (e.g., instructions stored in memory 804 are executed by processor 802). For example, processor 802 may support wireless communication at NE 800 according to the examples disclosed herein. NE 800 may be configured to support components for performing the methods described in the embodiments of this disclosure. In an embodiment, processor 802 may be configured to cause NE 800 to: send an A-IOT device ID to a CN entity for verification, wherein the A-IOT device ID is received from the UE during a random access procedure associated with an A-IOT device inventory for the UE; and receive a first indication from the CN entity, the first indication indicating that the A-IOT device ID is valid, or indicating whether at least one subsequent command message for the UE exists after the A-IOT device inventory, or indicating that the A-IOT device ID is invalid.

[0176] Controller 806 manages the input and output signals of NE 800. Controller 806 can also manage peripheral devices not integrated into NE 800. In some embodiments, controller 806 may utilize an operating system such as iOS®, Android®, Windows®, or other operating systems. In some embodiments, controller 806 may be implemented as part of processor 802.

[0177] In some embodiments, NE 800 may include at least one transceiver 808. In other embodiments, NE 800 may have more than one transceiver 808. Transceiver 808 may represent a wireless transceiver. Transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

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

[0179] Transmitter chain 812 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. 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 amplitude modulation (QAM). Transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 812 may also include one or more antennas for transmitting the amplified signal over the air or into a wireless medium.

[0180] Figure 9 An example of a CN entity 900 according to various aspects of this disclosure is shown. The CN entity 900 may include at least one processor 902 and at least one memory 904. Additionally, the CN entity 900 may also include one or more of at least one controller 906 or at least one transceiver 908. The processor 902, memory 904, controller 906, or transceiver 908, or various combinations thereof, or various components thereof, may be examples of building blocks for performing the various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, or electrically).

[0181] Processor 902, memory 904, controller 906, or transceiver 908, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure.

[0182] Processor 902 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 902 may be configured to operate memory 904. In some other embodiments, memory 904 may be integrated into processor 902. Processor 902 may be configured to execute computer-readable instructions stored in memory 904 to cause CN entity 900 to perform various functions of this disclosure.

[0183] Memory 904 may comprise volatile or non-volatile memory. Memory 904 may store computer-readable, computer-executable code containing instructions that, when executed by processor 902, cause CN entity 900 to perform the various functions described herein. The code may be stored in non-transitory computer-readable media (e.g., memory 904 or another type of memory). Computer-readable media includes both non-transitory computer storage media and communication media containing any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0184] In some implementations, processor 902 and memory 904 coupled to processor 902 may be configured to cause CN entity 900 to perform one or more of the functions described herein (e.g., instructions stored in memory 904 are executed by processor 902). For example, processor 902 may support wireless communication at CN entity 900 according to the examples disclosed herein. CN entity 900 may be configured to support components for performing the methods described in embodiments of this disclosure. In an embodiment, processor 902 may be configured to cause CN entity 900 to: receive the A-IoT device ID of the UE from NE for verification; verify whether the A-IoT device ID is valid; and send a first indication to NE, the first indication indicating that the A-IoT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after an A-IoT device inventory for the UE, or indicating that the A-IoT device ID is invalid.

[0185] Controller 906 manages the input and output signals of CN entity 900. Controller 906 can also manage peripheral devices not integrated into CN entity 900. In some embodiments, controller 906 may utilize an operating system such as iOS®, Android®, Windows®, or other operating systems. In some embodiments, controller 906 may be implemented as part of processor 902.

[0186] In some embodiments, CN entity 900 may include at least one transceiver 908. In other embodiments, CN entity 900 may have more than one transceiver 908. Transceiver 908 may represent a wireless transceiver. Transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

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

[0188] Transmitter chain 912 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. 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 amplitude modulation (QAM). Transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 912 may also include one or more antennas for transmitting the amplified signal over the air or into a wireless medium.

[0189] Figure 10 An example of a UE 1000 according to various aspects of this disclosure is shown. The UE 1000 may include at least one processor 1002 and at least one memory 1004. Additionally, the UE 1000 may also include one or more of at least one controller 1006 or at least one transceiver 1008. The processor 1002, memory 1004, controller 1006, or transceiver 1008, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, or electrically).

[0190] Processor 1002, memory 1004, controller 1006, or transceiver 1008, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure.

[0191] Processor 1002 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 1002 may be configured to operate memory 1004. In some other embodiments, memory 1004 may be integrated into processor 1002. Processor 1002 may be configured to execute computer-readable instructions stored in memory 1004 to cause UE 1000 to perform various functions of this disclosure.

[0192] Memory 1004 may include volatile or non-volatile memory. Memory 1004 may store computer-readable, computer-executable code containing instructions that, when executed by processor 1002, cause UE 1000 to perform the various functions described herein. The code may be stored in non-transitory computer-readable media (e.g., memory 1004 or another type of memory). Computer-readable media includes both non-transitory computer storage media and communication media containing any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0193] In some embodiments, processor 1002 and memory 1004 coupled to processor 1002 may be configured to cause UE 1000 to perform one or more of the functions described herein (e.g., instructions stored in memory 1004 are executed by processor 1002). For example, processor 1002 may support wireless communication at UE 1000 according to the examples disclosed herein. UE 1000 may be configured to support components for performing the methods described in the embodiments of this disclosure. In another embodiment, the processor 1002 may be configured to cause the UE 1000 to: send the UE's A-IoT device ID to the NE during a random access procedure associated with an A-IoT device inventory for the UE; and in response to sending the A-IoT device ID, receive from the NE one of the following: an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating the completion of communication for the A-IoT device inventory; an acknowledgment that the A-IoT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an inventory for another UE; an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating that at least one subsequent command message exists after the inventory; or an indication indicating the retransmission of the A-IoT device ID.

[0194] Controller 1006 manages the input and output signals of UE 1000. Controller 1006 can also manage peripheral devices not integrated into UE 1000. In some embodiments, controller 1006 may utilize an operating system such as iOS®, Android®, Windows®, or other operating systems. In some embodiments, controller 1006 may be implemented as part of processor 1002.

[0195] In some embodiments, UE 1000 may include at least one transceiver 1008. In other embodiments, UE 1000 may have more than one transceiver 1008. Transceiver 1008 may represent a wireless transceiver. Transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

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

[0197] Transmitter chain 1012 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 1012 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. 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 amplitude modulation (QAM). Transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal over the air or into a wireless medium.

[0198] Figure 11An example of a processor 1100 according to various aspects of this disclosure is shown. Processor 1100 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 1100 may include a controller 1102 configured to perform various operations according to the examples described herein. Processor 1100 may optionally include at least one memory 1104, which may be, for example, a layer 1 (L1), layer 2 (L2), or layer 3 (L3) cache. Additionally or alternatively, processor 1100 may optionally include one or more arithmetic logic units (ALUs) 1106. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more interfaces (e.g., buses).

[0199] Processor 1100 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 1100) or contained within the processor chipset) 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), etc.).

[0200] Controller 1102 can be configured to manage and coordinate various operations of processor 1100 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 1100 to support various operations according to the examples described herein. For example, controller 1102 can act as a control unit of processor 1100, generating control signals that manage the operation of various components of processor 1100. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0201] Controller 1102 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 1104 and determine one or more subsequent instructions to be executed to enable processor 1100 to support various operations according to the examples described herein. Controller 1102 may be configured to track the memory addresses of instructions associated with memory 1104. Controller 1102 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 1102 may be configured to interpret instructions and determine control signals to be output to other components of processor 1100 to enable processor 1100 to support various operations according to the examples described herein. Alternatively or additionally, controller 1102 may be configured to manage data flow within processor 1100. Controller 1102 may be configured to control data transfers between registers, ALU, and other functional units of processor 1100.

[0202] Memory 1104 may include one or more caches (e.g., memory local to processor 1100 or included in said processor, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some embodiments, memory 1104 may reside within or on the processor chipset (e.g., locally to processor 1100). In some other embodiments, memory 1104 may reside external to the processor chipset (e.g., remote from processor 1100).

[0203] Memory 1104 may store computer-readable, computer-executable code containing instructions that, when executed by processor 1100, cause processor 1100 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium (e.g., system memory or another type of memory). Controller 1102 and / or processor 1100 may be configured to execute the computer-readable instructions stored in memory 1104 to cause processor 1100 to perform various functions. For example, processor 1100 and / or controller 1102 may be coupled to or coupled to memory 1104, processor 1100, and controller 1102, and memory 1104 may be configured to perform the various functions described herein. In some examples, processor 1100 may include multiple processors, and memory 1104 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or collectively configured to perform the various functions described herein.

[0204] One or more ALUs 1106 may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALUs 1106 may reside within or on a processor chipset (e.g., processor 1100). In some other embodiments, one or more ALUs 1106 may reside outside the processor chipset (e.g., processor 1100). One or more ALUs 1106 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 1106 may receive input operands and operation codes that determine the operation to be performed. One or more ALUs 1106 are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 1106s may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 1106s to handle conditional operations, comparisons, and bitwise operations.

[0205] Processor 1100 may support wireless communication according to the examples disclosed herein. Processor 1100 may be configured or operable to support components for performing the methods described in the embodiments of this disclosure.

[0206] In an embodiment, controller 1102 may enable processor 1100 to: send an A-IoT device ID to a CN entity for verification, wherein the A-IoT device ID is received from the UE during a random access procedure associated with an A-IoT device inventory for the UE; and receive a first indication from the CN entity, the first indication indicating that the A-IoT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after the A-IoT device inventory, or indicating that the A-IoT device ID is invalid.

[0207] In another embodiment, controller 1102 may enable processor 1100 to: receive the A-IoT device ID of the UE from the NE for verification; verify whether the A-IoT device ID is valid; and send a first indication to the NE, the first indication indicating that the A-IoT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after an A-IoT device inventory for the UE, or indicating that the A-IoT device ID is invalid.

[0208] In another embodiment, controller 1102 may enable processor 1100 to: send the UE's A-IoT device ID to NE during a random access procedure associated with an A-IoT device inventory for a UE; and in response to sending the A-IoT device ID, receive from NE one of the following: an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating the completion of communication for the A-IoT device inventory; an acknowledgment that the A-IoT device ID has been successfully identified and a DL signal for triggering another random access procedure associated with an inventory for another UE; an acknowledgment that the A-IoT device ID has been successfully identified and an indication indicating that at least one subsequent command message exists after the inventory; or an indication indicating the retransmission of the A-IoT device ID.

[0209] Those skilled in the art will readily recognize the various modifications to this disclosure and will be able to apply the general principles defined herein to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but is endowed with the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A network device NE for wireless communication, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to cause the NE: Sending the Environmental Internet of Things (A-IoT) Device Identifier ID to the core network (CN) entity for verification, wherein the A-IoT Device ID is received from the UE during a random access procedure associated with an A-IoT device inventory for the user equipment (UE); and The CN entity receives a first indication, which indicates that the A-IOT device ID is valid, or indicates whether there is at least one subsequent command message for the UE after the A-IOT device inventory, or indicates that the A-IOT device ID is invalid.

2. The NE of claim 1, wherein the first indication indicates that the A-IoT device ID is valid, or indicates that there are no subsequent commands for the UE after the A-IoT device inventory, and the at least one processor is configured to cause the NE to: Send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and an indication that the communication for the A-IOT device inventory of the UE is complete.

3. The NE of claim 1, wherein the first indication indicates that the A-IoT device ID is valid, and the at least one processor is configured to cause the NE to receive a second indication, the second indication indicating that no subsequent commands for the UE exist after the A-IoT device inventory, and the at least one processor is configured to cause the NE to: Send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and an indication that the communication for the A-IOT device inventory of the UE is complete.

4. The NE of claim 1, wherein the first indication indicates that the A-IoT device ID is valid, or indicates that there are no subsequent commands for the UE after the A-IoT device inventory, and the at least one processor is configured to cause the NE to: Send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and a downlink DL signal for triggering another random access procedure associated with an A-IOT device inventory for another UE.

5. The NE of claim 1, wherein the first indication indicates that the A-IoT device ID is valid, and the at least one processor is configured to cause the NE to receive a second indication, the second indication indicating that there are no subsequent commands for the UE after the A-IoT device inventory, and the at least one processor is configured to cause the NE to: Send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and a downlink DL signal for triggering another random access procedure associated with an A-IOT device inventory for another UE.

6. The NE of claim 1, wherein the first indication indicates that the A-IoT device ID is valid or that at least one subsequent command message for the UE exists after the A-IoT device inventory, and the at least one processor is configured to cause the NE to: Send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and an indication that at least one subsequent command message for the UE exists after the A-IOT device inventory.

7. The NE of claim 1, wherein the first indication indicates that the A-IoT device ID is valid, and the at least one processor is configured to cause the NE to receive a second indication, the second indication indicating that at least one subsequent command message for the UE exists after the A-IoT device inventory, and the at least one processor is configured to cause the NE to: Send to the UE an acknowledgment that the A-IOT device ID has been successfully identified and an indication that at least one subsequent command message for the UE exists after the A-IOT device inventory.

8. The NE according to claim 6 or 7, wherein the at least one processor is configured to cause the NE to: A third indication is received from the CN entity, the third indication indicating that communication with the UE is terminated together with the last command message for the UE or after the last command message for the UE.

9. The NE according to claim 1, wherein the first indication is a negative acknowledgment (NACK) message indicating that the A-IOT device ID is invalid, and the at least one processor is configured to cause the NE to: send an indication to the UE indicating a retransmission of the A-IOT device ID.

10. A core network (CN) entity, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to cause the CN entity to: Receive the Environmental IoT Device Identifier (A-IoT) ID from the Network Equipment (NE) for verification purposes; Verify whether the A-IoT device ID is valid; and Send a first indication to the NE, the first indication indicating that the A-IOT device ID is valid, or indicating whether there is at least one subsequent command message for the UE after the A-IOT device inventory for the UE, or indicating that the A-IOT device ID is invalid.

11. The CN entity of claim 10, wherein in response to the validity of the A-IoT device ID and after the A-IoT device inventory for the UE, there are no subsequent command messages for the UE. The first indication indicates that the A-IoT device ID is valid, or indicates that there are no subsequent command messages for the UE after the A-IoT device inventory for the UE; or The first indication indicates that the A-IOT device ID is valid, and the at least one processor is configured to cause the CN entity to send a second indication, the second indication indicating that there are no subsequent commands for the UE after the A-IOT device inventory.

12. The CN entity of claim 10, wherein in response to the validity of the A-IoT device ID, and after an inventory of the A-IoT device for the UE, there is at least one subsequent command for the UE. The first indication indicates that the A-IoT device ID is valid or that at least one subsequent command message for the UE exists after an inventory of the A-IoT devices for the UE; or The first indication indicates that the A-IOT device ID is valid, and the at least one processor is configured to cause the CN entity to send a second indication, the second indication indicating that there is at least one subsequent command message for the UE after the A-IOT device inventory.

13. The CN entity of claim 12, wherein the at least one processor is configured to cause the CN entity to: A third instruction is sent to the NE, the third instruction indicating that communication with the UE is terminated together with the last command message for the UE or after the last command message for the UE.

14. The CN entity of claim 10, wherein in response to verifying that the A-IOT device ID is invalid, the first indication is a negative acknowledgment (NACK) message indicating that the A-IOT device ID is invalid.

15. The CN entity of claim 10, wherein the at least one processor is configured to cause the CN entity to: In response to the validity of the A-IOT device ID, determine whether there is at least one subsequent command for the UE after the A-IOT device inventory for the UE.

16. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to cause NE: During the random access procedure associated with the A-IoT device inventory for the UE, the UE's environmental IoT A-IoT device identifier ID is sent to the network entity NE; and In response to sending the A-IoT device ID, one of the following is received from the NE: The confirmation that the A-IoT device ID has been successfully identified and the indication that the communication for the inventory of the A-IoT device has been completed; The confirmation that the A-IOT device ID has been successfully identified and the downlink DL signal used to trigger another random access procedure associated with an inventory of another UE. The successful identification of the A-IOT device ID confirms and indicates that at least one subsequent command message exists after the inventory count; or Instructions for retransmission of the A-IOT device ID.

17. The A-IoT device of claim 16, wherein in response to receiving the instruction indicating a retransmission of the A-IoT device ID, the at least one processor is configured to cause the UE to: retransmit the A-IoT device ID to the NE.

18. A processor for wireless communication, comprising: At least one controller, coupled to the at least one memory and configured to cause the processor to: Sending the Environmental Internet of Things (A-IoT) Device Identifier ID to the core network (CN) entity for verification, wherein the A-IoT Device ID is received from the UE during a random access procedure associated with an A-IoT device inventory for the user equipment (UE); and The CN entity receives a first indication, which indicates that the A-IOT device ID is valid, or indicates whether there is at least one subsequent command message for the UE after the A-IOT device inventory, or indicates that the A-IOT device ID is invalid.

Images