Techniques for zero power internet of things communications

Abstract

Certain aspects of the present disclosure provide techniques for zero power Internet of Things communications. An example method performed by a user equipment (UE) includes receiving configuration information for communication with one or more zero power Internet of Things (ZP-IoT) devices, wherein the configuration information indicates a first ZP-IoT frequency range for the ZP-IoT communication. The method may also include transmitting an uplink (UL) signal to a first ZP-IoT device in the first ZP-IoT frequency range using a first resource sharing scheme, wherein the first resource sharing scheme for transmitting the UL signal is different from a second resource sharing scheme for transmitting a downlink (DL) signal to the first ZP-IoT device.

Description

Background Art Technical Field

[0001] Aspects of the present disclosure relate to wireless communications, and more particularly to techniques for zero-power Internet of Things communications.

[0002] Related technologies

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources.

[0004] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continued desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0005] One aspect provides a method for wireless communication by a user equipment. The method includes receiving configuration information for communicating with one or more zero power Internet of Things (ZP IoT) devices, wherein the configuration information indicates a first ZP IoT frequency range for ZP IoT communication; and sending an uplink (UL) signal to the first ZP IoT device in the first ZP IoT frequency range using a first resource sharing scheme, wherein the first resource sharing scheme for sending the UL signal is different from a second resource sharing scheme for sending a downlink (DL) signal to the first ZP IoT device.

[0006] In another aspect, a method for wireless communication by a network entity is provided. The method includes sending configuration information for communicating with one or more ZP IoT devices to a user equipment, wherein the configuration information indicates a first ZP IoT frequency range for ZP IoT communication; and sending a DL signal to the first ZP IoT device in the first ZP IoT frequency range using a second resource sharing scheme, wherein the second resource sharing scheme for sending the one or more DL signals is different from the first resource sharing scheme for sending UL signals to the first ZP IoT device.

[0007] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium comprising code for performing the foregoing methods and those described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating through one or more networks.

[0008] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings depict certain features of the various aspects described herein and should not be considered to limit the scope of the disclosure.

[0010] Figure 1 An example wireless communication network is depicted.

[0011] Figure 2 An example disaggregated base station architecture is depicted.

[0012] Figure 3 Aspects of an example base station and example user equipment are depicted.

[0013] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0014] Figure 5A A radio frequency identification (RFID) system is illustrated.

[0015] Figure 5BExample topologies of circuits for RFID readers and energy harvesting circuits are illustrated.

[0016] Fig. 6A , Figure 6B and Figure 6C Different deployment scenarios of ZP-IoT communication are illustrated.

[0017] Fig. 7A and Figure 7B Different interference scenarios associated with ZP-IoT communications are illustrated.

[0018] Figure 8 A process flow for communication between a network entity, a user equipment, a first ZP-IoT device, and a second ZP-IoT device in a network is depicted.

[0019] Fig. 9 An example of a resource sharing scheme that can be used when an uplink signal is transmitted using a time division duplex scheme for ZP-IoT communication is illustrated.

[0020] Fig.10 An example of a resource sharing scheme that can be used when a downlink signal is transmitted using a time division duplex scheme for ZP-IoT communication is illustrated.

[0021] Fig.11 Examples of protection periods that may be used for ZP-IoT communications are illustrated.

[0022] Fig. 12A and Fig. 12B Examples of timing advance associated with fifth generation new radio communications and ZP-IoT communications are illustrated.

[0023] Fig.13 Examples of a first resource sharing scheme and a second resource sharing scheme that can be used when an uplink signal is transmitted using a frequency division duplex scheme for ZP-IoT communication are illustrated.

[0024] Fig.14 Multiple ZP-IoT frequency ranges that can be used for ZP-IoT communications are illustrated.

[0025] Fig.15 Reconfiguration of the ZP-IoT frequency range t for ZP-IoT communication is illustrated.

[0026] Fig.16A User equipment support for communications on different bandwidth portions is illustrated.

[0027] Fig. 16B ZP-IoT device support for communications on the ZP-IoT band is illustrated.

[0028] Fig.17Different frequency ranges within the ZP-IoT frequency band that may be supported by different ZP-IoT devices for ZP-IoT communications are illustrated.

[0029] Fig.18 Frequency hopping for ZP-IoT communication is illustrated.

[0030] Fig.19 A method for wireless communication is described.

[0031] Fig. 20 A method for wireless communication is described.

[0032] Fig.21 Aspects of an example communications device are depicted.

[0033] Fig. 22 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0034] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for zero-power Internet of Things communications.

[0035] In some cases, certain devices, referred to as zero-power passive Internet of Things (ZP-IoT) devices, may be able to collect energy from one or more wireless energy sources, such as RF signals, thermal energy, solar energy, etc. In some cases, when RF signals are used to collect energy, a first device (such as a reader device) may send an energy signal to a second device (such as a PIoT device). The second device may then collect energy from the energy signal (e.g., using an energy collection circuit) and may use this collected energy to power one or more other components of the second device. After accumulating a sufficient amount of energy, the second device may begin to modulate the energy signal with a transmit bit and send the energy signal back to the first device, which is referred to as a backscatter signal or backscatter communication.

[0036] In some cases, ZP-IoT devices may coexist in a wireless network with other more advanced types of devices that may not operate based on energy signals, such as fifth generation (5G) NR-based devices. In some cases, due to the high transmit power required to communicate with ZP-IoT devices, when these ZP-IoT devices are co-deployed with other more advanced types of devices, communications with the ZP-IoT devices may cause significant interference to these other devices within the wireless network.

[0037] In some cases, to avoid such interference, the frequency range used for ZP-IoT communications may be limited. However, limiting the frequency range used for ZP-IoT communications may not be desirable because different ZP-IoT devices may not all be configured to communicate on the same ZP-IoT frequency range. In addition, due to the simplistic nature of ZP-IoT devices, it may not be possible to reconfigure the operating bandwidth of the ZP-IoT device. Therefore, reconfiguring the frequency range used for ZP-IoT communications from a first frequency range to a second frequency range (e.g., to avoid interference with other devices in the wireless network) may be problematic because it may ultimately render certain ZP-IoT devices unable to communicate. In addition, even if a larger operating bandwidth dedicated to ZP-IoT communications is configured to support more ZP-IoT devices, there may be situations where not all of the spectrum in the operating bandwidth is used by ZP-IoT devices, resulting in a waste of time-frequency resources within the wireless network.

[0038] Thus, aspects of the present disclosure provide techniques for improving ZP-IoT communications within wireless networks. In some cases, the techniques presented herein may help reduce interference associated with the ZP-IoT communications discussed above, as well as improve spectral efficiency. For example, to help reduce interference associated with ZP-IoT communications, the techniques presented herein may include using a different resource sharing scheme when sending a downlink ZP-IoT transmission to a ZP-IoT device than when sending an uplink ZP-IoT transmission to the ZP-IoT device. In addition, in order to help improve spectral efficiency and reduce wasted time-frequency resources, the techniques presented herein relate to the configuration of different frequency bands that can be used by different ZP-IoT devices for communication. In addition, different frequency bands may be indicated to a reader device (e.g., NR-UE), thereby allowing the reader device to communicate with different ZP-IoT devices on different frequency bands and use the spectrum more efficiently, thereby reducing wasted time-frequency resources.

[0039] Introduction to wireless communication networks

[0040] The techniques and methods described herein can be used in various wireless communication networks. Although various aspects may be described herein using terms commonly associated with 3G, 4G and / or 5G wireless technologies, various aspects of the present disclosure may also be applicable to other communication systems and standards not explicitly mentioned herein.

[0041] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0042] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 102), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground BSs) and user equipment.

[0043] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0044] Figure 1 Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0045] BS 102 communicates wirelessly with (e.g., sends signals to or receives signals from) UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0046] BS 102 may generally include: NodeB, enhanced NodeB (eNB), next generation enhanced NodeB (ng-eNB), next generation NodeB (gNB or gNodeB), access point, base transceiver, radio base station, radio transceiver, transceiver function, transmission and reception point, and / or other. Each of BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and may overlap in some cases (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (relatively small geographic area (e.g., a home)), and / or other types of cells.

[0047] Although BS102 is depicted as a single communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS102) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functions similar to those of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0048] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0049] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz-7125 MHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS180) configured to communicate using mmWave / near mmWave radio bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0050] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL).

[0051] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Figure 1180) may utilize beamforming 182 with UE 104 to improve path loss and range. For example, BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, BS 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182". UE 104 may also send beamformed signals to BS 180 in one or more transmit directions 182". BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beam training to determine the best receive and transmit directions for each of BS 180 and UE 104. It is noteworthy that the transmit direction and receive direction of BS 180 may be the same or different. Similarly, the transmit direction and receive direction of UE 104 may be the same or different.

[0052] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi station (STA) 152 via communication link 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0053] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0054] The EPC 160 may include various functional components, including: a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0055] Generally, user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0056] The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0057] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0058] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0059] Internet Protocol (IP) packets are delivered through UPF 195, which is connected to IP Services 197 and provides UE IP address allocation and other functions for 5GC 190. IP Services 197 may include, for example, the Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0060] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0061] Figure 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0062] Each of the units, such as CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205, may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each unit in the unit or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0063] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 210. CU 210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.

[0064] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to functional divisions such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0065] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, a RU 240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional partitioning (such as a lower layer functional partitioning). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0066] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. In addition, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0067] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0068] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0069] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0070] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0071] Generally speaking, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0072] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0073] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols (such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS)).

[0074] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in a transceiver 332a-332t. Each modulator in the transceiver 332a-332t may process a corresponding output symbol stream to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from the modulators in the transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0075] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0076] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0077] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., for a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0078] At BS 102, uplink signals from UE 104 may be received by antennas 334 a-334 t, processed by demodulators in transceivers 332 a-332 t, detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340.

