Status management for environmental IoT communication

By managing the short-term and long-term states of environmental IoT devices at the reader and environmental IoT controller devices, the problem of resource waste in wireless communication systems is solved, and efficient network resource management and device power saving are achieved.

CN123077141APending Publication Date: 2026-11-10QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090487.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-04-05
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing wireless communication systems suffer from high network resource consumption, increased power consumption, and resource waste when managing the status of environmental IoT devices. In particular, because environmental IoT devices cannot support state management and state switching, readers and controllers frequently attempt invalid requests.

Method used

By maintaining and managing the short-term and long-term states of environmental IoT devices at the reader device and environmental IoT controller device, state signaling and maintenance are achieved, invalid requests and commands are reduced, and communication efficiency is improved.

Benefits of technology

Effectively manage network resources, reduce network, power and computing resource consumption, improve communication performance between reader devices and environmental IoT devices, and save device power consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123077141A_ABST
    Figure CN123077141A_ABST
Patent Text Reader

Abstract

Various aspects of this disclosure relate generally to wireless communication. In some aspects, the reader device can receive communications indicating the short-term environmental IoT state of an environmental Internet of Things (IoT) device. The reader device can store state information identifying the short-term environmental IoT state of the environmental IoT device. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more specifically to techniques, apparatus and methods for state management of environmental Internet of Things (IoT) communications. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0004] Some aspects described herein relate to an apparatus configured for wireless communication. The apparatus may include one or more memories and one or more processors, the memories including processor-executable instructions. The one or more processors may be configured to execute the processor-executable instructions and cause the apparatus to receive communications indicating a short-term environmental IoT state of an environmental Internet of Things (IoT) device. The one or more processors may be configured to execute the processor-executable instructions and cause the apparatus to store state information identifying the short-term environmental IoT state of the environmental IoT device.

[0005] Some aspects described herein relate to an apparatus configured for wireless communication. The apparatus may include one or more memories and one or more processors, the memories including processor-executable instructions. The one or more processors may be configured to execute the processor-executable instructions and cause the apparatus to convey a first communication indicating a short-term environmental IoT state of an environmental IoT device. The one or more processors may be configured to execute the processor-executable instructions and cause the apparatus to convey a second communication indicating a long-term environmental IoT state of the environmental IoT device.

[0006] Some aspects described herein relate to an apparatus configured for wireless communication. The apparatus may include one or more memories and one or more processors, the memories including processor-executable instructions. The one or more processors may be configured to execute the processor-executable instructions and cause the apparatus to receive communications indicating a long-term environmental IoT state of an environmental IoT device. The one or more processors may be configured to execute the processor-executable instructions and cause the apparatus to store state information of the environmental IoT device identifying the long-term environmental IoT state.

[0007] Some aspects described herein relate to a method for wireless communication performed by a reader device. The method may include receiving communications indicating a short-term environmental IoT state of an environmental IoT device. The method may also include storing state information identifying the short-term environmental IoT state of the environmental IoT device.

[0008] Some aspects described herein relate to a method for wireless communication performed by an environmental IoT device. The method may include a first communication conveying an indication of a short-term environmental IoT state of the environmental IoT device. The method may also include a second communication conveying an indication of a long-term environmental IoT state of the environmental IoT device.

[0009] Some aspects described herein relate to a method for wireless communication performed by an environmental IoT controller device. The method may include receiving communications indicating a long-term environmental IoT state of the environmental IoT device. The method may also include storing state information identifying the long-term environmental IoT state of the environmental IoT device.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a reader device. When executed by one or more processors of the reader device, the set of instructions enables the reader device to receive communications indicating a short-term environmental IoT state of an environmental IoT device. When executed by one or more processors of the reader device, the set of instructions also enables the reader device to store state information identifying the short-term environmental IoT state of the environmental IoT device.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by an environmental IoT device. When executed by one or more processors of the environmental IoT device, the set of instructions enables the environmental IoT device to convey first communications indicating a short-term environmental IoT state. When executed by one or more processors of the environmental IoT device, the set of instructions also enables the environmental IoT device to convey second communications indicating a long-term environmental IoT state.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by an environmental IoT controller device. When executed by one or more processors of the environmental IoT controller device, the set of instructions enables the environmental IoT controller device to receive communications indicating a long-term environmental IoT state. When executed by one or more processors of the environmental IoT controller device, the set of instructions also enables the environmental IoT controller device to store state information identifying the long-term environmental IoT state.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving communications indicating a short-term environmental IoT state of an environmental IoT device. The apparatus may also include components for storing state information identifying the short-term environmental IoT state of the environmental IoT device.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for conveying a first communication indicating a short-term environmental IoT state of an environmental IoT device. The apparatus may also include components for conveying a second communication indicating a long-term environmental IoT state of the environmental IoT device.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving communications indicating a long-term environmental IoT state of an environmental IoT device. The apparatus may also include components for storing state information identifying the long-term environmental IoT state of the environmental IoT device.

[0016] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0017] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0018] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0019] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0020] Figure 2 This is a diagram illustrating communication between an example network node and an example user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0022] Figure 4 This is a diagram illustrating an example of backscatter communication according to this disclosure.

[0023] Figure 5 This is a diagram illustrating an example of a topology for an environmental Internet of Things (IoT) device according to this disclosure.

[0024] Figure 6 This is a diagram illustrating an example of an A-IoT architecture associated with this disclosure.

[0025] Figure 7 This is a diagram illustrating an example of state management for A-IoT communication in accordance with this disclosure.

[0026] Figure 8 This is a flowchart of an example method for wireless communication.

[0027] Figure 9 This is a flowchart of an example method for wireless communication.

[0028] Figure 10 This is a flowchart of an example method for wireless communication.

[0029] Figure 11 This is a diagram of an example device for wireless communication according to the present disclosure.

[0030] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure.

[0031] Figure 13 This is a diagram of an example device for wireless communication according to the present disclosure.

[0032] Figure 14 The diagram illustrates an example of a specific implementation of the code and circuitry for a communication device according to this disclosure.

[0033] Figure 15 The diagram illustrates an example of a specific implementation of the code and circuitry for a communication device according to this disclosure.

[0034] Figure 16 The diagram illustrates an example of a specific implementation of the code and circuitry for a communication device according to this disclosure. Detailed Implementation

[0035] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0036] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0037] Some wireless communication devices can be considered Internet of Things (IoT) devices, such as environmental IoT devices (sometimes referred to as ultralight IoT devices) or similar IoT devices. In environmental IoT, the endpoints (e.g., radio frequency identification (RFID) devices, tags, or similar devices) may not include batteries, and the endpoints can accumulate energy from radio signaling. To achieve further cost reduction and zero-power communication, wireless networks may utilize a type of environmental IoT device known as an "environmental backscattering device," "energy harvesting device," or simply a "backscattering device." For example, an environmental IoT device can communicate with a reader device (e.g., a user equipment (UE) or network node) by modulating reflected radio signals from a radio frequency (RF) source. One or more reader devices can provide information read from the environmental IoT device to an environmental IoT controller device, which may be a device (e.g., a core network device or network node) that implements application functions or core network functions of the wireless communication network (e.g., access and mobility management functions (AMF)).

[0038] Due to their low complexity, environmental IoT devices may not support states such as Radio Resource Control (RRC) states, Connection Management (CM) states, and / or Registration Management (RM) states (e.g., different operating conditions or modes). Therefore, wireless networks typically lack state management for environmental IoT devices, leading to higher network resource consumption due to inefficient management of network resources. Additionally, without the ability to switch between states, environmental IoT devices and / or associated readers may maintain unnecessary activity, resulting in increased power consumption. Furthermore, without the ability to enable environmental IoT devices to indicate their current state, readers and / or environmental IoT controller devices may repeatedly attempt to issue requests and / or commands to unavailable environmental IoT devices, excessively consuming network, power, and / or computing resources.

[0039] Various aspects collectively relate to state management for environmental IoT communications. Some aspects more specifically relate to signaling and maintenance of the state of environmental IoT devices and / or readers. In some aspects, environmental IoT devices may support and indicate one or more short-term environmental IoT states (e.g., transmitting information for local communication between the environmental IoT device and the reader device) and / or long-term environmental IoT states (e.g., transmitting information for end-to-end communication between the environmental IoT device and the environmental IoT controller device). In some aspects, reader devices may maintain and manage the short-term environmental IoT states of environmental IoT devices. In some aspects, environmental IoT controller devices may maintain and manage the long-term environmental IoT states of environmental IoT devices. In some aspects, reader devices and / or environmental IoT controller devices may issue requests to the environmental IoT devices to change the environmental IoT states.

[0040] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by implementing state management for environmental IoT communication, the described techniques can be used to efficiently manage network resources, thereby reducing network resource consumption. Furthermore, by maintaining and managing the short-term environmental IoT state of the environmental IoT device at the reader device, the described techniques can be used to improve the performance of communication between the reader device and the environmental IoT device, such as by reducing attempts by the reader device to issue requests and / or commands to currently unavailable environmental IoT devices. Similarly, by maintaining and managing the long-term state of the environmental IoT device at the environmental IoT controller device, the described techniques can be used to efficiently notify the reader device of environmental IoT devices with long-term unavailability, enabling the reader device to issue requests and / or commands to those unavailable environmental IoT devices without consuming network, power, and / or computing resources. Moreover, by enabling the reader device and / or the environmental IoT controller device to request the environmental IoT device to change its environmental IoT state (e.g., between a sleep state and a wake-up state), the described techniques can be used to save power for the environmental IoT device and / or the reader device (e.g., by enabling the reader device to reduce power consumption based on when the environmental IoT device is asleep).

[0041] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0042] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0043] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0044] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0045] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0047] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0048] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0049] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0050] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0051] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0052] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0053] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. "Downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0054] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UE 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0055] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0056] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0057] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0058] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0059] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems) or be coupled to such modems. In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0060] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0061] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may possess intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category may be referred to as reduced-capacity UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0062] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0063] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0064] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0065] In some examples, the environmental IoT device 135 may communicate with network node 110 and / or UE 120. In some examples, the environmental IoT device 135 may be configured to accumulate energy from radio signaling received from network node 110 and / or UE 120. In some examples, the environmental IoT device 135 may be configured to transmit data to network node 110 and / or UE 120 by backscattering radio signaling received from network node 110 and / or UE 120.

