WO2023197281A1 - Techniques de communication bistatique pour dispositifs ido - Google Patents

Techniques de communication bistatique pour dispositifs ido Download PDF

Info

Publication number
WO2023197281A1
WO2023197281A1 PCT/CN2022/086977 CN2022086977W WO2023197281A1 WO 2023197281 A1 WO2023197281 A1 WO 2023197281A1 CN 2022086977 W CN2022086977 W CN 2022086977W WO 2023197281 A1 WO2023197281 A1 WO 2023197281A1
Authority
WO
WIPO (PCT)
Prior art keywords
iot
slot
directional
tag
directional slot
Prior art date
Application number
PCT/CN2022/086977
Other languages
English (en)
Inventor
Zhikun WU
Yuchul Kim
Ahmed Elshafie
Yu Zhang
Huilin Xu
Linhai He
Seyedkianoush HOSSEINI
Cong Nguyen
Muhammad Sayed Khairy Abdelghaffar
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2022/086977 priority Critical patent/WO2023197281A1/fr
Publication of WO2023197281A1 publication Critical patent/WO2023197281A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/1469—Two-way operation using the same type of signal, i.e. duplex using time-sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present disclosure relates generally to communication systems, and more particularly, to wireless communication systems utilizing Internet of Things (IoT) devices.
  • IoT Internet of Things
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • 5G New Radio is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements.
  • 3GPP Third Generation Partnership Project
  • 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable low latency communications
  • Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
  • LTE Long Term Evolution
  • An apparatus may include a wireless node, such as a user equipment (UE) or a network node.
  • the apparatus may output IoT data for an IoT device via an IoT transmit channel in a first directional slot of a time division duplex (TDD) system.
  • the apparatus may also obtain, in response to the IoT data and via an IoT receive channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • TDD time division duplex
  • An apparatus may include a wireless node, such as a UE or a network node.
  • the apparatus may output IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information.
  • the apparatus may also obtain an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • An apparatus may include an IoT device.
  • the apparatus may receive a command via an IoT communication channel.
  • the apparatus may also receive timing information via the IoT communication channel, the timing information including information related to a TDD system. Additionally, the apparatus may transmit an IoT response signal based on the command and the timing information.
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.
  • FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.
  • FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.
  • FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
  • FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.
  • FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.
  • UE user equipment
  • FIG. 4A illustrates a timing diagram associated with an RFID system including an RFID reader and anRFID tag, in accordance with the teachings disclosed herein.
  • FIG. 4B illustrates a timing diagram associated with an NR-IoT system including an IoT reader and an IoT tag, in accordance with the teachings disclosed herein.
  • FIG. 5 illustrates a first NR-IoT system and a second NR-IoT system, in accordance with the teachings disclosed herein.
  • FIG. 6A illustrates a timing diagram of an NR-IoT system including a UE and a tag, in accordance with the teachings disclosed herein.
  • FIG. 6B illustrates a timing diagram of an NR-IoT system including a base station and a tag, in accordance with the teachings disclosed herein.
  • FIG. 7 illustrates an example communication flow between a reader and a tag, in accordance with the teachings disclosed herein.
  • FIG. 8 illustrates a timing diagram of an NR-IoT system including a UE in communication with a tag, in accordance with the teachings disclosed herein.
  • FIG. 9 illustrates a timing diagram of an NR-IoT system including a base station in communication with a tag, in accordance with the teachings disclosed herein.
  • FIG. 10 illustrates a timing diagram of an NR-IoT system including a UE in communication with a tag and in D2D communication with an assist UE, in accordance with the teachings disclosed herein.
  • FIG. 11 illustrates an example communication flow between a reader, a tag, and a relay device, in accordance with the teachings disclosed herein.
  • FIG. 12 illustrates a timing diagram of an NR-IoT system including a UE in communication with a tag via a relay base station, in accordance with the teachings disclosed herein.
  • FIG. 13 illustrates a timing diagram of an NR-IoT system including a base station in communication with a tag via a relay UE, in accordance with the teachings disclosed herein.
  • FIG. 14 illustrates a timing diagram of an NR-IoT system including a UE in communication with a tag via a relay UE in D2D communication with the UE, in accordance with the teachings disclosed herein.
  • FIG. 15 is a flowchart of a method of wireless communication at a wireless node, in accordance with the teachings disclosed herein.
  • FIG. 16 is a flowchart of a method of wireless communication at awireless node, in accordance with the teachings disclosed herein.
  • FIG. 17 is a flowchart of a method of wireless communication at awireless node, in accordance with the teachings disclosed herein.
  • FIG. 18 is a flowchart of a method of wireless communication at awireless node, in accordance with the teachings disclosed herein.
  • FIG. 19 is a diagram illustrating an example of a hardware implementation for an example apparatus and/or network entity.
  • FIG. 20 is a diagram illustrating an example of a hardware implementation for an example network entity
  • FIG. 21 is a flowchart of a method of wireless communication at an IoT device, in accordance with the teachings disclosed herein.
  • FIG. 22 is a diagram illustrating an example of a hardware implementation for an example apparatus and/or IoT device.
  • aspects disclosed herein provide techniques for facilitating IoT communication between an IoT reader and an IoT tag using a TDD system in which the IoT reader and the IoT tag are half-duplex devices or full-duplex devices.
  • the techniques disclosed herein include the IoT reader providing timing information with a command that is received by the IoT tag.
  • the timing information may provide information to the IoT tag to cause the IoT tag to delay providing feedback to the IoT reader while the IoT reader is operating in a transmitter state.
  • the timing information may include information indicating to the IoT tag when the IoT reader is transitioning from the transmitter state to the receiver state.
  • the IoT tag may use the timing information to determine when to transmit the feedback to the IoT reader.
  • the techniques disclosed herein include the IoT reader using arelay device to relay a command to the IoT tag.
  • the IoT reader may output IoT data that is received by the relay device.
  • the IoT data may include a tag identifier of the IoT tag and may also include the command.
  • the relay device may use the IoT data to transmit the command to the IoT tag.
  • the relay device may transmit the command to the IoT tag associated with the tag identifier included in the IoT data.
  • the IoT reader may transmit the IoT data to the relay device using a Uu link.
  • the relay device may use IoT communication channels to transmit the command to the IoT tag.
  • processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • processors in the processing system may execute software.
  • Software whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
  • the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessedby a computer.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • optical disk storage magnetic disk storage
  • magnetic disk storage other magnetic storage devices
  • combinations of the types of computer-readable media or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessedby a computer.
  • aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) .
  • non-module-component based devices e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc.
  • OFEM original equipment manufacturer
  • Deployment of communication systems may be arranged in multiple manners with various components or constituent parts.
  • a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or disaggregated architecture.
  • a BS such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, accesspoint (AP) , atransmit receive point (TRP) , or a cell, etc.
  • NB Node B
  • eNB evolved NB
  • NR BS 5G NB
  • AP accesspoint
  • TRP transmit receive point
  • a cell etc.
  • a BS such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, accesspoint (AP) , atransmit receive point (TRP) , or a cell, etc.
  • AP accesspoint
  • TRP transmit receive point
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node.
  • a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (RUs) ) .
  • a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .
  • VCU virtual central unit
  • VDU virtual distributed unit
  • Base station operation or network design may con sider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilize d in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) .
  • Disaggregation may include distributing functionality across two or more units atvarious physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station, or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.
  • FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network.
  • the illustrated wireless communications system includes a disaggregated base station architecture.
  • the disaggregated base station architecture may include one or more CUs (e.g., a CU 110) that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework (e.g., an SMO Framework 105) , or both) .
  • SMO Service Management and Orchestration
  • a CU 110 may communicate with one or more DUs (e.g., a DU 130) via respective midhaul links, such as an Fl interface.
  • the DU 130 may communicate with one or more RUs (e.g., an RU 140) via respective fronthaul links.
  • the RU 140 may communicate with respective UEs (e.g., a UE 104) via one or more radio frequency (RF) access links.
  • RF radio frequency
  • the UE 104 may be simultaneously served by multiple RUs.
  • Each of the units i.e., the CUs (e.g., a CU 110) , the DUs (e.g., a DU 130) , the RUs (e.g., anRU 140) , as well as the Near-RT RICs (e.g., the Near-RT RIC 125) , the Non-RT RICs (e.g., the Non-RT RIC 115) , and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • the CUs e.g., a CU 110
  • the DUs e.g., a DU 130
  • the RUs e.g., anRU 140
  • the Near-RT RICs e.g., the Near-RT RIC 125
  • the Non-RT RICs e.g., the Non
  • Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units can be configured to communicate with one or more of the other units via the transmission medium.
  • the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units.
  • the units caninclude a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) , configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • the CU 110 may host one or more higher layer control functions.
  • control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110.
  • the CU 110 may be configured to handle user plane functionality (i.e., Central Unit -User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit -Control Plane (CU-CP) ) , or a combination thereof.
  • the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration.
  • the CU 110 can be implemented to communicate with
  • the DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs.
  • the DU 130 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, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP.
  • the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
  • Lower-layer functionality can be implemented by one or more RUs.
  • an RU 140 controlled by a DU 130, 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, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split.
  • the RU 140 can be implemented to handle over the air (OTA) communication with one or more UEs (e.g., the UE 104) .
  • OTA over the air
  • real-time and non-real-time aspects of control and user plane communication with the RU 140 can be controlled by a corresponding DU.
  • this configuration can enable the DU (s) and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
  • the SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements.
  • the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface) .
  • the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing phtform interface (such as an O2 interface) .
  • a cloud computing platform such as an open cloud (O-Cloud) 190
  • network element life cycle management such as to instantiate virtualized network elements
  • a cloud computing phtform interface such as an O2 interface
  • Such virtualized network elements can include, but are not limited to, CUs, DUs, RUs and Near-RT RICs.
  • the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs via an O1 interface.
  • the SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
  • the Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) /machine learning (ML) (AI/ML) workfiows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125.
  • the Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125.
  • the Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs, one or more DUs, or both, as well as an O-eNB, with the Near-RT RIC 125.
  • the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
  • SMO Framework 105 such as reconfiguration via O1
  • A1 policies such as A1 policies
  • a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102) .
  • the base station 102 provides an access point to the core network 120 for a UE 104.
  • the base station 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) .
  • the small cells include femtocells, picocells, and microcells.
  • a network that includes both small cell and macrocells may be known as a heterogeneous network.
  • a heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) .
  • the communication links between the RUs (e.g., an RU 140) and the UEs (e.g., a UE 104) may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referredto as forward link) transmissions from an RU 140 to a UE 104.
  • the communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • MIMO multiple-input and multiple-output
  • the communication links may be through one or more carriers.
  • the base station 102 /UE 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction.
  • the carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) .
  • the component carriers may include a primary component carrier and one or more secondary component carriers.
  • a primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
  • PCell primary cell
  • SCell secondary cell
  • D2D communication may use the DL/UL wireless wide area network (WWAN) spectrum.
  • 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) , and a physical sidelink control channel (PSCCH) .
  • sidelink channels such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) .
  • D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
  • IEEE Institute of Electrical and Electronics Engineers
  • the wireless communications system may further include a Wi-Fi AP 150 in communication with a UE 104 (also referred to as Wi-Fi stations (STAs) ) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like.
  • a Wi-Fi AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • FR1 frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz -52.6 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles.
  • FR2 which is often referredto (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz -300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz -24.25 GHz
  • FR4 71 GHz-114.25 GHz
  • FR5 114.25 GHz-300 GHz
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
  • the base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming.
  • the base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions.
  • the UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions.
  • the UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions.
  • the base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions.
  • the base station 102 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 /UE 104.
  • the transmit and receive directions for the base station 102 may or may not be the same.
  • the transmit and receive directions for the UE 104 may or may not be the same.
  • the base station 102 may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , network node, network entity, network equipment, or some other suitable terminology.
  • the base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU.
  • the set of base stations which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN) .
  • NG next generation
  • NG-RAN next generation
  • the core network 120 may include an Access and Mobility Management Function (AMF) (e.g., an AMF 161) , a Session Management Function (SMF) (e.g., an SMF 162) , a User Plane Function (UPF) (e.g., a UPF 163) , a Unified Data Management (UDM) (e.g., a UDM 164) , one or more location servers 168, and other functional entities.
  • AMF 161 is the control node that processes the signaling between the UE 104 and the core network 120.
  • the AMF 161 supports registration management, connection management, mobility management, and other functions.
  • the SMF 162 supports session management and other functions.
  • the UPF 163 supports packet routing, packet forwarding, and other functions.
  • the UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management.
  • the one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) (e.g., a GMLC 165) and a Location Management Function (LMF) (e.g., an LMF 166) .
  • GMLC Gateway Mobile Location Center
  • LMF Location Management Function
  • the one or more location servers 168 mayinclude one or more location/positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE) , a serving mobile location center (SMLC) , a mobile positioning center (MPC) , or the like.
  • PDE position determination entity
  • SMLC serving mobile location center
  • MPC mobile positioning center
  • the GMLC 165 and the LMF 166 support UE location services.
  • the GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information.
  • the LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104.
  • the NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104.
  • Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements.
  • the signal measurements may be made by the UE 104 and/or the serving base station (e.g., a base station 102) .
  • the signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS) , global position system (GPS) , non-terrestrial network (NTN) , or other satellite position/location system) , LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS) , sensor-based information (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID (NRE-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT) , DL angle-of-departure (DL-AoD) , DL time difference of arrival (DL-TDOA) , UL time difference of arrival (UL-TDOA) , and UL angle-of-arrival (UL-AoA) positioning) , and/or other systems/signals/sensors.
  • SPS satellite positioning system
  • GNSS Global Navigation Satellite
  • Examples of UEs 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 (e.g., MP3 player) , a camera, a game console, a tablet, 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, or any other similar functioning device.
  • SIP session initiation protocol
  • PDA personal digital assistant
  • the UEs may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) .
  • the UE 104 may also be referredto as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
  • the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
  • An IoT device 106 may refer to a device that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID) , a near-field communication (NFC) ID, etc. ) and that can transmit information to one or more other devices, for example, over a wired connection or a wireless connection.
  • the IoT device 106 may include an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like, or may include a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like.
  • QR quick response
  • RFID radio-frequency identification
  • An active IoT device may detect, store, communicate, and/or act on attributes or changes in attributes of other devices.
  • a non-active IoT device may include a passive loT device, a semi-passive IoT device, or a semi-active IoT device.
  • a passive loT device may have the ability to provide its identifier and attributes to another device when queried (e.g., via a “query” command) without a power source.
  • a semi-passive IoT device sometimes referred to as a “passive battery-assisted IoT device” includes a battery or other power source onboard and transmits its identifier and attributes to another device when queried.
  • a semi-active IoT device may have the ability to actively transmit and to passively reflect. As described herein, a non-active IoT device may use envelop decoding to receive a command and may use backscatter communication for transmitting feedback.
  • the IoT device 106 may communicate with the UE 104 and/or the base station 102. In some examples, communications between the IoT device 106 and the UE 104 and/or the base station 102 may via an IoT communication channel.
  • a UE such as the UE 104, may be configured to manage one or more aspects of wireless communication by facilitating communication with an IoT device, such as the example IoT device 106.
  • the UE 104 may include a UE reader component 198 configured to output IoT data for an IoT device via an IoT transmit channel in a first directional slot of a TDD system.
  • the UE reader component 198 may also be configured to obtain, in response to the IoT data and via an IoT receive channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the UE reader component 198 may be configured to output IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information.
  • the UE reader component 198 may also be configured to obtain an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • a base station such as the base station 102
  • the base station 102 may include a base station reader component 199 configured to output IoT data for an IoT device via an IoT transmit channel in a first directional slot of a TDD system.
  • the base station reader component 199 may also be configured to obtain, in response to the IoT data and via an IoT receive channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the base station reader component 199 may be configured to output IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information.
  • the base station reader component 199 may also be configured to obtain an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • an IoT device such as the IoT device 106
  • the IoT device 106 may be configured to manage one or more aspects of wireless communication by facilitating communication with a wireless node, such as the UE 104 or the base station 102.
  • the IoT device 106 may include an IoT tag component 197 configured to receive a command via an IoT communication channel.
  • the IoT tag component 197 may also be configured to receive timing information via the IoT communication channel, the timing information including information related to a TDD system.
  • the IoT tag component 197 may be configured to transmit an IoT response signal based on the command and the timing information.
  • the aspects presented herein may enable a wireless node, such as a UE or a network node, to communicate with an IoT device via a TDD system, which may facilitate improving communication performance, for example, by improving the likelihood of IoT communications being successfully transmitted and received.
  • a wireless node such as a UE or a network node
  • passive IoT devices sometimes referred to as a “passive tags” herein
  • the concepts described herein may be applicable to other similar areas, such as semi-passive IoT devices and/or semi-active IoT devices communicating in a TDD system.
  • 5G NR and, in particular, to IoT devices utilizing an NR TDD system
  • the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and/or other wireless technologies, in which devices may communicate in a TDD system.
  • FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure.
  • FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe.
  • FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure.
  • FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe.
  • the 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL.
  • FDD frequency division duplexed
  • TDD time division duplexed
  • the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols.
  • UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) .
  • DCI DL control information
  • RRC radio resource control
  • SFI received slot format indicator
  • FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels.
  • a frame (10 ms) may be divided into 10 equally sized subframes (1 ms) .
  • Eachsubframe may include one or more time slots.
  • Subframes may also include mini-slots, which may include 7, 4, or 2 symbols.
  • Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended.
  • CP cyclic prefix
  • the symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols.
  • OFDM orthogonal frequency division multiplexing
  • the symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single streamtransmission) .
  • DFT discrete Fourier transform
  • SC-FDMA single carrier frequency-division multiple access
  • the number of slots within a subframe is based on the CP and the numerology.
  • the numerology defines the subcarrier spacing (SCS) and, effectively, the symbol length/duration, which is equal to 1/SCS.
  • the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology ⁇ , there are 14 symbols/slot and 2 ⁇ slots/subframe.
  • the symbol length/duration is inversely related to the subcarrier spacing.
  • the slot duration is 0.25 ms
  • the subcarrier spacing is 60 kHz
  • the symbol duration is approximately 16.67 ⁇ s.
  • BWPs bandwidth parts
  • Each BWP may have a particular numerology and CP (normal or extended) .
  • a resource grid may be used to represent the frame structure.
  • Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers.
  • RB resource block
  • PRBs physical RBs
  • the resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
  • the RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE.
  • DM-RS demodulation RS
  • CSI-RS channel state information reference signals
  • the RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
  • BRS beam measurement RS
  • BRRS beam refinement RS
  • PT-RS phase tracking RS
  • FIG. 2B illustrates an example of various DL channels within a subframe of a frame.
  • the physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , eachREG including 12 consecutive REs in an OFDM symbol of an RB.
  • CCEs control channel elements
  • REGs RE groups
  • a PDCCH within one BWP may be referred to as a control resource set (CORESET) .
  • CORESET control resource set
  • a UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth.
  • a primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity.
  • a secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
  • the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS.
  • the physical broadcast channel (PBCH) which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) .
  • the MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) .
  • the physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
  • SIBs system information blocks
  • some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station.
  • the UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) .
  • the PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH.
  • the PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used.
  • the UE may transmit sounding reference signals (SRS) .
  • the SRS may be transmitted in the last symbol of a subframe.
  • the SRS may have a comb structure, and a UE may transmit SRS on one of the combs.
  • the SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
  • FIG. 2D illustrates an example of various UL channels within a subframe of a frame.
  • the PUCCH may be located as indicated in one configuration.
  • the PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK) ) .
  • the PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.
  • BSR buffer status report
  • PHR power headroom report
  • FIG. 3 is a block diagram that illustrates an example of a first wireless device that is configured to exchange wireless communication with a second wireless device.
  • the first wireless device may include abase station 310
  • the second wireless device may include a UE 350
  • the base station 310 may be in communication with the UE 350 in an access network.
  • the base station 310 includes a transmit processor (TX processor 316) , a transmitter 318Tx, a receiver 318Rx, antennas 320, a receive processor (RX processor 370) , a channel estimator 374, a controller/processor 375, and memory 376.
  • the example UE 350 includes antennas 352, a transmitter 354Tx, a receiver 354Rx, an RX processor 356, a channel estimator 358, a controller/processor 359, memory 360, and a TX processor 368.
  • the base station 310 and/or the UE 350 may include additional or alternative components.
  • IP Internet protocol
  • the controller/processor 375 implements layer 3 and layer 2 functionality.
  • Layer 3 includes a radio resource control (RRC) layer
  • layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDU
  • the TX processor 316 and the RX processor 370 implement layer 1 functionality associated with various signal processing functions.
  • Layer 1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • the TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) .
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • the coded and modulated symbols may then be split into parallel streams.
  • Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • IFFT Inverse Fast Fourier Transform
  • the OFDM stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from the channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350.
  • Each spatial stream may then be provided to a different antenna of the antennas 320 via a separate transmitter (e.g., the transmitter 318Tx) .
  • Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
  • RF radio frequency
  • each receiver 354Rx receives a signal through its respective antenna of the antennas 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 356.
  • the TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions.
  • the RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. Ifmultiple spatial streams are destined for the UE 350, two or more of the multiple spatial streams may be combined by the RX processor 356 into a single OFDM symbol stream.
  • the RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) .
  • FFT Fast Fourier Transform
  • the frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358.
  • the soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel.
  • the data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
  • the controller/processor 359 can be associated with the memory 360 that stores program codes and data.
  • the memory 360 may be referred to as a computer-readable medium.
  • the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets.
  • the controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • PDCP layer functionality associated with
  • Channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the TX processor 368 may be provided to different antenna of the antennas 352 via separate transmitters (e.g., the transmitter 354Tx) . Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
  • the UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350.
  • Each receiver 318Rx receives a signal through its respective antenna of the antennas 320.
  • Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.
  • the controller/processor 375 can be associated with the memory 376 that stores program codes and data.
  • the memory 376 may be referred to as a computer-readable medium.
  • the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets.
  • the controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
  • At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the UE reader component 198 of FIG. 1.
  • At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the base station reader component 199 of FIG. 1.
  • An IoT device may refer to a device that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID) , a near-field communication (NFC) ID, etc. ) and that can transmit information to one or more other devices, for example, over a wired connection or a wireless connection.
  • An IoT device may include an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like, or may include a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like.
  • QR quick response
  • RFID radio-frequency identification
  • An active IoT device may detect, store, communicate, and/or act on attributes or changes in attributes of other devices.
  • a non-active IoT device may include a passive IoT device, a semi-passive IoT device, or a semi-active IoT device.
  • a passive IoT device may have the ability to provide its identifier and attributes to another device when queried (e.g., via a “query” command) without a power source.
  • a semi-passive IoT device sometimes referred to as a “passive battery-assisted IoT device” includes a battery or other power source onboard and transmits its identifier and attributes to another device when queried.
  • a semi-active IoT device may have the ability to actively transmit and to passively reflect. As described herein, a non-active IoT device may use envelop decoding to receive a command and may use backscatter communication for transmitting feedback.
  • an active IoT device may be referred to as an “IoT reader” or a “reader, ” and a non-active IoT device may be referred to as an “IoT tag” or a “tag. ”
  • a container of orange juice may have tag and a refrigerator may have a reader that can communicate with the tag.
  • the reader may have the ability to receive signals from the tag and perform actions based on the received signals.
  • the reader may communicate with the tag to determine when the container of orange juice is removed from the refrigerator.
  • the tag may employ a passive communication interface to respond to a command.
  • the tag may use incident radio frequency signals to transmit data without a battery or power-grid connection.
  • the tag may use an antenna to detect an incident signal and convert the signal into electricity.
  • the tag may convert an incident signal into tens to hundreds of microwatts of electricity.
  • the passive communication interface may employ backscatter communication, sometimes referred to as “ambient backscatter” or “bistatic communication. ”
  • backscatter communication the tag reflects waves, particles, or signals back in the direction from which they were detected.
  • the tag may use the converted power to modify and reflect the signal with encoded data.
  • the encoded data may include a response to a command.
  • Antennas on other devices e.g., a reader
  • the passive communication interface of the tag allows unpowered sensors or devices to communicate, allowing the tag to function in places where external power may not be conveniently supplied, for example, on a container of orange juice.
  • tags employing the passive communication interface may be associated with low power consumption and low cost of devices.
  • a wireless communication system may employ an RFID system including an RFID reader and an RFID tag.
  • the RFID system (sometimes referred to as an ultra-high frequency radio frequency identification (UHF RFID) system)
  • UHF RFID ultra-high frequency radio frequency identification
  • the RFID reader and the RFID tag communicate in an ISM band.
  • the ISM band may be a portion of the radio spectrum that is reserved for industrial, scientific, and medical (ISM) purposes.
  • FIG. 4A illustrates a timing diagram 400 associated with an RFID system including an RFID reader 402 and an RFID tag 406, as presented herein.
  • the RFID reader 402 includes an antenna 404 to facilitate communication with the RFID tag 406.
  • the RFID reader 402 and the RFID tag 406 may continuously occupy a channel for a period 410.
  • the RFID reader 402 and the RFID tag 406 may occupy a sub-band 408 for a period of 0.5 seconds.
  • the RFID reader 402 may transmit a command 412 that is received by the RFID tag 406.
  • the RFID tag 406 may provide feedback 414 that is received by the RFID reader 402.
  • the tag uses incident signals or radio wavesto power-up and provide a response.
  • the RFID reader 402 may output continuous waves 416 that power-up the RFID tag 406.
  • the RFID tag 406 may receive the command 412 and use the continuous waves 416 to power-up the RFID tag 406 to transmit the feedback 414.
  • the RFID reader 402 may be a full-duplex device that has the ability to transmit and receive at the same time.
  • the RFID reader 402 may output the continuous waves 416 and simultaneously receive the feedback 414.
  • the RFID system of FIG. 4A may not be compatible with NR systems.
  • NR systems may work in a licensed band.
  • the RFID system may occupy a block of resources for a continuous period (e.g., the sub-band 408 for the period 410)
  • the NR system may employ a time-division duplex (TDD) system in which slots are discontinuous in a time domain.
  • TDD time-division duplex
  • a scheduler e.g., a base station
  • IoT devices of the NR system may be half-duplex devices in which the IoT devices are incapable of transmitting and receiving at the same time.
  • NR-IoT devices may transmit during uplink slots and receive during downlink slots.
  • the IoT devices may be full-duplex devices in which the IoT devices are capable of transmitting and receiving at the same time.
  • FIG. 4B illustrates a timing diagram 450 associated with an NR-IoT system including an IoT reader 452 and an IoT tag 454, as presented herein.
  • the IoT reader 452 of FIG. 4B does not include a coupled antenna, it may be appreciated that the IoT reader 452 may include an antenna to facilitate transmitting and receiving.
  • the IoT reader 452 is a half-duplex device and may be allocated resources 456 occupying a sub-band over a period 458.
  • the resources 456 include downlink slots 460 anduplink slots 462.
  • the downlink slots 460 and the uplink slots 462 occupy 1 ms in the time domain.
  • the IoT reader 452 may be in a receiver state during the downlink slots 460 and may be in a transmitter state during the uplink slots 462. Thus, the IoT reader 452 may transmit a command 464 during the uplink slots 462 and may receive feedback 466 during the downlink slots 460.
  • a tag employing a passive communication interface may use incident signals to power-up and transmit the feedback.
  • the IoT tag 454 may power-up during the uplink slots 462 when the IoT reader 452 is transmitting.
  • the IoT tag 454 may power-off during the downlink slots 460 when the IoT reader 452 is operating in the receiver state. That is, as the IoT reader 452 is a half-duplex device, the IoT reader 452 is unable to output continuous waves to power-up the IoT tag 454 during the downlink slots 460, as described in connection with the continuous waves 416 output by the RFID reader 402 of the RFID system of FIG. 4A.
  • FIG. 5 illustrates a first NR-IoT system 500 and a second NR-IoT system 550, as presented herein.
  • the first NR-IoT system 500 includes a UE 502 communicating with a tag 504.
  • the UE 502 may be an active IoT device configured to communicate with a non-active IoT device, such as the tag 504.
  • the UE 502 may communicate with the tag 504 via the licensed band in a TDD system.
  • the UE 502 may be a half-duplex device with the ability to either transmit or receive at a time. For example, the UE 502 may transmit commands to the tag 504 during uplink slots and may receive feedback from the tag 504 during downlink slots.
  • the secondNR-IoT system 550 includes a base station 552 communicating with a tag 554. Similar to the first NR-IoT system 500, the base station 552 may be an active IoT device configured to communicate with a non-active IoT device, such as the tag 554. The base station 552 may communicate with the tag 554 via the licensed band in a TDD system. Additionally, the base station 552 may be a half-duplex device with the ability to either transmit or receive at a time. For example, the base station 552 may transmit commands to the tag 554 during downlink slots and may receive feedback from the tag 554 during uplink slots.
  • the tag 504 and the tag 554 may perform envelop decoding receiving commands.
  • the tag 504 and the tag 554 may employ backscatter communication for transmitting feedback.
  • communication between an IoT reader, such as the UE 502 or the base station 552, and a tag, such as the tag 504 or the tag 554, may include a command and feedback.
  • the command may include a query command, a reader command, a write command, etc.
  • the feedback may include a response to the command.
  • the command may include a query command in which the IoT reader may query nearby tags for an identifier and/or attributes.
  • the tag may output a response that includes an identifier of the tag and/or any attributes of the tag. Examples of attributes of the tag include identifier information, information stored at the tag, an acknowledgement and/or negative acknowledgement, a random value, a handle, etc.
  • the IoT reader may transmit a read command to read information from a tag.
  • the IoT reader may transmit a write command to write information to a tag.
  • a scheduler may allocate resources to the IoT reader for communication with the tag.
  • the UE 502 may transmit a request 510 that is received by a scheduler 506.
  • the scheduler 506 may include a base station configured to allocate resources for communication.
  • the scheduler 506 may transmit a schedule 512 allocating resources allocated for the communication between the UE 502 and the tag 504.
  • the scheduler may be the base station 552.
  • the base station 552 may allocate resources for communicating with the tag 554.
  • the resources allocated for IoT communication may include resources 514 including downlink resources associated with downlink slots 516 and uplink resources associated with uplink slots 518.
  • the resources 514 include first downlink resources 516a ( “DLI” ) associated with a first downlink slot, second downlink resources 516b ( “DL2” ) associated with a second downlink slot, and third downlink resources516c ( “DL3” ) associated with athird downlink slot.
  • the resources 514 also include first uplink resources 518a ( “UL1” ) associated with a first uplink slot, second uplink resources 518b ( “UL2” ) associated with a second uplink slot, and third uplink resources 518c ( “UL3” ) associated with a third uplink slot.
  • first uplink resources 518a “UL1”
  • second uplink resources 518b “UL2”
  • third uplink resources 518c “UL3”
  • the resources allocated for IoT communication may include discontinuous slots.
  • the continuous slots or the discontinuous slots may include periodic resources, aperiodic resources, semi-persistent scheduling (SPS) resources, and/or configured grant resources.
  • SPS semi-persistent scheduling
  • the UE 502 may transmit commands to the tag 504 using the uplink resources of the uplink slots 518.
  • the UE 502 may receive feedback from the tag 504 using the downlink resources of the downlink slots 516.
  • the UE 502 may be a half-duplex device, the UE 502 may be unable to transmit communications during the downlink slots 516 and may be unable to receive communications during the uplink slots 518.
  • the base station 552 may transmit commands to the tag 554 using the downlink resources of the downlink slots 516.
  • the base station 552 may receive feedback from the tag 554 using the uplink resources of the uplink slots 518.
  • the base station 552 may be a half-duplex device, the base station 552 may be unable to transmit communications during the uplink slots 518 and may be unable to receive communications during the downlink slots 516.
  • FIG. 6A illustrates a timing diagram 600 of an NR-IoT system including a UE 602 and a tag 604, as presented herein.
  • Aspects of the UE 602 may be implemented by the UE 502 of FIG. 5, and aspects of the tag 604 may be implemented by the tag 504 of FIG. 5.
  • the UE 602 may attempt to communicate with the tag 604 using uplink resources 606 of an uplink slot 608.
  • Aspects of the uplink resources 606 and the uplink slot 608 may be implemented by the uplink resources of the uplink slots 518 of FIG. 5.
  • the UE 602 may transmit during the uplink slot 608 using the uplink resources 606.
  • the UE 602 may transmit unmodulated continuous waves, such as the continuous waves 416 of FIG. 4A.
  • the UE 602 may transmit modulated data to the tag 604, such as a command 610.
  • the UE 602 may transmit the command 610 using the uplink resources 606.
  • the tag 604 may transmit feedback 612 based on the command 610. However, if the tag 604 transmits the feedback 612 during the uplink slot 608, the feedback 612 may not be received by the UE 602. For example, during the uplink slot 608, the UE 602 is operating in a transmitter state and, thus, is unable to receive the feedback 612.
  • FIG. 6B illustrates a timing diagram 650 of an NR-IoT system including a base station 652 and a tag 654, as presented herein.
  • Aspects of the base station 652 may be implemented by the base station 552 of FIG. 5, and aspects of the tag 654 may be implemented by the tag 554 of FIG. 5.
  • the base station 652 may attempt to communicate with the tag 654 using downlink resources 656 of a downlink slot 658.
  • Aspects of the downlink resources 656 and the downlink slot 658 may be implemented by the downlink resources of the downlink slots 516 of FIG. 5.
  • the base station 652 may transmit during the downlink slot 658 using the downlink resources 656.
  • the base station 652 may transmit unmodulated continuous waves, such as the continuous waves 416 of FIG. 4A.
  • the base station 652 may transmit modulated data to the tag 654, such as a command 660.
  • the base station 652 may transmit the command 660 using the downlink resources 656.
  • the tag 654 may transmit feedback 662 based on the command 660. However, and similar to the example of FIG. 6A, if the tag 654 transmits the feedback 662 during the downlink slot 658, the feedback 662 may not be received by the base station 652. For example, during the downlink slot 658, the base station 652 is operating in a transmitter state and, thus, may be unable to receive the feedback 662.
  • aspects disclosed herein provide techniques for facilitating IoT communication between an IoT reader and an IoT tag using a TDD system.
  • One or both of the IoT reader and the IoT tag may be a half-duplex device or a full-duplex device.
  • the techniques disclosed herein include the IoT reader providing timing information with a command that is received by the IoT tag.
  • the timing information may provide information to the IoT tag to cause the IoT tag to delay providing feedback to the IoT reader while the IoT reader is operating in a transmitter state.
  • the timing information may include information indicating to the IoT tag when the IoT reader is transitioning from the transmitter state to the receiver state.
  • the IoT tag may use the timing information to determine when to transmit the feedback to the IoT reader. Aspects of the IoT reader providing the timing information are described in connection with FIGs. 7 to 10.
  • the techniques disclosed herein include the IoT readerusing arelay device to relay a command to the IoT tag.
  • the IoT reader may output IoT data that is received by the relay device.
  • the IoT data may include a tag identifier of the IoT tag and may also include the command.
  • the IoT data may include information to write to the IoT tag (e.g., information associated with a write command) and/or information to read from the IoT tag (e.g., information associated with a read command) .
  • the relay device may use the IoT data to transmit the command to the IoT tag.
  • the relay device may transmit the command to the IoT tag associated with the tag identifier included in the IoT data.
  • the IoT reader may transmit the IoT data to the relay device using a Uu link.
  • the relay device may use IoT communication channels to transmit the command to the IoT tag.
  • the IoT communication channel may include time resources and/or frequency resources that are allocated for IoT communication.
  • the IoT communication channel resources may be single subcarrier or multiple subcarriers. Aspects of the IoT reader using the relay device to relay the command to the IoT tag are described in connection with FIGs. 11 to 14.
  • FIG. 7 illustrates an example communication flow 700 between a reader 702 and a tag 704, as presented herein.
  • the communication flow 700 facilitates the reader 702 providing timing information to the tag 704 indicating when the reader 702 is switching to a receiver state.
  • Aspects of the reader 702 may be implemented by the IoT reader 452, the UE 502, the base station 552, the UE 602, and/or the base station 652.
  • Aspects of the tag 704 may be implemented by the IoT tag 454, the tag 504, the tag 554, the tag 604, and/or the tag 654.
  • the reader 702 may be in communication with one or more other readers, tags, base stations or UEs, and/or the tag 704 may be in communication with one or more other readers, tags, base stations or UEs.
  • the reader 702 transmits an IoT command 716 that is received by the tag 704.
  • the reader 702 also transmits timing information 718 that is received by the tag 704.
  • the reader 702 may transmit the IoT command 716 and the timing information 718 using an IoT communication channel. Although shown as separate communications in the example of FIG. 7, in other examples, the reader 702 may transmit the IoT command 716 and the timing information 718 in a single IoT communication.
  • the timing information 718 may include a start time, a window duration, a start time and an end time, an IoT symbol duration, and/or a quantity of IoT symbols configured.
  • the start time may correspond to a start time of the current slot during which the reader 702 is transmitting the IoT command 716.
  • the start time may correspond to a start time of the next slot during which the reader 702 is operating in the receiver state.
  • the window duration may correspond to the current slot during which the reader 702 is transmitting the IoT command 716.
  • the window duration may correspond to the next slot during which the reader 702 is operating in the receiver state.
  • the start time and the end time may correspond to the start time and the end time of the current slot during which the reader 702 is transmitting the IoT command 716. In some examples, the start time and the end time may correspond to the start time and the end time of the next slot during which the reader 702 is operating in the receiver state.
  • the IoT symbol duration may correspond to a duration associated with an IoT symbol
  • a slot may be associated with a quantity of IoT symbols and the IoT symbol duration may indicate when the current slot is ending or the next slot is starting.
  • the quantity of IoT symbols configured may correspond to how many IoT symbols are associated with a slot, such as the current slot.
  • the tag 704 may use the quantity of IoT symbols to determine when the current slot is ending and the next slot is starting.
  • the tag 704 may wait to respond to the IoT command 716.
  • the tag 704 may wait for a period based on the timing information 718. For example, based on the timing information 718, the tag 704 may be able to determine when the reader 702 is transitioning from the transmitter state to the receiver state and is able to receive feedback from the tag 704.
  • the tag 704 may output feedback 722 that is received by the reader 702.
  • the tag 704 may transmit the feedback 722 after waiting for the period based on the timing information 718.
  • the tag 704 may transmit the feedback 722 as a response to the IoT command 716.
  • the tag 704 may transmit the feedback 722 via an IoT communication channel.
  • the tag 704 may transmit the feedback 722 via backscatter communication.
  • the reader 702 may perform IoT channel decoding. For example, the reader 702 may perform the IoT channel decoding to receive and decode the feedback 722. The reader 702 may then act on the information included in the feedback 722.
  • the reader 702 may be a UE, as described in connection with the first NR-IoT system 500 of FIG. 5 and the example timing diagram 600 of FIG. 6A.
  • the reader 702 may transmit a request 710 that is received by a base station 706.
  • the base station 706 may be a scheduler, such as the scheduler 506 of FIG. 5.
  • the reader 702 may transmit the request 710 via a Uu link to the base station 706.
  • the request 710 may include a request for resources that the reader 702 may use for IoT communication with the tag 704.
  • the base station 706 may transmit a schedule 712 that is received by the reader 702.
  • the schedule 712 may allocate resources for the reader 702 to use for communicating with the tag 704.
  • the schedule 712 may include uplink resources that the reader 702 may use to transmit the IoT command 716 and the timing information 718 to the tag 704.
  • the schedule 712 may also include downlink resources that the reader 702 may use to receive the feedback 722.
  • the timing information corresponding to the current slot may correspond to an uplink slot and the timing information corresponding to the next slot may correspond to a downlink slot.
  • the start time and the end time may correspond to the start time and the end time of the current slot (e.g., an uplink slot) during which the reader 702 is transmitting the IoT command 716.
  • the start time and the end time may correspond to the start time and the end time of the next slot (e.g., a downlink slot) during which the reader 702 is operating in the receiver state.
  • the base station 706 may provide timing information to the tag 704 based on the schedule 712. For example, the base station 706 may receive the request 710 and determine the schedule 712. The base station 706 may then provide timing information 714 that is received by the tag 704. The base station 706 may transmit the timing information 714 via the IoT communication channel. The timing information 714 may correspond to the reader 702, such as when the reader 702 is transitioning from the transmitter state to the receiver state. In such examples, the reader 702 may forgo transmitting the timing information 718. Additionally, the tag 704 may use the timing information 714 to determine the period to wait to respond (e.g., at 720) .
  • the reader 702 may be a base station, as described in connection with the second NR-IoT system 550 of FIG. 5 and the example timing diagram 650 of FIG. 6B.
  • the timing information corresponding to the current slot may correspond to a downlink slot and the timing information corresponding to the next slot may correspond to an uplink slot.
  • the start time and the end time may correspond to the start time and the end time of the current slot (e.g., a downlink slot) during which the reader 702 is transmitting the IoT command 716.
  • the start time and the end time may correspond to the start time and the end time of the next slot (e.g., an uplink downlink slot) during which the reader 702 is operating in the receiver state.
  • FIG. 8 illustrates a timing diagram 800 of an NR-IoT system including a UE 802 in communication with a tag 804, as presented herein.
  • the UE 802 may be allocated uplink resources 810 associated with an uplink slot 812 and downlink resources 814 associatedwith a downlink slot 816.
  • the UE 802 may operate in a transmitter state during the uplink slot 812 and may operate in a receiver state during the downlink slot 816.
  • the UE 802 may transmit an IoT communication 820 that is received by the tag 804.
  • the IoT communication 820 may include an IoT command, such as the example IoT command 716 of FIG. 7, and timing information, such as the example timing information 718 of FIG. 7.
  • the UE 802 transmits the IoT communication 820 using the uplink resources 810 during the uplink slot 812.
  • the UE 802 may transmit the IoT communication 820 using the IoT communication channel.
  • the tag 804 mayreceive the IoT communication 820 during the uplink slot 812. Based on the timing information included in the IoT communication 820, the tag 804 may delay responding to the IoT command of the IoT communication 820, as described in connection with 720 of FIG. 7. After the waiting period expires, the tag 804 may output feedback 822 that is received by the UE 802. The tag 804 may transmit the feedback 822 using the IoT communication channel. The tag 804 may transmit the feedback 822 using the downlink resources 814 associatedwith the downlink slot 816.
  • the timing information of the IoT communication 820 may provide the tag 804 with information regarding when the UE 802 will be operating in the receiver state to receive the feedback 822.
  • the tag 804 may not receive incident signals to power-up the tag 804 and transmit the feedback 822 during the downlink slot 816.
  • an energy emitter 806 may transmit RF waves 824 that may be received by the tag 804.
  • the energy emitter 806 may transmit the RF waves 824 during the downlink slot 816 so that the tag 804 may use the incident signals to power-on and transmit the feedback 822.
  • the energy emitter 806 may be a base station.
  • the base station may transmit the RF waves 824 based on a schedule of resources allocated to the UE 802 for communicating with the tag 804.
  • the UE 802 may perform IoT channel decoding during the downlink slot 816 to receive the feedback 822. Aspects of performing the IoT channel decoding may implemented by 730 of FIG. 7. In some examples, the IoT channel decoding may be different than NR channel decoding associated with a Uu link.
  • FIG. 9 illustrates a timing diagram 900 of an NR-IoT system including a base station 902 in communication with a tag 904, as presented herein.
  • the base station 902 may allocate downlink resources 910 associated with a first downlink slot 912, uplink resources 914 associated with a first uplink slot 916, downlink resources 918 associated with a second downlink slot 920, and uplink resources 922 associated with a second uplink slot 924.
  • the base station 902 may operate in a transmitter state during the first downlink slot 912 and the second downlink slot 920, and may operate in a receiver state during the first uplink slot 916 and the second uplink slot 924.
  • the base station 902 may transmit an IoT communication 932 that is received by the tag 904.
  • the IoT communication 932 may include an IoT command, such as the example IoT command 716 of FIG. 7, and timing information, such as the example timing information 718 of FIG. 7.
  • the base station 902 transmits the IoT communication 932 using the downlink resources 918 during the second downlink slot 920.
  • the base station 902 may transmit the IoT communication 932 using the IoT communication channel.
  • the tag 904 may receive the IoT communication 932 during the second downlink slot 920. Based on the timing information included in the IoT communication 932, the tag 904 may delay responding to the IoT command of the IoT communication 932, as described in connection with 720 of FIG. 7. After the waiting period expires, the tag 904 may output feedback 934 that is received by the base station 902. The tag 904 may transmit the feedback 934 using the IoT communication channel. The tag 904 may transmit the feedback 934 using the uplink resources 922 associated with the second uplink slot 924.
  • the timing information of the IoT communication 932 may provide the tag 904 with information regarding when the base station 902 will be operating in the receiver state to receive the feedback 934. However, and as described in connection with the timing diagram 450 of FIG. 4B, the tag 904 may not receive incident signals to power-up the tag 904 and transmit the feedback 934 during the second uplink slot 924.
  • the base station 902 may initialize a UE 906 of the IoT communication 932. For example, the base station 902 may transmit resources 930 that are received by the UE 906. The base station 902 may transmit the resources 930 using the downlink resources 910 of the first downlink slot 912.
  • the resources 930 may include information regarding the uplink resources 914 associated with the first uplink slot 916 and regarding the uplink resources 922 associated with the second uplink slot 924.
  • the base station 902 may initialize the UE 906 so that the UE 906 may output RF waves 936 during the second uplink slot 924.
  • the UE 906 may transmit the RF waves 936 during the second uplink slot 924 so that the tag 904 may use the incident signals to power-on and transmit the feedback 934.
  • the base station 902 may perform IoT channel decoding during the second uplink slot 924 to receive the feedback 934. Aspects of performing the IoT channel decoding may implemented by 730 of FIG. 7. In some examples, the IoT channel decoding may be different than NR channel decoding associated with a Uu link.
  • the IoT reader may include a UE in D2D communication with a second UE.
  • FIG. 10 illustrates a timing diagram 1000 of an NR-IoT system including a UE 1002 in communication with a tag 1004 and in D2D communication with an assist UE 1006, as presented herein.
  • the UE 1002 may be allocated uplink resources associated with anuplink slot 1010.
  • the uplink slot 1010 may be associatedwith afirst uplink duration 1012 and a second uplink duration 1014.
  • the first uplink duration 1012 and the second uplink duration 1014 may each be a portion of the duration associated with the uplink slot 1010.
  • the uplink slot 1010 may be associated with 14 symbols.
  • the first uplink duration 1012 may be associated with the first 7 symbols of the uplink slot 1010 and the second uplink duration 1014 maybe associated with the second 7 symbols of the uplink slot 1010.
  • the UE 1002 may operate in a transmitter state during the first uplink duration 1012 and may operate in a receiver state during the second uplink duration 1014.
  • the UE 1002 may transmit an IoT communication 1020 that is received by the tag 1004.
  • the IoT communication 1020 may include an IoT command, such as the example IoT command 716 of FIG. 7, and timing information, such asthe example timing information 718 of FIG. 7.
  • the UE 1002 transmits the IoT communication 1020 using uplink resources associated with the first uplink duration 1012.
  • the UE 1002 may transmit the IoT communication 1020 using the IoT communication channel.
  • the tag 1004 may receive the IoT communication 1020 during the first uplink duration 1012. Based on the timing information included in the IoT communication 1020, the tag 1004 may delay responding to the IoT command of the IoT communication 1020, as described in connection with 720 of FIG. 7. After the waiting period expires, the tag 1004 may output feedback 1022 that is received by the UE 1002. The tag 1004 may transmit the feedback 1022 using the IoT communication channel. The tag 1004 may transmit the feedback 1022 using the resources associated with the second uplink duration 1014.
  • the timing information of the IoT communication 1020 may provide the tag 1004 with information regarding when the UE 1002 will be operating in the receiver state to receive the feedback 1022.
  • the tag 1004 may not receive incident signals to power-up the tag 1004 and transmit the feedback 1022 during the second uplink duration 1014.
  • the assist UE 1006 may transmit RF waves 1024 that may be received by the tag 1004. The assist UE 1006 may transmit the RF waves 1024 during the second uplink duration 1014 so that the tag 1004 may use the incident signals to power-on and transmit the feedback 1022.
  • the UE 1002 and the assist UE 1006 may be in D2D communication.
  • the D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
  • the D2D communication may be via sidelink communication.
  • the UE 1002 may perform IoT channel decoding during the second uplink duration 1014 to receive the feedback 1022. Aspects of performing the IoT channel decoding may implemented by 730 of FIG. 7. In some examples, the IoT channel decoding may be different than NR channel decoding associated with a Uu link.
  • the techniques disclosed herein include the IoT reader providing timing information with a command that is received by the IoT tag, as descried in connection with FIGs. 7 to 10.
  • the techniques disclosed herein include the IoT reader using a relay device to relay a command to the IoT tag.
  • FIG. 11 illustrates an example communication flow 1100 between a reader 1102, a tag 1104, and a relay device 1106, as presented herein.
  • the communication flow 1100 facilitates the reader 1102 communicating with the tag 1104 via the relay device 1106.
  • Aspects of the reader 1102 may be implemented by the IoT reader 452, the UE 502, the base station 552, the UE 602, and/or the base station 652.
  • Aspects of the tag 1104 may be implemented by the IoT tag 454, the tag 504, the tag 554, the tag 604, and/or the tag 654.
  • Aspects of the relay device 1106 may be implemented by the UE 104 or the base station 102 of FIG. 1.
  • the reader 1102, the tag 1104, and/or the relay device 1106 may be in communication with one or more other readers, tags, base stations or UEs.
  • the reader 1102 determines to communicate with the tag 1104. For example, the reader 1102 may determine to transmit a query command to identify surrounding or nearby tags. In the example of FIG. 11, the reader 1102 uses the relay device 1106 to operate as a relay between the reader 1102 and the tag 1104. For example, the reader 1102 may transmit IoT data 1114 that is received by the relay device 1106. The reader 1102 may transmit the IoT data 1114 via a Uu link established between the reader 1102 and the relay device 1106. The IoT data 1114 may include a tag identifier 1130 that is associated with the tag 1104. The IoT data 1114 may also include a command 1132 for the tag 1104. In other examples, the IoT data 1114 may include additional or alternate information.
  • the relay device 1106 transmits an IoT command 1116 that is received by the tag 1104.
  • the relay device 1106 may transmit the IoT command 1116 using an IoT communication channel.
  • the relay device 1106 may transmit the IoT command 1116 based on the IoT data 1114.
  • the IoT command 1116 may correspond to the command 1132 of the IoT data 1114.
  • the relay device 1106 may direct the IoT command 1116 to the tag 1104 based on the tag identifier 1130 of the IoT data 1114.
  • the tag 1104 may output feedback 1122 that is received by the reader 1102.
  • the tag 1104 may transmit the feedback 1122 as a response to the IoT command 1116.
  • the tag 1104 may transmit the feedback 1122 via an IoT communication channel.
  • the tag 1104 may use backscatter communication to transmit the feedback 1122.
  • the reader 1102 may perform IoT channel decoding. For example, the reader 1102 may perform the IoT channel decoding to receive and decode the feedback 1122. The reader 1102 may then act on the information included in the feedback 1122.
  • the relay device 1106 may transmit timing information 1118 that is received by the tag 1104.
  • the relay device 1106 may transmit the timing information 1118 using an IoT communication channel. Although shown as separate communications in the example of FIG. 11, in other examples, the relay device 1106 may transmit the IoT command 1116 and the timing information 1118 in a single IoT communication.
  • the timing information 1118 may include a start time, a window duration, a start time and an end time, an IoT symbol duration, and/or a quantity of IoT symbols configured.
  • the start time corresponds to a start time of the current slot during which the relay device 1106 is transmitting the IoT command 1116.
  • the start time may correspond to a start time of the next slot during which the reader 1102 is operating in the receiver state to be able to receive the feedback 1122.
  • the window duration may correspond to the current slot during which the relay device 1106 is transmitting the IoT command 1116.
  • the window duration may correspond to the next slot during which the reader 1102 may be operating in the receiver state to be able to receive the feedback 1122.
  • the start time and the end time may correspond to the start time and the end time of the current slot during which the relay device 1106 is transmitting the IoT command 1116.
  • the start time and the end time may correspond to the start time and the end time of the next slot during which the reader 1102 may be operating in the receiver state to be able to receive the feedback 1122.
  • the IoT symbol duration may correspond to a duration associated with an IoT symbol.
  • the quantity of IoT symbols configured may correspond to how many IoT symbols are associated with a slot, such as the current slot.
  • the tag 1104 may use the information of the timing information 1118 to determine when to transmit the feedback 1122. For example, at 1120, the tag 1104 maywait to respond to the IoT command 1116. The tag 1104 may wait for a period based on the timing information 1118. For example, based on the timing information 1118, the tag 1104 may be able to determine when the tag 1104 will be operating in the receiver state and is able to receive the feedback 1122 from the tag 1104.
  • the reader 1102 may be a UE, as descried in connection with the first NR-IoT system 500 of FIG. 5 and the example timing diagram 600 of FIG. 6A.
  • the relay device 1106 may include a base station, such as the base station 102 of FIG. 1.
  • the reader 1102 may transmit a request 1110 that is received by the relay device 1106.
  • the relay device 1106 may be a scheduler, such as the scheduler 506 of FIG. 5.
  • the reader 1102 may transmit the request 1110 via a Uu link to the relay device 1106.
  • the request 1110 may include a request for resources that the reader 1102 may use for facilitating IoT communication with the tag 1104. As shown in FIG.
  • the relay device 1106 may transmit a schedule 1112 that is received by the reader 1102.
  • the schedule 1112 may allocate resources for the reader 1102 to use to facilitate communicating with the tag 1104.
  • the schedule 1112 may include uplink resources that the reader 1102 may use to the IoT data 1114 to the relay device 1106.
  • the schedule 1112 may also include downlink resources that the reader 1102 may use to receive the feedback 1122.
  • the reader 1102 may transmit the IoT data 1114 to the relay device 1106 via an uplink channel, such as a PUCCH or a PUSCH.
  • an uplink channel such as a PUCCH or a PUSCH.
  • the tag 1104 may be unable to decode the IoT data 1114, the incident RF waves associated with transmitting the IoT data 1114 may power up the tag 1104.
  • the relay device 1106 may provide timing information 1118 to the tag 1104.
  • the relay device 1106 may provide the timing information 1118 based on the schedule 1112. For example, the relay device 1106 may receive the request 1110 and determine the schedule 1112. The relay device 1106 may then provide the timing information 1118 that is received by the tag 1104. The relay device 1106 may transmit the timing information 1118 via the IoT communication channel.
  • the timing information 1118 may correspond to the reader 1102, such as when the reader 1102 will be operating in the receiver state.
  • the reader 1102 may be a base station, as described in connection with the second NR-IoT system 550 of FIG. 5 and the example timing diagram 650 of FIG. 6B.
  • the relay device 1106 may include a UE, such as the UE 104 of FIG. 1.
  • the reader 1102 may transmit the IoT data 1114 to the relay device 1106 via a downlink channel, such as a PDCCH or a PDSCH.
  • a downlink channel such as a PDCCH or a PDSCH.
  • the tag 1104 may be unable to decode the IoT data 1114, the incident RF waves associated with transmitting the IoT data 1114 may power up the tag 1104.
  • FIG. 12 illustrates a timing diagram of an NR-IoT system 1200 including a UE 1202 in communication with a tag via a relay base station 1204, as presented herein.
  • the UE 1202 may be allocated uplink resources 1210 associated with an uplink slot 1212.
  • the UE 1202 may also be allocated downlink resources 1214 associated with a first downlink slot 1216, downlink resources 1218 associated with a second downlink slot 1220, and downlink resources 1222 associated with a third downlink slot 1224.
  • the uplink slot 1212, the first downlink slot 1216, the second downlink slot 1220, and the third downlink slot 1224 may be continuous uplink /downlink slots.
  • the uplink slot 1212, the first downlink slot 1216, the second downlink slot 1220, and/or the third downlink slot 1224 may discontinuous uplink /downlink slots.
  • the first downlink slot 1216 and the second downlink slot 1220 may be separatedby one or more other slots, and/or the second downlink slot 1220 and the third downlink slot 1224 may be separated by one or more other slots.
  • the UE 1202 may operate in a transmitter state during the uplink slot 1212 and may operate in a receiver state during the first downlink slot 1216, the second downlink slot 1220, and the third downlink slot 1224. In the illustrated example of FIG. 12, the UE 1202 may transmit IoT data 1230 that is receivedby the relay base station 1204.
  • the UE 1202 may transmit the IoT data 1230 to the relay base station 1204 via a physical channel 1228 of a Uu link between the UE 1202 and the relay base station 1204.
  • the physical channel 1228 may include PUCCH and/or PUSCH.
  • the UE 1202 may transmit the IoT data 1230 using the uplink resources 1210 associated with the uplink slot 1212.
  • the IoT data 1230 may include a tag identifier, such as the tag identifier 1130 of FIG. 11, and a command, such as the command 1132 of FIG. 11.
  • the tag identifier may be associated with a tag, such as a first tag 1206.
  • the command may be a command directed to one or more tags.
  • the command may be a query command in which surrounding tags may identify themselves to the UE 1202.
  • the relay base station 1204 may then transmit an IoT command based on the IoT data 1230.
  • the IoT command may correspond to the command included in the IoT data 1230 and the relay base station 1204 may use tag identifying information (e.g., a tag identifier) of the IoT data 1230 to direct the IoT command to the respective tag.
  • tag identifying information e.g., a tag identifier
  • the IoT data 1230 may include a command and a tag identifier associated with the first tag 1206.
  • the relay base station 1204 may transmit anIoT command 1232 to the first tag 1206.
  • the relay base station 1204 may transmit the IoT command 1232 to the first tag 1206 using an IoT communication channel.
  • the first tag 1206 may then transmit feedback 1234 that is received by the UE 1202.
  • the first tag 1206 may transmit the feedback 1234 when the response is ready (e.g., without waiting for a period) .
  • the first tag 1206 may receive the IoT command 1232 during the first downlink slot 1216 and may also transmit the feedback 1234 during the first downlink slot 1216.
  • the UE 1202 may be operating in a receiver state during the first downlink slot 1216 and, thus, the first tag 1206 may forgo waiting a period before transmitting the feedback 1234.
  • the first tag 1206 may wait a period before transmitting the feedback 1234.
  • the IoT command 1232 may include timing information, such as the example timing information 1118 of FIG. 11, that may indicate to the first tag 1206 when the UE 1202 will be operating in the receiver state and has the ability to receive the feedback 1234.
  • the first tag 1206 may wait a period based on the timing information before transmitting the feedback 1234. For example, the first tag 1206 may wait to transmit the feedback 1234 until the second downlink slot 1220 or the third downlink slot 1224.
  • the IoT data 1230 may include a query command that the UE 1202 may use to identify any surrounding or nearby tags.
  • the tag identifying information of the IoT data 1230 may indicate that the query command is to be broadcast and is not intended for any particular tag.
  • the relay base station 1204 may broadcast an IoT command 1236 corresponding to the query command.
  • the relay base station 1204 may broadcast the IoT command 1236 using the IoT communication channel.
  • the IoT command 1236 may be received by a second tag 1208 and a third tag 1209.
  • the second tag 1208 may transmit feedback 1238 in response to the IoT command 1236.
  • the second tag 1208 may transmit the feedback 1238 that is received by the UE 1202 using the IoT communication channel.
  • the third tag 1209 may transmit feedback 1240 in response to the IoT command 1236.
  • the third tag 1209 may transmit the feedback 1240 that is received by the UE 1202 using the IoT communication channel.
  • the second tag 1208 may transmit the feedback 1238 and the third tag 1209 may transmit the feedback 1240 when the respective responses are ready (e.g., without waiting for a period) , or after waiting a period (e.g., based on timing information included in the IoT command 1236) .
  • the second tag 1208 may receive the IoT command 1236 using the downlink resources 1218 associated with the second downlink slot 1220 and may wait until the third downlink slot 1224 to transmit the feedback 1238.
  • the third tag 1209 may receive the IoT command 1236 in the second downlink slot 1220 and may also transmit the feedback 1240 during the second downlink slot 1220.
  • the UE 1202 may perform IoT channel decoding during the first downlink slot 1216, the second downlink slot 1220, and/or the third downlink slot 1224 to receive the feedback from the tags. Aspects of performing the IoT channel decoding may be implemented by 1124 of FIG. 11. In some examples, the IoT channel decoding maybe different than NR channel decoding associated with a Uu link.
  • FIG. 13 illustrates a timing diagram 1300 of an NR-IoT system including a base station 1302 in communication with a tag 1306 via a relay UE 1304, as presented herein.
  • the base station 1302 may allocate downlink resources 1310 associated with a first downlink slot 1312, uplink resources 1314 associated with a first uplink slot 1316, downlink resources 1318 associated with a second downlink slot 1320, and uplink resources 1322 associated with a seconduplink slot 1324.
  • the first downlink slot 1312, the first uplink slot 1316, the second downlink slot 1320, and the second uplink slot 1324 may be continuous uplink /downlink slots.
  • first downlink slot 1312, the first uplink slot 1316, the second downlink slot 1320, and/or the second uplink slot 1324 may discontinuous uplink /downlink slots.
  • first downlink slot 1312 and the second downlink slot first uplink slot 1316 may be separated by one or more other slots
  • first uplink slot 1316 and the second downlink slot 1320 may be separated by one or more slots
  • second downlink slot 1320 and the second uplink slot 1324 may be separated by one or more other slots.
  • the base station 1302 may operate in a transmitter state during the first downlink slot 1312 and the second downlink slot 1320, and may operate in a receiver state during the first uplink slot 1316 and the second uplink slot 1324.
  • the base station 1302 may transmit IoT data 1330 that is received by the relay UE 1304.
  • the base station 1302 may transmit the IoT data 1330 using a physical channel 1328 of a Uu link between the base station 1302 and the relay UE 1304.
  • the physical channel 1328 may include PDCCH and/or PDSCH.
  • the base station 1302 may transmit the IoT data 1330 using the downlink resources 1318 associated with the second downlink slot 1320.
  • the IoT data 1330 may include a tag identifier, such as the tag identifier 1130 of FIG. 11, and a command, such as the command 1132 of FIG. 11.
  • the tag identifier maybe associated with a tag, such as the tag 1306.
  • the command may be a command directed to one or more tags.
  • the command may be a query command in which surrounding tags may identify themselves to the base station 1302.
  • the relay UE 1304 may then transmit an IoT command based on the IoT data 1330.
  • the IoT command may correspond to the command included in the IoT data 1330 and the relayUE 1304 mayuse tag identifying information (e.g., a tag identifier) of the IoT data 1330 to direct the IoT command to the respective tag.
  • the IoT data 1330 may include a command and a tag identifier associated with the tag 1306.
  • the relay UE 1304 may transmit an IoT command 1332 to the tag 1306.
  • the relay UE 1304 may transmit the IoT command 1332 to the tag 1306 using an IoT communication channel.
  • the tag 1306 may then transmit feedback 1334 that is received by the base station 1302.
  • the tag 1306 may transmit the feedback 1334 when the response is ready (e.g., without waiting for a period) .
  • the first tag 1206 may receive the IoT command 1332 during the second uplink slot 1324 and may also transmit the feedback 1334 during the second uplink slot 1324.
  • the base station 1302 may be operating in a receiver state during the second uplink slot 1324 and, thus, the tag 1306 may forgo waiting a period before transmitting the feedback 1334.
  • the tag 1306 may wait a period before transmitting the feedback 1334.
  • the IoT command 1332 may include timing information, such as the example timing information 1118 of FIG.
  • the tag 1306 may wait a period based on the timing information before transmitting the feedback 1334. For example, the tag 1306 may wait to transmit the feedback 1334 in a subsequent uplink slot.
  • the base station 1302 may provide communicate with the relay UE 1304 before transmitting the IoT data 1330.
  • the base station 1302 may transmit a resource allocation 1326 that is received by the relay UE 1304.
  • the base station 1302 may transmit the resource allocation 1326 via a Uu link between the base station 1302 and the relay UE 1304. Aspects of the resource allocation 1326 may be implemented by the schedule 1112 of FIG. 11.
  • the resource allocation 1326 may indicate to the relay UE 1304 the resources to use to receive the IoT data 1330 from the base station 1302 and/or to transmit the IoT command 1332 to the tag 1306.
  • the relay UE 1304 may monitor the downlink resources 1318 to receive the IoT data 1330 during the second downlink slot 1320.
  • the relay UE 1304 may use the uplink resources 1322 to transmit the IoT command 1332 to the tag 1306 during the second uplink slot 1324.
  • the base station 1302 may perform loT channel decoding during the first uplink slot 1316 and/or the second uplink slot 1324 to receive the feedback 1334 from the tag 1306. Aspects of performing the IoT channel decoding may be implemented by 1124 of FIG. 11. In some examples, the IoT channel decoding may be different than NR channel decoding associated with a Uu link.
  • the IoT reader may include a UE in D2D communication with a second UE.
  • FIG. 14 illustrates a timing diagram 1400 of an NR-IoT system including a UE 1402 in communication with a tag 1406 via a relay UE 1404 in D2D communication with the UE 1402, in accordance with the teachings disclosed herein.
  • the UE 1402 and the relay UE 1404 may be in D2D communication.
  • the D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
  • the D2D communication may be via sidelink communication.
  • the UE 1402 may be allocated uplink resources associated with an uplink slot 1410.
  • the uplink slot 1410 may be associated with a first uplink duration 1412 and a second uplink duration 1414.
  • the first uplink duration 1412 and the seconduplink duration 1414 may eachbe a portion of the duration associated with the uplink slot 1410.
  • the uplink slot 1410 may be associated with 14 symbols.
  • the first uplink duration 1412 may be associated with the first 7 symbols of the uplink slot 1410 and the second uplink duration 1414 may be associated with the second 7 symbols of the uplink slot 1410.
  • the UE 1402 may operate in a transmitter state during the first uplink duration 1412 and may operate in a receiver state during the second uplink duration 1414.
  • the UE 1402 may transmit IoT data 1430 that is received by the relay UE 1404.
  • the UE 1402 may transmit the IoT data 1430 to the relay UE 1404 via a physical channel 1428 between the UE 1402 and the relay UE 1404.
  • the physical channel 1428 may include a physical sidelink control channel (PSCCH) and/or a physical sidelink shared channel (PSSCH) .
  • PSCCH physical sidelink control channel
  • PSSCH physical sidelink shared channel
  • the UE 1402 may transmit the IoT data 1430 using the uplink resources associated with the first uplink duration 1412.
  • the IoT data 1430 may include a tag identifier, such as the tag identifier 1130 of FIG. 11, and a command, such as the command 1132 of FIG. 11.
  • the tag identifier may be associated with a tag, such as the tag 1406.
  • the command may be a command directed to one or more tags.
  • the command may be a query command in which surrounding tags may identify themselves to the UE 1402 in response to the command.
  • the relay UE 1404 may then transmit an IoT command based on the IoT data 1430.
  • the IoT command may correspond to the command included in the IoT data 1430 and the relay UE 1404 may use tag identifying information (e.g., a tag identifier) of the IoT data 1430 to direct the IoT command to the respective tag.
  • the IoT data 1430 may include a command and a tag identifier associated with the tag 1406.
  • the relay UE 1404 may transmit an IoT command 1432 to the tag 1406.
  • the relay UE 1404 may transmit the IoT command 1432 to the tag 1406 using an IoT communication channel.
  • the tag 1406 may then transmit feedback 1434 that is received by the UE 1402.
  • the tag 1406 may transmit the feedback 1434 when the response is ready (e.g., without waiting for a period) .
  • the tag 1406 may receive the IoT command 1432 during the second uplink duration 1414 of the uplink slot 1410 and may also transmit the feedback 1434 during the second uplink duration 1414.
  • the relay UE 1404 may be operating in a receiver state during the second uplink duration 1414 and, thus, the tag 1406 may forgo waiting a period before transmitting the feedback 1434. In other examples, the tag 1406 may wait a period before transmitting the feedback 1434.
  • the IoT command 1432 may include timing information, such as the example timing information 1118 of FIG. 11, that may indicate to the tag 1406 when the UE 1402 will be operating in the receiver state and has the ability to receive the feedback 1434.
  • the tag 1406 may wait a period based on the timing information before transmitting the feedback 1434. For example, the tag 1406 may wait to transmit the feedback 1434 until a subsequent uplink slot or duration of a subsequent uplink slot.
  • the UE 1402 may perform IoT channel decoding during the second uplink duration 1414 to receive the feedback 1434 from the tag 1406. Aspects of performing the IoT channel decoding may be implemented by 1124 of FIG. 11. In some examples, the IoT channel decoding may be different than NR channel decoding associated with a Uu link.
  • FIG. 15 is a flowchart 1500 of a method of wireless communication.
  • the method may be performed by a wireless node.
  • the wireless node may include a UE (e.g., the UE 104, and/or an apparatus 1904 of FIG. 19) .
  • the wireless node may include a base station (e.g., the base station 102, and/or a network entity 2002 of FIG. 20) .
  • the method may facilitate improving communication performance by improving IoT communication in a TDD system with half-duplex devices and/or full-duplex devices.
  • the wireless node outputs IoT data for an IoT device via an IoT communication channel in a first directional slot of a TDD system, as described in connection with the IoT command 716 of FIG. 7.
  • 1502 may be performed by a cellular RF transceiver 1922 /the UE reader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the wireless node obtains, in response to the IoT data and via the IoT communication channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot, as described in connection with the feedback 722 of FIG. 7.
  • 1504 may be performed by the cellular RF transceiver 1922 /the UE reader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the IoT response signal may include feedback in response to a command, such as a query command, a write command, a read command, etc.
  • FIG. 16 is a flowchart 1600 of a method of wireless communication.
  • the method may be performed by a wireless node.
  • the wireless node may include a UE (e.g., the UE 104, and/or an apparatus 1904 of FIG. 19) .
  • the wireless node may include a base station (e.g., the base station 102, and/or a network entity 2002 of FIG. 20) .
  • the method may facilitate improving communication performance by improving IoT communication in a TDD system with half-duplex devices and/or full-duplex devices.
  • the wireless node outputs IoT data for an IoT device via an IoT communication channel in a first directional slot of a TDD system, as described in connection with the IoT command 716 of FIG. 7.
  • 1612 may be performed by a cellular RF transceiver 1922 /the UE reader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the wireless node obtains, in response to the IoT data and via the IoT communication channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot, as described in connection with the feedback 722 of FIG. 7.
  • 1614 may be performed by the cellular RF transceiver 1922 /the UE reader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the IoT response signal may include feedback in response to a command, such as a query command, a write command, a read command, etc.
  • the wireless node may include a UE or an IoT reader
  • the first directional slot may include a first uplink slot, as described in connection with the UE 802 and the uplink slot 812 of FIG. 8.
  • the UE or the IoT reader may transmit an IoT communication request to a network node in a third directional slot of the TDD system, the third directional slot being a second uplink slot and occurring prior to the first directional slot in a time domain, as described in connection with the request 510 of FIG. 5 and/or the request 710 of FIG. 7.
  • 1602 may be performed by the cellular RF transceiver 1922/the UE reader component 198 of the apparatus 1904 of FIG. 19.
  • the IoT communication request may include one or more frequency resources and/or time resources allocated for IoT communication.
  • the UE or the IoT reader may receive a resource allocation associated with the first directional slot and the second directional slot in a fourth directional slot of the TDD system, the resource allocation being based on the IoT communication request, as descried in connection with the schedule 512 and resources 514 of FIG. 5, and/or the schedule 712 of FIG. 7.
  • 1604 may be performed by the cellular RF transceiver 1922/the UE reader component 198 of the apparatus 1904 of FIG. 19.
  • the resource allocation may include continuous uplink/downlink resources, as descried in connection with the resources 514 of FIG. 5. In other examples, the resource allocations may include discontinuous uplink/downlink resources.
  • the IoT data (e.g., at 1612) includes at least one command, as descried in connection with the IoT command 716 of FIG. 7, and/or an IoT command of the IoT communication 820 of FIG. 8.
  • the IoT data may further include timing information, as described in connection with the timing information 718 of FIG. 7 or the timing information of the IoT communication 820 of FIG. 8.
  • the timing information may include at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • the UE or the IoT reader may be in communication with a second UE via a direct communication interface, such as the UE 1002 and the assist UE 1006 of FIG. 10.
  • the direct communication interface may facilitate D2D communication through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
  • the D2D communication may be via sidelink.
  • the first directional slot may be associated with a first duration of the first uplink slot, as descried in connection with the first uplink duration 1012 of the uplink slot 1010.
  • the second directional slot may be associated with a second duration of the first uplink slot, as described in connection with the seconduplink duration 1014 of the uplink slot 1010.
  • the UE or the IoT reader may relay IoT commands from a network node to the IoT device, as described in connection with the relay device 1106 of FIG. 11, and/or the UE 1304 of FIG. 13.
  • the UE or the IoT reader may obtain the IoT data and information related to the IoT device from a network node, as described in connection with the IoT data 1114 from the reader 1102 of FIG. 11, and/or the IoT data 1330 from the base station 1302 of FIG. 13.
  • 1606 may be performed by the cellular RF transceiver 1922/the UE reader component 198 of the apparatus 1904 of FIG. 19.
  • the wireless node may include a network node or an IoT reader
  • the first directional slot may include a first downlink slot
  • the second directional slot may include a first uplink slot, as described in connection with the base station 902, the second downlink slot 920, and the second uplink slot 924 of FIG. 9.
  • the network node or the IoT reader may output a resource allocation to a UE in a third directional slot of the TDD system, the resource allocation including one or more resources associated with at least one uplink slot, the third directional slot being a second downlink slot and occurring prior to the first directional slot in a time domain, as described in connection with the schedule 512 and the resources 514 of FIG. 5, the schedule 712 of FIG. 7, and/or the resources 930 of FIG. 9.
  • 1608 may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the one or more resources may include a frequency allocation (e.g. one or more sub-bands in a frequency domain) and/or a time allocation (e.g., one or more symbols in a time domain) .
  • the IoT data (e.g., at 1612) includes at least one command, as described in connection with the IoT command 716 of FIG. 7, and/or an IoT command of the IoT communication 932 of FIG. 9.
  • the IoT data may further include timing information, as described in connection with the timing information 718 of FIG. 7 or the timing information of the IoT communication 932 of FIG. 9.
  • the timing information may include at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • the network node or the IoT reader may obtain the IoT data and information related to the IoT device from a UE, as described in connection with the IoT data 1114 and the reader 1102 of FIG. 11, and/or the IoT data 1230 of FIG. 12.
  • 1610 may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • FIG. 17 is a flowchart 1700 of a method of wireless communication.
  • the method may be performed by a wireless node.
  • the wireless node may include a UE (e.g., the UE 104, and/or an apparatus 1904 of FIG. 19) .
  • the wireless node may include a base station (e.g., the base station 102, and/or a network entity 2002 of FIG. 20) .
  • the method may facilitate improving IoT communication via a relay device in a TDD system with half-duplex devices and/or full-duplex devices.
  • the wireless node outputs IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information, as descried in connection with the IoT data 1114, the tag identifier 1130, and the command 1132 of FIG. 11, the IoT data 1230 of FIG. 12, and/or the IoT data 1330 of FIG. 13.
  • 1702 may be performed by a cellular RF transceiver 1922/the UE reader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the wireless node obtains an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot, as descried in connection with the feedback 1122 of FIG. 11, the feedback 1234 and/or the feedback 1238 of FIG. 12, and/or the feedback 1334 of FIG. 13.
  • 1704 may be performed by the cellular RF transceiver 1922/the UEreader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the wireless node may include a UE or an IoT reader
  • the first directional slot may include a first uplink slot
  • the physical channel may include a PUCCH, as descried in connection with the UE 1202, the uplink slot 1212, and the physical channel 1228 of FIG. 12.
  • FIG. 18 is a flowchart 1800 of a method of wireless communication.
  • the method may be performed by a wireless node.
  • the wireless node may include a UE (e.g., the UE 104, and/or an apparatus 1904 of FIG. 19) .
  • the wireless node may include a base station (e.g., the base station 102, and/or a network entity 2002 of FIG. 20) .
  • the method may facilitate improving IoT communication via a relay device in a TDD system with half-duplex devices and/or full-duplex devices.
  • the wireless node outputs IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information, as described in connection with the IoT data 1114, the tag identifier 1130, and the command 1132 of FIG. 11, the IoT data 1230 of FIG. 12, and/or the IoT data 1330 of FIG. 13.
  • 1808 may be performed by a cellular RF transceiver 1922/the UE reader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the wireless node obtains an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot, as described in connection with the feedback 1122 of FIG. 11, the feedback 1234 and/or the feedback 1238 of FIG. 12, and/or the feedback 1334 of FIG. 13.
  • 1810 may be performed by the cellular RF transceiver 1922/the UEreader component 198 of the apparatus 1904 of FIG. 19, or may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the wireless node may include a UE or an IoT reader
  • the first directional slot may include a first uplink slot
  • the physical channel may include a PUCCH, as descried in connection with the UE 1202, the uplink slot 1212, and the physical channel 1228 of FIG. 12.
  • the UE or the IoT reader may transmit an IoT communication request to a network node in a third directional slot of the TDD system, the third directional slot being a second uplink slot and occurring prior to the first directional slot in a time domain, as descried in connection with the request 510 of FIG. 5 and/or the request 1110 of FIG. 11.
  • 1802 maybe performed bythe cellular RF transceiver 1922/the UEreader component 198 of the apparatus 1904 of FIG. 19.
  • the UE or the IoT reader may receive a resource allocation associated with the first directional slot and the second directional slot in a fourth directional slot of the TDD system, the resource allocation being based on the IoT communication request, as described in connection with the schedule 512 and resources 514 of FIG. 5, and/or the schedule 1112 of FIG. 11.
  • 1504 may be performed by the cellular RF transceiver 1922/the UE reader component 198 of the apparatus 1904 of FIG. 19.
  • the resource allocation may include continuous uplink/downlink resources, as described in connection with the resources 514 of FIG. 5. In other examples, the resource allocations may include discontinuous uplink/downlink resources.
  • the IoT data may further include timing information, as described in connection with the timing information 1118 of FIG. 11.
  • the timing information may include at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • the UE or the IoT reader may be in communication with a second UE via a direct communication interface, such as the UE 1402 and the relay UE 1404 of FIG. 14.
  • the direct communication interface may facilitate D2D communication through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
  • the D2D communication may be via sidelink.
  • the first directional slot may be associated with a first duration of the first uplink slot, as described in connection with the first uplink duration 1412 of the uplink slot 1410.
  • the second directional slot may be associated with a second duration of the first uplink slot, as described in connection with the seconduplink duration 1414 of the uplink slot 1410. Additionally, theUE or the IoT reader may transmit the IoT data to the second UE via a physical sidelink channel, as described in connection with the physical channel 1428 of FIG. 14.
  • the wireless node may include a network node or an IoT reader
  • the first directional slot may include a first downlink slot
  • the second directional slot may include a first uplink slot
  • the physical channel may include a PDSCH, as described in connection with the base station 1302, the second downlink slot 1320, the seconduplink slot 1324, and the physical channel 1328 of FIG. 13.
  • the network node or the IoT reader may output a resource allocation to a UE in a third directional slot of the TDD system, the resource allocation including one or more resources associated with at least one uplink slot, the third directional slot being a second downlink slot and occurring prior to the first directional slot in a time domain, as described in connection with the schedule 512 and the resources 514 of FIG. 5, the schedule 1112 of FIG. 11, and/or resource allocation 1326 during the first downlink slot 1312 of FIG. 13.
  • 1806 may be performed by the base station reader component 199 of the network entity 2002 of FIG. 20.
  • the IoT data may further include timing information, as described in connection with timing information 1118 of FIG. 11.
  • the timing information may include at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • FIG. 19 is a diagram 1900 illustrating an example of a hardware implementation for an apparatus 1904.
  • the apparatus 1904 may be a UE, a component of a UE, or may implement UE functionality.
  • the apparatusl904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers (e.g., the cellular RF transceiver 1922) .
  • the cellular baseband processor 1924 may include on-chip memory 1924′.
  • the apparatus 1904 may further include one or more subscriber identity modules (SIM) cards 1920 and an application processor 1906 coupled to a secure digital (SD) card 1908 and a screen 1910.
  • SIM subscriber identity modules
  • SD secure digital
  • the application processor 1906 may include on-chip memory 1906′.
  • the apparatus 1904 may further include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., GNSS module) , one or more sensor modules 1918 (e.g., barometric pressure sensor/altimeter; motion sensor such as inertial management unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning) , additional memory modules 1926, a power supply 1930, and/or a camera 1932.
  • a Bluetooth module 1912 e.g., a WLAN module 1914
  • an SPS module 1916 e.g., GNSS module
  • sensor modules 1918 e.g., barometric pressure sensor/altimeter; motion sensor such as inertial management unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection
  • the Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) .
  • TRX on-chip transceiver
  • the Bluetooth module 1912, the WLAN module 1914, and the SPS module 1916 may include their own dedicated antennas and/or utilize one or more antennas 1980 for communication.
  • the cellular baseband processor 1924 communicates through transceiver (s) (e.g., the cellular RF transceiver 1922) via one or more antennas 1980 with the UE 104 and/or with an RU associated with a network entity 1902.
  • the cellular baseband processor 1924 and the application processor 1906 may each include a computer-readable medium/memory, such as the on-chip memory 1924′, and the on-chip memory 1906′, respectively.
  • the additional memory modules 1926 may also be considered a computer-readable medium/memory.
  • Each of the on-chip memory 1924′, the on-chip memory 1906′, and/or the additional memory modules 1926 may be non-transitory.
  • the cellular baseband processor 1924 and the application processor 1906 are each responsible for general processing, including the execution of software stored on the computer-readable medium/memory.
  • the software when executed by the cellular baseband processor 1924/application processor 1906, causes the cellular baseband processor 1924/application processor 1906 to perform the various functions described supra.
  • the computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor 1924/application processor 1906 when executing software.
  • the cellular baseband processor 1924/application processor 1906 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359.
  • the apparatus 1904 may be a processor chip (modem and/or application) and include just the cellular baseband processor 1924 and/or the application processor 1906, and in another configuration, the apparatus 1904 may be the entire UE (e.g., see the UE 350 of FIG. 3) and include the additional modules of the apparatus 1904.
  • the UE reader component 198 may be configured to output IoT data for an IoT device via an IoT communication channel in a first directional slot of a TDD system.
  • the UE reader component 198 may also be configured to obtain, in response to the IoT data and via the IoT communication channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the UE reader component 198 may be configured to output IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information.
  • the UE reader component 198 may also be configured to obtain an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the UE reader component 198 may be within the cellular baseband processor 1924, the application processor 1906, or both the cellular baseband processor 1924 and the application processor 1906.
  • the UE reader component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.
  • the apparatus 1904 may include a variety of components configured for various functions.
  • the UE reader component 198 may include one or more hardware components that perform each of the blocks of the algorithm in the flowcharts of FIGs. 15, 16, 17, and/or 18.
  • the apparatus 1904 includes means for outputting IoT data for an IoT device via anIoT communication channel in a first directional slot of a TDD system.
  • the example apparatus 1904 also includes means for obtaining, in response to the IoT data and via the IoT communication channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the example apparatus 1904 also includes means for transmitting an IoT communication request to a network node in a third directional slot of the TDD system, the third directional slot being a second uplink slot and occurring prior to the first directional slot in a time domain.
  • the example apparatus 1904 also includes means for receiving a resource allocation associated with the first directional slot and the second directional slot in a fourth directional slot of the TDD system, the resource allocation being based on the IoT communication request.
  • the example apparatus 1904 also includes means for obtaining the IoT data and information related to the IoT device from a network node.
  • the apparatus 1904 includes means for outputting IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information.
  • the example apparatus 1904 also includes means for obtaining an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the example apparatus 1904 also includes means for transmitting an IoT communication request to a network node in a third directional slot of the TDD system, the third directional slot being a second uplink slot and occurring prior to the first directional slot in a time domain.
  • the example apparatus 1904 also includes means for receiving a resource allocation associated with the first directional slot and the second directional slot in a fourth directional slot of the TDD system, the resource allocation being based on the IoT communication request.
  • the means may be the UE reader component 198 of the apparatus 1904 configured to perform the functions recited by the means.
  • the apparatus 1904 may include the TX processor 368, the RX processor 356, and the controller/proces sot 359.
  • the means may be the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the means.
  • FIG. 20 is a diagram 2000 illustrating an example of a hardware implementation for a network entity 2002.
  • the network entity 2002 may be a BS, a component of a BS, or may implement BS functionality.
  • the network entity 2002 may include at least one of a CU 2010, a DU 2030, or an RU 2040.
  • the network entity 2002 may include the CU 2010; both the CU 2010 and the DU 2030; each of the CU 2010, the DU 2030, and the RU 2040; the DU 2030; both the DU 2030 and the RU 2040; or the RU 2040.
  • the CU 2010 may include a CU processor 2012.
  • the CU processor 2012 may include on-chip memory 2012'.
  • the CU 2010 communicates with the DU 2030 through a midhaul link, such as an Fl interface.
  • the DU 2030 may include a DU processor 2032.
  • the DU processor 2032 may include on-chip memory 2032'.
  • the DU 2030 may further include additional memory modules 2034 and a communications interface 2038.
  • the DU 2030 communicates with the RU 2040 through a fronthaul link.
  • the RU 2040 may include an RU processor 2042.
  • the RU processor 2042 may include on-chip memory 2042'.
  • the RU 2040 may further include additional memory modules 2044, one or more transceivers 2046, antennas 2080, and a communications interface 2048.
  • the RU 2040 communicates with the UE 104.
  • the on-chip memories e.g., the on-chip memory 2012', the on-chip memory 2032', and/or the on-chip memory 2042'
  • the additional memory modules e.g., the additional memory modules 2014, the additional memory modules 2034, and/or the additional memory modules 2044
  • Each computer-readable medium /memory may be non-transitory.
  • Each of the CU processor 2012, the DU processor 2032, the RU processor 2042 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory.
  • the software when executed by the corresponding processor (s) causes the processor (s) to perform the various functions described supra.
  • the computer-readable medium /memory may also be used for storing data that is manipulated by the processor (s) when executing software.
  • the base station reader component 199 may be configured to output IoT data for an IoT device via an IoT communication channel in a first directional slot of a TDD system.
  • the base station reader component 199 may also be configured to obtain, in response to the IoT data and via the IoT communication channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the base station reader component 199 may be configured to output IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information.
  • the base station reader component 199 may also be configured to obtain an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the base station reader component 199 may be within one or more processors of one or more of the CU 2010, DU 2030, and the RU 2040.
  • the base station reader component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.
  • the network entity 2002 may include a variety of components configured for various functions.
  • the base station reader component 199 may include one or more hardware components that perform each of the blocks of the algorithm in the flowcharts of FIGs. 15, 16, 17, and/or 18.
  • the network entity 2002 includes means for outputting IoT data for an IoT device via an IoT communication channel in a first directional slot of a TDD system.
  • the example network entity 2002 also includes means for obtaining, in response to the IoT data and via the IoT communication channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the example network entity 2002 also includes means for outputting a resource allocation to a UE in a third directional slot of the TDD system, the resource allocation including one or more resources associated with at least one uplink slot, the third directional slot being a second downlink slot and occurring prior to the first directional slot in a time domain.
  • the example network entity 2002 also includes means for obtaining the IoT data and information related to the IoT device from a UE.
  • the example network entity 2002 includes means for outputting IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information.
  • the example network entity 2002 also includes means for obtaining an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • the example network entity 2002 also includes means for outputting a resource allocation to a UE in a third directional slot of the TDD system, the resource allocation including one or more resources associated with at least one uplink slot, the third directional slot being a second downlink slot and occurring prior to the first directional slot in a time domain.
  • the means may be the base station reader component 199 of the network entity 2002 configured to perform the functions recited by the means.
  • the network entity 2002 may include the TX processor 316, the RX processor 370, and the controller/processor 375.
  • the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.
  • FIG. 21 is a flowchart 2100 of a method of wireless communication.
  • the method may be performed by an IoT device (e.g., the IoT device 106, and/or an apparatus 2204 of FIG. 22) .
  • the method may facilitate improving communication performance by improving IoT communication in a TDD system with half-duplex devices and/or full-duplex devices.
  • the IoT device receives a command via an IoT communication channel, as described in connection with the IoT command 716 of FIG. 7 and/or the IoT command 1116 of FIG. 11.
  • 2102 may be performed by a cellular RF transceiver 2222 /the IoT tag component 197 of the apparatus 2204 of FIG. 22.
  • the IoT device receives timing information via the IoT communication channel, the timing information related to a TDD system, as described in connection with the timing information 714 and/or the timing information 718 of FIG. 7, and/or the timing information 1118 of FIG. 11.
  • 2104 may be performed by the cellular RF transceiver 2222 /the IoT tag component 197 of the apparatus 2204 of FIG. 22.
  • the timing information may include at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • the IoT device transmits an IoT response signal based on the command and the timing information, as described in connection with the feedback 722 of FIG. 7 and/or the feedback 1122 of FIG. 11.
  • 2106 may be performed by the cellular RF transceiver 2222 /the IoT tag component 197 of the apparatus 2204 of FIG. 22.
  • the IoT response signal may include a backscatter signal.
  • FIG. 22 is a diagram 2200 illustrating an example of a hardware implementation for an apparatus 2204.
  • the apparatus 2204 may be an IoT device, a component of an IoT device, or may implement IoT device functionality.
  • the apparatus 2204 may include one or more transceivers (e.g., a cellular RF transceiver 2222) .
  • the apparatus 2204 may further include an application processor 2206 coupled to a secure digital (SD) card 2208.
  • the application processor 2206 may include on-chip memory 2206'.
  • the apparatus 2204 may further include one or more sensor modules 2218 (e.g., barometric pressure sensor /altimeter; motion sensor such as inertial management unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning) , additional memory modules 2226, and/or a power supply 2230.
  • sensor modules 2218 e.g., barometric pressure sensor /altimeter; motion sensor such as inertial management unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning
  • IMU inertial management unit
  • RADAR radio assisted detection and ranging
  • the application processor 2206 may communicate with the UE 104 and/or with an RU associated with a network entity 2202 through transceiver (s) (e.g., the cellular RF transceiver 2222) via one or more antennas 2280.
  • the application processor 2206 may include a computer-readable medium /memory, such as the on-chip memory 2206'.
  • the additional memory modules 2226 may also be considered a computer-readable medium /memory. Each of the on-chip memory 2206' and/or the additional memory modules 2226 may be non-transitory.
  • the application processor 2206 may be responsible for general processing, including the execution of software stored on the computer-readable medium /memory.
  • the software when executed by the application processor 2206, causes the application processor 2206 to perform the various functions described supra.
  • the computer-readable medium /memory may also be used for storing data that is manipulated by the application processor 2206 when executing software.
  • the application processor 2206 may be a component of the IoT device 106 of FIG. 1 and may include memory and/or at least one of a TX processor, an RX processor, and a controller/processor.
  • the apparatus 2204 may be a processor chip (modem and/or application) and include just the application processor 2206, and in another configuration, the apparatus 2204 may be the IoT device 106 and include the additional modules of the apparatus 2204.
  • the IoT tag component 197 is configured to receive a command via an IoT communication channel.
  • the IoT tag component 197 may also be configured to receive timing information via the IoT communication channel, the timing information including information related to a TDD system. Additionally, the IoT tag component 197 may be configured to transmit an IoT response signal based on the command and the timing information.
  • the IoT tag component 197 may be within the application processor 2206.
  • the IoT tag component 197 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof.
  • the apparatus 2204 may include a variety of components configured for various functions.
  • the IoT tag component 197 may include one or more hardware components that perform each of the blocks of the algorithm in the flowchart of FIG. 21.
  • the apparatus 2204 includes means for receiving a command via an IoT communication channel.
  • the example apparatus 2204 also includes means for receiving timing information via the IoT communication channel, the timing information including information related to a TDD system.
  • the example apparatus 2204 also includes means for transmitting an IoT response signal based on the command and the timing information.
  • the means may be the IoT tag component 197 of the apparatus 2204 configured to perform the functions recited by the means.
  • the apparatus 2204 may include the TX processor 368, the RX processor 356, and the controller/process or 359.
  • the means may be the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the means.
  • the aspects presented herein may enable a wireless node, such as a UE or a network node, to communicate with an IoT device via a TDD system, which may facilitate improving communication performance, for example, by improving the likelihood of IoT communications being successfully transmitted and received.
  • a wireless node such as a UE or a network node
  • aspects disclosed herein provide techniques for facilitating IoT communication between an IoT reader and an IoT tag using a TDD.
  • the techniques disclosed herein include the IoT readerproviding timing information with a command that is received by the IoT tag.
  • the timing information may provide information to the IoT tag to cause the IoT tag to delay providing feedback to the IoT reader while the IoT reader is operating in a transmitter state.
  • the timing information may include information indicating to the IoT tag when the IoT reader is transitioning from the transmitter state to the receiver state.
  • the IoT tag may use the timing information to determine when to transmit the feedback to the IoT reader.
  • the techniques disclosed herein include the IoT readerusing a relay device to relay a command to the IoT tag.
  • the IoT reader may output IoT data that is received by the relay device.
  • the IoT data may include a tag identifier of the IoT tag and may also include the command.
  • the relay device may use the IoT data to transmit the command to the IoT tag.
  • the relay device may transmit the command to the IoT tag associated with the tag identifier included in the IoT data.
  • the IoT reader may transmit the IoT data to the relay device using a Uu link.
  • the relay device may use IoT communication channels to transmit the command to the IoT tag.
  • Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C.
  • combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C.
  • Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements.
  • a first apparatus receives data from or transmits data to a second apparatus
  • the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses.
  • All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.
  • the words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”
  • the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like.
  • the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
  • Aspect 1 is a method of wireless communication at a wireless node, including: outputting IoT data for an IoT device via an IoT communication channel in a first directional slot of a TDD system; and obtaining, in response to the IoT data and via the IoT communication channel from the IoT device, an IoT response signal in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • Aspect 2 is the method of aspect 1, further including that the wireless node includes a UE or an IoT reader, and the first directional slot includes a first uplink slot.
  • Aspect 3 is the method of any of aspects 1 and 2, further including: transmitting an IoT communication request to a network node in a third directional slot of the TDD system, the third directional slot being a second uplink slot and occurring prior to the first directional slot in a time domain; and receiving a resource allocation associated with the first directional slot and the sec ond directional slot in a fourth directional slot of the TDD system, the resource allocation being based on the IoT communication request.
  • Aspect 4 is the method of any of aspects 1 to 3, further including that the IoT data includes at least one command.
  • Aspect 5 is the method of any of aspects 1 to 4, further including that the IoT data further includes timing information including at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • Aspect 6 is the method of any of aspects 1 to 5, further including that the UE is a first UE in communication with a second UE via a direct communication interface, the first directional slot is associated with a first duration of the first uplink slot, and the second directional slot is associated with a second duration of the first uplink slot.
  • Aspect 7 is the method of any of aspects 1 to 6, further including: obtaining the IoT data and information related to the IoT device from a network node.
  • Aspect 8 is the method of aspect 1, further including that the wireless node includes a network node or an IoT reader, the first directional slot includes a first downlink slot, and the second directional slot includes a first uplink slot.
  • Aspect 9 is the method of any of aspects 1 and 8, further including: outputting a resource allocation to a UE in a third directional slot of the TDD system, the resource allocation including one or more resources associatedwith at least one uplink slot, the third directional slot being a second downlink slot and occurring prior to the first directional slot in a time domain.
  • Aspect 10 is the method of any of aspects 1, 8, and 9, further including that the IoT data includes timing information and a command, wherein the timing information includes at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • Aspect 11 is the method of any of aspects 1 and 8 to 10, further including: obtaining the IoT data and information related to the IoT device from a UE.
  • Aspect 12 is an apparatus for wireless communication at a wireless node including at least one processor coupled to a memory and configured to implement any of aspects 1 to 11.
  • the apparatus of aspect 12 further includes at least one antenna coupled to the at least one processor.
  • the apparatus of aspect 12 or 13 further includes at least one transceiver coupled to the at least one processor.
  • Aspect 15 is an apparatus for wireless communication including means for implementing any of aspects 1 to 11.
  • the apparatus of aspect 15 further includes at least one antenna coupled to the means to perform the method of any of aspects 1 to 11.
  • the apparatus of aspect 15 or 16 further includes at least one transceiver coupled to the means to perform the method of any of aspects 1 to 1.
  • Aspect 18 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 1 to 11.
  • Aspect 19 is a method of wireless communication at a wireless node, including: outputting IoT data associated with an IoT device via a physical channel in a first directional slot of a TDD system, the IoT data including a command and IoT device information; and obtaining an IoT response signal in response to the command in a second directional slot of the TDD system, the second directional slot being different than the first directional slot.
  • Aspect 20 is the method of aspect 19, further including that the wireless node includes a UE or an IoT reader, the first directional slot includes a first uplink slot, and the physical channel includes a PUCCH.
  • Aspect 21 is the method of any of aspects 19 and 20, further including: transmitting anIoT communication request to a network node in a third directional slot of the TDD system, the third directional slot being a second uplink slot and occurring prior to the first directional slot in a time domain; and receiving a resource allocation associated with the first directional slot and the second directional slot in a fourth directional slot of the TDD system, the resource allocation being based on the IoT communication request.
  • Aspect 22 is the method of any of aspects 19 and 20, further including that the UE is a first UE in communication with a second UE via a direct communication interface, the first directional slot is associated with a first duration of the first uplink slot, and the second directional slot is associated with a second duration of the first uplink slot.
  • Aspect 23 is the method of aspect 19, further including that the wireless node includes a network node or an IoT reader, the first directional slot includes a first downlink slot, the second directional slot includes a first uplink slot, and the physical channel includes a PDSCH.
  • Aspect 24 is the method of any of aspects 19 and 23, further including: outputting a resource allocation to a UE in a third directional slot of the TDD system, the resource allocation including one or more resources associatedwith at least one uplink slot, the third directional slot being a second downlink slot and occurring prior to the first directional slot in a time domain.
  • Aspect 25 is an apparatus for wireless communication at a wireless node including at least one processor coupled to a memory and configured to implement any of aspects 19 to 24.
  • the apparatus of aspect25 further includes atleast one antenna coupled to the at least one processor.
  • the apparatus of aspect 25 or 26 further includes at least one transceiver coupled to the at least one processor.
  • Aspect 28 is an apparatus for wireless communication including means for implementing any of aspects 19 to 24.
  • the apparatus of aspect28 further includes atleast one antenna coupled to the means to perform the method of any of aspects 19 to 24.
  • the apparatus of aspect 28 or 29 further includes at least one transceiver coupled to the means to perform the method of any of aspects 19 to 24.
  • Aspect 31 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 19 to 24.
  • Aspect 32 is a method of wireless communication at an IoT device, including: receiving a command via an IoT communication channel; receiving timing information via the IoT communication channel, the timing information including information related to a TDD system; and transmitting an IoT response signal based on the command and the timing information.
  • Aspect 33 is the method of aspect 32, further including that the IoT response signal includes a backscattered signal.
  • Aspect 34 is the method of any of aspects 32 and 33, further including that the timing information includes at least one of: a start time, a window duration, the start time and an end time, an IoT symbol duration, and a quantity of IoT symbols.
  • Aspect 35 is an apparatus for wireless communication at a UE including at least one processor coupled to a memory and configured to implement any of aspects 32 to 34.
  • the apparatus of aspect 35 further includes at least one antenna coupled to the at least one processor.
  • the apparatus of aspect 35 or 36 further includes at least one transceiver coupled to the at least one processor.
  • Aspect 38 is an apparatus for wireless communication including means for implementing any of aspects 32 to 34.
  • the apparatus of aspect 38 further includes at least one antenna coupled to the means to perform the method of any of aspects 32 to 34.
  • the apparatus of aspect 38 or 39 further includes at least one transceiver coupled to the means to perform the method of any of aspects 32 to 34.
  • Aspect 41 is a non-transitory computer-readable storage medium storing computer executable code, where the code, when executed, causes a processor to implement any of aspects 32 to 34.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un appareil, des procédés et des supports lisibles par ordinateur pour faciliter une communication IdO. Les aspects présentés ici peuvent permettre à un nœud sans fil, tel qu'un UE ou un nœud de réseau, de communiquer avec un dispositif IdO par l'intermédiaire d'un système TDD, ce qui peut faciliter l'amélioration des performances de communication, par exemple, en améliorant la probabilité que des communications IdO soient transmises et reçues avec succès. Un procédé donné à titre d'exemple pour une communication sans fil au niveau d'un nœud de fils consiste à délivrer en sortie des données IdO pour un dispositif IdO par l'intermédiaire d'un canal de communication IdO dans un premier créneau directionnel d'un système TDD. Le procédé donné à titre d'exemple consiste également à obtenir, en réponse aux données IdO et par l'intermédiaire du canal de communication IdO à partir du dispositif IdO, un signal de réponse IdO dans un second créneau directionnel du système TDD, le second créneau directionnel étant différent du premier créneau directionnel.