[0079] Memory 342 and memory 382 may store data and program codes for BS 102 and UE 104, respectively.

[0080] The scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0081] In various aspects, BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0082] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0083] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0084] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0085] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0086] Wireless communication systems may utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems may also support half-duplex operation using time division duplex (TDD). OFDM and single carrier frequency division multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D The modulation symbols may be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0087] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0088] exist Figure 4A and Figure 4CIn the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X is used flexibly between DL / UL. The UE can be configured with a time slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include micro-time slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0089] In certain aspects, the number of time slots within a subframe is based on the time slot configuration and the parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Thus, for time slot configuration 0 and parameter set μ, there are 14 symbols / time slot and 2μ time slots / subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing may be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0090] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted in , a resource grid can be used to represent a frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending, for example, 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0091] like Figure 4A As illustrated, some REs carry data for UEs (e.g. Figure 1 and Figure 3The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0092] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0093] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identity.

[0094] A Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0095] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0096] As in Figure 4C As illustrated, some REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE may send DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. UE 104 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0097] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0098] An Introduction to Energy Harvesting in RFID Systems

[0099] Figure 5A A radio frequency identification (RFID) system 500 is shown. As shown, the RFID system 500 includes an RFID reader 510 and an RFID tag 550. The RFID reader 510 may also be referred to as an interrogator or a scanner. The RFID tag 550 may also be referred to as an RFID tag or an electronic tag.

[0100] The RFID reader 510 includes an antenna 520 and an electronics unit 530. The antenna 520 radiates signals sent by the RFID reader 510 and receives signals from RFID tags and / or other devices. The electronics unit 530 may include a transmitter and a receiver for reading RFID tags (such as RFID tag 550). The same pair of transmitter and receiver (or another pair of transmitter and receiver) may support two-way communication with a wireless network, wireless device, etc. The electronics unit 530 may include processing circuitry (e.g., a processor) to perform processing on data sent and received by the RFID reader 510.

[0101] As shown, the RFID tag 550 includes an antenna 560 and a data storage element 570. The antenna 560 radiates the signal sent by the RFID tag 550 and receives the signal from the RFID reader 510 and / or other devices. The data storage element 570 stores the information of the RFID tag 550 in, for example, an electrically erasable programmable read-only memory (EEPROM) or another type of memory. The RFID tag 550 may also include an electronic unit that processes the received signal and generates a signal to be sent. The RFID tag 550 may be a passive RFID tag without a battery. In this case, induction may be used to power the RFID tag 550. For example, in some cases, the magnetic field from the signal sent by the RFID reader 510 may induce a current in the RFID tag 550, which may then operate based on the induced current. The RFID tag 550 may radiate its signal in response to receiving a signal from the RFID reader 510 or some other device.

[0102] In one example, the RFID tag 550 may be read by placing the RFID reader 510 near the RFID tag 550. The RFID reader 510 may radiate a first signal 525 via the antenna 520. In some cases, the first signal 525 may be referred to as an interrogation signal or an energy signal. In some cases, the energy of the first signal 525 may be coupled from the RFID reader antenna 520 to the RFID tag antenna 560 via magnetic coupling and / or other phenomena. In other words, the RFID tag 550 may receive the first signal 525 from the RFID reader 510 via the antenna 560, and the energy of the first signal 525 may be collected using the energy harvesting circuit 555 and used to power the RFID tag 550.

[0103] For example, the energy of the first signal 525 received by the RFID tag 550 can be used to power the microprocessor 545 of the RFID tag 550. The microprocessor 545 can, in turn, retrieve the information stored in the data storage element 570 of the RFID tag 550 and transmit the retrieved information via the second signal 535 using the antenna 560. For example, in some cases, the microprocessor 545 can generate the second signal 535 by modulating a baseband signal (e.g., a baseband signal generated using the energy of the first signal 525) with the information retrieved from the data storage element 570. In some cases, this second signal 535 can be referred to as a backscatter modulated information signal. Thereafter, as noted, the microprocessor 545 transmits the second signal 535 to the RFID reader 510. The RFID reader 510 can receive the second signal 535 from the RFID tag 550 via the antenna 520, and can process (e.g., demodulate) the received signal to obtain the information of the data storage element 570 transmitted in the second signal 535.

[0104] In some cases, the RFID system 500 may be designed to operate at 13.56 MHz or some other frequency (e.g., the 900 MHz ultra-high frequency (UHF) band). The RFID reader 510 may have a specified maximum transmit power level, which may be regulated by the Federal Communications Commission (FCC) in the United States or other regulatory agencies in other countries. The specified maximum transmit power level of the RFID reader 510 may limit the distance at which the RFID tag 550 can be read by the RFID reader 510.

[0105] Figure 5B An example equivalent circuit 553 and an example topology of an antenna 560 of an energy harvesting circuit 555 of an RFID tag 550 are illustrated. In some cases, as illustrated by the equivalent circuit 553 of the antenna 560, a lossless antenna can be modeled as an alternating current (AC) voltage source (v s (t)), followed by the series antenna resistance (Rant ). In some cases, the voltage source (v s (t)) may be based on the energy signal y received from the RFID reader 510 rf (t). The equivalent circuit 553 of the antenna 560 also includes an input resistor (R in ), which represents the resistance associated with the energy harvesting circuit 555. In some cases, with perfect impedance matching, R in Can be equal to R ant .

[0106] As shown, the energy harvesting circuit 555 includes a half-wave rectifier circuit configured to convert AC input power (v) (eg, received via antenna 560) into a in ) is converted to DC output power (v out In addition, as shown in the figure, the energy harvesting circuit 555 includes a diode, a capacitor (C) and a load impedance (R L ). The diode is configured to pass only half of each complete sine wave of the AC voltage in order to convert it to a DC voltage. Figure 5B As shown in the energy harvesting circuit 555 in FIG. d is the diode current and v d is the voltage across the diode. In some cases, with perfect matching, v in (t) can be v s (t) and both can be compared with the signal energy signal (y) received at the energy harvesting circuit 555 rf (t)) related, such as and

[0107] Aspects related to technologies used for zero-power IoT communications

[0108] Wireless technology is increasingly useful in industrial applications such as ultra-reliable low-latency communications (URLLC) and machine-type communications (MTC). In such and other fields, it is desirable to support devices that can collect energy from alternative energy sources (e.g., instead of batteries or other energy storage devices (such as capacitors) or in combination with batteries or other energy storage devices). For example, in some cases, these devices may not include local power storage components and may alternatively collect energy from objects (such as RF signals, thermal energy, solar energy). In some cases, these devices may be referred to as passive IoT (PIoT) devices or more generally as zero-power Internet of Things (ZP-IoT) devices. ZP-IoT devices may use RFID type technology and therefore may not include a local power supply. Instead, ZP-IoT devices may collect energy from radio signals (these radio signals are emitted from reader devices such as network entities or user equipment (UE)) for performing data collection, transmission, and distributed computing.

[0109] Wireless standards bodies have developed specifications for supporting narrowband IoT (NB-IoT) / MTC devices and devices with reduced capabilities (RedCap) for MTC use cases. RedCap type devices may be associated with reduced operating bandwidth, reduced maximum number of MIMO layers, and relaxation of maximum downlink modulation order. However, although current wireless technologies (such as fifth generation (5G) new radio (NR)) are capable of supporting NB-IoT and RedCap devices, the technology may not currently be able to efficiently support the most common RFID type sensors (e.g., ZP-IoT devices) in many future use cases (such as asset management, logistics, warehousing, and manufacturing). For example, using current 5G NR technology to support ZP-IoT devices will require these ZP-IoT devices to have more complex circuits, thereby requiring additional costs and maintenance associated with battery replacement, which may not be feasible in these future use cases. Therefore, additional wireless communication technologies may be required to support and manage communications with ZP-IoT type devices.