[0066] In some examples, the environmental IoT controller device 137 may communicate with network node 110. In some examples, the environmental IoT controller device 137 may implement application functions or core network functions of the wireless communication network 100. In some examples, the environmental IoT controller device 137 may be network node 110, or may be included in the network node.

[0067] In some aspects, the UE may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive communications indicating a short-term environmental IoT state of an environmental IoT device; and store status information identifying the short-term environmental IoT state of the environmental IoT device. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0068] In some aspects, the network node may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: receive communications indicating short-term environmental IoT states of environmental IoT devices; and store status information identifying the short-term environmental IoT states of environmental IoT devices. As described in more detail elsewhere herein, the communication manager 150 may: receive communications indicating long-term environmental IoT states of environmental IoT devices; and store status information identifying the long-term environmental IoT states of environmental IoT devices. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0069] In some aspects, the ambient IoT device 135 may include a communication manager 160. As described in more detail elsewhere herein, the communication manager 160 may: convey a first communication indicating a short-term ambient IoT state of the ambient IoT device; and convey a second communication indicating a long-term ambient IoT state of the ambient IoT device. Additionally or alternatively, the communication manager 160 may perform one or more other operations described herein.

[0070] In some aspects, the environmental IoT controller device 137 may include a communication manager 170. As described in more detail elsewhere herein, the communication manager 170 may: receive communications indicating the long-term environmental IoT state of the environmental IoT device; and store status information identifying the long-term environmental IoT state of the environmental IoT device. Additionally or alternatively, the communication manager 170 may perform one or more other operations described herein.

[0071] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0072] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0073] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0074] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0075] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0076] For downlink communication from network node 110 to UE 120, transmit processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmit processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmit processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0077] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T A set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0078] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0079] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0080] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0081] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0082] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0083] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0084] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0085] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0086] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0087] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0088] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0089] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals transmitted individually by antenna elements at desired wavelengths to interact or interfere with each other constructively and destructively in various directions (such as to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference patterns of signals transmitted by individual antenna elements within that desired range.

[0090] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0091] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0092] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0093] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0094] Each component in the components of the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0095] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0096] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0097] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0098] In some respects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and may be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns of performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0099] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0100] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with state management for environmental IoT communications or perform one or more operations associated with state management for environmental IoT communications, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with state management for environmental IoT communications or perform one or more operations associated with state management for environmental IoT communications, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 8 The process 800 Figure 9 The process 900 Figure 10 The operation of process 1000 or other processes as described herein. In some aspects, the reader device described herein is UE 120, included in UE 120, or comprising Figure 2 One or more components of the UE 120 shown. In some aspects, the reader device described herein is network node 110, included in network node 110, or comprising... Figure 2 One or more components of the network node 110 shown. In some aspects, the IoT device in the environment described herein is UE 120, included in UE 120, or comprising... Figure 2One or more components of the UE 120 shown herein. In some aspects, the environment IoT controller device described herein is network node 110, included in network node 110, or comprising... Figure 2 One or more components of the network node 110 shown.

[0101] Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 8 The process 800 Figure 9 The process 900 Figure 10 The process 1000 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0102] In some aspects, the reader device (e.g., UE 120 or network node 110) includes: components for receiving communications indicating a short-term environmental IoT state of an environmental IoT device; and / or components for storing state information identifying the short-term environmental IoT state of the environmental IoT device. In some aspects, components enabling the reader device to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246. In some aspects, components enabling the reader device to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0103] In some aspects, an environmental IoT device (e.g., environmental IoT device 135) includes: components for conveying first communications indicating a short-term environmental IoT state of the environmental IoT device; and / or components for conveying second communications indicating a long-term environmental IoT state of the environmental IoT device. In some aspects, components for the environmental IoT device to perform the operations described herein may include, for example, one or more of a communication manager 140, a communication manager 160, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0104] In some aspects, an environmental IoT controller device (e.g., environmental IoT controller device 137) includes: components for receiving communications indicating the long-term environmental IoT state of the environmental IoT device; and / or components for storing state information identifying the long-term environmental IoT state of the environmental IoT device. In some aspects, components for the environmental IoT controller device to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a communication manager 170, a transmit processor 214, a TX MIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0105] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0106] Figure 4 This is a diagram illustrating example 400 associated with backscatter communication according to this disclosure.

[0107] Some wireless communication devices can be considered IoT devices, such as environmental IoT devices (sometimes referred to as ultralight IoT devices) or similar IoT devices. IoT technologies can include passive IoT (e.g., NR passive IoT for 5G advanced), semi-passive IoT, ultralight IoT, or environmental IoT, etc. In passive IoT, the terminal (e.g., a radio frequency identification (RFID) device, tag, or similar device) may not include a battery, and the terminal can accumulate energy from radio signaling. Additionally, the terminal can accumulate solar energy to supplement the accumulated energy from radio signaling. In passive IoT, the communication distance can be up to 30 meters (or longer) to facilitate feasible network coverage over large areas (e.g., 5000 square meters) such as in a warehouse. Furthermore, the power consumption of a passive IoT terminal (e.g., a UE) can be less than 0.1 milliwatts (mW) to support battery-free operation, and the terminal can be relatively inexpensive to facilitate cost-sensitive use. The positioning accuracy of a passive IoT terminal can be approximately 3 to 5 meters in both the horizontal and vertical directions.

[0108] Passive IoT combined with industrial sensors can be useful, for which battery replacement can be very difficult or undesirable (e.g., for security monitoring or fault detection in smart factories, infrastructure, or environments). Additionally, the characteristics of passive IoT devices, such as low cost, small size, maintenance-free operation, durability, and long lifespan, can facilitate smart logistics / warehousing (e.g., combined with automated asset management via RFID tag replacement). Furthermore, passive IoT can be combined with smart home networks for home appliance management, wearable devices (e.g., wearables for medical monitoring of patients that do not require battery replacement), and / or environmental monitoring. To achieve further cost reductions and zero-power communication, 5G+ / 6G wireless networks can utilize a type of passive IoT device known as an "ambient backscatter device" or "backscatter device."

[0109] like Figure 4As shown, the backscattering device 405 (e.g., a tag, sensor, environmental IoT device 135, etc.) (which can be an example of a passive IoT device) may employ a simplified hardware design (e.g., including a power divider, energy harvester, and microcontroller) that does not include a battery, allowing the backscattering device 405 to rely on energy harvesting for power, and does not include radio wave generation circuitry, enabling the backscattering device 405 to transmit information solely by reflecting radio waves. More specifically, the backscattering device 405 communicates with the reader 408 (e.g., UE 120, network node 110, or another network device) by modulating reflected radio signals from an RF source 410 (e.g., network node 110, UE 120, or another network device). In some examples, the RF source 410 and the reader 408 may be the same device and / or may be co-located. For example, in some cases, the reader 408 and the RF source 410 may be associated with the same network node 110.

[0110] To facilitate communication between the backscattering device 405 and the backscattering device 405, the RF source 410 may transmit an energy harvesting wave to the backscattering device 405. The energy harvesting wave may be transmitted for a sufficient duration to achieve a communication phase within the target range between the reader 408 and the backscattering device 405. Additionally or alternatively, in some cases, the range between the RF source 410 and the backscattering device 405 may be limited by a minimum received power, such as -20 dBm, to trigger energy harvesting at the backscattering device 405.

[0111] Once sufficient energy has accumulated at backscattering device 405, backscattering device 405 can begin reflecting radio waves radiated to it via backscattering link 415. For example, RF source 410 can initiate a communication session with a query (sometimes referred to as query-response communication), which can be a modulated envelope of a continuous wave (CW). Backscattering device 405 can respond by backscattering the CW. The communication session can include multiple rounds, such as for contention resolution purposes when multiple backscattering devices respond to a query. The channel between RF source 410 and backscattering device 405 on backscattering link 415 can be correlated with a first backscattering link channel response value (sometimes referred to as a first backscattering link channel coefficient or first backscattering link gain value), h BDAssociated with, as described below, the backscattering device 405 may have a reflection on-time and reflection off-time that follow at least in part based on the pattern of information bit transmission by the backscattering device 405. The reader 408 may detect the reflection pattern of the backscattering device 405 and obtain backscattering communication information via the backscattering link 415. The channel between the reader 408 and the backscattering device 405 of the backscattering link 415 may be associated with a second backscattering link channel response value (sometimes referred to as the second backscattering link channel coefficient or the second backscattering link channel gain value). DU Associated with each other. Furthermore, RF source 410 and reader 408 can communicate (e.g., reference signals and / or data signals) via direct link 420. The channel between RF source 410 and reader 408 of direct link 420 can be correlated with the direct link channel response value (sometimes referred to as the direct link channel coefficient or direct link channel gain value) h. BU Related.

[0112] The backscattering device 405 can use information modulation schemes such as amplitude shift keying (ASK) modulation or on / off keying (OOK) modulation. For ASK or OOK modulation, the backscattering device 405 can turn on reflection when transmitting an information bit "1" and turn off reflection when transmitting an information bit "0". In backscatter communication, the RF source 410 can transmit a specific radio wave (e.g., a reference signal or data signal, such as PDSCH), which can be represented as x(n). The reader 408 can receive the radio wave x(n) directly from the RF source 410 via a direct link 420, and receive the radio wave from the backscattering device 405, which modulates the radio wave and reflects it to the reader 408, via a backscattering link 415. The signal received at the reader 408 via the direct link 420 (indicated by reference numeral 425) is the radio wave x(n) transmitted by the RF source 410 multiplied by the direct link channel response value h. BU The product of the signals and any signal noise is added. The information bit signal of the backscattering device 405 can be represented as s(n), where s(n)∈{0,1}. Therefore, the signal received at the reader 408 via the backscattering link 415 (indicated by reference numeral 430) is the signal x(n) transmitted by the RF source 410 multiplied by the first backscattering link channel response value h. BD Second backscatter link channel response value h DU The product of the information bit signal s(n) from the backscattering device 405 and the reflection coefficient associated with the backscattering device 405, plus any noise.

