Downlink communications with downlink grant and uplink grant

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, an ambient Internet of Things (A-IoT) device can receive a downlink communication having an uplink grant and a downlink grant. The A-IoT device can transmit an uplink communication based at least in part on the uplink grant. Numerous other aspects are described.

Description

Technical Field

[0001] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for instructing downlink and uplink authorization for environmental Internet of Things (IoT) devices. 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. 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). Aspects 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. In some respects, the telecommunications standard is New Radio (NR). NR (which can also be referred to 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. 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. Attached Figure Description

[0004] 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.

[0005] Figure 1This is an illustration of an aspect of a wireless communication network according to the present disclosure.

[0006] Figure 2 This is an illustration of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0007] Figure 3 This is a diagram illustrating the decomposed base station architecture according to this disclosure.

[0008] Figure 4 This is a diagram illustrating aspects of energy harvesting according to this disclosure.

[0009] Figure 5 This is a diagram illustrating an aspect of backscatter communication according to this disclosure.

[0010] Figure 6 This is a diagram illustrating an example of a downlink channel structure according to this disclosure.

[0011] Figure 7 This is a diagram illustrating an example of a downlink channel structure with two headers according to this disclosure.

[0012] Figure 8 This is a diagram illustrating an example of a downlink channel structure with two headers according to this disclosure.

[0013] Figure 9 This is a diagram illustrating an example of the initial location of uplink data according to this disclosure.

[0014] Figure 10 This is a diagram illustrating an example of a backscattered square wave according to this disclosure.

[0015] Figure 11 This is a diagram illustrating an example process performed, for example, at an Ambient Internet of Things (A-IoT) device or an apparatus of an A-IoT device, according to the present disclosure.

[0016] Figure 12 This is a diagram illustrating an example process performed, for example, at a reader device or a device of a reader device, according to the present disclosure.

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

[0018] Figure 14 This is a diagram of an example device for wireless communication according to the present disclosure. Summary of the Invention

[0019] Some aspects described herein relate to a method for performing wireless communication by a wireless device. The method may include: receiving a carrier wave. The method may include: backscattering a square wave, the square wave being at least partially based on the carrier wave.

[0020] Some aspects described herein relate to a method of wireless communication performed by a transmitting device. The method may include: transmitting a carrier wave. The method may also include: receiving a square wave backscattered at least in part based on the carrier wave.

[0021] Some aspects described herein relate to an apparatus for wireless communication at a wireless device. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to receive a carrier wave. The one or more processors may be configured individually or collectively to backscatter a square wave, the square wave being at least partially based on the carrier wave.

[0022] Some aspects described herein relate to an apparatus for wireless communication at a transmitting device. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to transmit a carrier wave. The one or more processors may be configured individually or collectively to receive a square wave backscattered at least partially based on the carrier wave.

[0023] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a wireless device. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to receive a carrier wave. When executed by one or more processors of the wireless device, the set of instructions enables the wireless device to backscatter a square wave, which is at least partially based on the carrier wave.

[0024] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a transmitting device. When executed by one or more processors of the transmitting device, the set of instructions causes the transmitting device to transmit a carrier wave. When executed by one or more processors of the transmitting device, the set of instructions causes the transmitting device to receive a square wave backscattered at least partially based on the carrier wave.

[0025] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a carrier wave. The apparatus may include components for backscattering a square wave, the square wave being at least partially based on the carrier wave.

[0026] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for transmitting a carrier wave. The apparatus may also include components for receiving a square wave backscattered at least in part based on the carrier wave.

[0027] 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.

[0028] 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. Detailed Implementation

[0029] 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. In some aspects, apparatuses may be implemented using various combinations or numbers of aspects set forth herein, or methods may be practiced using these aspects. 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.

[0030] 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 blocks, 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0031] Low-powered devices, such as environmental Internet of Things (A-IoT) devices or radio frequency identification (RFID) tags, may rely on passive communication technologies, such as backscatter communication. Backscatter communication involves using radio frequency (RF) signals to write or transmit data. Backscatter devices may or may not include batteries or power sources. The transmitter / reader may be an RF source that transmits a continuous wave (CW) signal, which can be received by multiple devices, such as readers. Wireless devices, such as passive user equipment (UEs) (e.g., tags, A-IoT devices, UEs without a power source, backscatter devices), can harvest energy (e.g., tens or hundreds of microwatts of power) from this signal. Passive UEs can use the passive reflection and modulation of the signal to transmit backscatter signals using the harvested energy. That is, a passive UE can modulate the signal to encode data and then reflect a portion of the wave back to a reader or transmitter / reader. The backscatter signal can be encoded with information bits of the passive UE (e.g., identification information, sensor information). A reader can receive the backscatter signal and read the information bits.

[0032] A-IoT devices can be categorized according to their type. In some respects, Type A A-IoT devices may lack energy storage and independent signal generation (i.e., backscatter transmission). Type B (or Types 1 and 2a) A-IoT devices may have energy storage but lack independent signal generation (i.e., backscatter transmission). Type C (or Type 2b) A-IoT devices may have both energy storage and independent signal generation (i.e., active RF components for transmission).

[0033] A-IoT devices can receive permissions for both uplink and downlink communication. Reader devices and / or transmitting devices (such as UEs or network entities) can send two separate scheduling messages, one for downlink permission and one for uplink permission. For A-IoT device inventory and commands, the message with uplink permission can always follow the message with downlink permission. Sending two messages for both downlink and uplink permission consumes signaling resources and causes the A-IoT device to consume power to process both messages.

[0034] The various aspects generally relate to wireless communication for A-IoT devices. Some aspects more specifically relate to A-IoT devices receiving downlink and uplink grants from a transmitter / reader device in the same message. The message may include a preamble, one or two headers, and data. The preamble may indicate whether the downlink channel message includes only downlink grant, only uplink grant, or both. In some aspects, the message may include a header indicating both downlink and uplink grants. In some aspects, the first header of the message may indicate downlink grant, and a second header of the same message may indicate uplink grant.

[0035] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages: By receiving downlink and uplink grants in the same message, signaling resources are saved (overhead is reduced), and power consumption of A-IoT devices is reduced.

[0036] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables different wireless communication devices to communicate at the city, national, regional, or global level. In some respects, 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).

[0037] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted or implemented in 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. Such 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 A-IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, RF sensing, and / or artificial intelligence or machine learning (AI / ML). These 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. 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.

[0038] Figure 1 This is an illustration of an aspect 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. 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).