[0110] As described above, the ZP-IoT device may be capable of harvesting energy from one or more wireless energy sources such as RF signals, thermal energy, solar energy, etc. In some cases, when RF signals are used to harvest energy, a first device such as a reader device (e.g., BS 102, as described above) may be capable of harvesting energy from one or more wireless energy sources such as RF signals, thermal energy, solar energy, etc. Figure 2 The decomposed BS described herein, UE 104, or any other device described herein capable of transmitting wireless signals) may transmit an energy signal to a second device such as a ZP-IoT device (e.g., UE 104, RFID tag 550, etc.). The second device may then harvest energy from the energy signal (e.g., using an energy harvesting circuit such as Figure 5A and Figure 5BThe energy collection circuit 555 illustrated is provided and this collected energy may be used to power one or more other components of the second device. In some cases, a portion of the collected energy may be used to charge a local energy storage device of the second device for later use (i.e., the collected energy may be stored in a local power storage component). After accumulating a sufficient amount of energy, the second device may begin to reflect energy signals radiated onto the second device, which is referred to as backscatter signals or backscatter communications. When reflecting the energy signal, the second device may modulate a specific switching pattern corresponding to a set of transmitted bits onto the energy signal. The first device (e.g., a reader device) detects and demodulates the reflected pattern to obtain the set of transmitted bits.

[0111] In some cases, ZP-IoT devices may coexist in a wireless network with other types of devices that may not operate based on energy signals, such as 5G NR-based devices. Thus, different types of deployment scenarios may be used to support ZP-IoT communications and 5G NR communications, such as Fig. 6A , Figure 6B and Figure 6C exemplified. For example, Fig. 6A A first deployment type 602 for communicating with a ZP-IoT device is illustrated. As shown, the first deployment type 602 includes an out-of-band or standalone deployment, in which frequency resources for PIoT communication and frequency resources for 5G NR communication are separated into different frequency bands or bandwidth parts (BWPs). Fig. 6A As shown, a first deployment type 602 (e.g., an out-of-band deployment) includes a first frequency band 604 for 5G NR communications and a separate second frequency band 606 with a dedicated carrier for PIoT communications.

[0112] Figure 6B A second deployment type 608 for communicating with a ZP-IoT device is illustrated. As shown, the second deployment type 608 includes an in-band deployment, where the frequency resources used for PIoT communication are defined within the frequency band used for 5G NR communication. Figure 6B As shown, a frequency resource set 610 for PIoT communication is defined within a frequency band 612 for 5G NR communication. In other words, a portion of the frequency resources allocated for 5G NR communication can be reused for PIoT communication.

[0113] Figure 6C A third deployment type 614 for communicating with a ZP-IoT device is illustrated. As shown, the third deployment type 614 includes a guard band deployment, where the frequency resources for PIoT communication and the frequency resources for 5G NR communication are defined within the same frequency band or BWP, but are separated by a guard band. Figure 6CAs shown, a first set of frequency resources 616 and a second set of frequency resources 618 for PIoT communication are defined within a frequency band 620 and separated by a guard band 622.

[0114] In some cases, when a ZP-IoT device is co-deployed with a NR-UE in a wireless communication network, the NR-UE may experience significant interference due to ZP-IoT communications, at least in the downlink (DL) direction. Fig. 7A and Figure 7B Two interference scenarios associated with ZP-IoT communications are illustrated. For example, Fig. 7A The first interference scenario that may occur in the downlink (DL) when the network entity acts as a reader device for communicating with a ZP-IoT device is illustrated. For example, as shown in the figure, Fig. 7A The network entity 702 (eg, BS 102, Figure 2 1 , a decomposed BS as described above), a NR-UE 704, and a ZP-IoT device 706. The network entity 702 transmits downlink (DL) signals 708 and 710 to the NR-UE 704 and the ZP-IoT device 706, respectively. In some cases, due to the high transmission power associated with the DL signal 710 transmitted to the ZP-IoT device 706, the DL signal 710 may interfere with the DL signal 708 transmitted to the NR-UE 704, thereby preventing the NR-UE 704 from correctly receiving the DL signal 708.

[0115] Figure 7B A second interference scenario that may occur in the uplink (UL) when the NR-UE acts as a reader device for communicating with a ZP-IoT device is illustrated. For example, as shown in the figure, Figure 7B Again, a network entity 702, a NR-UE 704 and a ZP-IoT device 706 are included. In addition, as shown in the figure, Figure 7BAlso included is another NR-UE 714 that is capable of communicating with the ZP-IoT device 706 using ZP-IoT communications. For example, as shown, the NR-UE 714 sends an uplink (UL) signal 716 to the ZP-IoT device 706. The ZP-IoT device 706 may collect energy from these UL signals and may send a backscatter signal 718 to the network entity 702. However, in some cases, the UL signal 720 sent by the NR-UE 704 may cause interference 722 to the backscatter signal 718. In some cases, due to the relatively low transmit power associated with the UL signal 720 sent by the NR-UE 704, the interference 722 caused by the UL signal 720 sent by the NR-UE 704 may not be as significant as the interference 712 caused by the DL signal 710 sent to the ZP-IoT device 706. In addition, the network entity 702 may have strong processing capabilities to eliminate any interference associated with the backscatter signal 718.

[0116] In some cases, the frequency range used for ZP-IoT communication can be tens of megahertz (MHz) and sometimes even greater than 100 MHz. In some cases, for certain ZP-IoT devices (e.g., operating at a BW of 110 MHz), if a center frequency between, for example, 902 MHz-928 MHz is used for ZP-IoT communication in a wireless network, the ZP-IoT communication may be strongly interfered by other signals (such as 5G NR signals) within the remaining bandwidth of the wireless network. For example, a ZP-IoT device may require a received power of up to -10 dBm in order to receive an energy signal. However, due to the relatively simple nature of ZP-IoT devices, these ZP-IoT devices may not have interference cancellation capabilities for removing strong interference from other signals within the wireless network.

[0117] In some cases, to avoid such interference, a portion of the bandwidth of the wireless network may be dedicated only to a frequency range of ZP-IoT, such as tens of megahertz (e.g., 40 MHz). However, dedicating a portion of the bandwidth in the wireless network to ZP-IoT communications may result in a waste of time-frequency resources in the wireless network, because there may be instances in which not all of the spectrum within the dedicated portion is used by ZP-IoT devices. In this case, it may be more reasonable for ZP-IoT devices and ZP-IoT communications to coexist with 5G NR devices and communications. For example, a bandwidth of 100 MHz within a wireless network may be allocated to 5G NR communications, and a bandwidth of 40 MHz may be allocated to ZP-IoT communications. In some cases, when 5G communications and ZP-IoT communications coexist within a bandwidth (e.g., 100 MHz), there may be instances in which the frequency range used for ZP-IoT communications may need to be adjusted to avoid interference with 5G NR communications. However, due to the simplified nature of ZP-IoT devices, the frequency range used for ZP-IoT communication may not be reconfigured (for example, the center frequency of the ZP-IoT receiving bandwidth may not be reconfigured), resulting in scheduling difficulties between 5G communication and ZP-IoT communication as well as interference, time-frequency resources and waste of power resources.

[0118] Thus, aspects of the present disclosure provide techniques for improving ZP-IoT communications within a wireless network. In some cases, the techniques presented herein may help reduce interference associated with the ZP-IoT communications discussed above, as well as improve spectral efficiency. For example, to help reduce interference associated with ZP-IoT communications, the techniques presented herein may include using a different resource sharing scheme when sending DL ZP-IoT transmissions to a ZP-IoT device than when sending UL ZP-IoT transmissions to the ZP-IoT device. In addition, to help improve spectral efficiency and reduce wasted time-frequency resources, the techniques presented herein relate to the configuration of different frequency bands that can be used by different ZP-IoT devices for communication. In addition, different frequency bands can be indicated to a reader device (e.g., NR-UE), thereby allowing the reader device to communicate with different ZP-IoT devices on different frequency bands and use the spectrum more efficiently, thereby reducing wasted time-frequency resources. In some cases, these techniques may be applied to Fig. 6A , Figure 6B and Figure 6C All different deployment scenarios illustrated.

[0119] Example Operations of Entities in a Communication Network

[0120] Figure 87 . Figure 5A The RFID tag 550 shown in the example or Figure 1 and Figure 3 An example of a UE 104 is depicted and described. In some aspects, the network entity 802 may be an example of a reader device capable of ZP-IoT communications (e.g., sending energy signals and receiving backscattered signals), such as with respect to Figure 1 and Figure 3 BS102 as depicted and described or with respect to Figure 2 Similarly, UE 804 may be an example of a reader device capable of ZP-IoT communications (e.g., sending energy signals and receiving backscattered signals), such as with respect to Figure 1 and Figure 3 The depicted and described UE 104. However, in other aspects, UE 104 may be another type of wireless communication device and BS 102 may be another type of network entity or network node, such as those described herein.

[0121] As shown, operations 800 begin at step 810, where a network entity 802 sends configuration information to a UE 804 for communicating with one or more ZP-IoT devices, such as a first ZP-IoT device 806. In some cases, the configuration information may indicate a first ZP-IoT frequency range for ZP-IoT communications.

[0122] In step 820, the UE 804 transmits an UL signal in the first ZP-IoT frequency range to at least the first ZP-IoT device 806 using a first resource sharing scheme. In some cases, to improve spectrum efficiency, the first ZP-IoT frequency range may be shared with other 5G NR communications (e.g., orthogonal frequency division multiplexing (OFDM) communications). To facilitate such sharing and to avoid or reduce interference associated with ZP-IoT communications and other 5G NR communications, the first resource sharing scheme may be used to transmit the UL signal. In some cases, this first resource sharing scheme may be different from a second resource sharing scheme used to transmit a DL signal to the first ZP-IoT device 806 or to other devices (e.g., UEs) in the network.

[0123] For example, as shown in step 830, the network entity 802 may use a second resource sharing scheme to send a DL signal to the first ZP-IoT device 806 (or other ZP-IoT devices within the network, such as the second ZP-IoT device 808).

[0124] In some cases, the UE 804 may use a specific duplexing scheme to send a UL signal to the first ZP-IoT device 806. In addition, in some cases, the network entity 802 may also use the specific duplexing scheme to send a DP signal to the first ZP-IoT device 806. For example, in some cases, the duplexing scheme may include a time division duplexing (TDD) scheme, in which the UL signal and the DL signal are separated into different timings, such as a UL timing for the UL signal and a DL timing for the DL signal.

[0125] Therefore, when Figure 8 In step 820, when a UL signal is transmitted using a TDD scheme, a first resource sharing scheme that may be used in a UL opportunity may include a UL time division multiplexing (TDM) scheme and a UL frequency division multiplexing (FDM) scheme. Fig. 9 Included is an example of a TDM+FDM resource sharing scheme that can be used when a UL signal is transmitted using a TDD scheme.

[0126] Fig. 9 A time-frequency grid 900 for a TDD scheme is included, which illustrates resource allocation for UL ZP-IoT communication and UL OFDM communication. As shown, resources for UL ZP-IoT communication and UL OFDM communication can be allocated within a ZP-IoT frequency band 902 and multiple UL opportunities (such as UL time slot 904, UL time slot 906, and UL time slot 908). Although in Fig. 9 The multiple UL opportunities are illustrated as time slots, but it should be understood that the multiple opportunities can be any type of opportunities, including symbols, frames, etc.

[0127] In addition, as described above, when sending a UL signal to the first ZP-IoT device 806, the UE 804 may use a first resource sharing scheme including a UL TDM scheme and a UL FDM scheme. Fig. 9As shown, when a UL signal is sent within the UL time slot 904, a UL FDM scheme may be used, thereby allowing the UL signal (e.g., ZP-IoT signal) sent to the first ZP-IoT device 806 to share the ZP-IoT frequency band with the UL OFDM signal. For example, as shown, the UL signal sent to the first ZP-IoT device 806 may be FDM multiplexed and transmitted in the first ZP-IoT frequency range 910 of the ZP-IoT frequency band 902 in the UL time slot 904, while the UL OFDM signal (e.g., sent by other UEs to the network entity 802) may be FDM multiplexed and transmitted in the frequency range 912 used for OFDM communication in the ZP-IoT frequency band 902 in the UL time slot 904.

[0128] Instead, a TDM scheme may be used to transmit the UL transmissions in the UL time slot 906 and the UL time slot 908. For example, as shown, in order to share the ZP-IoT frequency band 902 with the UL OFDM signal, the UL signal transmitted to the first ZP-IoT device 806 may be TDM multiplexed and transmitted within the ZP-IoT frequency band 902 of the UL time slot 908, and the ULOFDM signal (e.g., transmitted by other UEs to the network entity 802) may be TDM multiplexed and transmitted within the ZP-IoT frequency band 902 of the UL time slot 906.

[0129] As mentioned above, in Figure 8 In step 830, the network entity 802 may use a second resource sharing scheme to send a DL signal to the first ZP-IoT device 806. Fig.10 An example of the second resource sharing scheme is illustrated in FIG. Fig.10 A time-frequency grid 1000 for a TDD scheme is included, which illustrates resource allocation for UL ZP-IoT communication and UL OFDM communication. As shown, resources for UL ZP-IoT communication and UL OFDM communication can be allocated within a ZP-IoT frequency band 1002 and multiple DL opportunities (such as DL time slot 1004, DL time slot 1006, DL time slot 1008, and DL time slot 1010). Although in Fig.10 The multiple DL opportunities are illustrated as time slots, but it should be understood that the multiple DL opportunities can be any type of opportunities, including symbols, frames, etc.

[0130] When Figure 8 In step 830, when a DL signal is transmitted using a TDD scheme, a second resource sharing scheme that can be used in a DL opportunity may include a DL TDM scheme. In some cases, the second resource sharing scheme may not include a DL FDM scheme. Fig.10As shown, when a DL signal is sent using a DL TDM scheme, the DL signal sent to the first ZP-IoT device 806 may be time multiplexed with other DL OFDM signals within DL time slots 1004, DL time slots 1006, DL time slots 1008, and DL time slots 1010. For example, as shown, the DL signal sent to the first ZP-IoT device 806 may be sent in DL time slots 1004 and DL time slots 1008, while other DL OFDM signals may be sent in DL time slots 1006 and DL time slots 1010. Therefore, by time multiplexing the DL signal sent to the first ZP-IoT device 806 and other DL OFDM signals (e.g., sent to other UEs in the network), the DL signal sent to the first ZP-IoT device 806 and other DL OFDM signals may share the ZP-IoT frequency band 1002 without interfering with each other.

[0131] In some cases, when TDD is used, a guard period may be configured between a DL opportunity (e.g., used by the network entity 802 to send a DL signal to the first ZP-IoT device 806) and a UL opportunity (e.g., used by the UE 804 to send a UL signal to the first ZP-IoT device 806). Figure 8 The configuration information sent by the network entity 802 to the UE 804 in step 810 may include an indication of a guard period configured between the UL signal to the first ZP-IoT device 806 in the UL opportunities (e.g., UL time slot 904, UL time slot 906, and UL time slot 908) and the DL signal to the first ZP-IoT device 806 in the DL opportunities (DL time slot 1004, DL time slot 1006, DL time slot 1008, and DL time slot 1010). Fig.11 An example of this protection period is illustrated in .

[0132] For example, Fig.11 A resource allocation 1100 including a plurality of DL opportunities (DL time slot 1004, DL time slot 1006, DL time slot 1008, and DL time slot 1010) and a plurality of UL opportunities (e.g., UL time slot 904, UL time slot 906, and UL time slot 908) is illustrated. The plurality of DL opportunities and the plurality of UL opportunities may be used for ZP-IoT communications, such as for sending DL signals and UL signals to the first ZP-IoT device 806. Although the plurality of DL opportunities and the plurality of UL opportunities are described as time slots, it should be understood that the plurality of opportunities may be any type of opportunity, including symbols, frames, etc.

[0133] In addition, as shown, resource allocation 1100 includes a guard period 1102 located between the plurality of DL opportunities and the plurality of UL opportunities. Guard period 1102 may include one or more guard symbols (e.g., 1-14 symbols) or time slots to allow switching between transmission of DL signals and transmission of UL signals. Fig.11 In the example shown, the guard period 1102 consists of a number of flexible symbols that can be configured for UL transmission, DL transmission, or unavailable for transmission. In some cases, for ZP-IoT communications, the minimum time of the guard period can be approximately 0.581 milliseconds.

[0134] In some cases, when TDD is used to transmit signals within the network, the UL timing advance and offset (e.g., N TA +N TA_offset ) can be used by UE 804 to ensure that UL NR OFDM transmissions (e.g., performed by UE 804 and other UEs in the network) are aligned with the reception timing at the network entity 802. Fig. 12A An example timing advance that may be used for UL OFDM transmissions is illustrated. For example, as shown, a DL OFDM transmission 1202 may be sent in time slot n. Thereafter, the UE 804 may be scheduled to send the UL OFDM transmission 1204 in time slot n+1. However, in some cases, the UE 804 may receive a timing advance command from the network entity 802, including the timing advance 1206 (and in some cases, the time offset). The timing advance may be used by the UE 804 to advance the UL OFDM transmission 1204 in time, as shown at 1208.

[0135] However, in some cases, when sending a UL signal to the first ZP-IoT device 806, the use of UL timing advance may be optional (e.g., because the UL signal does not need to be aligned when it arrives at the first ZP-IoT device 806). Fig. 12B As shown, a DL OFDM transmission 1202 may be sent in time slot n. Thereafter, the UE 804 may be scheduled to send a UL ZP-IoT transmission 1210 (e.g., a UL transmission to the first ZP-IoT device 806) in time slot n+1. Fig. 12B In the example shown, the UE 804 may be configured to send the UL ZP-IoT transmission 1210 without using the UL timing advance. In other cases, the UE 804 may be configured to send the UL ZP-IoT transmission 1210 using a first UL timing advance different from a second UL timing advance (e.g., 1206) used for the UL OFDM transmission 1204.

[0136] As described above, the network entity 802 and the UE 804 may use a specific duplexing scheme to send a DL signal and a UL signal to the first ZP-IoT device 806, respectively. In some cases, the duplexing scheme includes a frequency division duplexing (FDD) scheme, in which the UL signal and the DL signal are separated into different frequency bands within a time slot. In some cases, the different frequency ranges include a UL frequency band for UL signals and a DL frequency band for DL ​​signals. In some cases, the first ZP-IoT frequency range in which the UL signal is sent by the UE 804 may be included in the UL frequency band.

[0137] In some cases, when Figure 8 In step 820, when the UL signal is transmitted in the UL frequency band using the FDD scheme, the first resource sharing scheme that can be used in the first UL frequency range to transmit the UL signal may include a UL TDM scheme and a UL FDM scheme. Figure 8 In step 830, when the DL signal is transmitted in the UL frequency band using the FDD scheme, the second resource sharing scheme may include a DL TDM scheme. In some cases, the second resource sharing scheme may not include a DL FDM scheme.

[0138] Fig.13 Examples of TDM+FDM resource sharing schemes for transmitting UL signals and TDM resource sharing schemes for transmitting DL signals are included. For example, as shown in the figure, Fig.13 A time-frequency grid 1300 is included, which includes a UL frequency band 1302 for UL transmission, a DL frequency band 1304 for DL ​​transmission, and a plurality of opportunities for transmitting DL transmission and UL transmission. As shown, the plurality of opportunities include a first time slot 1306, a second time slot 1308, a third time slot 1310, and a fourth time slot 1312. Although the plurality of opportunities are described as time slots, it should be understood that the plurality of opportunities can be any type of opportunity, including symbols, frames, etc.

[0139] As described above, when sending a UL signal to the first ZP-IoT device 806, the UE 804 may use a first resource sharing scheme including a UL TDM scheme and a UL FDM scheme. Fig.13As shown, when a UL signal is transmitted in the first time slot 1306 of the UL band 1302, a UL FDM scheme may be used, thereby allowing a UL signal (e.g., a ZP-IoT signal) transmitted by the UE 804 to the first ZP-IoT device 806 to share the UL band with a UL OFDM signal. For example, as shown, a UL signal transmitted by the UE 804 to the first ZP-IoT device 806 may be FDM multiplexed and transmitted in the first ZP-IoT frequency range 1314 of the UL band 1302 in the first time slot 1306, while a UL OFDM signal (e.g., transmitted by other UEs to the network entity 802) may be FDM multiplexed and transmitted in the frequency range 1316 used for OFDM communication in the ZP-IoT band 902 in the first time slot 1306.

[0140] Instead, the UL transmissions in the second time slot 1308, the third time slot 1310, and the fourth time slot 1312 of the UL frequency band 1302 may be transmitted using a TDM scheme. For example, as shown, in order to share the UL frequency band 1302 with the UL OFDM signal, the UL signal transmitted by the UE 804 to the first ZP-IoT device 806 may be TDM multiplexed and transmitted within the UL frequency band 1302 in the third time slot 1310, while the UL OFDM signal (e.g., transmitted by other UEs to the network entity 802) may be TDM multiplexed and transmitted within the UL frequency band 1302 in the second time slot 1308 and the fourth time slot 1312.

[0141] In addition, as mentioned above, Figure 8 In step 830, the network entity 802 may use a second resource sharing scheme (e.g., a DL TDM resource sharing scheme) to send a DL signal to the first ZP-IoT device 806. For example, when the DL signal is sent using the DL TDM scheme, the DL signal sent to the first ZP-IoT device 806 may be time multiplexed with other DL OFDM signals within the DL frequency band 1304 of the first time slot 1306, the second time slot 1308, the third time slot 1310, and the fourth time slot 1312. For example, as shown, the DL signal sent to the first ZP-IoT device 806 may be sent in the DL frequency band 1304 of the first time slot 1306 and the third time slot 1310, while other DL OFDM signals may be sent in the DL frequency band 1304 of the second time slot 1308 and the fourth time slot 1312. Therefore, by time multiplexing the DL signal sent to the first ZP-IoT device 806 and other DL OFDM signals (e.g., sent to other UEs in the network), the DL signal sent to the first ZP-IoT device 806 and the other DL OFDM signals can share the ZP-IoT frequency band 1002 without interfering with each other.

[0142] In some cases, the network entity 802 and the UE 804 may be configured to send DL signals and UL signals to one or more second ZP-IoT devices (such as the second ZP-IoT device 808), respectively. Figure 8 840 and 850 in . In some cases, because it is difficult to reconfigure the ZP-IoT frequency range used for ZP-IoT communication (e.g., because different ZP-IoT devices may support different frequency ranges for ZP-IoT communication), it may be advantageous to define multiple frequency ranges specifically for ZP-IoT communication so that different ZP-IoT devices can use different frequency ranges to communicate. In some cases, a reader device (e.g., network entity 802 or UE 804) performing ZP-IoT communication may be configured to use a frequency range or may select a frequency range from the multiple ZP-IoT frequency ranges to perform ZP-IoT communication.

[0143] For example, as described above, the network entity 802 and the UE 804 may be configured to send DL signals and UL signals to the first ZP-IoT device 806 in the first ZP-IoT frequency range. In addition, one or more additional ZP-IoT frequency ranges may be configured for and supported by the one or more second ZP-IoT devices (e.g., the second ZP-IoT device 808) for ZP-IoT communications that are different from the first ZP-IoT frequency range supported by the first ZP-IoT device 806. In such cases, the configuration information sent by the network entity 802 to the UE 804 in step 810 may indicate the one or more additional ZP-IoT frequency ranges. In some cases, Fig.14 Examples of these additional ZP-IoT frequency ranges are provided.

[0144] Fig.14 A time-frequency resource grid 1400 including multiple ZP-IoT frequency ranges that can be used for ZP-IoT communications is illustrated. For example, as shown, the time-frequency resource grid 1400 includes a first ZP-IoT frequency range 1402, a second ZP-IoT frequency range 1404, and a third ZP-IoT frequency range 1406. As shown, the first ZP-IoT frequency range 1402, the second ZP-IoT frequency range 1404, and the third ZP-IoT frequency range 1406 can be defined within a ZP-IoT frequency band 1401. In some cases, the ZP-IoT frequency band 1401 can have a bandwidth of 4 gigahertz (GHz). Additionally, in some cases, the first ZP-IoT frequency range 1402 can have a bandwidth of 10 megahertz (MHz), the second ZP-IoT frequency range 1404 can have a bandwidth of 20 MHz, and the third ZP-IoT frequency range 1406 can have a bandwidth of 30 MHz.

[0145] In some cases, for example, the network entity 802 and the UE 804 may use the first ZP-IoT frequency range 1402 to send DL signals and UL signals, respectively, to the first ZP-IoT device 806. Additionally, in some cases, the network entity 802 and the UE 804 may use the second ZP-IoT frequency range 1404 to send DL signals and UL signals, respectively, to the second ZP-IoT device 808. In some cases, the third ZP-IoT frequency range 1406 may be used to send DL signals or UL signals to another ZP-IoT device (or the first ZP-IoT device 806 or the second ZP-IoT device 808, if supported).

[0146] In some cases, reconfiguration of the multiple ZP-IoT frequency ranges is possible, but may be subject to certain timing constraints. In addition, although ZP-IoT communication is possible over multiple ZP-IoT frequency ranges, the multiple ZP-IoT frequency ranges used for ZP-IoT communication may need to be selected or configured from a set of candidate frequency ranges.

[0147] For example, Fig.15 As illustrated, the network entity 802 and / or the UE 804 may use a ZP-IoT frequency range, such as the first ZP-IoT frequency range 1502, to transmit DL signals and UL signals, respectively, for a first time period 1504. Thereafter, the ZP-IoT frequency range may be reconfigured to a second ZP-IoT frequency range 1506. In such a case, the network entity 802 and / or the UE 804 may then use the second ZP-IoT frequency range 1506 to transmit DL signals and UL signals, respectively, for a second time period 1508. Furthermore, as illustrated, the ZP-IoT frequency range may again be reconfigured to a third ZP-IoT frequency range 1510. In such a case, the network entity 802 and / or the UE 804 may then use the third ZP-IoT frequency range 1510 to transmit DL signals and UL signals, respectively, for a third time period 1512. In some cases, the first time period 1504, the second time period 1508, and the third time period 1512 may be defined as multiple time units, such as hours, days, etc.

[0148] In some cases, different UEs (e.g., UE 104, UE 804, etc.) in a 5G NR system may have the capability to receive at different frequency ranges within the 5G NR frequency band. Fig.16AAs illustrated, the first UE may support reception on a first bandwidth part (BWP) 1602 in the 5G NR band 1604, while the second UE may support reception on a second BWP 1606 in the 5G NR band 1604. In some cases, the first UE and the second UE may also have the capability to periodically change their reception capabilities. For example, in some cases, the first UE may have the capability to switch from receiving on the first BWP 1602 to receiving on the second BWP 1606. Similarly, the second UE may have the capability to switch from receiving on the second BWP 1606 to receiving on the first BWP 1602.

[0149] In some cases, these techniques can also be used for ZP-IoT communications. However, when applied to ZP-IoT communications, additional conditions may need to be met. For example, for a particular frequency band, a ZP-IoT device intended to communicate in that frequency band may need to have good reception capabilities throughout the frequency band. For example, Fig. 16B As shown, the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1608 may support communication within the ZP-IoT frequency band 1610. In addition, in some cases, the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1608 may support ZP-IoT communication on different frequency ranges within the ZP-IoT frequency band 1610. However, in such cases, the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1608 may still need to have good reception capabilities throughout the ZP-IoT frequency band 1610, as illustrated in FIG.

[0150] Fig.17 An illustration of different frequency ranges within a ZP-IoT band that may be supported by different ZP-IoT devices for ZP-IoT communications is provided. For example, as shown, a first ZP-IoT device 806, a second ZP-IoT device 808, and a third ZP-IoT device 1702 may support ZP-IoT communications over different frequency ranges within a ZP-IoT band 1704. For example, a first ZP-IoT device 806 may support ZP-IoT communications in a first ZP-IoT frequency range 1706 within the ZP-IoT band 1704. A second ZP-IoT device 808 may support ZP-IoT communications in a second ZP-IoT frequency range 1708 within the ZP-IoT band 1704. A third ZP-IoT device 1702 may support ZP-IoT communications in a third ZP-IoT frequency range 1710 within the ZP-IoT band 1704.

[0151] In some cases, when a specific frequency band is configured for ZP-IoT communication and different ZP-IoT devices support ZP-IoT communication in different frequency ranges within the specific frequency band configured for ZP-IoT communication, the different frequency ranges supported by the different ZP-IoT devices may be indicated to the reader device so that the reader device knows which ZP-IoT frequency ranges to use to communicate with which ZP-IoT devices. For example, when the reader device is a user equipment such as UE 804, the network entity 802 may indicate in Figure 8 An indication of different frequency ranges supported by different ZP-IoT devices (e.g., the first ZP-IoT device 806 and the second ZP-IoT device 808) is sent within the configuration information sent in step 810.

[0152] In some cases, when different ZP-IoT devices support different ZP-IoT frequency ranges within the ZP-IoT frequency band, the reader device (e.g., network entity 802 or UE 804) may use frequency hopping to ensure that ZP-IoT communication with different ZP-IoT communication devices is possible. Fig.17 In the example shown, to facilitate communication with the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1702, the network entity 802 and the UE 804 may use frequency hopping to send and receive signals within each of the different ZP-IoT frequency ranges (e.g., the first ZP-IoT frequency range 1706, the second ZP-IoT frequency range 1708, and the third ZP-IoT frequency range 1710). For example, in some cases, the network entity 802 and the UE 804 may send a DL signal and / or a UL signal to the first ZP-IoT device 806 within the first ZP-IoT frequency range 1706. Thereafter, the network entity 802 and the UE 804 may then switch to the second ZP-IoT frequency range and send a DL signal and / or a UL signal to the second ZP-IoT device 808 within the second ZP-IoT frequency range 1708.

[0153] In some cases, when frequency hopping is used, the transmission of DL signals / UL signals may be based on a frequency hopping pattern involving different subchannels within the ZP-IoT frequency band defined for ZP-IoT communications. In some cases, different frequency hopping patterns may be assigned to different UEs, ZP-IoT devices, etc., so that interference can be reduced. Fig.18 Examples of these frequency hopping techniques are provided.

[0154] For example, Fig.18As illustrated, as shown, the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1802 may support ZP-IoT communications at different frequency ranges within the ZP-IoT frequency band 1804. For example, the first ZP-IoT device 806 may support ZP-IoT communications in a first ZP-IoT frequency range 1806 within the ZP-IoT frequency band 1804. The second ZP-IoT device 808 may support ZP-IoT communications in a second ZP-IoT frequency range 1808 within the ZP-IoT frequency band 1804. The third ZP-IoT device 1702 may support ZP-IoT communications in a third ZP-IoT frequency range 1810 within the ZP-IoT frequency band 1804.

[0155] Furthermore, as illustrated, the ZP-IoT frequency band 1804 includes a plurality of subchannels, such as subchannel 1, subchannel 2, subchannel 3, and subchannel 1. Furthermore, as can be seen, each of the plurality of subchannels is included in at least one of the first ZP-IoT frequency range 1806, the second ZP-IoT frequency range 1808, or the third ZP-IoT frequency range 1810. In some cases, when the network entity 802 and the UE 804 are in Figure 8 These subchannels may be used to perform frequency hopping when sending DL signals and UL signals to the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1802 in steps 820-850.

[0156] For example, in some cases, the network entity and / or UE 804 may use subchannel 1 or subchannel 2 to send a DL signal / UL signal to the first ZP-IoT device 806. Similarly, the network entity and / or UE 804 may use subchannel 3 or subchannel 4 to send a DL signal / UL signal to the second ZP-IoT device 808. In addition, the network entity and / or UE 804 may use subchannel 1, subchannel 2, subchannel 3, or subchannel 4 to send a DL signal / UL signal to the first ZP-IoT device 806.

[0157] In some cases, in order to limit the number of hops that need to be performed when sending DL signals / UL signals, a subchannel hopping pattern may be used that accurately indicates which subchannels are to be used for transmission. For example, in some cases, the subchannel hopping pattern may indicate a subset of subchannels from the multiple subchannels that are used to send DL signals or UL signals to the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1802. For example, instead of using all four subchannels to send DL signals and UL signals, the subchannel hopping pattern may indicate that only subchannel 1 and subchannel 3 are used because these subchannels are each included in at least one ZP-IoT frequency range supported by each of the first ZP-IoT device 806, the second ZP-IoT device 808, and the third ZP-IoT device 1802. In some cases, in Figure 8 The configuration information sent in step 810 may indicate a sub-channel hopping pattern to be used.

[0158] Example Operation of User Equipment

[0159] Fig.19 A method for performing a task by a user device such as Figure 1 and Figure 3 An example of method 1900 for performing wireless communications with a UE 104).