PCT/CN2022/086977 2022-04-15 2022-04-15 Techniques de communication bistatique pour dispositifs ido WO2023197281A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/086977 WO2023197281A1 (fr) 2022-04-15 2022-04-15 Techniques de communication bistatique pour dispositifs ido

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/086977 WO2023197281A1 (fr) 2022-04-15 2022-04-15 Techniques de communication bistatique pour dispositifs ido

Publications (1)

Publication Number Publication Date
WO2023197281A1 true WO2023197281A1 (fr) 2023-10-19

Family

ID=88328603

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/086977 WO2023197281A1 (fr) 2022-04-15 2022-04-15 Techniques de communication bistatique pour dispositifs ido

Country Status (1)

Country Link
WO (1) WO2023197281A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109802812A (zh) * 2017-11-17 2019-05-24 夏普株式会社 Ack/nack资源分配方法以及相应的用户设备和基站
WO2020074343A1 (fr) * 2018-10-08 2020-04-16 Nokia Technologies Oy Procédé pour la coexistence de l'internet des objets et d'une nouvelle radio
WO2021007711A1 (fr) * 2019-07-12 2021-01-21 Lenovo (Beijing) Limited Procédé et appareil d'indication de configuration de liaison montante-liaison descendante de tdd
CN112514437A (zh) * 2018-08-10 2021-03-16 高通股份有限公司 动态资源复用

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109802812A (zh) * 2017-11-17 2019-05-24 夏普株式会社 Ack/nack资源分配方法以及相应的用户设备和基站
CN112514437A (zh) * 2018-08-10 2021-03-16 高通股份有限公司 动态资源复用
WO2020074343A1 (fr) * 2018-10-08 2020-04-16 Nokia Technologies Oy Procédé pour la coexistence de l'internet des objets et d'une nouvelle radio
WO2021007711A1 (fr) * 2019-07-12 2021-01-21 Lenovo (Beijing) Limited Procédé et appareil d'indication de configuration de liaison montante-liaison descendante de tdd

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Passive IoT for 5G Advanced", 3GPP TSG RAN REL-18 WORKSHOP RWS-210453, 8 June 2021 (2021-06-08), XP052027039 *