[0113] Therefore, the signal received at reader 408 is a superposition of the signal received via direct link 420 and the signal received via backscatter link 415, and can be represented as y(n). This signal y(n) is indicated by reference numeral 435. As shown, when s(n) = 0 (indicated by reference numeral 440 in the drawing shown at reference numeral 430), backscattering device 405 can turn off reflection, and therefore reader 408 receives only the direct link 420 signal. When s(n) = 1 (indicated by reference numeral 445 in the drawing shown at reference numeral 430), backscattering device 405 can turn on reflection, and therefore reader 408 receives the superposition of both the direct link 420 signal and the backscatter link 415 signal. In order to receive the information bits transmitted by backscattering device 405, reader 408 can first treat the backscatter link 415 signal as interference, at least in part based on the direct link channel response value h. BU x(n) is decoded using (n). Then, the reader 408 can detect the presence of the signal component. In some cases, the backscatter device 405 may not maintain the state from communication session to communication session except for the contents stored in the memory of the backscatter device 405, such as the electronic product code (EPC) or similar information associated with the backscatter device 405.

[0114] Some IoT devices can be referred to as semi-passive IoT devices because communication between the reader and the IoT device does not require an energy harvesting waveform as a precondition. For example, a semi-passive IoT device may include a battery or similar energy source that can power the receiver and / or logic circuitry. For such devices, energy harvesting can still be triggered in some cases, such as for long-range communication. In such examples, the rectifier circuitry of the IoT device may have a hot start from a battery or other energy source and can therefore be associated with a lower minimum receive power requirement than that of a passive IoT device (e.g., -30 dBm instead of -20 dBm). However, long-range communication may require battery power consumption to incentivize each decoding. More specifically, for long-range communication where the energy harvesting rate is lower than required by the decoding circuitry, such as when the energy harvesting rate is below -30 dBm, a semi-passive IoT device may consume battery power to incentivize each decoding. Therefore, continuous IoT device monitoring (such as for receiving long-range query communications) can lead to excessive battery consumption at the IoT device.

[0115] In this respect, passive and semi-passive IoT devices can inherently limit their applications. For example, passive IoT devices (such as backscattering device 405) can be associated with low cost and form factor because no RF chain is required at the IoT device. However, these devices require an energy harvesting waveform, thus limiting the application of such passive IoT devices to short-range communication. While semi-passive IoT devices can eliminate the need for an energy harvesting waveform and / or enable long-range communication, such devices increase cost and complexity because they require the use of batteries or similar power sources. Furthermore, because passive and semi-passive devices can be associated with communication sessions initiated by RF sources, these devices may inherently limit their use in sensing scenarios or similar latency-critical applications requiring non-periodic operations, and these devices may not scale well for high IoT density applications.

[0116] In some examples, Ambient IoT (A-IoT) devices may include a class of low-complexity devices (e.g., tags, sensors, etc.) that can operate using only environmental signaling from the reader (e.g., an incident RF source). Ambient IoT devices may rely on backscattering the incident signal to transmit data to the reader.

[0117] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0118] Figure 5 These are illustrations of examples 500 and 510 illustrating topologies for environmental IoT devices according to this disclosure.

[0119] Example 500 relates to a first topology, which may be referred to as Topology 1. Topology 1 may relate to a network node-based reader (e.g., a gNB-based reader). In Topology 1, A-IoT device 135 may communicate directly and bidirectionally with one or more network nodes 110 (e.g., on A-IoT link Ua). For example, A-IoT device 135 and one or more network nodes 110 may exchange A-IoT data and / or signaling. In some examples, a first network node 110 may send communication to A-IoT device 135, and a second network node 110 may receive communication from A-IoT device 135.

[0120] Example 510 relates to a second topology, which may be referred to as Topology 2. Topology 2 may involve a UE-based reader. In Topology 2, A-IoT device 135 can communicate bidirectionally with an intermediate node between A-IoT device 135 and network node 110 (e.g., on A-IoT link Ua). The intermediate node can be any suitable device with A-IoT capabilities, such as a UE, repeater, IAB node, or transponder, etc. The intermediate node can transmit A-IoT data and / or signaling between network node 110 and A-IoT device 135 (e.g., on access link Uu). The intermediate node can be a reader, such as reader 408 or an A-IoT reader, etc.

[0121] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0122] Figure 6 This is a diagram illustrating example 600 associated with an A-IoT architecture according to this disclosure.

[0123] As shown in the figure, Example 600 includes an A-IoT device 135, a reader device 610, an A-IoT controller device 137, and an application function (AF) 620. The reader device 610 may correspond to one or more readers described herein (e.g., reader 408). The A-IoT controller device 137 may be implemented in a core network associated with a wireless communication network (e.g., wireless communication network 100). The AF 620 may be implemented in a computing device (e.g., a server) that can communicate with the core network via a communication network (e.g., the Internet). The A-IoT device 135 and the reader device 610 may have a communication link (e.g., using a Ua interface), the reader device 610 and the A-IoT controller device 137 may have a communication link (e.g., using an A-IoT reader controller (A-RC) interface), and the A-IoT controller device 137 and the AF 620 may have a communication link (e.g., using an A-IoT controller application (A-CA) interface).

[0124] Reader device 610 may support a Ua air interface to one or more A-IoT devices 135. In some examples, reader device 610 may register with A-IoT controller device 137 (e.g., using a registration process). Reader device 610 may receive requests from A-IoT controller device 137 requesting reader device 610 to perform specific functions regarding one or more A-IoT devices 135. For example, A-IoT controller device 137 may request reader device 610 to perform a one-time or periodic inventory of A-IoT devices 135, and reader device 610 may deliver the inventory results to A-IoT controller device 137. As another example, A-IoT controller device 137 may request reader device 610 to deliver commands from A-IoT controller device 137 to A-IoT devices 135. Furthermore, reader device 610 may deliver command responses received from A-IoT devices 135 to A-IoT controller device 137.

[0125] A-IoT controller device 137 may register (e.g., using a registration process) one or more reader devices 610. Additionally, A-IoT controller device 137 may authenticate and authorize AF 620. A-IoT controller device 137 may receive requests from AF 620 requesting that A-IoT controller device 137 perform specific functions regarding one or more A-IoT devices 135 and / or one or more reader devices 610. In some examples, AF 620 may issue an inventory request or command request to A-IoT controller device 137. In some examples, A-IoT controller device 137 may verify whether AF 620 is authorized to issue a specific inventory request or command request. A-IoT controller device 137 may select one or more reader devices 610 to satisfy AF 620's inventory request or command request. A-IoT controller device 137 may forward the inventory request to one or more reader devices 610, and A-IoT controller device 137 may deliver one or more inventory results to AF 620. Similarly, A-IoT controller device 137 may forward command requests to one or more reader devices 610, and A-IoT controller device 137 may deliver one or more command responses to AF 620.

[0126] In some examples, the A-IoT controller device 137 may collect usage data per AF 620 (e.g., for use in conjunction with charging purposes). Additionally, the A-IoT controller device 137 may store information indicating the last known reader device 610 used for a particular A-IoT device 135.

[0127] The AF 620 can perform the authentication operation to the A-IoT controller device 137. In addition, the AF 620 can transmit inventory requests and / or command requests to the A-IoT controller device 137, and the AF 620 can receive inventory responses and / or command responses from the A-IoT controller device 137.

[0128] The UE can support multiple states. For example, the UE can support multiple RRC states, such as connected (RRC_CONNECTED), idle (RRC_IDLE), and inactive (RRC_INACTIVE). The UE can also support multiple CM states, such as idle (CM_IDLE) and connected (CM_CONNECTED). Furthermore, the UE can support multiple RM states, such as deregistered (RM_DEREGISTERED) and registered (RM_REGISTERED). For A-IoT devices with low complexity, supporting all states in RRC, CM, and / or RM communication may be too complex. Therefore, wireless networks often lack state management for A-IoT devices, resulting in higher network resource consumption due to inefficient management of network resources. Additionally, without the ability to switch between states, A-IoT devices and / or associated readers may maintain unnecessary activity, leading to increased power consumption. Furthermore, without the ability to enable A-IoT devices to indicate their current state, reader and / or A-IoT controller devices may repeatedly attempt to issue requests and / or commands to unavailable A-IoT devices, thereby excessively consuming network resources, power resources, and / or computing resources.

[0129] The various aspects collectively relate to state management for A-IoT communication. Some aspects more specifically involve signaling and maintenance of A-IoT device state and / or reader state. In some aspects, A-IoT devices may support and indicate one or more short-term A-IoT states (e.g., transmitting information for local communication between the A-IoT device and the reader device) and / or long-term A-IoT states (e.g., transmitting information for end-to-end communication between the A-IoT device and the A-IoT controller device). In some aspects, reader devices may maintain and manage the short-term A-IoT states of A-IoT devices. In some aspects, A-IoT controller devices may maintain and manage the long-term A-IoT states of A-IoT devices. In some aspects, reader devices and / or A-IoT controller devices may issue requests to A-IoT devices to change their A-IoT states.

[0130] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by implementing state management for A-IoT communication, the described techniques can be used to efficiently manage network resources, thereby reducing network resource consumption. Furthermore, by maintaining and managing the short-term A-IoT state of A-IoT devices at the reader device, the described techniques can be used to improve the performance of communication between the reader device and the A-IoT devices, such as by reducing attempts by the reader device to issue requests and / or commands to currently unavailable A-IoT devices. Similarly, by maintaining and managing the long-term state of A-IoT devices at the A-IoT controller device, the described techniques can be used to efficiently notify the reader device of A-IoT devices with long-term unavailability, so that the reader device does not consume network, power, and / or computing resources to issue requests and / or commands to those unavailable A-IoT devices. Furthermore, by enabling the reader device and / or A-IoT controller device to request the A-IoT device to change its A-IoT state (e.g., between a sleep state and a wake state), the described techniques can be used to save power for the A-IoT device and / or the reader device (e.g., by enabling the reader device to reduce power consumption based on when the A-IoT device is asleep).