[0160] Method 1900 begins at step 1905, where configuration information for communicating with one or more ZP IoT devices is received, where the configuration information indicates a first ZP IoT frequency range for ZP IoT communication. In some cases, the operation of this step refers to the operation of Fig.21 The described circuits for receiving and / or codes for receiving may be or may be executed by the circuits and / or codes.

[0161] Method 1900 then proceeds to step 1910, where an UL signal is transmitted to a first ZP IoT device in a first ZP IoT frequency range using a first resource sharing scheme, wherein the first resource sharing scheme for transmitting the UL signal is different from a second resource sharing scheme for transmitting the DL signal to the first ZP IoT device. In some cases, the operation of this step refers to as described in reference Fig.21 The described circuits for transmitting and / or codes for transmitting, or executable by the circuits and / or the codes.

[0162] In some aspects, sending the UL signal to the first ZP IoT device includes sending the UL signal using a duplex scheme.

[0163] In some aspects, the duplexing scheme includes a TDD scheme in which a UL signal and a DL signal are separated into different timings; and the different timings include a UL timing for the UL signal and a DL timing for the DL signal.

[0164] In some aspects, for UL opportunities, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for DL ​​opportunities, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

[0165] In some aspects, the configuration information includes an indication of a guard period configured between UL signals to the first ZP IoT device in UL opportunities and DL signals to the first ZP IoT device in DL opportunities.