[0039] Network nodes 110 and UEs 120 of the 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. In some aspects, devices of the 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 radio access technology (RAT) (which may also be referred to as an air interface) and can operate on one or more carrier frequencies within one or more frequency ranges. Aspects of RATs include 4G RAT, 5G / NR RAT, and / or 6G RAT. In some aspects, 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.

[0040] 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 the 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 the mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in the 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. In some aspects, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some aspects, 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.

[0041] 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 be referred to as: 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 the radio access network (RAN).

[0042] 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). In some aspects, 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. In some aspects, and as shown in the figure, 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. In some aspects, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0043] Alternatively, and also as shown, network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 may use protocol stacks that are physically distributed and / or logically distributed across two or more nodes in the same or different geographic locations. In some aspects, decomposed network nodes 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 separately deployable units.

[0044] 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. DUs may, at least in part, 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 according to functional splits (such as functional splits defined by 3GPP). In some aspects, 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. In some aspects, RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, 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.

[0045] 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 aspects, 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). Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0046] 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 aspects, 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 home) and can allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for macro cells can be referred to as a macro network node. Network node 110 used for a pico cell 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 respects, the cell may not necessarily be stationary. In some respects, 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, unmanned aerial vehicle, or non-terrestrial network (NTN) network node).

[0047] 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. Figure 1 In this configuration, 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. 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 compared to other types of network nodes 110. In some aspects, 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).

[0048] In some aspects, network node 110 may be, or may include, 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), or may operate as such a RU, TRP, or base station. 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.

[0049] 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). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP 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.

[0050] 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. In some aspects, 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 aspects, network resources (such as time resources, frequency resources, and / or spatial resources) used for wireless communication can be shared between the access link and the backhaul link.

[0051] In some respects, any network node 110 relaying communications 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 this configuration, 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 UEs 120, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE.

[0052] 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 extended reality (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.

[0053] 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.

[0054] 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, configures one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some aspects, 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 or be coupled to 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). 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.

[0055] 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 collectively 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. 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).

[0056] 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 cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise location 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 have intermediate-tier complexity and / or capabilities (e.g., capabilities between UEs 120 in the first category and UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capacity UEs (“RedCap UEs”), intermediate-tier UEs, NR lightweight UEs, and / or NR simplified UEs. 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 wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support deployments in healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart cities.

[0057] In some respects, two or more UEs 120 (shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (without communicating through a network node 110 acting as an intermediary). For example, UE 120a can directly send data, control information, or other signaling to UE 120e as sidelink communication. This contrasts with UE 120a first sending data to network node 110 in uplink (UL) communication, which then sends data to UE 120e in downlink (DL) communication. In various respects, 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.

[0058] In various respects, in addition to half-duplex operation, some of the network nodes 110 and UE 120 of the wireless communication network 100 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 aspects, 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 second component carrier being different from the first frequency band or first component carrier, respectively. In some aspects, full-duplex operation may be enabled for UE 120 but not for network node 110. In some aspects, 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 aspects, full-duplex operation may be enabled for network node 110 but not for UE 120. In some aspects, 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 aspects, full-duplex operation may be enabled for both network node 110 and UE 120.

[0059] In some respects, 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 technology typically utilizes multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some respects, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) can employ advanced MIMO techniques such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NCJT).

[0060] In some aspects, an A-IoT device (e.g., UE 120, a passive UE, a semi-passive UE) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive downlink communication with uplink and downlink permissions; and transmit uplink communication at least in part based on uplink permissions. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0061] In some aspects, the reader device (e.g., UE 120, network node 110) may include a communication manager 140 or 150. As described in more detail elsewhere herein, the communication manager 140 or 150 may transmit downlink communications with uplink and downlink authorization; and receive uplink communications associated with uplink authorization. Additionally or alternatively, the communication manager 140 or 150 may perform one or more other operations described herein.

[0062] As indicated above, Figure 1 This is provided as one aspect. Other aspects may be discussed with regard to... Figure 1 The aspects described are different.

[0063] Figure 2 The diagram illustrates, in some respects, the communication between network node 110 and UE 120 in a wireless network according to the present disclosure.

[0064] 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. 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.

[0065] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. In some respects, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to the 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 2 Any one or more processors described herein. In some aspects, 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.

[0066] 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 those in combination. Figure 2 The memory described. In some respects, it is described that operations performed by one or more memories can be performed by the same subset of one or more memories or by different subsets of one or more memories.

[0067] For downlink communication from network node 110 to UE 120, transmitting 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 aspects, transmitting processor 214 may select one or more modulation and decoding schemes (MCS) 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. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling), and provide overhead symbols and 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)).

[0068] 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. In some aspects, 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 up-convert) 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).

[0069] 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 on 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.

[0070] 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.

[0071] 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 aspects, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication using RRC configuration (e.g., semi-static configuration), and in some aspects, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0072] 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 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.

[0073] In some respects, 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. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0074] UE 120 may include a set of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a set 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. 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.

[0075] 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 transmit the set of received downlink signals (e.g., R Each received signal is provided to a set of modems 254. In some aspects, 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.

[0076] 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 executing 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 Channel Quality Indicator (CQI) parameter, or a Transmit Power Control (TPC) parameter. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0077] 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. In some aspects, 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.

[0078] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or U Uplink 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).

[0079] 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, 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. 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), sets of coplanar antenna elements, sets 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.

[0080] In some aspects, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. In some aspects, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which 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 may allow signals transmitted individually by antenna elements at desired wavelengths to interact or interfere (e.g., to form a desired beam) in various directions through constructive and destructive interactions. In some aspects, given a desired wavelength or frequency range, the spacing may provide a quarter-wavelength, half-wavelength, or another fraction of the wavelength of the spacing between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0081] 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.

[0082] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. In some aspects, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. In other aspects, 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).

[0083] 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. In some respects, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0084] Figure 3The diagram illustrates, in some respects, a disaggregated base station architecture 300 according to the present disclosure. One or more components of the disaggregated base station architecture 300 may be, include, or be incorporated into one or more network nodes (such as one or more network nodes 110). The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more disaggregated 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.

[0085] Each component of the disassembled 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.

[0086] In some aspects, 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. In some aspects, the DU 330 can 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 can 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 RU340 can be controlled by the corresponding DU 330.

[0087] 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.

[0088] The non-RT RIC 350 may include or implement logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (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 logical 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.

[0089] 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 respects, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. In some respects, the non-RT RIC 350 may monitor long-term trends and patterns in 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).