Similar Documents

Publication Publication Date Title
WO2023220850A1 (fr) Seuils multiples pour systèmes de communication avec dispositifs de communication basés sur la rétrodiffusion
WO2023197281A1 (fr) Techniques de communication bistatique pour dispositifs ido
WO2023240585A1 (fr) Configuration d'informations de synchronisation pour iot passif
WO2024020915A1 (fr) Communication iot passive
US20240049241A1 (en) Type 0 resource allocation in sub-band full-duplex slots
WO2024016105A1 (fr) Configuration d'intervalle de mesure de décalage temporel
WO2024020839A1 (fr) Amélioration de rar pour systèmes multi-trp inter-cellules
US20240049199A1 (en) Sub-band full duplex (sbfd) allocation with disjoint sub-bands
US20240172305A1 (en) Multi carrier aggregation addition and activation timeline optimization
US20240137755A1 (en) Steering ue capability information based on network capability features
WO2024065652A1 (fr) Indication dynamique de partage de tci unifiés pour coreset dans une opération mtrp
US20240155465A1 (en) Structure of minimum si
WO2024065237A1 (fr) Détermination de dernières dci pour des dci d'indication de tci
WO2023212910A1 (fr) Lp-wus pour communications de rétrodiffusion
US20240064704A1 (en) Slot type dependent vrb-to-prb interleaving in full duplex networks
US20240147430A1 (en) Adaptive configured grant allocation parameters for energy harvesting devices and xr applications
WO2023220846A1 (fr) Transmission d'énergie et d'informations sans fil
US20240137788A1 (en) Fr1 intra-band ca optimization
US20230388043A1 (en) Channel oriented modulation selection for improved spectral efficiency
WO2024026607A1 (fr) Maintien de l'intégrité d'authentification de signaux à partir de dispositifs de communication basés sur la rétrodiffusion
WO2024065602A1 (fr) Bwp et cellule par défaut pour un rs dans un état tci
US20240137913A1 (en) Signaling to indicate flexible uplink or downlink subbands
US20230328719A1 (en) Semi-persistent waveform switching for uplink
US20220369351A1 (en) Indication of scheduling delays for a shared channel with bwp switching in higher frequency bands
WO2024092746A1 (fr) Signalisation pour informer un noeud de réseau d'une liaison d'équipement utilisateur à équipement utilisateur entre un équipement utilisateur distant et un équipement utilisateur relais

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22936929

Country of ref document: EP

Kind code of ref document: A1