[0131] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0132] Figure 7 This is a diagram of example 700 associated with state management for A-IoT communication according to this disclosure. Figure 7 As shown, a reader device (e.g., reader device 610) can communicate with an A-IoT device (e.g., A-IoT device 135) and an A-IoT controller device (e.g., A-IoT controller device 137). In some aspects, the reader device, A-IoT device, and A-IoT controller device can be part of a wireless network (e.g., wireless network 100). The A-IoT device can include an IoT terminal, a tag, or a wireless communication device. The reader device can be a UE (e.g., co-located with it), a network node (e.g., a gNB or IAB node), a sidelink repeater, or a separate logical entity (e.g., a wireless communication device), etc. The A-IoT controller device can be a device that implements core network functions or application functions (e.g., a core network device or a network node). The reader device and A-IoT device can... Figure 7 The operation shown has been performed with a wireless connection already established.

[0133] In some aspects, the reader device (e.g., UE) may receive configuration information from a network node. In some aspects, the reader device may receive configuration information via one or more of the following: system information (e.g., Master Information Block (MIB) and / or System Information Block (SIB), etc.), RRC signaling, one or more MAC-CE and / or DCI messages, etc. In some aspects, the configuration information may indicate one or more candidate configuration and / or communication parameters. In some aspects, the one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated by subsequent indications. For example, a subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configuration and / or communication parameters. In some aspects, subsequent indications (e.g., the indications described herein) may include dynamic indications, such as one or more MAC-CE and / or one or more DCI messages, etc.

[0134] In some aspects, the configuration information may indicate the A-IoT states that the reader device should support and / or the reader device states that the reader device can use (e.g., RRC states). In some aspects, the configuration information may indicate that the reader device should communicate with A-IoT devices according to the A-IoT states, and / or indicate that the reader device should perform state management for A-IoT devices. The reader device may configure itself at least in part based on the configuration information. In some aspects, the reader device may be configured to perform one or more of the operations described herein, at least in part based on the configuration information.

[0135] In some aspects, the reader device may send a capability report for network nodes. The capability report may indicate whether the reader device supports a feature and / or one or more parameters associated with that feature. For example, capability information may indicate capabilities and / or parameters related to: whether the reader device can act as a reader for A-IoT devices, whether the reader device supports state management for A-IoT devices, A-IoT states supported by the reader device, and / or reader device states supported by the reader device (e.g., RRC states), etc. One or more operations described herein may be based on the capability information in the capability report. For example, the reader device may perform communication based on the capability information, or may receive configuration information based on that capability information. In some aspects, the capability report may indicate the reader device's support for state management of A-IoT devices.

[0136] In some aspects, configuration information and / or capability reports may include information transmitted via multiple communications. Additionally or alternatively, network nodes may transmit configuration information or communications including at least a portion of configuration information before and / or after the reader device transmits the capability report. For example, a network node may transmit a first portion of the configuration information before the capability report, the reader device may transmit at least a portion of the capability report, and the network node may transmit a second portion of the configuration information after receiving the capability report.

[0137] As used in this article, "state" can refer to a specific operating condition or mode in which a device is operating. Therefore, "A-IoT state" can refer to a specific operating condition or mode in which an A-IoT device is operating.

[0138] A-IoT devices can support one or more short-term A-IoT states and / or long-term A-IoT states. Short-term A-IoT states can convey information useful for local communication between the A-IoT device and the reader device. Short-term A-IoT states may involve: the power state of the A-IoT device (e.g., whether the A-IoT device is on or off); the sleep state of the A-IoT device (e.g., whether the A-IoT device is in light sleep, medium sleep, or deep sleep, etc.); the energy storage state of the A-IoT device (e.g., whether the A-IoT device is in a low-energy state, medium-energy state, or high-energy state, etc.); the packet processing state of the A-IoT device (e.g., whether the A-IoT device has received a packet and / or is waiting for a reply or acknowledgment); the packet communication (e.g., packet reception and / or transmission) or packet buffering state of the A-IoT device (e.g., whether a packet segment has been received and the A-IoT device is waiting for other segments, or whether packets are already buffered in the A-IoT device's transmit or receive buffer); and the inventory state of the A-IoT device (e.g., A...). The A-IoT device's short-term A-IoT state includes: whether the A-IoT device has been inventoried; the discovery status of the A-IoT device (e.g., whether the A-IoT device has discovery permissions enabled); the scanning status of the A-IoT device (e.g., whether the A-IoT device is in a scanning state, such as listening for beacons and / or announcement packets); the time and frequency synchronization status of the A-IoT device (e.g., whether the A-IoT device is time and frequency synchronized, such as whether the uplink timing of the A-IoT device is synchronized); the access process status of the A-IoT device (e.g., whether the A-IoT device has completed contention resolution); the identifier allocation status of the A-IoT device (e.g., whether the local identifier used for communication with the reader device has been allocated, assigned, released, or acknowledged for the A-IoT device); and / or the connection status of the A-IoT device (e.g., whether the A-IoT device can exchange data through connection or session), etc. The short-term A-IoT state of the A-IoT device can be managed by the reader device and / or the A-IoT controller device. The short-term A-IoT state can also be referred to as the "first A-IoT state" or "lower-level A-IoT state".

[0139] Long-term A-IoT states can convey information useful for end-to-end communication between A-IoT devices and A-IoT controller devices (e.g., and ultimately with the AF). The long-term A-IoT state of an A-IoT device can be transparent to the reader device (e.g., the reader device may not monitor or maintain information related to the long-term state). Long-term A-IoT states can involve the communication link security status of the A-IoT device (e.g., whether the communication link of the A-IoT device is secure), the registration status of the A-IoT device (e.g., whether the A-IoT device has been registered, such as being assigned a unique identifier), the network access status of the A-IoT device (e.g., whether the A-IoT device has been network accessed, such as being configured using specific information), and / or the disabled status of the A-IoT device (e.g., whether the A-IoT device has been permanently disabled, sometimes referred to as "killed"), etc. The long-term A-IoT state of an A-IoT device can be managed by the A-IoT controller device. Long-term A-IoT states can also be referred to as "secondary A-IoT states" or "higher-level A-IoT states."

[0140] In some aspects, one or more short-term A-IoT states and / or one or more long-term A-IoT states may be mandatory for the support of A-IoT devices, reader devices, and / or A-IoT controller devices. In other aspects, one or more short-term A-IoT states and / or one or more long-term A-IoT states may be optional for the support of A-IoT devices, reader devices, and / or A-IoT controller devices. Whether optional short-term A-IoT states and / or long-term A-IoT states are supported and / or applicable may depend on the capabilities of the A-IoT device (e.g., storage capacity), the amount of energy harvested and / or stored at the A-IoT device, and / or radio conditions, etc.

[0141] As shown by reference numeral 702 in the accompanying drawings, an A-IoT device can begin in one or more initial short-term A-IoT states and / or long-term A-IoT states. A reader device can also support one or more reader states. For example, reader states may include RRC state, CM state, RM state, and / or another type of state. As shown by reference numeral 704 in the accompanying drawings, a reader device can also begin in one or more initial reader states.

[0142] As indicated by reference numeral 706 in the accompanying drawings, an A-IoT device can communicate, and a reader device can receive, communications indicating short-term A-IoT states (e.g., one or more short-term A-IoT states) of the A-IoT device. For example, the A-IoT device can notify the reader device of the current short-term state and / or any short-term state change. In some aspects, the short-term A-IoT states that can be indicated by the A-IoT device (e.g., those that the A-IoT device is permitted to indicate) can be dynamic (e.g., may change from time to time) depending on the A-IoT device's capabilities (e.g., storage capacity), the amount of energy collected and / or stored at the A-IoT device, and / or radio conditions, etc. In some aspects, communications indicating short-term A-IoT states may additionally indicate contextual information of the A-IoT device, such as a device identifier associated with the A-IoT device, a session or bearer identifier associated with the A-IoT device, the A-IoT device's Layer 2 (L2) configuration (e.g., RLC channel configuration), and / or the security context associated with the A-IoT device, etc. In some respects, communication indicating short-term IoT states can be performed via Layer 1 (L1) (e.g., PHY signaling) or L2 signaling (e.g., MAC signaling) and / or via upper-layer signaling (e.g., RRC signaling and / or Non-Access Stratum (NAS) signaling).

[0143] In some respects, the reader device can detect changes in the short-term A-IoT state of an A-IoT device without explicit communication indicating a short-term A-IoT state (e.g., the reader device can implicitly detect changes in the short-term A-IoT state). For example, the reader device can detect changes in the short-term A-IoT state of an A-IoT device by detecting a connection failure with the A-IoT device, using one or more counters (e.g., a counter for a message sent without a response from the A-IoT device meeting a threshold, or a retransmission counter meeting a threshold), or based on other events (e.g., the expiration of one or more timers).

[0144] As shown by reference numeral 708 in the accompanying drawings, the reader device can store state information identifying short-term A-IoT states of the A-IoT devices. For example, the reader device can maintain short-term states of the A-IoT devices. Therefore, the reader device can receive indications of short-term states from one or more A-IoT devices (e.g., multiple A-IoT devices) and maintain those short-term states.

[0145] As shown by reference numeral 710, the reader device can send, and the A-IoT controller device can receive, communications indicating a short-term A-IoT state of the A-IoT device. As shown by reference numeral 712, the A-IoT device can send, and the A-IoT controller device can receive, communications indicating a long-term A-IoT state (e.g., one or more long-term A-IoT states) of the A-IoT device. For example, as shown, the reader device can forward communications indicating a long-term A-IoT state of the A-IoT device from the A-IoT device to the A-IoT controller device. To forward the communications, the reader device can receive a first communication, decode the first communication, and send a second communication containing information from the first communication. Alternatively, to forward the communications, the reader device can receive communications and send the communications without decoding them. In some aspects, communications indicating a long-term A-IoT state may additionally indicate a short-term A-IoT state of the A-IoT device. In this way, the A-IoT device can notify the A-IoT controller device of the current long-term state and / or any long-term state change of the A-IoT device, and in some examples, notify the A-IoT controller device of the current short-term state and / or any short-term state change of the A-IoT device.

[0146] As shown by reference numeral 714 in the accompanying drawings, the A-IoT controller device may store state information identifying the long-term A-IoT state of the A-IoT device (and in some examples, also identifying the short-term A-IoT state of the A-IoT device). For example, the A-IoT controller device may maintain the long-term state of the A-IoT device (and in some examples, also maintain the short-term state of the A-IoT device). Therefore, the A-IoT controller device may receive indications of long-term states from one or more A-IoT devices (e.g., multiple A-IoT devices) and maintain those long-term states (and in some examples, receive and maintain the short-term states of one or more A-IoT devices). In some aspects, the reader device may send, and the A-IoT controller device may receive, communications indicating the reader state of the reader device. In some aspects, the A-IoT controller device may store state information identifying the reader state of the reader device (e.g., the A-IoT controller device may maintain the reader state of the reader device).

[0147] In some aspects, A-IoT devices can respond to events (e.g., event triggering, such as radio conditions exceeding a threshold, the energy harvested by the A-IoT device exceeding a threshold, and / or when establishing a new connection or session), after a specific fixed time, or according to periodicity (e.g., the A-IoT device can periodically send communications) to indicate the short-term A-IoT state of the A-IoT device (described in conjunction with reference numeral 706) and / or the long-term A-IoT state of the A-IoT device (described in conjunction with reference numeral 712). Therefore, a reader device can receive communications indicating the short-term A-IoT state of the A-IoT device in response to events, after a specific fixed time, or according to periodicity. Similarly, an A-IoT controller device can receive communications indicating the long-term A-IoT state of the A-IoT device in response to events, after a specific fixed time, or according to periodicity.

[0148] As shown by reference numeral 716 in the accompanying drawings, the reader device can send, and the A-IoT device can receive, a request to change (e.g., update or modify) the short-term A-IoT state of the A-IoT device. For example, the reader device can request (e.g., instruct) the A-IoT device to change its short-term device state. As an example, the reader device can request the A-IoT device to change its sleep state (e.g., enter sleep mode to save power, or wake up from sleep mode to communicate with the reader device).

[0149] As shown by reference numeral 718, the A-IoT controller device can send, and the A-IoT device can receive, a request to change the long-term A-IoT state of the A-IoT device. For example, as shown, a reader device can forward a request to change the long-term A-IoT state of the A-IoT device from the A-IoT controller device to the A-IoT device. The reader device can forward the request in a manner similar to that described in conjunction with reference numeral 712. In some aspects, a request to change the long-term A-IoT state of the A-IoT device may additionally or alternatively request a change to the short-term A-IoT state of the A-IoT device. Thus, the A-IoT controller device can request (e.g., instruct) the A-IoT device to change its long-term and / or short-term states. As shown by reference numeral 720, the A-IoT device can change its short-term and / or long-term A-IoT state in response to a request sent by the reader device (described in conjunction with reference numeral 716) or a request sent by the A-IoT controller device (described in conjunction with reference numeral 718).

[0150] As shown by reference numeral 722 in the accompanying drawings, the A-IoT controller device can send, and the reader device can receive, a request (e.g., an instruction) to perform an action (e.g., to take a specific action) related to the A-IoT state of the A-IoT device and / or the reader state of the reader device (e.g., to perform a specific action). (For example, the request to perform an action may be in response to changes in the short-term and / or long-term A-IoT state of the A-IoT device). For instance, the A-IoT controller device may request (e.g., instruct) the reader device to take a specific action related to state management. As an example, this action could be releasing and / or modifying one or more short-term A-IoT states maintained at the reader device (e.g., to enable the reader device to consider long-term state changes of the A-IoT device that the reader device may not be aware of). As another example, the action could be changing the reader state of the reader device.

[0151] As shown by reference numeral 724 in the accompanying drawings, the reader device may change its reader state. For example, the reader device may change its reader state in response to a request to perform an action sent by the A-IoT controller device (described in conjunction with reference numeral 722). Alternatively, the reader device may change its reader state without a request from the A-IoT controller device. For example, the reader device may change its reader state in response to detecting a specific radio condition, in response to detecting a specific power level of the reader device, in response to transmitting or receiving communication, and / or in response to a change in a short-term A-IoT state by the A-IoT device, etc.

[0152] As shown by reference numeral 726 in the accompanying drawings, the reader device can send and the A-IoT device and / or the A-IoT controller device can receive one or more communications indicating the reader state of the reader device. For example, the reader device can send communications to the A-IoT device, and / or the reader device can send communications to the A-IoT controller device. The reader device can send one or more communications in response to a change in its reader state. In this way, the reader device can notify the A-IoT device and / or the A-IoT controller device of its current reader state and / or any change in reader state.

[0153] By using the control logic (e.g., status information) described herein at A-IoT devices, reader devices, and / or A-IoT controller devices, these entities can identify the appropriate action to be taken based on the status of their peers. For example, reader devices and / or A-IoT controller devices can avoid sending inventory requests or commands to A-IoT devices that are in an insecure state, permanently disabled state, and / or low-energy state, etc. In this way, network resources used for A-IoT communication are managed efficiently, the performance of A-IoT communication is improved, and A-IoT devices can experience improved power savings.

[0154] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0155] Figure 8 This is a flowchart of an example process 800 for wireless communication. Process 800 may be performed at, for example, a reader device (e.g., UE 120 or network node 110) or a device of the reader device.