[0090] As indicated above, Figure 3 This is provided as one aspect. Other aspects may be discussed with regard to... Figure 3 The aspects described are different.

[0091] 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 techniques associated with backscattered square waves or perform one or more operations associated with backscattered square waves, as described in more detail elsewhere herein. In some aspects, 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 techniques associated with backscattered square waves or perform one or more operations associated with backscattered square waves, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may perform or instruct in some respects for Figure 12 Process 1200 Figure 13 The operation of process 1300 or other processes as described herein (alone or in combination with one or more other processors). In some aspects, the wireless device described herein may be a UE 120, a passive UE, or a semi-passive UE. The wireless device described herein is a UE 120 without power supply, included in UE 120, or comprising Figure 2 One or more components of the UE 120 shown herein. In some aspects, the receiving device described herein (i.e., for receiving report data) is network node 110 or UE 120, included in or comprising network node 110 or UE 120. Figure 2One or more components of network node 110 or UE 120 are shown. 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 aspects, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (in some aspects, 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). In some aspects, the set of instructions may be made executable by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, translation, or interpretation). Figure 12 Process 1200 Figure 13 The process 1300 or other processes as described herein. In some aspects, the execution instructions may include run instructions, translation instructions, compilation instructions, and / or interpretation instructions.

[0092] In some aspects, A-IoT devices (e.g., UE 120, passive devices, semi-passive devices) include components for receiving downlink communication with uplink and downlink permission; and / or components for transmitting uplink communication at least in part based on uplink permission. In some aspects, components for an environmental IoT device to perform the operations described herein may include one or more of, for example, a communication manager 140, an antenna 252, a modem 254, a receive processor 258, a transmit processor 264, a controller / processor 280, or a memory 282.

[0093] In some aspects, the reader device (e.g., UE 120, network node 110) includes components for transmitting downlink communication with uplink and downlink permission; and / or for receiving uplink communication associated with uplink permission. 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.

[0094] Figure 4 This is a diagram illustrating aspect 400 of energy harvesting according to this disclosure.

[0095] Energy harvesting includes devices that obtain energy from sources other than the device's battery. This can include obtaining energy from sources external to the device. Devices using energy harvesting can have small energy storage devices or batteries (e.g., smartwatches, RedCap devices, eRedCap devices, IoT devices) or no energy storage devices or batteries (e.g., zero-power devices, IoT devices, wearable devices, or financial devices). Such devices can be categorized based on their energy storage capacity. Some devices may have no energy storage (storage capacity 1). Some devices can store up to E1 joules (storage capacity 2). Some devices can store up to E2 joules (storage capacity 3).

[0096] Energy harvesting can include converting RF energy transferred from another device. Harvesting RF energy may not fully charge a battery, but it can be used for tasks such as data decoding, operating filters, data reception, data encoding, and / or data transmission. Energy can accumulate over time. Energy harvesting can also be part of a self-sustaining network, where nodes in the network can interact by transmitting energy harvested within the network.

[0097] like Figure 4As shown, an RF receiver (e.g., UE 120) can receive signals (e.g., radio signals carried on radio waves) from an RF transmitter (e.g., network node 110 or UE 120) and (e.g., using a rectified antenna including a dipole antenna with an RF diode) convert the electromagnetic energy of these signals into direct current for use by the RF receiver. The RF receiver can be a low-power device or a zero-power device. The RF transmitter can be referred to as a "charging device".

[0098] As shown by reference numeral 405 in the accompanying drawings, in some aspects, the RF receiver may use a separate receiver architecture, wherein a first set of antennas is configured to harvest energy (e.g., using an energy harvester 406), and a second set of antennas is configured to receive data (e.g., using an information receiver 408). In this scenario, each set of antennas may be individually configured to receive signals at certain times, frequencies, and / or via one or more specific beams, such that all signals received by the first set of antennas are harvested to obtain energy, and all signals received by the second set of antennas are processed to receive information.

[0099] As indicated by reference numeral 410 in the accompanying drawings, in some aspects, the RF receiver may use a time-switching architecture (e.g., utilizing time switcher 412) to harvest energy. The time-switching architecture may use one or more antennas to receive signals, and whether these signals are harvested to obtain energy or processed to receive information depends on the timing of the signal reception. In some aspects, one or more first time slots may be time slots during which the received signals are transmitted to one or more energy harvesting components (such as energy harvester 406) to harvest energy, and one or more second time slots may be time slots during which the received signals are processed and decoded by one or more information receivers 408 to receive information. In some aspects, the time slots may be pre-configured (e.g., by an RF receiver, RF transmitter, or another device).

[0100] As indicated by reference numeral 415 in the accompanying drawings, in some aspects, the RF receiver may use a power-sharing architecture (e.g., utilizing power divider 416) to harvest energy. The power-sharing architecture may use one or more antennas to receive signals, and these signals are processed by one or both of the energy harvesting component and / or the information receiving component according to the energy harvesting rate. In some aspects, the RF receiver may be configured to use a first portion of the received signal for energy harvesting and the remaining received signal for information receiving. The energy harvesting mode for the device can be semi-statistically configured via RRC message passing. In some aspects, the energy harvesting rate may be pre-configured (e.g., by the RF receiver, RF transmitter, or another device). Even in energy harvesting mode, communication with network entities may be required, but with reduced radio capabilities to minimize power consumption.

[0101] An RF receiver can receive signals for energy harvesting on certain resources (e.g., time, frequency, and / or space resources) and at a power level that results in a specific charging rate. The energy harvested by the RF receiver can be used and / or stored for later use. In some respects, the RF receiver can be directly powered by the harvested energy. In other respects, the RF receiver can use energy storage devices (such as batteries, capacitors, and / or supercapacitors) to gather and store the harvested energy for immediate and / or later use.

[0102] The energy harvesting device may have a low-power or wake-up radio configured to detect low-power wake-up signals (WUS) but not perform other communications. The energy harvesting device may have a main radio configured to perform communications and consume more power than the low-power or wake-up radio. The energy harvesting device may have limited RF capabilities (less than an enhanced UE) or full RF capabilities (comparable to an enhanced UE).

[0103] More generally, energy harvesting devices may rely equally or differently on different energy harvesting technologies, such as solar, vibration, thermal, or RF energy harvesting. Because energy is intermittently available, energy harvesting can be predictable or unpredictable. Current communications use fixed active cycles for sending and receiving, such as the on-duration of an Active Discontinuous Receive (DRX) cycle. An active DRX cycle may include a portion of a DRX cycle while a DRX on-duration timer (the time the UE is monitoring PDCCH communication) or a DRX inactivity timer (the time the UE is active after successfully decoding PDCCH communication) is running. A timer can run once started and continue until it stops or expires; otherwise, it does not run. A timer can be started while it is not running, or restarted while it is running. A timer can be started or restarted from its initial value.