[0166] In some aspects, the UL opportunity includes: a first ZP IoT frequency range for ZP IoT communications; and at least one frequency range for OFDM communications.

[0167] In some aspects, the duplexing scheme comprises an FDD scheme in which UL signals and DL signals are separated into different frequency bands within a time slot; and the different frequency ranges comprise a UL frequency band for UL signals and a DL frequency band for DL ​​signals.

[0168] In some aspects, the first ZP IoT frequency range in which the UL signal is transmitted is included within the UL frequency band.

[0169] In some aspects, for a UL frequency band, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for a DL frequency band, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

[0170] In some aspects, sending the UL signal to the first ZP IoT device includes one of: sending the UL signal to the first ZP IoT device without using a UL timing advance; or sending the UL signal to the first ZP IoT device using a first UL timing advance different from a second UL timing advance used for OFDM communication.

[0171] In some aspects, the method 1900 further includes sending a UL signal to one or more second ZP IoT devices. In some cases, the operation of this step refers to the operation of Fig.21 The described circuits for transmitting and / or codes for transmitting, or executable by the circuits and / or the codes.

[0172] In some aspects, the one or more second ZP IoT devices support ZP IoT communications in one or more additional ZP IoT frequency ranges different from the first ZP IoT frequency range; and the configuration information further indicates the one or more additional ZP IoT frequency ranges.