[0156] Process 800 begins at 810: receiving communication indicating the short-term environmental IoT state of the environmental IoT device. For example, a reader device may receive communication indicating the short-term environmental IoT state of the environmental IoT device, as described above in conjunction with, for example... Figure 7 And as described at 706.

[0157] The process continues at 800 and then at 820: State information identifying the short-term environmental IoT state of the environmental IoT device is stored. For example, a reader device may store state information identifying the short-term environmental IoT state of the environmental IoT device, as described above in conjunction with examples... Figure 7 And as described at 708.

[0158] In some respects, short-term environmental IoT states involve one or more of the following: the power state of the environmental IoT device; the sleep state of the environmental IoT device; the energy storage state of the environmental IoT device; the packet processing state, packet communication state, or packet buffering state of the environmental IoT device; the inventory state of the environmental IoT device; the discovery state of the environmental IoT device; the scanning state of the environmental IoT device; the time and frequency synchronization state of the environmental IoT device; the access process state of the environmental IoT device; the identifier assignment state of the environmental IoT device; or the connection state of the environmental IoT device.

[0159] In some respects, process 800 includes: sending additional communications to the environmental IoT controller device indicating the short-term environmental IoT status of the environmental IoT device.

[0160] In some respects, process 800 includes sending a request to the environmental IoT device to change the short-term environmental IoT state of the environmental IoT device.

[0161] In some aspects, process 800 includes: forwarding additional communications from the environmental IoT device to the environmental IoT controller device that indicate the long-term environmental IoT status of the environmental IoT device.

[0162] In some aspects, process 800 includes: forwarding a request from the environmental IoT controller device to the environmental IoT device to change the long-term environmental IoT state or short-term environmental IoT state of the environmental IoT device.

[0163] In some respects, the long-term environmental IoT status involves one or more of the following: the security status of the communication links of the environmental IoT devices; the registration status of the environmental IoT devices; the network access status of the environmental IoT devices; or the disabled status of the environmental IoT devices.

[0164] In some aspects, process 800 includes: receiving from an environmental IoT controller device a request to perform an action related to the environmental IoT state of the environmental IoT device or the state of a reader device.

[0165] In some respects, process 800 includes sending one or more additional communications indicating the status of the reader device.

[0166] In some respects, receiving communications indicating the short-term environmental IoT status of an environmental IoT device includes: receiving communications indicating the short-term environmental IoT status of an environmental IoT device in response to an event, after a fixed period of time, or according to periodicity.

[0167] In some respects, communication indicating the short-term environmental IoT status of environmental IoT devices is via Layer 1 or Layer 2 signaling, or via upper-layer signaling.

[0168] In some respects, communications indicating the short-term environmental IoT state of environmental IoT devices additionally indicate the contextual information of the environmental IoT devices.

[0169] In one respect, process 800 or any aspect thereof may be made possible by means of a device (such as...) Figure 14 The communication device 1400 performs the operation, and the device includes various components capable of operating, being configured, or being adapted to perform the process 800. The communication device 1400 is described in further detail below.

[0170] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0171] Figure 9 This is a flowchart of an example process 900 for wireless communication. Process 900 may be performed at, for example, an environmental IoT device (e.g., environmental IoT device 135) or a device of the environmental IoT device.

[0172] Process 900 begins at 910: First communication indicating a short-term environmental IoT state of the environmental IoT device. For example, the environmental IoT device may communicate first communication indicating a short-term environmental IoT state, as described above in conjunction with examples. Figure 7 And as described at 706.

[0173] The process continues at 900 and then at 920: a second communication indicating the long-term environmental IoT state of the environmental IoT device is conveyed. For example, the environmental IoT device may convey a second communication indicating the long-term environmental IoT state of the environmental IoT device, as described above in conjunction with examples. Figure 7 And as described at 712.

[0174] In some respects, process 900 includes receiving a request to change the short-term environmental IoT state of the environmental IoT device.

[0175] In some respects, process 900 includes receiving a request to change the long-term environmental IoT state of the environmental IoT device.

[0176] In some respects, process 900 includes receiving additional communications indicating the status of the reader device.

[0177] In some respects, short-term environmental IoT states involve one or more of the following: the power state of the environmental IoT device; the sleep state of the environmental IoT device; the energy storage state of the environmental IoT device; the packet processing state, packet communication state, or packet buffering state of the environmental IoT device; the inventory state of the environmental IoT device; the discovery state of the environmental IoT device; the scanning state of the environmental IoT device; the time and frequency synchronization state of the environmental IoT device; the access process state of the environmental IoT device; the identifier assignment state of the environmental IoT device; or the connection state of the environmental IoT device.

[0178] In some respects, the long-term environmental IoT status involves one or more of the following: the security status of the communication links of the environmental IoT devices; the registration status of the environmental IoT devices; the network access status of the environmental IoT devices; or the disabled status of the environmental IoT devices.

[0179] In some respects, the first communication indicating the short-term environmental IoT state of an environmental IoT device includes: the first communication indicating the short-term environmental IoT state of an environmental IoT device in response to an event, after a fixed period of time, or according to periodicity.

[0180] In some respects, the second communication that conveys an indication of the long-term environmental IoT state of an environmental IoT device includes: in response to an event, after a fixed period of time, or according to periodicity, conveying a second communication that indicates the long-term environmental IoT state of an environmental IoT device.