[0104] As indicated above, Figure 4 This is provided as one aspect. Other aspects may be discussed with regard to... Figure 4 The aspects described are different.

[0105] Figure 5 This is a diagram illustrating aspect 500 of backscatter communication according to this disclosure.

[0106] Energy harvesting (EH) devices may include A-IoT devices (e.g., RFID tags) that rely on passive communication technologies such as backscatter communication. A-IoT may also be referred to as "A-IoT," "passive UE," "environmental backscatter device," or "backscatter device." A-IoT devices may include passive, semi-passive, or active devices. For transmission, A-IoT devices may include both backscatter communication and active transmission. Backscatter communication involves using RF signals to write or transmit data in the absence of a battery or power source. However, semi-passive UEs may involve backscatter communication while using energy storage. Transmitter / reader 502 may transmit continuous wave (CW) signals (represented as...). The RF source (radio waves) of the signal can be received by multiple devices, such as reader 504. Wireless devices such as passive UE 506 (e.g., tags, A-IoT devices, passive UEs, UE 120 without a power source, backscattering devices) or semi-passive UEs (e.g., some battery power) can harvest energy (e.g., tens or hundreds of microwatts of power) from the signal. Passive UE 506 or semi-passive UE can use the passive reflection and modulation of the signal to transmit the backscattered signal using the harvested energy. That is, passive UE 506 or semi-passive UE can modulate the signal to encode data and then reflect a portion of the wave back to reader 504 or transmitter / reader 502. The backscattered signal can be encoded with information bits (e.g., identification information, sensor information) of passive UE 506 or semi-passive UE. Reader 504 can receive the backscattered signal and read the information bits. In some scenarios, the passive UE 506 or the passive UE can use information commands (e.g., write, send) or bits (e.g., data, configuration, indication) modulated in the received data or control signals to write commands or bits to the passive UE 506 itself.

[0107] In the 500 aspects, D1 For use in transmitter / reader 502, D2 For reader 504, and T Used for passive UE506 to transmit signals. h As shown by reference numeral 508 in the attached figure, the CW signal can be generated by... The figure shows a modulation method for backscattering, which includes amplitude shift keying (ASK) that enables reflection when an information bit "1" is transmitted and disables reflection when an information bit "0" is transmitted. Reference numeral 510 shows the information bits of the backscattering device, denoted as follows. If the information bits of the backscattering device are The signal received at reader 504 can be As shown by reference numeral 512 in the attached figure. When At this time, reflection is disabled at passive UE 506, so that reader 504 only receives direct link signals ( ).when At this time, reflection is enabled at the passive UE 506, causing the reader 504 to receive the superposition of the direct link signal and the backscattered signal. This superposition is represented as... ,in This represents the reflection coefficient. The modulated wave from the passive UE 506 may involve ASK, phase shift keying (PSK), or frequency shift keying (FSK).

[0108] In order to receive information bits sent by the passive UE 506, the reader 504 can first rely on known... By treating the backscattered link signal as interference, Decoding is then performed. Then, reader 504 can access the data from... Subtract To detect items The existence of.

[0109] There is a trade-off between the energy harvested at passive UE 506 and the signal-to-noise ratio (SNR) received at the reader (e.g., reader 504). The energy harvested at passive UE 506 is a function of the first channel (forward link (FL)) between transmitter / reader 502 and passive UE 506, and the SNR at reader 504 is a function of both the first channel and the second channel (backscatter link (BL)) between passive UE 506 and reader 504. Due to the difference between the first and second channels and the nonlinearity of the energy harvester, the optimal transmit waveform design for SNR differs from the optimal transmit waveform design for maximizing energy.

[0110] The topology can be single-site, where the RF source and reader are the same device. The topology can also be two-site, where the RF source and reader are different devices, as shown in aspect 500. While RFID tags can have a simple structure and an envelope detector for the carrier wave from the reader, A-IoT devices can involve topologies that include network entities (e.g., gNB, UE, and tag (UE as a repeater)) or topologies that include the UE and the tag. A-IoT tags can be more robust and can harvest and store energy.

[0111] In RFID, read commands allow transmitting devices (e.g., readers, interrogators) to read part or all of the tag's reserved memory, Electronic Product Code (EPC) memory, Tag ID (TID) memory, or user memory. Reserved memory may include a destroy password and / or access password. The EPC memory may include a memory address or code (such as EPC, and hereinafter referred to as EPC) that identifies the object belonging to the tag and whether the tag implements Extended Protocol Control (XPC). The TID memory may include identification information that allows the interrogator to uniquely identify custom commands and / or optional features supported by the tag. User memory may allow user-specific data storage.

[0112] A-IoT devices can be categorized based on their type. In some aspects, Type A A-IoT devices may lack energy storage and independent signal generation (i.e., backscatter transmission). Type A A-IoT devices may lack passive filtering capabilities, and therefore, the transmitting device may not be able to send signals to different devices simultaneously but at different frequencies. Type B A-IoT devices may have energy storage but lack independent signal generation (i.e., backscatter transmission). Type A or Type B A-IoT devices may lack the energy to maintain a clock (e.g., pre-configured timing for downlink signal monitoring may not function). Use of the stored energy may include amplification of reflected signals. Type C A-IoT devices may have energy storage and independent signal generation (i.e., active RF components for transmission). Type B or Type C A-IoT devices may have the energy to maintain a clock, but clock stability may be poor.

[0113] In some respects, A-IoT devices or A-IoT device types can be grouped. Group 1 may include a group for indoor devices, a group for outdoor devices, and a group for both indoor and outdoor devices. Other groups (Group B) may include stock devices, sensor groups, location device groups, or command device groups. Group A and Group B may be separate or together (e.g., grouped by A first, then by B).

[0114] Indoor use cases for sensors can include smart homes, smart laundry, smart agriculture, smart farms, and smart livestock sheds. Outdoor use cases for sensors can include smart grids, forest fire monitoring, dairy farming, smart manhole covers, and smart bridge health monitoring. Commands for devices can include online modification of medical device status, device activation and deactivation, elderly healthcare, permanent device deactivation, and commands for electronic shelf labels or smart agricultural controllers.