[0173] In some aspects, the first ZP IoT frequency range and the one or more additional ZP IoT frequency ranges are included in the ZP IoT bandwidth; the ZP IoT bandwidth includes multiple subchannels; and each subchannel of the multiple subchannels is included in at least one of the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges.

[0174] In some aspects, the configuration information also includes a subchannel hopping pattern that indicates a subset of subchannels of the multiple subchannels that are included in the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges, and the subchannel subset is used to send UL signals to the first ZP IoT device and the one or more second ZP IoT devices.

[0175] In one aspect, method 1900 or any aspect related thereto may be performed by an apparatus such as Fig.21 The method 1900 is performed by a communication device 2100 that includes various components that are operable to, configured to, or adapted to perform the method 1900. The communication device 2100 is described in more detail below.

[0176] Please note that Fig.19 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are also possible consistent with the present disclosure.

[0177] Example Operations of Network Entities

[0178] Fig. 20 shows a method for use by network entities such as Figure 1 and Figure 3 BS102 or about Figure 2 An example of a method 2000 for performing wireless communications by a decomposed base station is discussed.

[0179] Method 2000 begins at step 2005, where configuration information for communicating with one or more ZP IoT devices is sent to a user equipment, where the configuration information indicates a first ZP IoT frequency range for ZP IoT communication. In some cases, the operation of this step refers to the operation described in reference to Fig. 22 The described circuits for transmitting and / or codes for transmitting, or executable by the circuits and / or the codes.

[0180] Method 2000 then proceeds to step 2010, where a DL signal is sent to the first ZP IoT device in the first ZP IoT frequency range using a second resource sharing scheme, wherein the second resource sharing scheme for sending the one or more DL signals is different from the first resource sharing scheme for sending UL signals to the first ZP IoT device. In some cases, the operation of this step refers to as described in reference Fig. 22 The described circuits for transmitting and / or codes for transmitting, or executable by the circuits and / or the codes.

[0181] In some aspects, sending the DL signal to the first ZP IoT device includes sending the DL signal using a duplex scheme.

[0182] In some aspects, the duplexing scheme includes a TDD scheme in which a UL signal and a DL signal are separated into different timings; and the different timings include a UL timing for the UL signal and a DL timing for the DL signal.

[0183] In some aspects, for UL opportunities, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for DL ​​opportunities, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

[0184] In some aspects, the configuration information includes an indication of a guard period configured between UL signals to the first ZP IoT device in UL opportunities and DL signals to the first ZP IoT device in DL opportunities.

[0185] In some aspects, the UL opportunity includes: a first ZP IoT frequency range for ZP IoT communications; and at least one frequency range for OFDM communications.

[0186] In some aspects, the duplexing scheme comprises an FDD scheme in which UL signals and DL signals are separated into different frequency bands within a time slot; and the different frequency ranges comprise a UL frequency band for UL signals and a DL frequency band for DL ​​signals.

[0187] In some aspects, the first ZP IoT frequency range in which the DL signals are transmitted is included within the DL frequency band.

[0188] In some aspects, for a UL frequency band, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for a DL frequency band, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

[0189] In some aspects, the UL signal is further sent to one or more second ZP IoT devices.

[0190] In some aspects, the one or more second ZP IoT devices support ZP IoT communications in one or more additional ZP IoT frequency ranges different from the first ZP IoT frequency range; and the configuration information further indicates the one or more additional ZP IoT frequency ranges.

[0191] In some aspects, the first ZP IoT frequency range and the one or more additional ZP IoT frequency ranges are included in the ZP IoT bandwidth; the ZP IoT bandwidth includes multiple subchannels; and each subchannel of the multiple subchannels is included in at least one of the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges.

[0192] In some aspects, the configuration information also includes a subchannel hopping pattern that indicates a subset of subchannels of the multiple subchannels that are included in the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges, and the subchannel subset is used to send UL signals to the first ZP IoT device and the one or more second ZP IoT devices.

[0193] In one aspect, method 2000 or any aspect related thereto may be performed by an apparatus such as Fig. 22 The method 2000 is performed by a communication device 2200 that includes various components operable to, configured to, or adapted to perform the method 2000. The communication device 2200 is described in more detail below.

[0194] Please note that Fig. 20 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are also possible consistent with the present disclosure.

[0195] Example Communication Device

[0196] Fig.21 Depicted are aspects of an example communications device 2100. In some examples, the communications device 2100 is a user equipment (UE), such as described above with respect to Figure 1 and Figure 3 UE 104 is described.

[0197] The communication device 2100 includes a processing system 2105 coupled to a transceiver 2145 (e.g., a transmitter and / or a receiver). The transceiver 2145 is configured to transmit and receive signals for the communication device 2100, such as various signals as described herein, via an antenna 2150. The processing system 2105 may be configured to perform processing functions for the communication device 2100, including processing signals received and / or to be transmitted by the communication device 2100.