[0181] In some respects, the first communication indicating the short-term environmental IoT status of environmental IoT devices is via Layer 1 or Layer 2 signaling, or via upper-layer signaling.

[0182] In some respects, the first communication indicating the short-term environmental IoT state of an environmental IoT device additionally indicates the contextual information of the environmental IoT device.

[0183] In one respect, process 900 or any aspect thereof may be made possible by means of a device (such as...) Figure 15 The communication device 1500 performs the operation, and the device includes various components capable of operating, being configured, or adapted to perform the process 900. The communication device 1500 is described in further detail below.

[0184] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0185] Figure 10 This is a flowchart of an example process 1000 for wireless communication. Process 1000 may be performed at, for example, an environmental IoT controller device (e.g., environmental IoT controller device 137) or a device of the environmental IoT controller device.

[0186] Process 1000 begins at 1010, where it receives communication indicating the long-term environmental IoT state of the environmental IoT device. For example, the environmental IoT controller device may receive communication indicating the long-term environmental IoT state of the environmental IoT device, as described above in conjunction with, for example... Figure 7 And as described at 712.

[0187] Process 1000 then continues at 1020: State information identifying the long-term environmental IoT state of the environmental IoT device is stored. For example, an environmental IoT controller device can store state information identifying the long-term environmental IoT state of the environmental IoT device, as described above in conjunction with examples... Figure 7 And as described at 714.

[0188] In some respects, the long-term environmental IoT status involves one or more of the following: the security status of the communication links of the environmental IoT devices; the registration status of the environmental IoT devices; the network access status of the environmental IoT devices; or the disabled status of the environmental IoT devices.

[0189] In some respects, process 1000 includes receiving additional communications indicating the short-term environmental IoT status of environmental IoT devices.

[0190] In some respects, short-term environmental IoT states involve one or more of the following: the power state of the environmental IoT device; the sleep state of the environmental IoT device; the energy storage state of the environmental IoT device; the packet processing state, packet communication state, or packet buffering state of the environmental IoT device; the inventory state of the environmental IoT device; the discovery state of the environmental IoT device; the scanning state of the environmental IoT device; the time and frequency synchronization state of the environmental IoT device; the access process state of the environmental IoT device; the identifier assignment state of the environmental IoT device; or the connection state of the environmental IoT device.

[0191] In some respects, process 1000 includes sending a request to change the long-term or short-term environmental IoT state of the environmental IoT device.

[0192] In some aspects, process 1000 includes sending a request to perform an action related to the environmental IoT state of the environmental IoT device or the state of the reader device.

[0193] In some respects, process 1000 includes receiving additional communications indicating the status of the reader device.

[0194] In some respects, receiving communications indicating the long-term environmental IoT state of an environmental IoT device includes: receiving communications indicating the long-term environmental IoT state of an environmental IoT device in response to an event, after a fixed period of time, or according to periodicity.

[0195] In one respect, process 1000 or any aspect thereof may be made possible by means of a device (such as...) Figure 16 The communication device 1600 performs the operation, and the device includes various components capable of operating, being configured, or adapted to perform the process 1000. The communication device 1600 is described in further detail below.

[0196] although Figure 10 An example box of process 1000 is shown, but in some respects, process 1000 may include... Figure 10 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0197] Figure 11This is a diagram illustrating an example device 1100 for wireless communication according to the present disclosure. Device 1100 may be a reader device (e.g., UE 120, network node 110), or a reader device may include device 1100. In some aspects, device 1100 includes a receiving component 1102, a transmitting component 1104, and / or a communication manager 1106 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1106 is combined with... Figure 1 The communication manager 140 or 150 is described. As shown, the device 1100 can communicate with another device 1108 (such as a UE, a network node (such as a CU, DU, RU or base station) or an environmental IoT device or an environmental IoT controller device) using the receiving component 1102 and the transmitting component 1104.

[0198] In some respects, device 1100 can be configured to perform the functions described herein. Figure 7 One or more operations as described herein. Additionally or alternatively, device 1100 may be configured to perform one or more processes described herein (such as...). Figure 8 Process 800) or combinations thereof. In some aspects, device 1100 and / or Figure 11 One or more components shown may include combinations Figure 2 One or more components of the described reader device. Additionally or alternatively, Figure 11 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0199] Receiver 1102 may receive communications from device 1108, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... Figure 2The described reader device includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0200] Transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1108. In some aspects, one or more other components of device 1100 may generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1108. In some aspects, transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1108. In some aspects, transmitting component 1104 may include combinations of... Figure 2 The described reader device includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in one or more transceivers.

[0201] The communication manager 1106 may support the operation of the receiving component 1102 and / or the transmitting component 1104. For example, the communication manager 1106 may receive information associated with configuring the receiving component 1102 to receive communication and / or the transmitting component 1104 to transmit communication. Additionally or alternatively, the communication manager 1106 may generate control information and / or provide control information to the receiving component 1102 and / or the transmitting component 1104 to control the receiving and / or transmitting of communication.

[0202] The receiving component 1102 can receive communications indicating the short-term environmental IoT status of the environmental IoT device. The communication manager 1106 can store status information identifying the short-term environmental IoT status of the environmental IoT device.

[0203] The transmitting component 1104 can transmit additional communications to the environmental IoT controller device, indicating the short-term environmental IoT status of the environmental IoT device.

[0204] The sending component 1104 can send a request to the environmental IoT device to change the short-term environmental IoT state of the environmental IoT device.

[0205] The communication manager 1106 can forward additional communications from the environmental IoT device to the environmental IoT controller device, indicating the long-term environmental IoT status of the environmental IoT device.

[0206] The communication manager 1106 can forward requests from the environmental IoT controller device to the environmental IoT device to change the long-term or short-term environmental IoT state of the environmental IoT device.

[0207] The receiving component 1102 can receive from the environmental IoT controller device a request to perform an action related to the environmental IoT status of the environmental IoT device or the status of the reader device.

[0208] The transmitting component 1104 can transmit one or more additional communications indicating the status of the reader device.

[0209] Figure 11 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 11 The two or more components shown can be implemented within a single component, or Figure 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 11 The collection of (one or more) components shown is executable and described as being composed of Figure 11 The other set of components shown performs one or more functions.

[0210] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be an environmental IoT device, or an environmental IoT device may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1206 is combined with... Figure 1 The described communication manager 160. As shown, device 1200 can communicate with another device 1208 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1202 and transmitting component 1204.

[0211] In some respects, device 1200 can be configured to perform the functions described herein. Figure 7 One or more operations as described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein (such as...). Figure 9 Process 900) or combinations thereof. In some aspects, device 1200 and / or Figure 12 One or more components shown may include combinations Figure 2 One or more components of an IoT device in the described environment. Additionally or alternatively, Figure 12One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0212] Receiver 1202 may receive communications from device 1208, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to one or more other components of device 1200. In some aspects, receiver 1202 may include combinations of... Figure 2 The described environment refers to one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof, of an IoT device.

[0213] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described environment includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmitting component 1204 may co-located with the receiving component 1202 in one or more transceivers.

[0214] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the receiving component 1202 to receive communication and / or the transmitting component 1204 to transmit communication. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the receiving and / or transmitting of communication.

[0215] The transmitting component 1204 can convey a first communication indicating the short-term environmental IoT state of the environmental IoT device. The transmitting component 1204 can also convey a second communication indicating the long-term environmental IoT state of the environmental IoT device.

[0216] Receiver 1202 can receive requests to change the short-term environmental IoT state of the environmental IoT device. Receiver 1202 can also receive requests to change the long-term environmental IoT state of the environmental IoT device. Receiver 1202 can also receive additional communications indicating the state of the reader device.

[0217] Figure 12 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown is executable and described as being composed of Figure 12 The other set of components shown performs one or more functions.

[0218] Figure 13 This is a diagram of an example device 1300 for wireless communication according to the present disclosure. Device 1300 may be an environmental IoT controller device, or an environmental IoT controller device may include device 1300. In some aspects, device 1300 includes a receiving component 1302, a transmitting component 1304, and / or a communication manager 1306 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1306 is combined with... Figure 1 The described communication manager 170. As shown, device 1300 can communicate with another device 1308 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1302 and transmitting component 1304.

[0219] In some respects, device 1300 can be configured to perform the functions described herein. Figure 7 One or more operations described herein. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein (such as...). Figure 10 Process 1000) or combinations thereof. In some aspects, device 1300 and / or Figure 13 One or more components shown may include combinations Figure 2 The described environment includes one or more components of an IoT controller device. Additionally or alternatively, Figure 13 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0220] Receiver 1302 may receive communications from device 1308, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 2 The described environment IoT controller device includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0221] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1308. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1308. In some aspects, transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1308. In some aspects, transmitting component 1304 may include combinations of... Figure 2The described environment IoT controller device includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1304 may co-located with the receive component 1302 in one or more transceivers.

[0222] The communication manager 1306 may support the operation of the receiving component 1302 and / or the transmitting component 1304. For example, the communication manager 1306 may receive information associated with configuring the receiving component 1302 to receive communication and / or the transmitting component 1304 to transmit communication. Additionally or alternatively, the communication manager 1306 may generate control information and / or provide control information to the receiving component 1302 and / or the transmitting component 1304 to control the receiving and / or transmitting of communication.

[0223] The receiving component 1202 can receive communications indicating the long-term environmental IoT status of the environmental IoT device. The communication manager 1206 can store status information identifying the long-term environmental IoT status of the environmental IoT device.

[0224] The receiving component 1202 can receive additional communications indicating the short-term environmental IoT state of the environmental IoT device. The transmitting component 1204 can send a request to change the long-term or short-term environmental IoT state of the environmental IoT device. The transmitting component 1204 can send a request to perform an action related to the environmental IoT state of the environmental IoT device or the state of the reader device. The receiving component 1202 can receive additional communications indicating the state of the reader device.

[0225] Figure 13 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 13 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 13 The two or more components shown can be implemented within a single component, or Figure 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The collection of (one or more) components shown is executable and described as being composed of Figure 13 The other set of components shown performs one or more functions.