[0115] In some aspects, environmental IoT devices can be configured for approximately 1 microwatt ( μW) Peak power consumption, energy storage, up to 10 X The initial sampling frequency offset (SFO) is in parts per million (ppm), but there is neither downlink nor uplink amplification in environmental IoT devices. SFO corresponds to the mismatch between the transmitter's oscillator and the receiver's oscillator. The device's uplink transmission can be backscattered on the carrier and provided externally. In some respects, environmental IoT devices can be configured for frequencies less than or equal to several hundred ppm. μ Peak power consumption, energy storage, up to 10W X The initial SFO is ppm, and the device has downlink and / or uplink amplification. The uplink transmission of the device can be generated internally or backscattered on an externally provided carrier. The device can have a range of 10 to 50 meters indoors.

[0116] A-IoT devices can receive permissions for both uplink and downlink communication. Reader devices and / or transmitting devices (such as UEs or network entities) can send two separate scheduling messages, one for downlink permission and one for uplink permission. For A-IoT device inventory and commands, the message with uplink permission can always follow the message with downlink permission. Sending two messages for both downlink and uplink permission consumes signaling resources and causes the A-IoT device to consume power to process both messages.

[0117] As indicated above, Figure 5 This is provided as one aspect. Other aspects may be discussed with regard to... Figure 5 The aspects described are different.

[0118] Figure 6 This is a diagram illustrating Example 600 of a downlink channel structure according to the present disclosure.

[0119] Based on the various aspects described herein, A-IoT devices can receive downlink and uplink grants in the same message. By receiving downlink and uplink grants in the same message, signaling resources are saved (overhead is reduced), and the power consumption of A-IoT devices is lowered.

[0120] Example 600 illustrates the structure of downlink communication (downlink channel message). A message may include a preamble 602 (information for processing the message), a header 604, and data 606. The preamble 602 (i.e., a sequence based on on / off keying (OOK)) may include delimiters, time synchronization bits, frequency synchronization bits, and / or information bits.

[0121] In some respects, preamble 602 can indicate whether the downlink channel message includes only downlink grant, only uplink grant, or both downlink and uplink grants. A-IoT devices can perform three blind detections. Whether blind detection is needed depends on the design of preamble 602.

[0122] Header 604 can be a PDCCH-like header (carried in the control channel), a data channel, or a MAC-CE header. In any case, header 604 can be decoded separately. In some respects, a gap may exist between header 604 and data 606. An additional preamble may be added at the beginning of data 606. In some respects, there may be no gap between header 604 and data 606. If header 604 is carried in the data channel and shares a single Cyclic Redundancy Check (CRC) with data 606, no gap may be added between header 604 and data 606. The length of header 604 can vary based on whether only downlink permission is present, only uplink permission is present, or both downlink and uplink permission are present. The length can be pre-configured or specified in stored configuration information.

[0123] In some respects, header 604 can indicate resource allocation for downlink (downlink grant) and resource allocation for uplink (uplink grant). If downlink grant indicates a query with selection criteria, uplink grant can be dynamic and indicate one or more common resources (e.g., time resources, frequency resources) for multiple A-IoT devices. Each A-IoT device can select one of the one or more common resources for uplink transmission.

[0124] In some respects, the bit fields in header 604 can indicate permission for downlink only, uplink only, or both downlink and uplink. In some respects, the bit fields can include two bits to explicitly indicate downlink only, uplink only, or both. In some respects, more than two bits can be added to indicate the command type. The length of report 604 can be fixed. It can have a downlink-only length, an uplink-only length, or a length for both downlink and uplink. In each case, the length can be the same or different.

[0125] In some respects, a resource allocation field may be present in header 604 to indicate separate resource allocations for the downlink and uplink. Resource allocation (RA) field 610 indicates authorization only for the uplink, where the RA for the downlink is all zeros. RA field 612 indicates authorization only for the downlink, where the RA for the uplink is all zeros. RA field 614 indicates authorization for both the downlink and uplink.

[0126] In some respects, postamble 608 (the bit at the end of the downlink channel message) can be used to indicate the Transport Block Size (TBS). Postamble 608 may include other information to assist in the processing of data 606 and the determination of resource allocation. If header 604 is a PDCCH-like message or is carried in the data channel (and decoded separately), the TBS can be indicated in header 604, and therefore postamble 608 is not required. In some respects, TBS can indicate the amount of information bits or chips transmitted.

[0127] As pointed out 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.

[0128] Figure 7 This is a diagram illustrating Example 700 of a downlink channel structure with two headers according to this disclosure.

[0129] In some aspects, a downlink channel message may include two headers indicating downlink and uplink authorization, one for downlink and one for uplink. Example 700 illustrates the structure of a downlink channel message with two headers. The message may include a preamble 702, a first header 704, data 706, and a second header 708.

[0130] Structure 710 illustrates a second header 708 following data 706. Structure 712 illustrates another possible design where the second header 708 precedes data 706. In some aspects, the first header 704 may be carried in or located in the control channel, and the second header 708 may be located in the data channel. Data 706 and the second header 708 may be decoded separately. Data 706 and the second header 708 may have separate CRCs. Data 706 and the second header 708 may be decoded jointly. Data 706 and the second header 708 may share a single CRC.

[0131] In some respects, the first header 704 and the second header 708 can be located as two separate headers in the data channel. The first header 704, data 706, and the second header 708 can have independent CRCs. The first header 704 can have a separate CRC, while data 706 and the second header 708 can share a single CRC.

[0132] In some respects, the first header 704 and the second header 708 can be located in the control channel. This may involve a two-level solution. The first header 704 and the second header 708 can have separate CRCs.

[0133] In some respects, the first header 704 can indicate the presence of a second header. For example, a bit 714 (e.g., value 1) can be present to indicate the presence of a second header or to indicate the absence of a second header (e.g., value 0). The length of the second header 708 can be fixed. In another example, a bit field 716 can be present, including bits for indicating the TBS of the second header 708. If all bits of TBS are zero, this indicates the absence of a second header.

[0134] As pointed out 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.

[0135] Figure 8 This is a diagram illustrating Example 800 of a downlink channel structure with two headers according to this disclosure.