[0198] The processing system 2105 includes one or more processors 2110. In various aspects, such as with respect to Figure 3 As described, the one or more processors 2110 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380. The one or more processors 2110 are coupled to the computer-readable medium / memory 2125 via the bus 2140. In some aspects, the computer-readable medium / memory 2125 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 2110, cause the one or more processors 2110 to perform operations related to the processing of the data transmission. Fig.19 The described method 1900 or any aspect related thereto. Note that references to a processor performing a function of the communication device 2100 may include one or more processors 2110 performing that function of the communication device 2100 .

[0199] In the depicted example, the computer readable medium / memory 2125 stores code (e.g., executable instructions), such as code for receiving 2130 and code for transmitting 2135. Processing of the code for receiving 2130 and the code for transmitting 2135 may cause the communication device 2100 to perform operations related to the communication. Fig.19 The described method 1900 or any aspect related thereto.

[0200] The one or more processors 2110 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 2125, including circuits such as circuits for receiving 2115 and circuits for transmitting 2120. Processing using the circuits for receiving 2115 and the circuits for transmitting 2120 may cause the communication device 2100 to perform operations related to the communication. Fig.19 The described method 1900 or any aspect related thereto.

[0201] The various components of the communication device 2100 may provide for performing Fig.19 The components of the described method 1900 or any aspect related thereto. For example, components for sending, transmitting, or outputting for sending may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104 and / or Fig.21 The transceiver 2145 and antenna 2150 of the communication device 2100 in FIG. 1 may include Figure 3 The illustrated transceiver 354 and / or antenna 352 and / or Fig.21 The transceiver 2145 and antenna 2150 of the communication device 2100.

[0202] Fig. 22 Aspects of an example communications device 2200 are depicted. In some aspects, communications device 2200 is a network entity such as Figure 1 and Figure 3 BS102 or such Figure 2 The decomposed base station in question.

[0203] The communication device 2200 includes a processing system 2205 coupled to a transceiver 2235 (e.g., a transmitter and / or a receiver) and / or a network interface 2245. The transceiver 2235 is configured to transmit and receive signals for the communication device 2200 via an antenna 2240, such as various signals as described herein. The network interface 2245 is configured to transmit and receive signals for the communication device 2200 via a communication link (such as, for example, a signal as described herein). Figure 2 The processing system 2205 may be configured to obtain and transmit signals for the communication device 2200 using the backhaul link, midhaul link, and / or fronthaul link described herein. The processing system 2205 may be configured to perform processing functions of the communication device 2200, including processing signals received and / or to be transmitted by the communication device 2200.

[0204] The processing system 2205 includes one or more processors 2210. In various aspects, such as with respect to Figure 3 As described, the one or more processors 2210 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340. The one or more processors 2210 are coupled to the computer-readable medium / memory 2220 via the bus 2230. In certain aspects, the computer-readable medium / memory 2220 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 2210, cause the one or more processors 2210 to perform operations related to the processing of the data transmission. Fig. 20 The described method 2000 or any aspect related thereto. Note that references to a processor of the communication device 2200 that performs a function may include one or more processors 2210 of the communication device 2200 that perform the function.

[0205] In the depicted example, the computer readable medium / memory 2220 stores code (e.g., executable instructions), such as code for transmitting 2225. Processing of the code for transmitting 2225 may cause the communication device 2200 to perform operations related to Fig. 20 The described method 2000 or any aspect related thereto.

[0206] The one or more processors 2210 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 2220, including circuits such as circuits for transmitting 2215. Processing using the circuits for transmitting 2215 may cause the communication device 2200 to perform operations related to Fig. 20 The described method 2000 or any aspect related thereto.

[0207] The various components of the communication device 2200 may provide for performing Fig. 20 The components of the described method 2000 or any aspect related thereto. The components for sending, transmitting or outputting for sending may include Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 102 and / or Fig. 22 The transceiver 2235 and antenna 2240 of the communication device 2200 in FIG. 1 may include Figure 3 The illustrated transceiver 332 and / or antenna 334 and / or Fig. 22 The transceiver 2235 and antenna 2240 of the communication device 2200.

[0208] Sample Clauses

[0209] Specific implementation examples are described in the following numbered clauses:

[0210] Clause 1: A method for wireless communication by a user equipment, the method comprising: receiving configuration information for communicating with one or more ZP IoT devices, wherein the configuration information indicates a first ZP IoT frequency range for ZP IoT communication; and sending an UL signal to a first ZP IoT device in the first ZP IoT frequency range using a first resource sharing scheme, wherein the first resource sharing scheme for sending the UL signal is different from a second resource sharing scheme for sending a DL signal to the first ZP IoT device.

[0211] Clause 2: The method of clause 1, wherein sending the UL signal to the first ZP IoT device comprises sending the UL signal using a duplex scheme.

[0212] Clause 3: The method of clause 2, wherein: the duplexing scheme comprises a TDD scheme, wherein the UL signal and the DL signal are separated into different timings; and the different timings comprise a UL timing for the UL signal and a DL timing for the DL signal.

[0213] Clause 4: The method of clause 3, wherein: for the UL opportunity, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for the DL opportunity, the second resource sharing scheme includes a DL TDM scheme and excludes a DL FDM scheme.

[0214] Clause 5: The method of clause 4, wherein the configuration information comprises an indication of a guard period configured between the UL signal to the first ZP IoT device in the UL opportunity and the DL signal to the first ZP IoT device in the DL opportunity.

[0215] Clause 6: The method of clause 4, wherein the UL opportunity comprises: the first ZP IoT frequency range for the ZP IoT communication; and at least one frequency range for OFDM communication.

[0216] Clause 7: The method of clause 2, wherein: the duplexing scheme comprises an FDD scheme, wherein the UL signal and the DL signal are separated into different frequency bands within a time slot; and the different frequency ranges comprise a UL frequency band for the UL signal and a DL frequency band for the DL signal.

[0217] Clause 8: The method of clause 7, wherein the first ZP IoT frequency range in which the UL signal is transmitted is included within the UL frequency band.

[0218] Clause 9: The method of clause 7, wherein: for the UL frequency band, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for the DL frequency band, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

[0219] Clause 10: A method according to any one of clauses 1 to 9, wherein sending the UL signal to the first ZP IoT device comprises one of the following: sending the UL signal to the first ZP IoT device without using UL timing advance; or sending the UL signal to the first ZP IoT device using a first UL timing advance different from a second UL timing advance used for OFDM communication.

[0220] Clause 11: A method as described in any of clauses 1 to 10, further comprising: sending the UL signal to one or more second ZP IoT devices.

[0221] Clause 12: A method according to clause 11, wherein: the one or more second ZP IoT devices support the ZP IoT communication in one or more additional ZP IoT frequency ranges different from the first ZP IoT frequency range; and the configuration information also indicates the one or more additional ZP IoT frequency ranges.

[0222] Clause 13: A method according to clause 12, wherein: the first ZP IoT frequency range and the one or more additional ZP IoT frequency ranges are included in a ZP IoT bandwidth; the ZP IoT bandwidth includes multiple subchannels; and each of the multiple subchannels is included in at least one of the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges.

[0223] Clause 14: A method according to clause 13, wherein the configuration information also includes a subchannel hopping pattern, the subchannel hopping pattern indicating a subset of subchannels of the multiple subchannels that are included in the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges, and the subchannel subset is used to send the UL signal to the first ZP IoT device and the one or more second ZP IoT devices.

[0224] Clause 15: A method for wireless communication by a network entity, the method comprising: sending configuration information for communicating with one or more ZP IoT devices to the user equipment, wherein the configuration information indicates a first ZP IoT frequency range for ZP IoT communication; and sending a DL signal to a first ZP IoT device in the first ZP IoT frequency range using a second resource sharing scheme, wherein the second resource sharing scheme for sending the one or more DL signals is different from the first resource sharing scheme for sending UL signals to the first ZP IoT device.

[0225] Clause 16: The method of clause 15, wherein sending the DL signal to the first ZP IoT device comprises sending the DL signal using a duplex scheme.

[0226] Clause 17: The method of clause 16, wherein: the duplexing scheme comprises a TDD scheme, wherein the UL signal and the DL signal are separated into different timings; and the different timings comprise a UL timing for the UL signal and a DL timing for the DL signal.

[0227] Clause 18: The method of clause 17, wherein: for the UL opportunity, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for the DL opportunity, the second resource sharing scheme includes a DL TDM scheme and excludes a DL FDM scheme.

[0228] Clause 19: The method of clause 18, wherein the configuration information comprises an indication of a guard period configured between the UL signal to the first ZP IoT device in the UL opportunity and the DL signal to the first ZP IoT device in the DL opportunity.

[0229] Clause 20: The method of clause 18, wherein the UL opportunity comprises: the first ZP IoT frequency range for the ZP IoT communication; and at least one frequency range for OFDM communication.

[0230] Clause 21: A method according to clause 16, wherein: the duplex scheme includes an FDD scheme, wherein the UL signal and the DL signal are separated into different frequency bands within a time slot; and the different frequency ranges include a UL frequency band for the UL signal and a DL frequency band for the DL signal.

[0231] Clause 22: The method of clause 21, wherein the first ZP IoT frequency range in which the DL signal is transmitted is included within the DL frequency band.

[0232] Clause 23: The method of clause 21, wherein: for the UL frequency band, the first resource sharing scheme includes a UL TDM scheme and a UL FDM scheme; and for the DL frequency band, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

[0233] Clause 24: A method as described in any of clauses 15 to 23, wherein the UL signal is further sent to one or more second ZPIoT devices.