[0226] Figure 14 This is a diagram illustrating an example of a specific implementation of the code and circuitry for a communication device 1400 according to this disclosure. The communication device 1400 may be a reader device (e.g., UE 120 or network node 110), or the reader device may include the communication device 1400.

[0227] The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or receiver, and which may include a single transceiver or multiple transceivers capable of performing various operations described herein). The transceiver 1408 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1400 via an antenna 1410. The processing system 1402 may be configured to perform processing functions for the communication device 1400, including processing signals received by and / or to be transmitted by the communication device 1400.

[0228] Processing system 1402 includes one or more processors 1420. In various aspects, the one or more processors 1420 may include one or more of the following: a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a receive processor 238, a transmit processor 214, a TX MIMO processor 216, and / or a controller / processor 240, as per [reference to...]. Figure 2 As described. One or more processors 1420 are coupled to computer-readable medium / memory 1430 via bus 1406. In various aspects, computer-readable medium / memory 1430 may include one or more memories, such as memory 282 and / or memory 242, as described above. Figure 2 As described. In some aspects, the computer-readable medium / memory 1430 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by one or more processors 1420, cause one or more processors 1420 to perform actions related to... Figure 8 The process 800 described herein or any aspect thereof. It should be noted that references to a processor performing the functions of communication device 1400 may include one or more processors performing the functions of communication device 1400. It should also be noted that references to one or more processors performing multiple functions may include a first processor performing a first function among multiple functions and a second processor performing a second function among multiple functions.

[0229] like Figure 14 As shown, the communication device 1400 may include circuitry (circuit 1435) for receiving communications indicating short-term environmental IoT status of the environmental IoT device.

[0230] like Figure 14 As shown, the communication device 1400 may include code (code 1440) stored in a computer-readable medium / memory 1430 for receiving communications indicating short-term environmental IoT status of the environmental IoT device.

[0231] like Figure 14 As shown, the communication device 1400 may include circuitry (circuit 1445) for storing state information identifying the short-term environmental IoT state of the environmental IoT device.

[0232] like Figure 14 As shown, the communication device 1400 may include a code (code 1450) stored in a computer-readable medium / memory 1430 for storing status information identifying the short-term environmental IoT state of the environmental IoT device.

[0233] The various components of the communication device 1400 can provide for performing tasks related to... Figure 8 The described process 800 or any component related to it. For example, components for transmitting, conveying, or outputting for transmission may include modem 254 and / or antenna 252 of UE 120, modem 232 and / or antenna 234 of network node 110, and / or Figure 14 The communication device 1400 includes a transceiver 1408 and an antenna 1410. Components for receiving or acquiring data may include a modem 254 and / or antenna 252 of the UE 120, a modem 232 and / or antenna 234 of the network node 110, and / or... Figure 14 The transceiver 1408 and antenna 1410 of the communication device 1400.

[0234] Figure 14 This is provided as an example. Other examples can be combined with it. Figure 14 The examples described are different.

[0235] Figure 15 This is a diagram illustrating an example of a specific implementation of the code and circuitry for a communication device 1500 according to this disclosure. The communication device 1500 may be an environmental IoT device, or an environmental IoT device may include the communication device 1500.

[0236] The communication device 1500 includes a processing system 1502 coupled to a transceiver 1508 (e.g., a transmitter and / or receiver, and which may include a single transceiver or multiple transceivers capable of performing various operations described to be performed by the transceiver 1508). The transceiver 1508 is configured to transmit and receive signals (such as various signals as described herein) for the communication device 1500 via an antenna 1510. The processing system 1502 may be configured to perform processing functions for the communication device 1500, including processing signals received by the communication device 1500 and / or to be transmitted by the communication device.

[0237] Processing system 1502 includes one or more processors 1520. In various aspects, the one or more processors 1520 may include one or more of a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and / or a controller / processor 280, as per [reference to...]. Figure 2 As described. One or more processors 1520 are coupled to computer-readable medium / memory 1530 via bus 1506. In various aspects, computer-readable medium / memory 1530 may include one or more memories, such as memory 282, as described above. Figure 2 As described. In some aspects, the computer-readable medium / memory 1530 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by one or more processors 1520, cause one or more processors 1520 to perform actions related to... Figure 9 The process 900 described herein or any aspect thereof. It should be noted that references to a processor performing the functions of communication device 1500 may include one or more processors performing the functions of communication device 1500. It should also be noted that references to one or more processors performing multiple functions may include a first processor performing a first function among the multiple functions and a second processor performing a second function among the multiple functions.

[0238] like Figure 15 As shown, the communication device 1500 may include circuitry (circuit 1535) for conveying a first communication indicating a short-term environmental IoT state of the environmental IoT device.

[0239] like Figure 15 As shown, the communication device 1500 may include code (code 1540) stored in a computer-readable medium / memory 1530 for conveying a first communication indicating a short-term environmental IoT state of the environmental IoT device.

[0240] like Figure 15 As shown, the communication device 1500 may include circuitry (circuit 1545) for conveying a second communication indicating the long-term environmental IoT state of the environmental IoT device.

[0241] like Figure 15 As shown, the communication device 1500 may include a code (code 1550) stored in a computer-readable medium / memory 1530 for conveying a second communication indicating the long-term environmental IoT state of the environmental IoT device.

[0242] The various components of the communication device 1500 can provide for performing tasks related to... Figure 9The described process 900 or any component related to it. For example, components for transmitting, conveying, or outputting for transmission may include the modem 254 and / or antenna 252 of UE 120, and / or Figure 15 The communication device 1500 includes a transceiver 1508 and an antenna 1510. Components for receiving or acquiring data may include a modem 254 and / or an antenna 252 of the UE 120, and / or... Figure 15 The transceiver 1508 and antenna 1510 of the communication equipment 1500.

[0243] Figure 15 This is provided as an example. Other examples can be combined with it. Figure 15 The examples described are different.

[0244] Figure 16 This is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device 1600 according to this disclosure. The communication device 1600 may be an environmental IoT controller device (such as a core network device, network node 110, or as per [other relevant information]). Figure 3 The described decomposed base station, or environmental IoT controller device, may include communication device 1600.

[0245] Communication device 1600 includes a processing system 1602 coupled to transceiver 1608 (e.g., a transmitter and / or receiver, and which may include a single transceiver or multiple transceivers capable of performing various operations described herein). Transceiver 1608 is configured to transmit and receive signals for communication device 1600 via antenna 1610 (e.g., one or more antennas), such as various signals as described herein. Network interface 1612 is configured to transmit via communication links (such as those described herein). Figure 3 The described backhaul link, midhaul link, and / or fronthaul link acquire and transmit signals for the communication device 1600. The processing system 1602 can be configured to perform processing functions for the communication device 1600, including processing signals received by the communication device 1600 and / or to be transmitted by the communication device.

[0246] Processing system 1602 includes one or more processors 1620. In various aspects, the one or more processors 1620 may include one or more of a receive processor 238, a transmit processor 214, a TX MIMO processor 216, and / or a controller / processor 240, as per [reference to...]. Figure 2 As described. One or more processors 1620 are coupled to computer-readable medium / memory 1630 via bus 1606. In various aspects, computer-readable medium / memory 1630 may include one or more memories, such as memory 242, as described above. Figure 2 As described. In some aspects, the computer-readable medium / memory 1630 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by one or more processors 1620, cause one or more processors 1620 to perform actions related to... Figure 10 The process 1000 described herein or any aspect thereof. It should be noted that references to a processor performing the functions of communication device 1600 may include one or more processors performing the functions of communication device 1600. It should also be noted that references to one or more processors performing multiple functions may include a first processor performing a first function among multiple functions and a second processor performing a second function among multiple functions.

[0247] like Figure 16 As shown, the communication device 1600 may include circuitry (circuit 1635) for receiving communications indicating the long-term environmental IoT status of the environmental IoT device.

[0248] like Figure 16 As shown, the communication device 1600 may include code (code 1640) stored in a computer-readable medium / memory 1630 for receiving communications indicating the long-term environmental IoT state of the environmental IoT device.

[0249] like Figure 16 As shown, the communication device 1600 may include circuitry (circuit 1645) for storing state information that identifies the long-term state of the environmental IoT device.

[0250] like Figure 16 As shown, the communication device 1600 may include a code (code 1650) stored in a computer-readable medium / memory 1630 for storing status information identifying the long-term environmental IoT state of the environmental IoT device.

[0251] The various components of the communication device 1600 can provide for performing tasks related to... Figure 10 The described process 1000 or any component related to it. For example, components for sending, transmitting, or outputting for transmission may include the modem 232 and / or antenna 234 of network node 110, and / or Figure 16 The transceiver 1608 and / or antenna 1610 of the communication device 1600 in the network node 110. Components for receiving or acquiring may include the modem 232 and / or antenna 234 of the network node 110, and / or Figure 16 The transceiver 1608 and / or antenna 1610 of the communication device 1600.

[0252] Figure 16 This is provided as an example. Other examples can be combined with it. Figure 16The examples described are different.

[0253] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a reader device, the method comprising: receiving communication indicating a short-term environmental IoT state of an environmental Internet of Things (IoT) device; and storing state information of the environmental IoT device identifying the short-term environmental IoT state.

[0254] Aspect 2: According to the method of Aspect 1, the short-term environmental IoT state involves one or more of the following: the power state of the environmental IoT device; the sleep state of the environmental IoT device; the energy storage state of the environmental IoT device; the packet processing state, packet communication state, or packet buffering state of the environmental IoT device; the inventory state of the environmental IoT device; the discovery state of the environmental IoT device; the scanning state of the environmental IoT device; the time and frequency synchronization state of the environmental IoT device; the access process state of the environmental IoT device; the identifier allocation state of the environmental IoT device; or the connection state of the environmental IoT device.

[0255] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: sending additional communication to the environmental IoT controller device indicating the short-term environmental IoT state of the environmental IoT device.

[0256] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: sending a request to the environmental IoT device to change the short-term environmental IoT state of the environmental IoT device.

[0257] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: forwarding additional communication from the environmental IoT device to the environmental IoT controller device indicating the long-term environmental IoT state of the environmental IoT device.

[0258] Aspect 6: According to the method of aspect 5, the method further includes: forwarding a request from the environmental IoT controller device to the environmental IoT device to change the long-term environmental IoT state or the short-term environmental IoT state of the environmental IoT device.