[0136] In some aspects, a preamble, intermolecular preamble, or delimiter (separating or marking the start of the next message) may indicate the presence of a second header. An intermolecular preamble may include bits not located at the beginning or end of the downlink channel message. An intermolecular preamble may include information used for processing the downlink channel message. In some aspects, an intermolecular preamble or delimiter may be present between the first header and the data, or between the data and the second header. Structure 810 illustrates an intermolecular preamble 802 between downlink (DL) data and the second header. The second header may indicate uplink permission for uplink (UL) data. Optionally, a post-preamble 804 may also be present. Structure 812 illustrates an intermolecular preamble 802 between the first header and the downlink data. Optionally, another intermolecular preamble 806 may be present between the downlink data and the second header. An intermolecular preamble preceding the second header may differ from an intermolecular preamble preceding the DL data. If TBS is not indicated in the first header (e.g., an intermolecular preamble or post-preamble is used to indicate TBS), the intermolecular preamble may differ from the post-preamble. If there is no intermediate preamble between the first header and the data, the intermediate preamble can be different. The intermediate preamble can be different from the post-preamble. Structure 816 shows downlink data, no second header, and post-preamble without an intermediate preamble. Structure 818 shows an intermediate preamble without a second header and located on either side of the downlink data.

[0137] In some aspects, the first header may indicate downlink permission (optional), TBS (optional, post-mapping / intermediate-mapping may be used to indicate the TBS of data), and the target device identifier (ID) for subsequent data. The first header may indicate the decoding rate and TBS of the second header (optional, post-mapping / intermediate-mapping may be used to indicate the TBS of data). The second header may be used to indicate uplink permission for uplink communication (e.g., a response) following downlink communication scheduled by the first header.

[0138] For unicast, the second header may indicate uplink permission (e.g., time resource allocation, frequency shift indication). For multicast, the second header may indicate a resource pool (e.g., one or more common resources) or resources per device. Resource indication may include resources in the time domain (baseline), frequency domain, power domain, and / or code domain.

[0139] As pointed out above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0140] Figure 9 This is a diagram illustrating example 900 of the initial positioning of uplink data according to this disclosure.

[0141] In some aspects, if the downlink channel message includes both downlink and uplink authorization, the uplink authorization may indicate the starting location of uplink data and / or the allowed transmission duration of the uplink. In some aspects, the starting location of uplink data may be associated with or at least partially based on a scheduling signal (e.g., in the second header), as shown in structure 902. In some aspects, the starting location of uplink data may be associated with or at least partially based on the reception of the entire downlink communication, as shown in structure 904.

[0142] As pointed out above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0143] Figure 10 This is a diagram illustrating Example 1000 of a backscattered square wave according to this disclosure. (See diagram for example.) Figure 10 As shown, reader device 1010 (e.g., network node 110, UE 120, transmitter / reader 502) and A-IoT device 1020 (e.g., UE 120, passive UE 506, semi-passive UE) can communicate with each other. Reader device 1010 can transmit a carrier wave backscattered by A-IoT device 1020.

[0144] As shown by reference numeral 1025 in the attached figure, reader device 1010 can transmit downlink communication including downlink grant (for DL ​​data) and uplink grant (for UL data). Reader device 1010 can transmit downlink communication on a carrier. Downlink communication may include data and one or both headers indicating both downlink grant and uplink grant, such as in combination. Figures 6 to 9 As described, by sending both downlink and uplink grants in the same message, signaling resources and power are saved.

[0145] As indicated by reference numeral 1030 in the attached figure, the A-IoT device 1020 can transmit uplink communication at least in part based on uplink permission. The A-IoT device 1020 can transmit uplink communication by backscattering a carrier and modulating the backscattered signal to include uplink communication.

[0146] As pointed out above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0147] Figure 11This is a diagram illustrating an example process 1100 performed, for example, at an ambient IoT device or a device of an ambient IoT device, according to the present disclosure. Example process 1100 is an example in which a device or ambient IoT device (e.g., passive UE 506, semi-passive UE, ambient IoT device 1020) performs operations associated with instructing uplink and downlink grants for the A-IoT device in the same message.

[0148] like Figure 11 As shown, in some aspects, process 1100 may include: receiving downlink communication with uplink grant and downlink grant (block 1110). For example, an environmental IoT device (e.g., using...) Figure 13 The described receiving component 1302 and / or communication manager 1306 can receive downlink communication with uplink permission and downlink permission, as described above.

[0149] like Figure 11 As further shown, in some aspects, process 1100 may include: sending uplink communication at least in part based on uplink permission (box 1120). For example, environmental IoT devices (e.g., using...) Figure 13 The transmitting component 1304 and / or the communication manager 1306 described herein can transmit uplink communication at least in part based on uplink permission, as described above.

[0150] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0151] In the first aspect, the downlink communication includes a header containing the uplink grant and the downlink grant, such as Figure 6 The structure is shown in Example 600.

[0152] In a second aspect, either alone or in combination with the first aspect, the downlink communication includes the gap between the header and the data of the downlink communication.

[0153] In a third aspect, either alone or in combination with one or more of the first and second aspects, the downlink communication does not include the gap between the header and the data of the downlink communication.

[0154] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the header is located in the data channel and communicates with the downlink via a data-shared CRC.

[0155] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the uplink is permitted to include one or more common resources for multiple IoT devices, and process 1100 includes selecting resources from the one or more common resources for the uplink communication.

[0156] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the downlink communication includes a post-compulsion code indicating the TBS of the data in the downlink communication, such as... Figure 6 The postcode 608 in Example 600 and Figure 8 The postcode 804 is shown in Example 800.

[0157] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the downlink communication includes a preamble indicating whether the header includes both uplink permission and downlink permission.

[0158] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the length of the header is associated with the header including both the downlink grant and the uplink grant.

[0159] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the bit fields in the downlink communication indicate the downlink permission and the uplink permission, such as Figure 6 The RA field in Example 600 and Figure 7 The example 700 shows bit field 716.

[0160] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the downlink communication includes a first header having the downlink permission and a second header having the uplink permission.

[0161] In the eleventh aspect, the first header is located in the control channel, either alone or in combination with one or more of the first to tenth aspects, and the second header is located in the data channel.

[0162] In the twelfth aspect, the first header and the second header are located in the data channel, either alone or in combination with one or more of the first to eleventh aspects.

[0163] In the thirteenth aspect, the first header and the second header are located in the control channel, either alone or in combination with one or more of the first to twelfth aspects.

[0164] In the fourteenth aspect, the first header indicates the second header, either alone or in combination with one or more of the first to thirteenth aspects.

[0165] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the downlink communication includes a preamble that indicates the second header, such as Figures 6 to 9 As shown.

[0166] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, a middle preamble preceding the first header or preceding the data in the downlink communication indicates the second header, such as... Figure 8 The example 800 shows the intro code 802.