[0234] Clause 25: A method according to clause 24, wherein: the one or more second ZP IoT devices support the ZP IoT communication in one or more additional ZP IoT frequency ranges different from the first ZP IoT frequency range; and the configuration information also indicates the one or more additional ZP IoT frequency ranges.

[0235] Clause 26: A method according to clause 25, wherein: the first ZP IoT frequency range and the one or more additional ZP IoT frequency ranges are included in a ZP IoT bandwidth; the ZP IoT bandwidth includes multiple subchannels; and each of the multiple subchannels is included in at least one of the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges.

[0236] Clause 27: A method according to clause 26, wherein the configuration information also includes a subchannel hopping pattern, the subchannel hopping pattern indicating a subset of subchannels of the multiple subchannels that are included in the first ZP IoT frequency range or the one or more additional ZP IoT frequency ranges, and the subchannel subset is used to send the UL signal to the first ZP IoT device and the one or more second ZP IoT devices.

[0237] Clause 28: An apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method of any one of clauses 1 to 27.

[0238] Clause 29: An apparatus comprising means for performing the method according to any one of clauses 1 to 27.

[0239] Clause 30: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 27.

[0240] Clause 31: A computer program product embodied on a computer readable storage medium, the computer program product comprising code for performing the method according to any of clauses 1 to 27.

[0241] Additional considerations

[0242] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limited to the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may ignore, replace or add various procedures or components as appropriate. For example, the described methods may be performed in a different order than the described order, and various actions may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionality, or structures and functionality that are supplementary or alternative to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0243] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0244] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items (including single members). As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0245] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a database, or another data structure), ascertaining, and the like. Moreover, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. In addition, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0246] The method disclosed herein includes one or more actions for implementing the method. The method actions may be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions may be modified without departing from the scope of the claims. In addition, the various operations of the method described above may be performed by any appropriate component capable of performing the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0247] The following claims are not intended to be limited to the various aspects shown herein, but should be given the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "parts for...". All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A method for wireless communication by a user equipment, the method comprising: receiving configuration information for communicating with one or more zero power internet of things (ZP-IoT) devices, wherein the configuration information indicates a first ZP-IoT frequency range for ZP-IoT communications; and An uplink (UL) signal is sent to a first ZP-IoT device in the first ZP-IoT frequency range using a first resource sharing scheme, wherein the first resource sharing scheme for sending the UL signal is different from a second resource sharing scheme for sending a downlink (DL) signal to the first ZP-IoT device.

2. The method of claim 1, wherein sending the UL signal to the first ZP-IoT device comprises sending the UL signal using a duplex scheme.

3. The method according to claim 2, wherein: The duplexing scheme includes a time division duplexing (TDD) scheme, in which the UL signal and the DL signal are separated into different timings; and The different timings include a UL timing for the UL signal and a DL timing for the DL signal.

4. The method according to claim 3, wherein: For the UL opportunity, the first resource sharing scheme includes a UL time division multiplexing (TDM) scheme and a UL frequency division multiplexing (FDM) scheme; and For the DL opportunity, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

5. The method of claim 4, wherein the configuration information comprises an indication of a guard period configured between the UL signal to the first ZP-IoT device in the UL opportunity and the DL signal to the first ZP-IoT device in the DL opportunity.

6. The method of claim 4, wherein the UL opportunity comprises: the first ZP-IoT frequency range for the ZP-IoT communication; and At least one frequency range is used for Orthogonal Frequency Division Multiplexing (OFDM) communications.

7. The method according to claim 2, wherein: The duplexing scheme comprises a frequency division duplexing (FDD) scheme, in which the UL signal and the DL signal are separated into different frequency bands within a time slot; and The different frequency ranges include a UL frequency band for the UL signal and a DL frequency band for the DL signal. 8 . The method of claim 7 , wherein the first ZP-IoT frequency range in which the UL signal is transmitted is included in the UL frequency band.

9. The method according to claim 7, wherein: For the UL frequency band, the first resource sharing scheme includes a UL time division multiplexing (TDM) scheme and a UL frequency division multiplexing (FDM) scheme; and For the DL frequency band, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

10. The method of claim 1, wherein sending the UL signal to the first ZP-IoT device comprises one of: Sending the UL signal to the first ZP-IoT device without using UL timing advance; or The UL signal is sent to the first ZP-IoT device using a first UL timing advance different from a second UL timing advance used for orthogonal frequency division multiplexing (OFDM) communication.

11. The method of claim 1 , further comprising sending the UL signal to one or more second ZP-IoT devices.

12. The method according to claim 11, wherein: said one or more second ZP-IoT devices support said ZP-IoT communications in one or more additional ZP-IoT frequency ranges different from said first ZP-IoT frequency range; and The configuration information also indicates the one or more additional ZP-IoT frequency ranges.

13. The method according to claim 12, wherein: The first ZP-IoT frequency range and the one or more additional ZP-IoT frequency ranges are included within a ZP-IoT bandwidth; The ZP-IoT bandwidth includes a plurality of sub-channels; and Each subchannel of the plurality of subchannels is included within at least one of the first ZP-IoT frequency range or the one or more additional ZP-IoT frequency ranges.

14. The method of claim 13, wherein the configuration information further includes a subchannel hopping pattern, the subchannel hopping pattern indicating a subset of subchannels among the multiple subchannels that are included in the first ZP-IoT frequency range or the one or more additional ZP-IoT frequency ranges, the subchannel subset being used to send the UL signal to the first ZP-IoT device and the one or more second ZP-IoT devices.

15. A method for wireless communication by a network entity, the method comprising: sending configuration information to a user equipment for communicating with one or more zero power internet of things (ZP-IoT) devices, wherein the configuration information indicates a first ZP-IoT frequency range for ZP-IoT communications; and A downlink (DL) signal is sent to a first ZP-IoT device in the first ZP-IoT frequency range using a second resource sharing scheme, wherein the second resource sharing scheme for sending the one or more DL signals is different from the first resource sharing scheme for sending an uplink (UL) signal to the first ZP-IoT device. 16 . The method of claim 15 , wherein sending the DL signal to the first ZP-IoT device comprises sending the DL signal using a duplex scheme.

17. The method of claim 16, wherein: The duplexing scheme includes a time division duplexing (TDD) scheme, in which the UL signal and the DL signal are separated into different timings; and The different timings include a UL timing for the UL signal and a DL timing for the DL signal.

18. The method of claim 17, wherein: For the UL opportunity, the first resource sharing scheme includes a UL time division multiplexing (TDM) scheme and a UL frequency division multiplexing (FDM) scheme; and For the DL opportunity, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

19. The method of claim 18, wherein the configuration information comprises an indication of a guard period configured between the UL signal to the first ZP-IoT device in the UL opportunity and the DL signal to the first ZP-IoT device in the DL opportunity.

20. The method of claim 18, wherein the UL opportunity comprises: the first ZP-IoT frequency range for the ZP-IoT communication; and At least one frequency range is used for Orthogonal Frequency Division Multiplexing (OFDM) communications.

21. The method of claim 16, wherein: The duplexing scheme comprises a frequency division duplexing (FDD) scheme, in which the UL signal and the DL signal are separated into different frequency bands within a time slot; and The different frequency ranges include a UL frequency band for the UL signal and a DL frequency band for the DL signal.

22. The method of claim 21, wherein the first ZP-IoT frequency range in which the DL signal is transmitted is included in the DL frequency band.

23. The method of claim 21, wherein: For the UL frequency band, the first resource sharing scheme includes a UL time division multiplexing (TDM) scheme and a UL frequency division multiplexing (FDM) scheme; and For the DL frequency band, the second resource sharing scheme includes a DL TDM scheme and does not include a DL FDM scheme.

24. The method of claim 15, wherein the UL signal is further transmitted to one or more second ZP-IoT devices.

25. The method of claim 24, wherein: said one or more second ZP-IoT devices support said ZP-IoT communications in one or more additional ZP-IoT frequency ranges different from said first ZP-IoT frequency range; and The configuration information also indicates the one or more additional ZP-IoT frequency ranges.

26. The method of claim 25, wherein: The first ZP-IoT frequency range and the one or more additional ZP-IoT frequency ranges are included within a ZP-IoT bandwidth; The ZP-IoT bandwidth includes a plurality of sub-channels; and Each subchannel of the plurality of subchannels is included within at least one of the first ZP-IoT frequency range or the one or more additional ZP-IoT frequency ranges.

27. The method of claim 26, wherein the configuration information further comprises a subchannel hopping pattern, the subchannel hopping pattern indicating a subset of subchannels among the multiple subchannels that are included in the first ZP-IoT frequency range or the one or more additional ZP-IoT frequency ranges, the subchannel subset being used to send the UL signal to the first ZP-IoT device and the one or more second ZP-IoT devices.

28. A user equipment (UE), the user equipment (UE) comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to: receiving configuration information for communicating with one or more zero power internet of things (ZP-IoT) devices, wherein the configuration information indicates a first ZP-IoT frequency range for ZP-IoT communications; and An uplink (UL) signal is sent to a first ZP-IoT device in the first ZP-IoT frequency range using a first resource sharing scheme, wherein the first resource sharing scheme for sending the UL signal is different from a second resource sharing scheme for sending a downlink (DL) signal to the first ZP-IoT device.

29. A network entity, comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to: sending configuration information to a user equipment for communicating with one or more zero power internet of things (ZP-IoT) devices, wherein the configuration information indicates a first ZP-IoT frequency range for ZP-IoT communications; and A downlink (DL) signal is sent to a first ZP-IoT device in the first ZP-IoT frequency range using a second resource sharing scheme, wherein the second resource sharing scheme for sending the one or more DL signals is different from the first resource sharing scheme for sending an uplink (UL) signal to the first ZP-IoT device.

Images