[0259] Aspect 7: The method according to any one of Aspects 5 to 6, wherein the long-term environmental IoT state involves one or more of the following: the communication link security state of the environmental IoT device; the registration state of the environmental IoT device; the network access state of the environmental IoT device; or the disabled state of the environmental IoT device.

[0260] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: receiving from an environmental IoT controller device a request to perform an action related to the environmental IoT state of the environmental IoT device or the state of the reader device.

[0261] Aspect 9: The method according to any one of aspects 1 to 8, the method further comprising: sending one or more additional communications indicating the state of the reader device.

[0262] Aspect 10: The method according to any one of Aspects 1 to 9, wherein receiving the communication indicating the short-term environmental IoT state of the environmental IoT device comprises: receiving the communication indicating the short-term environmental IoT state of the environmental IoT device in response to an event, after a fixed time, or according to periodicity.

[0263] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the communication indicating the short-term environmental IoT state of the environmental IoT device is via Layer 1 or Layer 2 signaling, or via upper-layer signaling.

[0264] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the communication indicating the short-term environmental IoT state of the environmental IoT device additionally indicates the context information of the environmental IoT device.

[0265] Aspect 13: A method of wireless communication performed by an environmental Internet of Things (IoT) device, the method comprising: conveying a first communication indicating a short-term environmental IoT state of the environmental IoT device; and conveying a second communication indicating a long-term environmental IoT state of the environmental IoT device.

[0266] Aspect 14: According to the method of aspect 13, the method further includes: receiving a request to change the short-term environmental IoT state of the environmental IoT device.

[0267] Aspect 15: The method according to any one of Aspects 13 to 14, the method further comprising: receiving a request to change the long-term environmental IoT state of the environmental IoT device.

[0268] Aspect 16: The method according to any one of aspects 13 to 15, the method further comprising: receiving additional communication indicating the status of the reader device.

[0269] Aspect 17: The method according to any one of Aspects 13 to 16, wherein the short-term environmental IoT state involves one or more of the following: the power state of the environmental IoT device; the sleep state of the environmental IoT device; the energy storage state of the environmental IoT device; the packet processing state, packet communication state, or packet buffering state of the environmental IoT device; the inventory state of the environmental IoT device; the discovery state of the environmental IoT device; the scanning state of the environmental IoT device; the time and frequency synchronization state of the environmental IoT device; the access process state of the environmental IoT device; the identifier allocation state of the environmental IoT device; or the connection state of the environmental IoT device.

[0270] Aspect 18: The method according to any one of Aspects 13 to 17, wherein the long-term environmental IoT state involves one or more of the following: the communication link security state of the environmental IoT device; the registration state of the environmental IoT device; the network access state of the environmental IoT device; or the disabled state of the environmental IoT device.

[0271] Aspect 19: The method according to any one of Aspects 13 to 18, wherein the first communication indicating the short-term environmental IoT state of the environmental IoT device comprises: in response to an event, after a fixed time, or according to periodicity, conveying the first communication indicating the short-term environmental IoT state of the environmental IoT device.

[0272] Aspect 20: The method according to any one of Aspects 13 to 19, wherein the second communication indicating the long-term environmental IoT state of the environmental IoT device comprises: in response to an event, after a fixed period of time, or according to periodicity, conveying the second communication indicating the long-term environmental IoT state of the environmental IoT device.

[0273] Aspect 21: The method according to any one of Aspects 13 to 20, wherein the first communication indicating the short-term environmental IoT state of the environmental IoT device is via Layer 1 or Layer 2 signaling, or via upper-layer signaling.

[0274] Aspect 22: The method according to any one of aspects 13 to 21, wherein the first communication indicating the short-term environmental IoT state of the environmental IoT device additionally indicates the context information of the environmental IoT device.

[0275] Aspect 23: A method of wireless communication performed by an environmental Internet of Things (IoT) controller device, the method comprising: receiving communication indicating a long-term environmental IoT state of the environmental IoT device; and storing state information of the environmental IoT device identifying the long-term environmental IoT state.

[0276] Aspect 24: According to the method of aspect 23, the long-term environmental IoT state involves one or more of the following: the communication link security state of the environmental IoT device; the registration state of the environmental IoT device; the network access state of the environmental IoT device; or the disabled state of the environmental IoT device.

[0277] Aspect 25: The method according to any one of Aspects 23 to 24, the method further comprising: receiving additional communication indicating a short-term environmental IoT state of the environmental IoT device.

[0278] Aspect 26: According to the method of aspect 25, the short-term environmental IoT state involves one or more of the following: the power state of the environmental IoT device; the sleep state of the environmental IoT device; the energy storage state of the environmental IoT device; the packet processing state, packet communication state, or packet buffering state of the environmental IoT device; the inventory state of the environmental IoT device; the discovery state of the environmental IoT device; the scanning state of the environmental IoT device; the time and frequency synchronization state of the environmental IoT device; the access process state of the environmental IoT device; the identifier allocation state of the environmental IoT device; or the connection state of the environmental IoT device.

[0279] Aspect 27: The method according to any one of Aspects 23 to 26, the method further comprising: sending a request to change the long-term environmental IoT state or the short-term environmental IoT state of the environmental IoT device.

[0280] Aspect 28: The method according to any one of Aspects 23 to 27, the method further comprising: sending a request to perform an action related to the environmental IoT state of the environmental IoT device or the state of the reader device.

[0281] Aspect 29: The method according to any one of aspects 23 to 28, the method further comprising: receiving additional communication indicating the status of the reader device.

[0282] Aspect 30: The method according to any one of Aspects 23 to 29, wherein receiving the communication indicating the long-term environmental IoT state of the environmental IoT device comprises: receiving the communication indicating the long-term environmental IoT state of the environmental IoT device in response to an event, after a fixed time, or according to periodicity.

[0283] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 30.

[0284] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0285] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 30.

[0286] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 30.

[0287] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 30.

[0288] Aspect 36: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0289] Aspect 37: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0290] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0291] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not required that the component actually performs that function.

[0292] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0293] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0294] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “collection” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0295] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and One or more processors, the one or more processors being configured to execute processor-executable instructions and cause the device to: Receive communications indicating the short-term environmental IoT status of the device; and The system stores status information that identifies the short-term environmental IoT state of the environmental IoT device.

2. The apparatus of claim 1, wherein the short-term environmental IoT state comprises one or more of the following: The power status of the environmental IoT device. The sleep state of the environmental IoT device. The energy storage status of the environmental IoT device. The packet processing status, packet communication status, or packet buffering status of the environmental IoT device. The inventory status of the environmental IoT devices. The discovery status of the environmental IoT devices. The scanning status of the environmental IoT device. The time and frequency synchronization status of the environmental IoT devices. The status of the access process of the environmental IoT device. The identifier allocation status of the environmental IoT device, or The connection status of the environmental IoT devices.

3. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: Additional communication is sent to the environmental IoT controller device to indicate the short-term environmental IoT state of the environmental IoT device.

4. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: Send a request to the environmental IoT device to change the short-term environmental IoT state of the environmental IoT device.

5. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: Additional communications indicating the long-term environmental IoT status of the environmental IoT device are forwarded from the environmental IoT device to the environmental IoT controller device.

6. The apparatus of claim 5, wherein the one or more processors are further configured to cause the apparatus to: The environmental IoT controller device forwards a request to the environmental IoT device to change the long-term environmental IoT state or the short-term environmental IoT state of the environmental IoT device.

7. The apparatus of claim 5, wherein the long-term environmental IoT state comprises one or more of the following: The security status of the communication link of the environmental IoT device. The registration status of the environmental IoT devices. The network access status of the environmental IoT device, or The environmental IoT device is in a disabled state.

8. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: Receive a request from the environmental IoT controller device to perform an action related to the environmental IoT state of the environmental IoT device or the state of the reader device.

9. The apparatus of claim 1, wherein the one or more processors are further configured to cause the apparatus to: Send one or more additional communications indicating the status of the reader device.

10. The apparatus of claim 1, wherein, in order for the apparatus to receive the communication indicating the short-term environmental IoT state of the environmental IoT device, the one or more processors are configured to cause the apparatus to: The communication indicating the short-term environmental IoT state of the environmental IoT device is received in response to an event, after a fixed period of time, or according to periodicity.

11. The apparatus of claim 1, wherein the communication indicating the short-term environmental IoT state of the environmental IoT device is via Layer 1 or Layer 2 signaling, or via upper-layer signaling.

12. The apparatus of claim 1, wherein the communication indicating the short-term environmental IoT state of the environmental IoT device additionally indicates context information of the environmental IoT device.

13. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and One or more processors, the one or more processors being configured to execute processor-executable instructions and cause the device to: The first communication conveying indications of the short-term environmental IoT status of environmental Internet of Things (IoT) devices; and A second communication conveying an indication of the long-term environmental IoT status of the environmental IoT device.

14. The apparatus of claim 13, wherein the one or more processors are further configured to cause the apparatus to: Receive a request to change at least one of the short-term environmental IoT state or the long-term environmental IoT state of the environmental IoT device.

15. The apparatus of claim 13, wherein the one or more processors are further configured to cause the apparatus to: Receive additional communications indicating the status of the reader device.

16. An apparatus configured for wireless communication, the apparatus comprising: One or more memories, the one or more memories including processor-executable instructions; and One or more processors, the one or more processors being configured to execute processor-executable instructions and cause the device to: Receive communications indicating the long-term environmental IoT status of devices; and The system stores state information that identifies the long-term environmental IoT state of the environmental IoT device.

17. The apparatus of claim 16, wherein the one or more processors are further configured to cause the apparatus to: Receive additional communications indicating the short-term environmental IoT status of the environmental IoT device.

18. The apparatus of claim 16, wherein the one or more processors are further configured to cause the apparatus to: Send a request to change the long-term or short-term environmental IoT state of the environmental IoT device.

19. The apparatus of claim 16, wherein the one or more processors are further configured to cause the apparatus to: Send a request to perform an action related to the environmental IoT state of the environmental IoT device or the state of the reader device.

20. The apparatus of claim 16, wherein the one or more processors are further configured to cause the apparatus to: Receive additional communications indicating the status of the reader device.