[0167] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the first header indicates the target device ID and the decoding rate or data rate of the data, and the second header indicates that the uplink is permitted.

[0168] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the uplink is permitted to indicate the starting location, absolute frequency, and relative frequency shift of the uplink communication, and the starting location is associated with a scheduling signal (e.g., a second header) or with the reception of the downlink communication.

[0169] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted herein 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 1100 may be executed in parallel.

[0170] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, at a reader device or a device of a reader device, according to this disclosure. Example process 1200 is an example in which a device or reader device (e.g., UE, network entity, transmitter / reader 504, reader device 1010) performs operations associated with instructing downlink and uplink permission to an A-IoT device in the same message.

[0171] like Figure 12 As shown, in some aspects, process 1200 may include: sending downlink communication with uplink grant and downlink grant (block 1210). For example, a reader device (e.g., using...) Figure 14The transmitting component 1404 and / or the communication manager 1406 depicted can transmit downlink communication with uplink permission and downlink permission, as described above.

[0172] like Figure 12 Further shown, in some aspects, process 1200 may include: receiving uplink communication associated with uplink permission (block 1220). For example, a reader device (e.g., using...) Figure 14 The depicted receiving component 1402 and / or communication manager 1406 can receive uplink communication associated with uplink permission, as described above.

[0173] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0174] In the first aspect, the downlink communication includes a header containing the uplink grant and the downlink grant, such as Figure 6 The structure is shown in Example 600.

[0175] In a second aspect, either alone or in combination with the first aspect, the downlink communication includes the gap between the header and the data of the downlink communication.

[0176] In a third aspect, either alone or in combination with one or more of the first and second aspects, the downlink communication does not include the gap between the header and the data of the downlink communication.

[0177] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the header is located in the data channel and communicates with the downlink via a data-shared CRC.

[0178] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the uplink is permitted to include one or more common resources for multiple IoT devices.

[0179] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the downlink communication includes a post-compulsion code indicating the TBS of the data in the downlink communication, such as... Figure 6 The postcode 608 in Example 600 and Figure 8 The postcode 804 is shown in Example 800.

[0180] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the downlink communication includes a preamble indicating whether the header includes both uplink permission and downlink permission.

[0181] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the length of the header is associated with the header including both the downlink grant and the uplink grant.

[0182] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the bit fields in the downlink communication indicate the downlink permission and the uplink permission, such as Figure 6 The RA field in Example 600 and Figure 7 The example 700 shows bit field 716.

[0183] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the downlink communication includes a first header having the downlink permission and a second header having the uplink permission.

[0184] In the eleventh aspect, the first header is located in the control channel, either alone or in combination with one or more of the first to tenth aspects, and the second header is located in the data channel.

[0185] In the twelfth aspect, the first header and the second header are located in the data channel, either alone or in combination with one or more of the first to eleventh aspects.

[0186] In the thirteenth aspect, the first header and the second header are located in the control channel, either alone or in combination with one or more of the first to twelfth aspects.

[0187] In the fourteenth aspect, the first header indicates the second header, either alone or in combination with one or more of the first to thirteenth aspects.

[0188] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the downlink communication includes a preamble that indicates the second header, such as Figures 6 to 9 As shown.

[0189] In the sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, a middle preamble preceding the first header or preceding the data in the downlink communication indicates the second header, such as... Figure 8 The example 800 shows the intro code 802.

[0190] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the first header indicates the target device ID and the decoding rate or data rate of the data, and the second header indicates that the uplink is permitted.

[0191] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the uplink is permitted to indicate the starting location, absolute frequency, and relative frequency shift of the uplink communication, and the starting location is associated with a scheduling signal (e.g., a second header) or with the reception of the downlink communication.

[0192] although Figure 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... Figure 12 The boxes depicted in the text 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 1200 may be executed in parallel.

[0193] Figure 13 This is a diagram of an example device 1300 for wireless communication according to the present disclosure. Device 1300 may be an A-IoT device, or an A-IoT 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 140. 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.

[0194] In some respects, device 1300 can be configured to perform the functions described herein. Figures 1 to 10 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 11 Process 1100. In some respects, apparatus 1300 and / or Figure 13 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 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.

[0195] 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 (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 the one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 2 The described environment IoT device includes one or more antennas, one or more modems, one or more demodulators, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0196] 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 2 The described A-IoT 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.

[0197] 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 reception of communications by the receiving component 1302 and / or the transmission of communications by the transmitting component 1304. 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 reception and / or transmission of communications.

[0198] The receiving component 1302 can receive downlink communication with uplink and downlink permissions. The transmitting component 1304 can transmit uplink communication based at least in part on uplink permissions.

[0199] Figure 13The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. 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 executable description of the collection of (one or more) components shown is composed of Figure 13 Another set of components shown performs one or more functions.

[0200] Figure 14 This is a diagram illustrating an example device 1400 for wireless communication according to the present disclosure. Device 1400 may be a reader device, or a reader device may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and / or a communication manager 1406 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is combined with... Figure 1 The described communication manager 140 or 150. As shown, device 1400 can communicate with another device 1408 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1402 and transmitting component 1404.

[0201] In some respects, device 1400 can be configured to perform the functions described herein. Figures 1 to 10 One or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 12 Process 1200. In some aspects, apparatus 1400 and / or Figure 14 One or more components shown may include combinations Figure 2 One or more components of the described reader device. Additionally or alternatively, Figure 14 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.

[0202] Receiver 1402 may receive communications from device 1408, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1400. In some aspects, receiver 1402 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 the one or more other components of device 1400. In some aspects, receiver 1402 may include combinations of... Figure 2 The 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.

[0203] Transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1408. In some aspects, one or more other components of device 1400 may generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1408. In some aspects, transmitting component 1404 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 1408. In some aspects, transmitting component 1404 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 1404 may co-located with the receive component 1402 in one or more transceivers.

[0204] The communication manager 1406 may support the operation of the receiving component 1402 and / or the transmitting component 1404. For example, the communication manager 1406 may receive information associated with configuring the reception of communications by the receiving component 1402 and / or the transmission of communications by the transmitting component 1404. Additionally or alternatively, the communication manager 1406 may generate control information and / or provide control information to the receiving component 1402 and / or the transmitting component 1404 to control the reception and / or transmission of communications.

[0205] Transmitting component 1404 can transmit downlink communication with uplink grant and downlink grant. Receiving component 1402 can receive uplink communication associated with uplink grant.

[0206] Figure 14The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 14 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The executable description of the collection of (one or more) components shown is composed of Figure 14 Another set of components shown performs one or more functions.

[0207] The following provides an overview of some aspects of this disclosure: Aspect 1: A method of wireless communication performed by an environmental Internet of Things (IoT) device, the method comprising: receiving downlink communication having uplink permission and downlink permission; and transmitting uplink communication at least in part based on the uplink permission.

[0208] Aspect 2: According to the method of aspect 1, the downlink communication includes a header having the uplink grant and the downlink grant.

[0209] Aspect 3: According to the method of aspect 2, the downlink communication includes the gap between the header and the data of the downlink communication.

[0210] Aspect 4: According to the method of aspect 2, the downlink communication does not include the gap between the header and the data of the downlink communication.

[0211] Aspect 5: According to the method of aspect 2, wherein the header is located in the data channel and communicates with the downlink via a data-shared cyclic redundancy check.

[0212] Aspect 6: The method according to aspect 2, wherein the uplink grant includes one or more common resources for multiple IoT devices, and wherein the method includes selecting a resource from the one or more common resources for the uplink communication.

[0213] Aspect 7: According to the method of aspect 2, the downlink communication includes a postcode indicating the transport block size of data in the downlink communication.

[0214] Aspect 8: According to the method of aspect 2, the downlink communication includes a preamble indicating whether the header includes both uplink permission and downlink permission.

[0215] Aspect 9: According to the method of aspect 2, the length of the header is associated with the header including both the downlink grant and the uplink grant.

[0216] Aspect 10: According to the method of aspect 2, wherein the bit field in the downlink communication indicates the downlink grant and the uplink grant.

[0217] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the downlink communication includes a first header having the downlink permission and a second header having the uplink permission.

[0218] Aspect 12: According to the method of aspect 11, wherein the first header is located in the control channel and the second header is located in the data channel.

[0219] Aspect 13: According to the method of aspect 11, wherein the first header and the second header are located in a data channel.

[0220] Aspect 14: According to the method of aspect 11, wherein the first header and the second header are located in the control channel.

[0221] Aspect 15: The method according to aspect 11, wherein the first header indicates the second header.

[0222] Aspect 16: According to the method of aspect 11, the downlink communication includes a preamble indicating the second header.

[0223] Aspect 17: According to the method of aspect 11, the middle preamble located before the first header or before the data in the downlink communication indicates the second header.

[0224] Aspect 18: The method according to aspect 11, wherein the first header indicates a target device identifier and the decoding rate or data rate of the data, and wherein the second header indicates that the uplink is permitted.

[0225] Aspect 19: The method according to aspect 11, wherein the uplink permission indicates the starting location, absolute frequency, and relative frequency shift of the uplink communication, and wherein the starting location is associated with a scheduling signal or with the reception of the downlink communication.

[0226] Aspect 20: A method of wireless communication performed by a reader device, the method comprising: transmitting downlink communication having uplink permission and downlink permission; and receiving uplink communication associated with the uplink permission.

[0227] Aspect 21: 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 aspects of aspects 1 to 20.

[0228] Aspect 22: 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 20.

[0229] Aspect 23: 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 20.

[0230] Aspect 24: 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 accordance with one or more aspects 1 to 20.

[0231] Aspect 25: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set 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 aspects of aspects 1 to 20.

[0232] Aspect 26: 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 aspects of aspects 1 to 20.

[0233] Aspect 27: 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 aspects of aspects 1 to 20.

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

[0235] 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. In some respects, "software" should be broadly interpreted to mean 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 respect. 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 necessary for the component to actually perform that function.

[0236] 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, or not equal to the threshold.

[0237] 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. In another respect, “at least one of: 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 identical elements (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).

[0238] 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 interchangeable with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Furthermore, as used herein, the terms “have,” “possess,” “have,” and similar terms are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Additionally, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”). It should be understood that “one or more” is equivalent to “at least one”.

[0239] 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 for wireless communication at an environmental Internet of Things (IoT) device, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the environment's IoT device: Receive downlink communication with uplink and downlink permission; and Uplink communication is sent at least in part based on the aforementioned uplink permission.

2. The apparatus of claim 1, wherein the downlink communication includes a header having the uplink grant and the downlink grant.

3. The apparatus of claim 2, wherein the downlink communication includes a gap between the header and the data of the downlink communication.

4. The apparatus of claim 2, wherein the downlink communication does not include the gap between the header and the data of the downlink communication.

5. The apparatus of claim 2, wherein the header is located in the data channel and communicates with the downlink via a data-shared cyclic redundancy check.

6. The apparatus of claim 2, wherein the uplink grant includes one or more common resources for a plurality of IoT devices, and wherein the one or more processors are individually or collectively configured to enable the environmental IoT devices to select resources from the one or more common resources for the uplink communication.

7. The apparatus of claim 2, wherein the downlink communication includes a postcode indicating the transport block size of data in the downlink communication.

8. The apparatus of claim 2, wherein the downlink communication includes a preamble indicating whether the header includes both the uplink grant and the downlink grant.

9. The apparatus of claim 2, wherein the length of the header is associated with a header that includes both the downlink grant and the uplink grant.

10. The apparatus of claim 2, wherein the bit fields in the downlink communication indicate the downlink grant and the uplink grant.

11. The apparatus of claim 1, wherein the downlink communication includes a first header having the downlink permission and a second header having the uplink permission.

12. The apparatus of claim 11, wherein the first header is located in a control channel and the second header is located in a data channel.

13. The apparatus of claim 11, wherein both the first header and the second header are located in a data channel or both are located in a control channel.

14. The apparatus of claim 11, wherein the first header indicates the second header.

15. The apparatus of claim 11, wherein the downlink communication includes a preamble indicating the second header.

16. The apparatus of claim 11, wherein the middle preamble located before the first header or before data in the downlink communication indicates the second header.

17. The apparatus of claim 11, wherein the first header indicates a target device identifier and a decoding rate or data rate of the data, and wherein the second header indicates uplink permission.

18. The apparatus of claim 11, wherein the uplink permits indication of the start location, absolute frequency, and relative frequency shift of the uplink communication, and wherein the start location is associated with a scheduling signal or with the reception of the downlink communication.

19. An apparatus for wireless communication at a reader device, the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to enable the reader device to: Send downlink communication with uplink and downlink permission; as well as Receive uplink communication associated with the uplink grant.

20. A method for wireless communication performed by an environmental Internet of Things (IoT) device, the method comprising: Receive downlink communication with uplink and downlink permission; as well as Uplink communication is sent at least in part based on the aforementioned uplink permission.

Images