Transmission and reception between a reader and a device

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Apparatuses and methods for transmission and reception between a reader and an IoT device. A method includes receiving a physical reader-to-device channel (PRDCH) from the reader. The PRDCH includes a MAC header and a payload. The MAC header indicates a type of reader-to-device (R2D) message and information related to determining a size of the payload. The MAC header and the payload are jointly attached with a single set of CRC bits. The method includes determining, based on reception of the PRDCH, a transmission of a physical device-to-reader channel (PDRCH) to the reader including determining a type of device-to-reader (D2R) message, a size of a payload of the D2R message, a length of the PDRCH transmission, and a transmission timing of the PDRCH. The method includes transmitting the PDRCH to the reader.

Description

TRANSMISSION AND RECEPTION BETWEEN A READER AND A DEVICE

[0001] The present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure is related to apparatuses and methods for transmission and reception between a reader and a device.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE (User Equipment) Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] The present disclosure relates to transmission and reception between a reader and a device.

[0009] In an embodiment, a method for an Internet of Things (IoT) device to communicate with a reader is provided. The method may include receiving a physical reader-to-device channel (PRDCH) from the reader. The PRDCH may include a medium access control (MAC) header and a payload. The MAC header may indicate (i) a type of reader-to-device (R2D) message and (ii) information related to determining a size of the payload. The MAC header and the payload may be jointly attached with a single set of cyclic redundancy check (CRC) bits. The method may include determining, based on reception of the PRDCH, a transmission of a physical device-to-reader channel (PDRCH) to the reader including determining a type of device-to-reader (D2R) message, a size of a payload of the D2R message, a length of the PDRCH transmission, and a transmission timing of the PDRCH. The method may include transmitting the PDRCH to the reader.

[0010] In an embodiment, an IoT device is provided. The IoT device may include a transceiver and processing circuitry connected to the transceiver, wherein the processing circuitry may be configured to receive a PRDCH from a reader. The PRDCH may include a MAC header and a payload. The MAC header may indicate a type of R2D message and information related to determining a size of the payload. The MAC header and the payload may be jointly attached with a single set of CRC bits. The processing circuitry may be configured to determine, based on reception of the PRDCH, a transmission of a PDRCH to the reader, including to determine a type of D2R message, a size of a payload of the D2R message, a length of the PDRCH transmission, and a transmission timing of the PDRCH. The processing circuitry may be configured to transmit the PDRCH to the reader.

[0011] In an embodiment, a reader is provided. The reader may include a transceiver and processing circuitry connected to the transceiver, wherein the processing circuitry may be configured to transmit a PRDCH to an IoT device. The PRDCH may include a MAC header and a payload. The MAC header may indicate a type of R2D message and information related to determining a size of the payload. The MAC header and the payload may be jointly attached with a single set of CRC bits. The processing circuitry may be configured to determine, based on transmission of the PRDCH, a reception of a PDRCH to the reader, including to determine a type of device-to-reader (D2R) message, a size of a payload of the D2R message, a length of the PDRCH reception, and a reception timing of the PDRCH. The processing circuitry may be configured to receive the PDRCH from the IoT device.

[0012] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0013] FIG. 1 illustrates an example wireless network according to an embodiment of the present disclosure;

[0014] FIG. 2 illustrates an example gNodeB (gNB) according to an embodiment of the present disclosure;

[0015] FIG. 3 illustrates an example user equipment (UE) according to an embodiment of the present disclosure;

[0016] FIGS. 4A and 4B illustrate an example of a wireless transmit and receive paths according to an embodiment of the present disclosure;

[0017] FIG. 5 illustrates an example of a transmitter structure using orthogonal frequency-division multiplexing (OFDM) according to an embodiment of the present disclosure;

[0018] FIG. 6 illustrates an example of a receiver structure using OFDM according to an embodiment of the present disclosure;

[0019] FIG. 7 illustrates an example encoding structure for a downlink control information (DCI) format according to an embodiment of the present disclosure;

[0020] FIG. 8 illustrates an example decoding structure for a downlink control information (DCI) format according to an embodiment of the present disclosure;

[0021] FIG. 9 illustrates a diagram of an example type-1 backscatter structure for internet of thing(s) (IoT) devices according to an embodiment of the present disclosure;

[0022] FIG. 10 illustrates a diagram of an example impedance matching circuit according to an embodiment of the present disclosure;

[0023] FIG. 11 illustrates a diagram of an example type-2a backscatter structure for IoT devices according to an embodiment of the present disclosure;

[0024] FIG. 12 illustrates a diagram of an example type-2a backscatter structure for IoT devices according to an embodiment of the present disclosure;

[0025] FIG. 13 illustrates a diagram of an example type-2a backscatter structure for IoT devices according to an embodiment of the present disclosure;

[0026] FIG. 14 illustrates a diagram of an example type-2b active structure for IoT devices according to an embodiment of the present disclosure;

[0027] FIG. 15 illustrates a diagram of an example type-2b active structure for IoT devices according to an embodiment of the present disclosure;

[0028] FIG. 16 illustrates a diagram of an example type-2b active structure for IoT devices according to an embodiment of the present disclosure;

[0029] FIG. 17 illustrates an example system for device to reader (D2R) / reader to device (R2D) transmission involving an intermediate node according to an embodiment of the present disclosure;

[0030] FIG. 18 illustrates a flowchart of an example device procedure for receiving physical reader to device channel (PRDCH) according to an embodiment of the present disclosure;

[0031] FIG. 19 illustrates a diagram of an example PRDCH / physical device to reader channel (PDRCH) transmission architecture according to an embodiment of the present disclosure;

[0032] FIG. 20 illustrates a flowchart of an example device procedure for determining the end of a PRDCH reception according to an embodiment of the present disclosure;

[0033] FIG. 21 illustrates a flowchart of an example reader procedure for determining the end of a PDRCH reception according to an embodiment of the present disclosure; and

[0034] FIG. 22 illustrates a flowchart of an example device procedure for determining PRDCH transmission timing according to an embodiment of the present disclosure.

[0035] Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," as well as derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with," as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term "controller" means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, "at least one of: A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0036] Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A "non-transitory" computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0037] Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.

[0038] Wireless communication has been one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeded five billion and continues to grow quickly. The demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, "note pad" computers, net books, eBook readers, and machine type of devices. In order to meet the high growth in mobile data traffic and support new applications and deployments, improvements in radio interface efficiency and coverage are of paramount importance. To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G communication systems have been developed and are currently being deployed.

[0039] FIGS. 1-22, discussed below, and the various, non-limiting embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0040] To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. The 5G / NR communication system is implemented in higher frequency (mmWave) bands, e.g., 28 GHz or 60GHz bands, so as to accomplish higher data rates or in lower frequency bands, such as 6 GHz, to enable robust coverage and mobility support. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G / NR communication systems.

[0041] In addition, in 5G / NR communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancelation, radio access technology (RAT)-dependent positioning and the like.

[0042] The discussion of 5G systems and frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems, or the frequency bands associated therewith, and embodiments of the present disclosure may be utilized in connection with any frequency band. For example, aspects of the present disclosure may also be applied to deployment of 5G communication systems, 6G or even later releases which may use terahertz (THz) bands.

[0043] The following documents and standards descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: [REF1] 3GPP TS 38.211 v17.5.0, "NR; Physical channels and modulation;" [REF2] 3GPP TS 38.212 v17.5.0, "NR; Multiplexing and channel coding;" [REF3] 3GPP TS 38.213 v17.6.0, "NR; Physical layer procedures for control;" [REF4] 3GPP TS 38.214 v17.6.0, "NR; Physical layer procedures for data;" [REF5] 3GPP TS 38.331 v17.5.0, "NR; Radio Resource Control (RRC) protocol specification;" and [REF6] 3GPP TS 38.321 v17.5.0, "NR; Medium Access Control (MAC) protocol specification."

[0044] FIGS. 1-3 below describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency-division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGS. 1-3 are not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0045] FIG. 1 illustrates an example wireless network 100 according to an embodiment of the present disclosure. The embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 could be used without departing from the scope of this disclosure.

[0046] As shown in FIG. 1, the wireless network 100 may include a gNB 101 (e.g., base station, BS), a gNB 102, and a gNB 103. The gNB 101 may communicate with the gNB 102 and the gNB 103. The gNB 101 may also communicate with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0047] The gNB 102 may provide wireless broadband access to the network 130 for a first plurality of user equipments (UEs) within a coverage area 120 of the gNB 102. The first plurality of UEs may include a UE 111, which may be located in a small business; a UE 112, which may be located in an enterprise; a UE 113, which may be a WiFi hotspot; a UE 114, which may be located in a first residence; a UE 115, which may be located in a second residence; and a UE 116, which may be a mobile device, such as a cell phone, a wireless laptop, a wireless PDA, or the like. The gNB 103 may provide wireless broadband access to the network 130 for a second plurality of UEs within a coverage area 125 of the gNB 103. The second plurality of UEs may include the UE 115 and the UE 116. In an embodiment, one or more of the gNBs 101-103 may communicate with each other and with the UEs 111-116 using 5G / NR, long term evolution (LTE), long term evolution-advanced (LTE-A), WiMAX, WiFi, or other wireless communication techniques.

[0048] Depending on the network type, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as transmit point (TP), transmit-receive point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., 5G / NR 3rdgeneration partnership project (3GPP) NR, long term evolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For the sake of convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Also, depending on the network type, the term "user equipment" or "UE" can refer to any component such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receive point," or "user device." For the sake of convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless equipment that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer or vending machine).

[0049] The dotted lines may show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions.

[0050] As described in more detail below, one or more of the UEs 111-116 may include circuitry, programing, or a combination thereof for supporting transmission and reception between a reader and a device. In an embodiment, one or more of the gNBs 101-103 may include circuitry, programing, or a combination thereof to provide for transmission and reception between a reader and a device.

[0051] Although FIG. 1 illustrates one example of a wireless network, various changes may be made to FIG. 1. For example, the wireless network 100 could include any number of gNBs and any number of UEs in any suitable arrangement. Also, the gNB 101 could communicate directly with any number of UEs and provide those UEs with wireless broadband access to the network 130. Similarly, each gNB 102-103 could communicate directly with the network 130 and provide UEs with direct wireless broadband access to the network 130. Further, the gNBs 101, 102, and / or 103 could provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0052] FIG. 2 illustrates an example gNB 102 according to an embodiment of the present disclosure. The embodiment of the gNB 102 illustrated in FIG. 2 is for illustration only, and the gNBs 101 and 103 of FIG. 1 could have the same or similar configuration. However, gNBs come in a wide variety of configurations, and FIG. 2 does not limit the scope of this disclosure to any particular implementation of a gNB.

[0053] As shown in FIG. 2, the gNB 102 may include multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, memory 230, and a backhaul or network interface 235.

[0054] The transceivers 210a-210n may receive, from the antennas 205a-205n, incoming radio frequency (RF) signals, such as signals transmitted by UEs in the wireless network 100. The transceivers 210a-210n may down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals may be processed by receive (RX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0055] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225 may receive analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry may encode, multiplex, and / or digitize the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n may up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0056] The controller / processor 225 can include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 could control the reception of uplink (UL) channel signals and the transmission of downlink (DL) channel signals by the transceivers 210a-210n in accordance with well-known principles. The controller / processor 225 could support additional functions as well, such as more advanced wireless communication functions. For instance, the controller / processor 225 could support beam forming or directional routing operations in which outgoing / incoming signals from / to multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. Any of a wide variety of other functions could be supported in the gNB 102 by the controller / processor 225.

[0057] The controller / processor 225 may also be capable of executing programs and other processes resident in the memory 230, such as providing for transmission and reception between a reader and a device. The controller / processor 225 can move data into or out of the memory 230 as required by an executing process.

[0058] The controller / processor 225 may also be coupled to the backhaul or network interface 235. The backhaul or network interface 235 may allow the gNB 102 to communicate with other devices or systems over a backhaul connection or over a network. The backhaul or network interface 235 could support communications over any suitable wired or wireless connection(s). For example, when the gNB 102 is implemented as part of a cellular communication system (such as one supporting 5G / NR, LTE, or LTE-A), the backhaul or network interface 235 could allow the gNB 102 to communicate with other gNBs over a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the backhaul or network interface 235 could allow the gNB 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The backhaul or network interface 235 may include any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or transceiver.

[0059] The memory 230 may be coupled to the controller / processor 225. Part of the memory 230 could include a RAM, and another part of the memory 230 could include a Flash memory or other ROM.

[0060] Although FIG. 2 illustrates one example of gNB 102, various changes may be made to FIG. 2. For example, the gNB 102 could include any number of each component shown in FIG. 2. Also, various components in FIG. 2 could be combined, further subdivided, or omitted and additional components could be added according to particular needs.

[0061] FIG. 3 illustrates an example UE 116 according to an embodiment of the present disclosure. The embodiment of the UE 116 illustrated in FIG. 3 is for illustration only, and the UEs 111-115 of FIG. 1 could have the same or similar configuration. However, UEs come in a wide variety of configurations, and FIG. 3 does not limit the scope of this disclosure to any particular implementation of a UE.

[0062] As shown in FIG. 3, the UE　116 may include antenna(s) 305, a transceiver(s) 310, and a microphone 320. The UE　116 may also include a speaker 330, a processor 340, an input / output (I / O) interface 345, an input 350, a display 355, and memory 360. The memory 360 may include an operating system (OS) 361 and one or more applications 362.

[0063] The transceiver(s) 310 may receive from the antenna(s) 305, an incoming RF signal transmitted by a gNB of the wireless network 100. The transceiver(s) 310 may down-convert the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal may be processed by RX processing circuitry in the transceiver(s) 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry may send the processed baseband signal to the speaker 330 (such as for voice data) or may be processed by the processor 340 (such as for web browsing data).

[0064] TX processing circuitry in the transceiver(s) 310 and / or processor 340 may receive analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry may encode, multiplex, and / or digitize the outgoing baseband data to generate a processed baseband or IF signal. The transceiver(s) 310 may up-convert the baseband or IF signal to an RF signal that is transmitted via the antenna(s) 305.

[0065] The processor 340 can include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 in order to control the overall operation of the UE 116. For example, the processor 340 could control the reception of DL channel signals and the transmission of UL channel signals by the transceiver(s) 310 in accordance with well-known principles. In an embodiment, the processor 340 may include at least one microprocessor or microcontroller.

[0066] The processor 340 may also be capable of executing other processes and programs resident in the memory 360. For example, the processor 340 may execute processes to support transmission and reception between a reader and a device as described in an embodiment of the present disclosure. The processor 340 can move data into or out of the memory 360 as required by an executing process. In an embodiment, the processor 340 may be configured to execute the applications 362 based on the OS 361 or in response to signals received from gNBs or an operator. The processor 340 may also be coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 may be the communication path between these accessories and the processor 340.

[0067] The processor 340 may also be coupled to the input 350, which includes, for example, a touchscreen, keypad, etc., and the display 355. The operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites.

[0068] The memory 360 may be coupled to the processor 340. Part of the memory 360 could include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0069] Although FIG. 3 illustrates one example of UE 116, various changes may be made to FIG. 3. For example, various components in FIG. 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. For example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). For example, the transceiver(s) 310 may include any number of transceivers and signal processing chains and may be connected to any number of antennas. Also, while FIG. 3 illustrates the UE 116 configured as a mobile telephone or smartphone, UEs could be configured to operate as other types of mobile or stationary devices.

[0070] FIG. 4A and FIG. 4B illustrate an example of wireless transmit and receive paths 400 and 450, respectively, according to an embodiment of the present disclosure. For example, a transmit path 400 may be described as being implemented in a gNB (such as gNB 102), while a receive path 450 may be described as being implemented in a UE (such as UE 116). However, it will be understood that the receive path 450 can be implemented in a gNB and that the transmit path 400 can be implemented in a UE. In an embodiment, the transmit path 400 may be configured for transmission between a reader and a device as described in an embodiment of the present disclosure. In an embodiment, the receive path may be configured for reception between a reader and a device as described in an embodiment of the present disclosure.

[0071] As illustrated in FIG. 4A, the transmit path 400 may include a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, a size N Inverse Fast Fourier Transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an up-converter (UC) 430. The receive path 450 may include a down-converter (DC) 455, a remove cyclic prefix block 460, a S-to-P block 465, a size N Fast Fourier Transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

[0072] In the transmit path 400, the channel coding and modulation block 405 may receive a set of information bits, apply coding (such as a low-density parity check (LDPC) coding), and modulate the input bits (such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulation symbols. The serial-to-parallel block 410 may convert (such as de-multiplex) the serial modulated symbols to parallel data in order to generate N parallel symbol streams, where N is the IFFT / FFT size used in the gNB 102 and the UE 116. The size N IFFT block 415 may perform an IFFT operation on the N parallel symbol streams to generate time-domain output signals. The parallel-to-serial block 420 may convert (such as multiplex) the parallel time-domain output symbols from the size N IFFT block 415 in order to generate a serial time-domain signal. The add cyclic prefix block 425 may insert a cyclic prefix to the time-domain signal. The up-converter 430 may modulate (such as up-convert) the output of the add cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at a baseband before conversion to the RF frequency.

[0073] As illustrated in FIG. 4B, the down-converter 455 may down-convert the received signal to a baseband frequency, and the remove cyclic prefix block 460 may remove the cyclic prefix to generate a serial time-domain baseband signal. The serial-to-parallel block 465 may convert the time-domain baseband signal to parallel time-domain signals. The size N FFT block 470 may perform an FFT algorithm to generate N parallel frequency-domain signals. The parallel-to-serial block 475 may convert the parallel frequency-domain signals to a sequence of modulated data symbols. The channel decoding and demodulation block 480 may demodulate and decode the modulated symbols to recover the original input data stream.

[0074] Each of the gNBs 101-103 may implement a transmit path 400 that is analogous to transmitting in the downlink to UEs 111-116 and may implement a receive path 450 that is analogous to receiving in the uplink from UEs 111-116. Similarly, each of UEs 111-116 may implement a transmit path 400 for transmitting in the uplink to gNBs 101-103 and may implement a receive path 450 for receiving in the downlink from gNBs 101-103.

[0075] Each of the components in FIGS. 4A and 4B can be implemented using only hardware or using a combination of hardware and software / firmware. For example, at least some of the components in FIGS. 4A and 4B may be implemented in software, while other components may be implemented by configurable hardware or a mixture of software and configurable hardware. For instance, the FFT block 470 and the IFFT block 415 may be implemented as configurable software algorithms, where the value of size N may be modified according to the implementation.

[0076] Furthermore, although described as using FFT and IFFT, this is by way of illustration only and should not be construed to limit the scope of this disclosure. Other types of transforms, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be appreciated that the value of the variable N may be any integer number (such as 1, 2, 3, 4, or the like) for DFT and IDFT functions, while the value of the variable N may be any integer number that is a power of two (such as 1, 2, 4, 8, 16, or the like) for FFT and IFFT functions.

[0077] Although FIGS. 4A and 4B illustrate examples of wireless transmit and receive paths 400 and 450, respectively, various changes may be made to FIGS. 4A and 4B. For example, various components in FIGS. 4A and 4B can be combined, further subdivided, or omitted and additional components can be added according to particular needs. Also, FIGS. 4A and 4B are meant to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architectures can be used to support wireless communications in a wireless network.

[0078] Internet of things (IoT) devices may include ambient-power-enabled IoT (A-IoT) devices, which are ultra-low-complexity devices with very small form factor and low-cost design that operate without a common battery that can be manually replaced or recharged. Instead, A-IoT devices can be battery-less or with a small battery (such as a small capacitor) that operate based on energy harvesting from RF waveforms or other ambient energy sources. Regarding the limited size and complexity required by practical applications for battery-less devices with no energy storage capability or devices with limited energy storage that do not need to be replaced or recharged manually, the output power of energy harvester is typically from 1μW to a few hundreds of μW.

[0079] In an embodiment throughout the disclosure, a UE (e.g., the UE 116) or a device may be referred to as an A-IoT device or an A-IoT UE based on energy harvesting with ultra-low complexity and power consumption and for low-end IoT applications. For example, the UE may have limited (or no) energy storage or battery capability (e.g., a capacitor), such as an energy storage unit for amplification of receptions at the UE or transmission by the UE, or for other UE operations, such as power-on, warm-up, memory, internal processing, and so on, or operating with backscattering communication.

[0080] An A-IoT device can be an IoT device that satisfies one or more of the following (or variations thereof):

[0081] - powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor) and the energy is provided through the harvesting of radio waves (including RF waveforms), light (including solar light or indoor light), motion, pressure, heat, or any other power source that could be seen suitable;

[0082] - with low complexity, small size and lower capabilities and lower power consumption than previously defined 3GPP IoT devices (e.g., NB-IoT / enhanced machine type communication (eMTC) devices);

[0083] - maintenance free and can have long life span (e.g., more than 10 years).

[0084] An A-IoT may directly communicate with a base station / gNB (e.g., the BS 102) (e.g., operating as a reader), or may indirectly communicate with a BS / gNB through an intermediate / assisting node, such as a handheld device / UE (for example, a "reader" UE that scans the A-IoT devices), a relay, integrated access and backhaul (IAB) node, a repeater for example a network-controlled repeater (NCR), and so on. The communication can be mono-static wherein the transmitter node to the A-IoT device is same as the receiving node from the A-IoT device, or can be bi-static (or multi-static) wherein the transmitter nodes to the A-IoT device can be different from the receiving nodes from the A-IoT device.

[0085] In an embodiment, the A-IoT device may operate with energy storage and power management capability. These devices may be characterized by ultra-low power consumption, and they employ energy harvesting mechanisms such as solar, RF energy and kinetic energy and thus don't require battery replacement or swapping frequently. In an embodiment, an A-IoT device may operate with energy harvesting (EH) or with limited (or no) energy storage / battery capability (such as a capacitor), such as an energy storage unit for amplification of receptions at the UE (e.g., the UE 116) or transmission by the UE, or for other UE operations, such as power-on, warm-up, memory, internal processing, and so on, or operating with backscattering communication.

[0086] In an embodiment, the A-IoT device may operate with RF envelope detection for receiving amplitude shift keying (ASK), e.g., OOK, modulated signal. RF envelope detection may be a key function that enables the Ambient IoT devices to filter and analyze RF signals. This technique may be applied in the reception of modulated RF signals with a view of acquiring information from the signals and hence enable communication between devices with efficiency and with minimum power consumption. RF envelope detection may be one of the most important techniques that are used in many of the low power consumption wireless communication protocols that are employed in Ambient IoT systems.

[0087] In an embodiment, the A-IoT device may operate with impedance matching. Impedance matching may be utilized in passive Ambient IoT devices backscattering externally provisioned carrier wave (CW) signal.

[0088] The disclosure relates to defining functionalities and procedures for A-IoT devices to perform transmission and reception between a reader and a device. DL and UL are also referred to as reader-to-device (R2D) and device-to-reader (D2R), respectively, and vice versa.

[0089] FIG. 5 illustrates an example of a transmitter structure 500 using OFDM according to an embodiment of the present disclosure. For example, transmitter structure 500 using OFDM can be implemented in gNB 102 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0090] Information bits, such as DCI bits or data bits 510, may be encoded by encoder 520, rate matched to assigned time / frequency resources by rate matcher 530, and modulated by modulator 540. Subsequently, modulated encoded symbols and demodulation reference signal (DM-RS) or channel state information reference signal (CSI-RS) 550 may be mapped to REs 560, an inverse fast Fourier transform (IFFT) may be performed by filter 570. A BW selector unit 565, a filter 580, a radio frequency (RF) amplifier 590, and transmitted signal 595 may also be included.

[0091] FIG. 6 illustrates an example of a receiver structure 600 using OFDM according to an embodiment of the present disclosure. For example, receiver structure 600 using OFDM can be implemented by any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0092] A received signal 610 may be filtered by filter 620, a CP removal unit may remove a CP 630, a filter 640 may apply a fast Fourier transform (FFT), RE de-mapping unit 650 may de-map REs selected by BW selector unit 655, received symbols may be demodulated by a channel estimator and a demodulator unit 660, a rate de-matcher 670 may restore a rate matching, and a decoder 680 may decode the resulting bits to provide information bits 690.

[0093] With reference to FIG. 5, an example transmitter structure using OFDM according to this disclosure is shown.

[0094] With reference to FIG. 6, an example receiver structure using OFDM according to this disclosure is shown.

[0095] FIG. 7 illustrates an example encoding structure 700 for a downlink control information (DCI) format according to an embodiment of the present disclosure. For example, encoding structure 700 can be implemented in gNB 102 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0096] A gNB may separately encode and transmit each DCI format in a respective physical downlink control channel (PDCCH). When applicable, a radio network temporary identifier (RNTI) for a UE (e.g., the UE 116) that a DCI format is intended for masks a cyclic redundancy check (CRC) of the DCI format codeword in order to enable the UE to identify the DCI format. For example, the CRC can include 24 bits and the RNTI can include 16 bits or 24 bits. The CRC of (non-coded) DCI format bits 710 may be determined using a CRC computation unit 720, and the CRC may be masked using an exclusive OR (XOR) operation unit 730 between CRC bits and RNTI bits 740. The XOR operation may be defined as XOR(0,0) = 0, XOR(0,1) = 1, XOR(1,0) = 1, XOR(1,1) = 0. The masked CRC bits may be appended to DCI format information bits using a CRC append unit 750. An encoder 760 may perform channel coding, such as polar coding, followed by rate matching to allocated resources by rate matcher 770. Interleaving and modulation units 780 may apply interleaving and modulation, such as QPSK, and the output control signal 790 may be transmitted.

[0097] FIG. 8 illustrates an example decoding structure 800 for a DCI format according to an embodiment of the present disclosure. For example, decoding structure 800 for a DCI format can be implemented by any of the UEs 111-116 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0098] A received control signal 810 may be demodulated and de-interleaved by a demodulator and a de-interleaver 820. A rate matching applied at a gNB transmitter may be restored by rate matcher 830, and resulting bits may be decoded by decoder 840. After decoding, a CRC extractor 850 may extract CRC bits and provide DCI format information bits 860. The DCI format information bits may be de-masked 870 by an XOR operation with a RNTI 880 (when applicable) and a CRC check may be performed by unit 890. When the CRC check succeeds (check-sum is zero), the DCI format information bits may be regarded to be valid. When the CRC check does not succeed, the DCI format information bits may be regarded to be invalid.

[0099] With reference to FIG. 7, an example encoding process for a DCI format according to this disclosure is shown.

[0100] With reference to FIG. 8, an example decoding process for a DCI format for use with a UE according to this disclosure is shown.

[0101] It is envisaged that the number of connected devices will reach ~500 billion by 2030, which is about ~59 times larger than the expected world population (~8.5 billion) by that time. Mobile devices will take various form-factors, such as augmented reality (AR) glasses, virtual reality (VR) headsets, hologram devices, while a large portion of the devices will be Internet-of-Things (IoT) devices for improving productivity efficiency and increasing comforts of life. As the number of IoT devices grows exponentially, those IoT devices will become dominant in the next generation wireless communication systems such as fifth generation (5G) advanced, sixth generation (6G) systems, and so on.

[0102] With the explosive number of IoT devices, it may be challenging to power the IoT devices by battery that needs to be replaced or recharged manually, which leads to high maintenance cost. The automation and digitalization of various industries demand new IoT technologies of supporting batteryless devices with no energy storage capability or devices with energy storage that does not need to be replaced or recharged manually. Such types of devices are collectively termed as ambient IoT (A-IoT) in this disclosure, which is powered by various renewable energy sources such as radio waves, light, motion, or heat, etc. Use cases of A-IoT devices include asset inventory / tracking and remote environmental monitoring. The following list provides example use cases of A-IoT devices:

[0103] - Indoor inventory

[0104] - Automated warehousing

[0105] - Medical instruments inventory management and positioning

[0106] - Non-Public Network for logistics

[0107] - Automobile manufacturing

[0108] - Airport terminal / shipping port

[0109] - Smart laundry

[0110] - Automated supply chain distribution

[0111] - Fresh food supply chain

[0112] - End-to-end logistics

[0113] - Flower auction

[0114] - Electronic shelf label

[0115] - Indoor sensor

[0116] - Smart homes

[0117] - Base station machine room environmental supervision

[0118] - Smart laundry

[0119] - Smart agriculture

[0120] - Smart pig farm

[0121] - Cow stable

[0122] - Indoor positioning

[0123] - Finding Remote Lost Item

[0124] - Location service

[0125] - Ranging in a home

[0126] - Personal belongings finding

[0127] - Positioning in shopping centre

[0128] - Museum Guide

[0129] - Indoor command

[0130] - Online modification of medical instruments status

[0131] - Device activation and deactivation

[0132] - Elderly Health Care

[0133] - Device Permanent Deactivation

[0134] - Electronic shelf label

[0135] - Outdoor inventory

[0136] - Medical instruments inventory management and positioning

[0137] - Non-public network for logistics

[0138] - Airport terminal / shipping port

[0139] - Automated supply chain distribution

[0140] - Outdoor sensor

[0141] - Smart grids

[0142] - Forest Fire Monitoring

[0143] - Dairy farming

[0144] - Smart manhole cover safety monitoring

[0145] - Smart bridge health monitoring

[0146] - Outdoor positioning

[0147] - Finding remote lost item

[0148] - Location service

[0149] - Personal belongings finding

[0150] - Outdoor command

[0151] - Online modification of medical instruments status

[0152] - Device activation and deactivation

[0153] - Elderly Health Care

[0154] - Controller in smart agriculture

[0155] Taking into account the limited size and low complexity required by practical applications of A-IoT devices, the output power of energy harvesting from ambient power sources is typically from 1μW to a few hundreds of μW, which is orders of magnitude lower than normal user equipment (UE) having peak power consumption higher than 10mW. This requires a new wireless access technology for A-IoT devices, which cannot be fulfilled by existing cellular systems including low-power IoT technologies such as NB-IoT and eMTC.

[0156] In the following, an italicized name for a parameter implies that the parameter is provided by higher layers.

[0157] DL (e.g., PRDCH) transmissions or UL (e.g., PDRCH) transmissions can be based on an OFDM waveform including a variant using DFT precoding that is known as DFT-spread-OFDM that is typically applicable to UL transmissions.

[0158] In the following, subframe (SF) refers to a transmission time unit for the LTE RAT and slot refers to a transmission time unit for an NR RAT. For example, the slot duration can be a sub-multiple of the SF duration. NR can use a different DL or UL slot structure than an LTE SF structure. Differences can include a structure for transmitting physical downlink control channels (PDCCHs), locations and structure of demodulation reference signals (DM-RS), transmission duration, and so on. Further, eNB refers to a base station serving UEs operating with LTE RAT and gNB refers to a base station serving UEs operating with NR RAT. Exemplary embodiments provide a same numerology, that includes a sub-carrier spacing (SCS) configuration and a cyclic prefix (CP) length for an OFDM symbol, for transmission with LTE RAT and with NR RAT. In such case, OFDM symbols for the LTE RAT as same as for the NR RAT, a subframe is same as a slot and, for brevity, the term slot is subsequently used in the remaining of the disclosure.

[0159] A unit for DL signaling or for UL signaling on a cell is referred to as a slot and can include one or more symbols. A bandwidth (BW) unit is referred to as a resource block (RB). One RB includes a number of sub-carriers (SCs). For example, a slot can have duration of one millisecond and an RB can have a bandwidth of 180 kHz and include 12 SCs with inter-SC spacing of 15 kHz. A sub-carrier spacing (SCS) can be determined by a SCS configuration as kHz. A unit of one sub-carrier over one symbol is referred to as resource element (RE). A unit of one RB over one symbol is referred to as physical RB (PRB).

[0160] DL signaling include physical downlink shared channels (PDSCHs) conveying information content, PDCCHs conveying DL control information (DCI), and reference signals (RS). A PDCCH can be transmitted over a variable number of slot symbols including one slot symbol and over a number of control channel elements (CCEs) from a predetermined set of numbers of CCEs referred to as CCE aggregation level within a control resource set (CORESET) as described in v17.6.0 of [REF 1] and v17.6.0 of [REF 3].

[0161] DCI can serve several purposes. A DCI format may include a number of fields, or information elements (IEs), and may typically be used for scheduling a PDSCH (DL DCI format) or a PUSCH (UL DCI format) transmission. A DCI format may include cyclic redundancy check (CRC) bits in order for a UE (e.g., the UE 116) to confirm a correct detection. A DCI format type may be identified by a radio network temporary identifier (RNTI) that scrambles the CRC bits. For a DCI format scheduling a physical downlink shared channel (PDSCH) or a PUSCH for a single UE with RRC connection to a gNB (e.g., the BS 102), the RNTI may bea cell RNTI (C-RNTI) or another RNTI type such as a modulation and coding scheme-cell RNTI (MCS-C-RNTI). For a DCI format scheduling a PDSCH conveying system information (SI) to a group of UEs, the RNTI may bea system information RNTI (SI-RNTI). For a DCI format scheduling a PDSCH providing a response to a random access (RA) from a group of UEs, the RNTI may bea random access (RA-RNTI). For a DCI format scheduling a PDSCH providing contention resolution in Msg4 of a RA process, the RNTI may bea temporary C-RNTI (TC-RNTI). For a DCI format scheduling a PDSCH paging a group of UEs, the RNTI may bea paging RNTI (P-RNTI). For a DCI format providing transmission power control (TPC) commands to a group of UEs, the RNTI may bea transmit power control radio network temporary identifier (TPC-RNTI), and so on. Each RNTI type may be configured to a UE through higher layer signaling. A UE may typically decode at multiple candidate locations for PDCCH receptions as determined by an associated search space set.

[0162] For each DL bandwidth part (BWP) indicated to a UE in a serving cell, the UE can be provided by higher layer signaling with control resource sets (CORESETs). For each CORESET, the UE may be provided a CORESET index , , a DM-RS scrambling sequence initialization value, a precoder granularity for a number of resource element groups (REGs) in the frequency domain where the UE can expect use of a same DM-RS precoder, a number of consecutive symbols for the CORESET, a set of resource blocks (RBs) for the CORESET, control channel element to resource element group (CCE-to-REG) mapping parameters, an antenna port quasi co-location, from a set of antenna port quasi co-locations, indicating quasi co-location information of the DM-RS antenna port for PDCCH reception in a respective CORESET, and an indication for a presence or absence of a transmission configuration indication (TCI) field for DCI format 1_1 transmitted by a PDCCH in CORESET .

[0163] For each DL BWP configured to a UE in a serving cell, the UE may be provided by higher layers with search space sets. For each search space set from the search space sets, the UE may be provided a search space set index , , an association between the search space set and a CORESET , a PDCCH monitoring periodicity of slots and a PDCCH monitoring offset of slots, a PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET within a slot for PDCCH monitoring, a duration of slots indicating a number of slots that the search space set exists, a number of PDCCH candidates per CCE aggregation level , and an indication that search space set is either a common search space (CSS) set or a UE-specific search space (USS) set. When search space set is a CSS set, the UE may monitor PDCCH for detection of DCI format 2_x, where x ranges from 0 to 7 as described in v17.6.0 of [REF2] or for DCI formats associated with scheduling broadcast / multicast PDSCH receptions, and for DCI format 0_0 and DCI format 1_0.

[0164] A UE may determine a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. For search space set , the UE may determine that a PDCCH monitoring occasion(s) exists in a slot with number in a frame with number if . The UE may monitor PDCCH candidates for search space set for consecutive slots, starting from slot , and does not monitor PDCCH candidates for search space set for the next consecutive slots. The UE may determine CCEs for monitoring PDCCH according to a search space set based on a search space equation as described in [REF3].

[0165] A UE may expect to monitor PDCCH candidates for up to 4 sizes of DCI formats that include up to 3 sizes of DCI formats with CRC scrambled by C-RNTI per serving cell. The UE may count a number of sizes for DCI formats per serving / scheduled cell based on a number of PDCCH candidates in respective search space sets for the corresponding active DL BWP. In the following, for brevity, that constraint for the number of DCI format sizes will be referred to as DCI size limit. When the DCI size limit would be exceeded for a UE based on a configuration of DCI formats that the UE monitors PDCCH, the UE may align the size of some DCI formats, as described in v17.6.0 of [REF2], so that the DCI size limit would not be exceeded.

[0166] For each scheduled cell, the UE may be not required to monitor on the active DL BWP with SCS configuration of the scheduling cell more than PDCCH candidates or more than non-overlapped CCEs per slot, wherein and are respectively a maximum number of PDCCH candidates and non-overlapping CCEs for a scheduled cell and and are respectively a total number of PDCCH candidates and non-overlapping CCEs for a scheduling cell, as described in [REF3].

[0167] A UE does not expect to be configured CSS sets, other than CSS sets for multicast PDSCH scheduling, that result to corresponding total, or per scheduled cell, numbers of monitored PDCCH candidates and non-overlapped CCEs per slot on the primary cell that exceed the corresponding maximum numbers per slot. For USS sets or for CSS sets associated with multicast PDSCH scheduling, when a number of PDCCH candidates or non-overlapping CCEs in a slot would exceed the limits / maximum per slot for scheduling on the primary cell mentioned herein, the UE may select the USS sets or the CSS sets to monitor corresponding PDCCH in an ascending order of a corresponding search space set index until and an index of a search space set for which PDCCH monitoring would result to exceeding the maximum number of PDCCH candidates or non-overlapping CCEs per slot for scheduling on the PCell as described in [REF3].

[0168] For same cell scheduling or for cross-carrier scheduling where a scheduling cell and scheduled cells have DL BWPs with same SCS configuration , a UE does not expect a number of PDCCH candidates, and a number of corresponding non-overlapped CCEs per slot on a secondary cell to be larger than the corresponding numbers that the UE is capable of monitoring on the secondary cell per slot. For cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapped CCEs per slot may be separately counted for each scheduled cell.

[0169] A UE can be configured for operation with carrier aggregation (CA) for PDSCH receptions over multiple cells (DL CA) or for PUSCH transmissions over multiple cells (UL CA). The UE can also be configured multiple transmission-reception points (TRPs) per cell via indication (or absence of indication) of acoresetPoolIndexfor CORESETs where the UE receives PDCCH / PDSCH from a corresponding TRP as described in v17.6.0 of [REF3]and [REF4].

[0170] MIMO technologies have a key role in boosting system throughput both in NR and LTE and such a role will continue and further expand in the future generations of wireless technologies. For MIMO operation, an antenna port is defined such that a channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. There is not necessarily a one to one correspondence between an antenna port and an antenna element, and a plurality of antenna elements can be mapped onto one antenna port.

[0171] FIG. 9 illustrates a diagram of an example type-1 backscatter structure 900 for IoT devices according to an embodiment of the present disclosure. For example, type-1 backscatter structure 900 can be implemented by any of the UEs 111-116 of FIG. 1, or may be devices with fewer components and functionality than a UE. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0172] As shown in FIG. 9, the type-1 backscatter structure 900 for IoT devices may include an antenna 905, a matching network 910, a RF energy harvester 915, a phasor measurement unit (PMU) 920, an energy storage 925, a RF bandpass filter (BPF) 930, a RF envelope detector 935, a baseband (BB) lowpass filter (LPF) 940, a comparator 945, a clock generator 950, a BB logistics 955, memory 960, backscatter (imp matching) 965, and processing circuitry 913.

[0173] In an embodiment, the processing circuitry 913, which may be a full-powered processor, such as included in UE 116, a lower-power microprocessor or microcontroller, an application specific integrated circuit (ASIC), or logic circuitry. The processing circuitry 913 can control the overall operation of the IoT device including determination of reception and / or transmission timing. The processing circuitry 913 may be powered via energy storage 925. The signal receiving and transmitting processing circuitry included in the IoT devices, such as RF BPF 930, a RF envelope detector 935, a BB LPF 940, a comparator 945, a clock generator 950, a BB logistics 955, memory 960, and a backscatter (impedance matching) 965, may be referred to as a transceiver, which may use separate antennas for reception and transmission, respectively, or may use a common antenna, such as antenna 905 for transmission and reception. One or more implementations described herein further include other implementation variations such as separate Tx-Rx antennas vs common Tx-Rx antenna, use of a sensor, etc. The implementations should be understood as an example and not as a restriction.

[0174] FIG. 10 illustrates a diagram of an example impedance matching circuit according to an embodiment of the present disclosure. For example, impedance matching circuit 1000 can be implemented in any of the IoT device described herein. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0175] FIG. 11 illustrates a diagram of an example type-2a backscatter structure 1100 for IoT devices according to an embodiment of the present disclosure. For example, backscatter structure 1100 can be implemented by any of the UEs 111-116 of FIG. 1, such as the UE 111, or may be devices with fewer components and functionality than a UE. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0176] As shown in FIG. 11, the type-2a backscatter structure 1100 may include an antenna 905, a matching network 910, a RF energy harvester 915, a PMU 920, an energy storage 925, an energy harvester (other than RF) 1122, a RF BPF 930, a low noise amplifier (LNA) 1132, a RF envelope detector 935, a BB amp 1137, a BB LPF 940, a comparator / ADC 1142, a clock generator 950, a BB logistics 955, memory 960, a frequency shifter 1162, backscatter (imp matching) 965, a reflection amp 1167, and processing circuitry 913.

[0177] FIG. 12 illustrates a diagram of an example type-2a backscatter structure 1200 for IoT devices according to an embodiment of the present disclosure. For example, backscatter structure 1200 can be implemented by any of the UEs 111-116 of FIG. 1, such as the UE 112, or may be devices with fewer components and functionality than a UE. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0178] As shown in FIG. 12, the type-2a backscatter structure 1200 may include an antenna 905, a matching network 910, a RF energy harvester 915, a PMU 920, an energy storage 925, an energy harvester (other than RF) 1122, a RF BPF 930, a LNA 1132, a mixer 1205, a LO 1225, an IF amp / BPF 1210, an IF ED 1215, a BB Amp / LPF 1220, a comparator / ADC 1142, a clock generator 950, a BB logistics 955, memory 960, a frequency shifter 1162, a backscatter (impedance Matching) 965, reflection amp 1167, and processing circuitry 913.

[0179] FIG. 13 illustrates a diagram of an example type-2b active structure 1300 for IoT devices according to an embodiment of the present disclosure. For example, structure 1300 can be implemented by any of the UEs 111-116 of FIG. 1, such as the UE 113, or may be devices with fewer components and functionality than a UE. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0180] As shown in FIG. 13, the type-2b active structure 1300 may include an antenna 905, a matching network 910, a RF energy harvester 915, a PMU 920, an energy storage 925, an energy harvester (other than RF) 1122, a RF BPF 930, a LNA 1132, a mixer 1205, an LO 1225, a BB amplifier 1137, a BB LPF 940, a comparator / ADC 1142, a clock generator 950, a BB logistics 955, memory 960, a frequency shifter 1162, a backscatter (impedance matching) 965, a reflection amp 1167, and processing circuitry 913.

[0181] FIG. 14 illustrates a diagram of an example type-2b active structure 1400 for IoT devices according to an embodiment of the present disclosure. For example, backscatter structure 1400 can be implemented by any of the UEs 111-116 of FIG. 1, such as the UE 114, or may be devices with fewer components and functionality than a UE. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0182] As shown in FIG. 14, the type-2b active structure 1400 may include an antenna 905, a matching network 910, a RF energy harvester 915, a PMU 920, an energy storage 925, an energy harvester (other than RF) 1122, a RF BPF 930, a LNA 1132, a RF envelope detector 935, a BB amp 1137, a BB LPF 940, a comparator / ADC 1142, a clock generator 950, a BB logistics 955, memory 960, a modulator 1465, a DAC 1470, a LO 1475, a mixer 1480, a PA 1485, and processing circuitry 913.

[0183] FIG. 15 illustrates a diagram of an example type-2b active backscatter structure 1500 for IoT devices according to an embodiment of the present disclosure. For example, backscatter structure 1500 can be implemented by any of the UEs 111-116 of FIG. 1, such as the UE 115, or may be devices with fewer components and functionality than a UE. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0184] As shown in FIG. 15, the structure 1500 may include an antenna 905, a matching network 910, a RF energy harvester 915, a PMU 920, an energy storage 925, an energy harvester (other than RF) 1122, a RF BPF 930, a LNA 1132, a mixer 1534, an IF amp / BPF 1536, an IF ED 1538, a BB amp / LPF 1540, a comparator / ADC 1142, a clock generator 950, a BB logistics 955, memory 960, a modulator 1465, a DAC 1470, a LO 1475, a mixer 1480, a PA 1485, and processing circuitry 913.

[0185] FIG. 16 illustrates a diagram of an example type-2b active structure 1600 for IoT devices according to an embodiment of the present disclosure. For example, backscatter structure 1600 can be implemented by any of the UEs 111-116 of FIG. 1, such as the UE 116, or may be devices with fewer components and functionality than a UE. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0186] As shown in FIG. 16, the structure 1600 may include an antenna 905, a matching network 910, a RF energy harvester 915, a PMU 920, an energy storage 925, an energy harvester (other than RF) 1122, a RF BPF 930, a LNA 1132, a mixer 1534, a BB amp 1137, a BB LPF 940, a comparator / ADC 1142, a clock generator 950, a BB logistics 955, memory 960, a modulator 1465, a DAC 1470, a LO 1475, a mixer 1480, a PA 1285, and processing circuitry 913.

[0187] Several different types of A-IoT devices can be regarded as following.

[0188] - Device 1: ~1 μW peak power consumption, may have energy storage, initial sampling frequency offset (SFO) up to 10X ppm, neither R2D nor D2R amplification in the device. The device's D2R transmission may be backscattered on a carrier wave provided externally.

[0189] - Device 2a: a few hundred μW peak power consumption, may have energy storage, initial sampling frequency offset (SFO) up to 10X ppm, both R2D and / or D2R amplification in the device. The device's D2R transmission may be backscattered on a carrier wave provided externally.

[0190] - Device 2b: a few hundred μW peak power consumption, may have energy storage, initial sampling frequency offset (SFO) up to 10X ppm, both R2D and / or D2R amplification in the device. The device's D2R transmission may be generated internally by the device.

[0191] The devices may operate in frequency division duplexing (FDD) spectrum or time division duplexing (TDD) spectrum, which may be licensed or unlicensed.

[0192] In the following, reference architectures for the device types herein are provided, which should be understood as an example and not as a restriction.

[0193] With reference to FIG. 9, an example Type-1 backscatter device structure according to the disclosure is shown.

[0194] The RF energy harvester 915 may convert RF signal to DC power and supplies the device. Either a R2D signal or an externally provisioned CW signal for backscattering can be utilized for RF energy harvesting. The CW may externally be provided from a gNB or a dedicated source. The source of CW signal, e.g., either a gNB or a dedicated node, may or may not be agnostic to A-IoT devices. The harvested energy, e.g., using a rectifier, can be stored using a capacitor, super-capacitor, or, generally speaking, an energy storage. Antenna could be either shared or separate for RF energy harvester and receiver / transmitter. Matching network 910 may be to match impedance between antenna and other components. Power management unit (PMU) 920 may manage storing energy to energy storage from energy harvester and supplying power to active component blocks which needs power supply. Clock generator 950 may provide required clock signal(s).

[0195] The R2D signal may be demodulated using a low complexity envelope detector and comparator, whose output is provided as an input to the baseband circuit. Given the low-power and low-complexity requirements of the Type-1 backscatter device, an RF envelope detection can be a viable solution for a receiver architecture, compared to a heterodyne architecture with IF envelope detection or a homodyne architecture with baseband envelope detection, which require LO and frequency mixer for frequency down-conversion. The input RF signal may pass through an RF band-pass filter (BPF) 930 for an adjacent channel interference suppression, and then the filtered RF signal may directly be converted into a baseband using an RF envelope detector 935, followed by a baseband low-pass filter (LPF) 940 for filtering out harmonics and high frequency components, and an n-bit comparator, where n can be 1, 2, 4, 8, ... The use of filters, e.g., BPF only, LPF only, or both, can be an implementation choice.

[0196] For the D2R backscatter transmission, any of the following can be used:

[0197] - Case 1) CW may be provisioned at DL spectrum and backscattered, e.g., CW @ DL spectrum, D2R backscattering @ DL spectrum.

[0198] - Case 2) CW may be provisioned at UL spectrum and backscattered, e.g., CW @ UL spectrum, D2R backscattering @ UL spectrum.

[0199] - Case 3) CW may be provisioned at DL spectrum, frequency shifted to UL spectrum, and then backscattered, e.g., CW @ DL spectrum, D2R backscattering @ UL spectrum.

[0200] In one example, Case 1) or Case 2) may be evaluated for device 1, e.g., CW and D2R backscattering on the same frequency and, therefore, a frequency shifter (FS) may not be required.

[0201] With reference to FIG. 10, an example impedance matching circuit for backscatter device D2R modulation according to the disclosure is shown.

[0202] The followings are simple examples of impedance matching operations:

[0203] - Open circuit: Full reflection of the received CW signal in the same phase. This can be used for on-off keying (OOK) modulation with matching circuit.

[0204] - Short circuit: Full reflection of the received CW signal in the reversed phase. This can be used for phase-shift keying (PSK) modulation.

[0205] - Matching circuit: No reflection as the impedance is matched to a load, e.g., absorption. This can be utilized for energy harvesting, Rx mode, or modulation with other matching states.

[0206] - Multi-level matching circuit: As illustrated in FIG. 10. Multi-level impedance matching to Z1, Z2, ..., ZLfor log2(L) bits per symbol ASK modulation.

[0207] Depending on the matched load impedance, the matching circuit can backscatter the incoming CW signal with different reflection coefficients in both amplitude and phase. In general, amplitude shift keying (ASK) / phase shift keying (PSK) / frequency shift keying (FSK) may be supported using an impedance matching circuit. As a simplest modulation scheme, OOK may be evaluated. The device may indicate its modulation capability or impedance matching capability to the network (e.g., the network 130), or certain requirement may be predefined in the specification of system operation.

[0208] With reference to FIG. 11, an example device 2a backscatter architecture based on RF envelope detection according to the disclosure is shown.

[0209] The device 2a may share similar structure at large with device 1 as the D2R transmission is still based on backscattering of an externally provided CW, while the device 2a may differ from device 1 from the following aspects.

[0210] The device 2a may have a few hundred μW peak power consumption and both R2D and / or D2R amplification in the device. In this case, alternative to the RF energy harvesting from a R2D signal or an externally provided CW signal, other renewable energy sources, e.g., solar, thermal, kinetic, etc., may be provided for energy harvesting. The presence of a certain energy harvesting capability from a certain renewable energy source may be expected for system design point of view. The use of energy harvesters, e.g., RF energy harvester only, other energy harvester only, or both, can be an implementation choice.

[0211] The device 2a may be equipped with both R2D and / or D2R amplification in the device. Given the power consumption requirement, e.g., a few hundred μW, the R2D / D2R amplification for device 2a may be based on an architecture that is different from the typical power amplifier (PA) and low noise amplifier (LNA). In some example low-power / complexity architectures for forward amplifier for reader-to-device (R2D) reception and reflection amplifier for device-to-reader (D2R) transmission, a single bipolar transistor terminated with microstrips may be used. The receiver amplification can be either RF amplification prior to the envelope detector, baseband amplification after the envelope detector, or both, which is an implementation choice. For example, a reflection amplifier may be used for both R2D reception and D2R transmission, and LNA may or may not exist. For example, a reflection amplifier may be used for D2R transmission only and LNA may be used for R2D reception amplification.

[0212] For example, a reflection amplifier can be used only for backscattering, e.g., one-way amplification. For example, a reflection amplifier can be used for both backscattering and receiving, e.g., two-way amplification. For a reflection amplifier, it can be expected that 10 ~ 25 dB gain is achievable, at a power consumption of a few tens to hundreds micro-Watts. It is noted that an exact power consumption value will be highly dependent on implementations. On the other hand, a stability of an amplifier may be a function of an input impedance and operating frequency. Since A-IoT devices are expected to be deployed for a certain operating frequency and not expected to adapt to another frequency after deployment, the implementation can ensure a stable operation of the amplifier for the target frequency.

[0213] One additional difference of device 2a compared to device 1 may be a use of a FS. With a few hundred μW peak power consumption, some low-power LO architectures with a frequency mixer can be taken into account for Case 3). With FS, it can be expected that the CW is provided in a frequency different than the UL carrier frequency. Because the A-IoT devices are targeting for low complexity and low power consumption, the following options can be evaluated as an example method for frequency shift:

[0214] - Ultra-low power local oscillator (LO), whose output frequency is multiplied in one or more stages using a frequency multiplier to obtain a desired amount of frequency shift.

[0215] - Calibrated RC (resistor-capacitor) oscillator, which uses CW frequency as an input to the RC oscillator with phase locked loop (PLL) circuitry.

[0216] - CW signal provided at the UL carrier frequency; In this case, no frequency shifter is needed.

[0217] - Use of harmonic frequencies of CW signal or intermodulation frequencies of two-tone CW signals.

[0218] The device 2a receiver architecture may be based on RF envelope detector, intermediate frequency (IF) envelope detector (ED), e.g., heterodyne receiver, or homodyne receiver with zero IF, as exemplified for device 2b.

[0219] The device 2b may share similar structure at large with the device 2a other than the UL signal is internally generated using LO rather than backscattering the externally provided CW. The example architecture shown in FIGS. 12-14 is based on an active transmitter chain, wherein the UL data is modulated, converted to an analog signal using digital to analog converter (DAC) and, then up-converted to a UL carrier frequency using LO and frequency mixer, which is followed by an amplifier.

[0220] In FIG. 12, the DL receiver chain is still based on the RF envelope detector as in the previous architectures. In FIG. 13, the DL receiver chain is based on heterodyne receiver with IF envelope detector. In the heterodyne architecture, the RF signal may be down converted into an intermediate frequency and then detected using an envelope detector. In FIG. 14, the DL receiver is based on homodyne receiver, e.g., zero-IF. In the homodyne / zero-IF architecture, the RF signal may directly be down converted into baseband signal and then detected using a comparator / ADC.

[0221] FIGS. 9-14 should be understood for illustration purpose only. There can be other components not explicitly shown in the figure such as switch, duplexer, and filters, or some components may be replaced to different options. Also, the devices can operate both in TDD and FDD spectrum, either licensed or unlicensed, and, depending on the operating spectrum, the actual architectures can be different from the conceptual illustrations in the figures.

[0222] In deploying A-IoT devices, different topology options can be evaluated. The following provides examples of topology options:

[0223] - Topology 1: BS A-IoT device

[0224] - An A-IoT device may directly and bidirectionally communicate with a base station. The communication between the base station and the A-IoT device may include A-IoT data and / or signalling. This topology may include the BS transmitting to the A-IoT device is different from the BS receiving from the A-IoT device.

[0225] - Topology 2: BS intermediate node Ambient IoT device

[0226] - An A-IoT device may communicate bidirectionally with an intermediate node between the device and base station. In this topology, the intermediate node can be a relay, IAB node, UE, repeater, etc. which is capable of A-IoT. The intermediate node may transfer A-IoT data and / or signalling between BS and the A-IoT device. The intermediate node may be referred to as I-node in this disclosure.

[0227] - Topology 3: BS assisting node Ambient IoT device BS

[0228] - An A-IoT device may transmit data / signalling to a base station, and receive data / signalling from the assisting node; or the A-IoT device may receive data / signalling from a base station and transmit data / signalling to the assisting node. In this topology, the assisting node can be a relay, IAB, UE, repeater, etc. which is capable of A-IoT.

[0229] - Topology 4: UE Ambient IoT device

[0230] - An A-IoT device may communicate bidirectionally with a UE. The communication between UE and the A-IoT device may include A-IoT data and / or signalling.

[0231] This disclosure is applicable at least to the following deployment scenarios:

[0232] - Scenario 1: Device indoors, BS indoors

[0233] - Scenario 2: Device indoors, BS outdoors

[0234] - Scenario 3: Device indoors, UE-based reader

[0235] - Scenario 4: Device outdoors, BS outdoors

[0236] - Scenario 5: Device outdoors, UE-based reader

[0237] The deployment of A-IoT can be on the same sites as an existing 3GPP deployment corresponding to the BS type, e.g., macro-cell, micro-cell, pic-cell, etc. In an embodiment, it may be expected that the deployment of A-IoT can be on new sites without an expectation of an existing 3GPP deployment. The deployment can be based on licensed or unlicensed TDD or FDD spectrum, which may be in-band to an existing deployment, in guard-band of an existing deployment, or in a standalone band. Different traffic types can be supported including device-terminated (DT) and device-originated (DO), wherein DO traffic can be further divided into DO autonomous (DO-A), and DO device-terminated triggered (DO-DTT) types.

[0238] A-IoT device may be one type of a UE. Embodiments in this disclosure can be generally applicable to other types of UEs, e.g., smartphones, AR / VR devices, or any other types of IoT devices.

[0239] FIG. 17 illustrates an example system 1700 for D2R / R2D transmission including an intermediate UE according to an embodiment of the present disclosure. For example, system 1700 can be implemented in the wireless network 100 of FIG. 1. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0240] With reference to FIG. 17, a topology involving an intermediate node is shown, wherein the intermediate node (I-node) can be any of a UE, relay, repeater, a dedicated node, or a gNB (e.g., the BS 102). Any operations performed by a BS can be also performed by the I-node instead of the BS, and all or part of interfaces are transparent to the A-IoT devices.

[0241] An entity directly communicating with a device, or tag, is collectively termed as a reader, which can be an intermediate node as illustrated in FIG. 17, an assisting node, a UE, or a BS directly communicating with a device.

[0242] This disclosure is applicable to any of the following spectrum options, wherein a reader can be any of a BS, an intermediate node, an assisting node, or a UE in any of the topologies or scenarios disclosed herein:

[0243] - The scenario when a reader is an intermediate node, an assisting node, or a UE

[0244] - CW may be transmitted on DL spectrum and D2R may be transmitted on the DL spectrum or shifted to UL spectrum.

[0245] - CW may be transmitted on UL spectrum and D2R may be transmitted on the UL spectrum or shifted to DL spectrum.

[0246] - R2D transmission by a reader may be on DL spectrum or UL spectrum.

[0247] - A node transmitting the CW can be a node inside the topology, e.g., a BS, an intermediate node, an assisting node, or a UE (e.g., the UE 116), or a node outside the topology, e.g., a dedicated CW source.

[0248] - A reader receiving D2R transmission and a reader transmitting R2D may be the same or different.

[0249] - For example, CW may be transmitted on DL spectrum and D2R transmission may be shifted to UL spectrum, wherein the node transmitting the CW is a node inside topology or outside topology, and a reader transmitting R2D and a reader receiving D2R may be the same or different.

[0250] - For example, CW may be transmitted on DL or UL spectrum and D2R transmission may be on the same spectrum for which the CW is transmitted, wherein the node transmitting the CW is a node inside topology or outside topology, and a reader transmitting R2D and a reader receiving D2R may be the same or different.

[0251] A physical channel for reader to device transmission may be referred to as a physical reader to device (R2D) channel (PRDCH), and a physical channel for device to reader transmission is referred to as a physical device to reader (D2R) channel (PDRCH) in this disclosure.

[0252] For PRDCH and PDRCH transmission, a timing acquisition signal, e.g., a preamble, may be included at least for timing acquisition and for indicating the start of the transmission in time domain, respectively.

[0253] There may be a timing relationship between transmissions as herein:

[0254] - TR2D_min, TR2D_max: Minimum / maximum time between a R2D transmission and the corresponding D2R transmission following it.

[0255] - TD2R_min, TD2R_max: Minimum / maximum time between a D2R transmission and the corresponding R2D transmission following it.

[0256] - TR2D_R2D_min, TR2D_R2D_max: Minimum / maximum time between two different consecutive R2D transmissions to the same A-IoT device.

[0257] - TD2R_D2R_min, TD2R_D2R_max: Minimum / maximum time between two different consecutive D2R transmissions from the same A-IoT device.

[0258] Given the low complexity and the low power consumption requirements for A-IoT devices, it is apparent that the oscillators equipped with A-IoT devices will be significantly subpar to that equipped with a normal NR UE. It is therefore impractical to expected a precise timing capability for A-IoT devices as it is usually expected for normal NR UEs. Furthermore, given that A-IoT devices are powered by harvesting energy, the device maybe running out of power time to time and, thereby, loosing timing, e.g., lacking timing maintaining capability.

[0259] Embodiments of the present disclosure recognizes that, when PRDCH or PDRCH provide header fields, there is a need to define procedures and methods for a receiving node, e.g., a device or a reader, to retrieve control information provided in the header field to determine whether to decode the following payload and parameters related to decode the payload.

[0260] Embodiments of the present disclosure further recognizes that, with an asynchronous system operation without fixed boundaries, there is a need to define procedures and methods for a receiving node, e.g., a device or a reader, to determine the end of PRDCH or PDRCH reception.

[0261] Embodiments of the present disclosure further recognizes that, when a device transmits PDRCH to a reader, there is another need to define procedures and methods for a device to determine the PDRCH transmission timing.

[0262] The disclosure relates to a communication system. The disclosure relates to defining functionalities and procedures for communication with A-IoT devices which may be lacking a precise timing capability and may operate in a passive or active D2R transmission mode.

[0263] The disclosure relates to defining functionalities and procedures for A-IoT devices to transmit a D2R signal and receive a R2D signal in an asynchronous manner with a lack of precise synchronization maintenance capability.

[0264] The disclosure also relates to defining functionalities and procedures for a receiving node, e.g., a device or a reader, to retrieve control information provided in the header field to determine whether to decode the following payload and parameters related to decode the payload.

[0265] The disclosure further relates to defining functionalities and procedures for a receiving node, e.g., a device or a reader, to determine the end of PRDCH or PDRCH reception.

[0266] The disclosure also relates to defining functionalities and procedures for a device to determine the PDRCH transmission timing.

[0267] Embodiments of the disclosure for communication with A-IoT devices, which may be lacking a precise timing capability and may operate in a passive or active UL transmission mode, are summarized in the following and are fully elaborated further herein.

[0268] - Method and apparatus for defining functionalities and procedures for a receiving node, e.g., a device or a reader, to retrieve control information provided in the header field to determine whether to decode the following payload and parameters related to decode the payload.

[0269] - Method and apparatus for defining functionalities and procedures for a receiving node, e.g., a device or a reader, to determine the end of PRDCH or PDRCH reception.

[0270] - Method and apparatus for defining functionalities and procedures for a device to determine the PDRCH transmission timing.

[0271] FIG. 18 illustrates a flowchart of an example device procedure 1800 for receiving PRDCH according to an embodiment of the present disclosure. For example, procedure 1800 can be performed by any of the IoT devices described herein. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0272] The procedure begins in 1810, a device may receive PRDCH transmission from a reader. In 1820, the device may read header field of the PRDCH and determine to read or skip the rest of the PRDCH based on the message type or receiver address field. In 1830, the device may read the rest of the PRDCH, if it determines that the message is intended to the device, based on the information obtained from the header field, e.g., modulation and resource information.

[0273] FIG. 19 illustrates a diagram of an example PRDCH / PDRCH transmission architecture 1900 according to an embodiment of the present disclosure. For example, PRDCH / PDRCH transmission architecture 1900 can be transmitted by any of the IoT devices described herein and / or any of the reader devices described herein. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0274] The PRDCH / PDRCH transmission architecture 1900 may include preamble (e.g., start indicator and / or clock acquisition), control info (e.g., header), payload (data, control, etc.), and / or postamble (e.g., end indicator).

[0275] The header field of PRDCH / PDRCH may carry necessary control information for R2D / D2R signal reception. Some additional control information may be contained in the payload and that handling may be similar to NR MAC CE and MAC service data unit (SDU). Header may include the following sub-elements.

[0276] - Message type: Indicator for the signal type conveyed in the payload such as R2D data, control information, broadcast information such as paging, if defined, random access triggering, random access response, command for PRDCH. Similarly, it can be D2R data, control information, random access, etc., for PDRCH.

[0277] - Transmitter ID: Transmitter ID of the signal. For R2D, it may be the reader ID. For D2R, it may be a device ID.

[0278] - Receiver ADDR: Receiver address ID, e.g., the intended receiver. For D2R, it may be the reader ID. For R2D, it may indicate a specific device ID or device group ID. For broadcast, this field may indicate NULL, which is intended to be received by the devices within the proximity.

[0279] - Payload size: This field may indicate the length of the following payload.

[0280] - Modulation type / order: The modulation type / order applied to the following payload.

[0281] - Time and frequency domain resource allocation information

[0282] - Repetition: A number of repetition may be indicated. In a simple example, only on / off of repetition may be indicated for a predefined repetition scheme in the specifications of system operation, if applied.

[0283] - For example, the repetition may be performed in a chip level, in a bit level, in a unit of certain message size, for an entire payload (not including control field, preamble), for an entire control field and payload (not including preamble), or for an entire PRDCH or PDRCH.

[0284] - For example, PRDCH or PDRCH may include one or more block-wise repetitions of entire bits transmitted in PRDCH or PDRCH.

[0285] From the message type and / or receiver ADDR, a cast type, e.g., unicast / multicast / broadcast, of the message can be derived by a device. After identifying that the message is intended to the device, the device may read the rest of the PRDCH including payload.

[0286] For PDRCH, a device may encode the one or more information in the header field of PDRCH herein.

[0287] For PRDCH, in one example, CRC may separately be attached to the header and the remaining payload. For example, a single CRC may be attached for both the header and the payload.

[0288] If CRC is separately attached to the header and the remaining payload, a device may first decode and read the header field and, if the device identifies that the message is intended to the device, then the device may decode and read the following payload. In case if the device identifies that the message is not intended to the device, then the device may skip decoding the following payload.

[0289] If a single CRC is attached for both the header and the payload, the device may first decode the entire signal, read the header field. If the device identifies that the message is intended to the device, then the device may read the rest of the signal, e.g., payload. In case if the device identifies that the message is not intended to the device, then the device may skip reading the rest of the signal.

[0290] For PDRCH, in one example, CRC may separately be attached to the header and the remaining payload. For example, a single CRC may be attached for both the header and the payload. For example, the device may expect one operation based on the specifications of the system operation and performs CRC attachment without any explicit indication from the reader. For example, the device indicated from a reader in the preceding R2D control information to attach separate CRCs for the header and the remaining payload or a single CRC for the entire message and performs CRC attachment accordingly.

[0291] In the header field of PRDCH / PDRCH, for example, Receiver ADDR field may be located first, and the rest of control information follow. For example, message type field may be located first and the rest of control information follow. In this way, a device can early identify whether the corresponding message is addressed to the device or not and early terminate reading the message if it is not addressed to it.

[0292] FIG. 20 illustrates a flowchart of an example device procedure 2000 for determining the end of a PRDCH reception according to an embodiment of the present disclosure. For example, procedure 2000 can be performed by any of the IoT devices described herein. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0293] The procedure begins in 2010, a device may receive PRDCH transmission from a reader. In 2020, the device may determine the end of PRDCH (or payload size) either implicitly based on the message type or explicitly based on the R2D control information. In 2030, the device may read the PRDCH based on the determined end of the PRDCH or until a postamble attached to the PRDCH is detected.

[0294] FIG. 21 illustrates a flowchart of an example reader procedure 2100 for determining the end of a PDRCH reception according to an embodiment of the present disclosure. For example, procedure 2100 can be performed by any of the reader devices described herein. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0295] The procedure begins in 2110, a reader may receive PDRCH transmission from a device. In 2120, the reader may determine the end of PDRCH (or payload size) either implicitly based on the message type or explicitly based on the R2D control information previously provided to the device or D2R control information included in the PDRCH. In 2130, the reader may read the PDRCH based on the determined end of the PDRCH or until a postamble attached to the PDRCH is detected.

[0296] For the determination or derivation of the end of PRDCH, in an embodiment, R2D postamble immediately following the PRDCH may indicate the end of the PRDCH. In an embodiment, it may be determined based on R2D control information.

[0297] Similarly, for the determination or derivation of the end of PDRCH, in an embodiment, D2R postamble immediately following the PDRCH may be used. In an embodiment, it may be determined based on R2D control information or D2R control information.

[0298] In most A-IoT use cases, there can be a limited number of message types to be defined and many of them will have a fixed message size. As an example, a query message, e.g., paging or random access triggering message, from a reader to a device to initiate an inventory round is most likely to have a fixed set of fields comprising the message and, thereby, a known message size. Similarly, a query response message, e.g., random access message, from a device to the reader will also have a known message size, unless a temporary device ID has a varying length.

[0299] Therefore, for a certain set of messages with a fixed size, the end of PRDCH or PDRCH reception can be implicitly determined at the receiver based on the message type indicated in a control field of the PRDCH or PDRCH.

[0300] A certain set of message types can have a variable message size. As an example, write command from a reader or a reply by a device to read command from a reader can include data with variable size. In this case, the payload size needs to be explicitly indicated in a control field of PRDCH or PDRCH such that an intended receiver can determine the end of PRDCH or PDRCH based on the indication.

[0301] The followings can be examples of messages having variable size: Reply to a successful ReadBuffer command, KeyUpdate command, SecureComm command, AuthComm command, Authenticate command, BlockPermalock command, Reply to BlockPermalock command, BlockWrite command, Reply to a successful Read command, Challenge command, and Select.

[0302] When payload size is explicitly indicated in a control field of PRDCH or PDRCH, there may be a minimum message size Nminassociated with a certain message type. The variable size of the message, N, may be indicated in its absolute number of bits. For example, the message size exceeding Nminin a number of bits is indicated, e.g., N - Nmin. In this case, if the indicated message size is zero, then N = Nmin. For example, there can be a set of predefined message size values, wherein the set can be common across different message types or separate for each message type, and an index from the set of predefined message size values is indicated.

[0303] For example, there may be a field indicating whether the length information is included in the control field or not. If the field indicates that the length information is included in the control field, the reader (or device) may read the length information from a predetermined field in the message. Otherwise, the reader (or device) may expect a known fixed message size.

[0304] With a determination of a payload size based on control information of PRDCH or PDRCH either implicitly or explicitly, the use of postamble for the indication of the end of PRDCH or PDRCH is not strictly required. However, given the clock drift at a device, it may be still beneficial to also attach postamble at least for the determination of the end of PRDCH at a device.

[0305] FIG. 22 illustrates a flowchart of an example device procedure 2200 for determining PRDCH transmission timing according to an embodiment of the present disclosure. For example, procedure 2200 can be performed by any of the IoT devices described herein. This example is for illustration only and other embodiments can be used without departing from the scope of the present disclosure.

[0306] The procedure begins in 2210, a device may determine to transmit PDRCH to a reader following a preceding PRDCH transmission from a reader. In 2220, the device may determine the PDRCH transmission timing based on the R2D control information if it is provided in the preceding PRDCH reception. Otherwise, the device may determine the PDRCH transmission timing based on one or more predefined timing parameters. In 2230, the device may transmit the PDRCH based on the determined start timing.

[0307] Regarding a device determining D2R transmission timing, an embodiment may be to define a maximum time TR2D_maxbetween the end of a R2D transmission and the start of the corresponding D2R transmission following it, and a device may perform D2R transmission within [TR2D_min, TR2D_max]. In an embodiment, for a given type of PDRCH message, there may be a timing parameter, Tdelay, defined from the end of the reception of the preceding PRDCH to the start timing of PDRCH. In an embodiment, the D2R transmission timing may be determined based on R2D control information.

[0308] When the D2R transmission timing is determined based on R2D control information, e.g., by providing a timing parameter in the R2D control information, a guard time between time-multiplexed devices may be taken into account by the reader evaluating timing drift or processing delay for PDRCH transmission at the devices.

[0309] For example, R2D control information may provide a start timing parameter, T, and allowed timing drift, e.g., , , such that a device may determine PDRCH start timing within , wherein and can be the same.

[0310] For example, R2D control information may provide a start timing parameter, T, to a device, and the device may determine its PDRCH start timing within [T + TR2D_min, T + TR2D_max]. For example, a device may determine its PDRCH start timing within [T, T + TR2D_max- TR2D_min].

[0311] For example, a device may determine the transmission timing of the PDRCH based on a predefined time interval from the reception of the PRDCH or an explicit timing indication provided in the PRDCH.

[0312] For D2R transmissions based on multi-access, the D2R transmission timing may be determined based on timing parameter provided in the R2D control information. When a transmission from only a single device is expected, e.g., a response from a device to a targeted command from a reader, the corresponding D2R transmission timing may be determined based on predefined timing parameter, such as [TR2D_min, TR2D_max] or Tdelay, without an explicit timing indication in R2D control information.

[0313] In one scenario, the device does not have sufficient energy to perform a PDRCH transmission corresponding to the preceding PRDCH reception. In this case, in one example, the device does not transmit PDRCH. For example, the device may determine the length of PDRCH transmission based on the available amount of energy, e.g., shortening the transmission, and transmit the PDRCH. For example, the device may send a PDRCH indicating that the device is unable to perform the corresponding PDRCH transmission, e.g., due to low energy level. For example, the device may determine to shorten the length of PDRCH transmission or transmit the PDRCH providing an energy status report in case that an energy level of the IoT device is insufficient to execute an entirety of the PDRCH transmission. This message may also include when the device is expected to be turned back on. Using this information, the reader can send the PRDCH again when the device is expected to be turned back on. Alternatively, there may be a fixed timer that the device is expected to be turned back on, which is expected by both the device and a reader, without an explicit indication.

[0314] In one example, a device may operate continuously as long as the device has energy to operate. When the device is running out of energy, the device goes into energy harvesting and charging mode and the device resumes operating when it is sufficiently recharged, e.g., the stored energy level exceeds a certain threshold. The device may report to the reader the statistics of on-duration for operation and off-duration for charging such as mean, median, max / min range, inter-quarter range, etc.

[0315] For example, the device may operate with a certain fixed time pattern with on-duration and off-duration. The periodicity and on / off-duration may be based on device-specific charging time and discharging time, which may be pre-programmed during implementation or calculated during the operation. The periodicity and on / off-duration, and offset that determines the timing may be expected only by the device itself. For example, a reader may request a device to report the duty cycle related parameters, as disclosed herein, and the device may reply accordingly. For example, a device may report to the reader the duty cycle related parameters, when it first communicates with the reader, periodically, or aperiodically when parameters are updated.

[0316] When a device operates with a certain time pattern with on-duration and off-duration, there can be long and short cycles. In one example, on / off-durations of a short cycle may be defined on on-duration of a long cycle, e.g., within a long cycle on-duration, the device may perform on / off operations to save the energy. For off-duration of a long cycle, the device may remain off.

[0317] For a given time pattern with on-duration and off-duration, the device operation may be still based on its best effort, e.g., if the device is running out of energy or no R2D transmission is received for a certain timer duration, the device may early go into off-mode.

[0318] In an embodiment, a method for an Internet of Things (IoT) device to communicate with a reader is provided.

[0319] In an embodiment, the method, wherein the type of R2D message may include at least one of a message type triggering random access, a message type providing R2D data, or a message type providing a command. The method, wherein the type of D2R message may include at least one of a message type for random access or a message type providing D2R data.

[0320] In an embodiment, the method, wherein receiving the PRDCH may include receiving the PRDCH based on a determination of the size of the payload of the PRDCH. The method, wherein the determination of the size of the payload of the PRDCH is based on the type of R2D message or an explicit indication provided in the PRDCH.

[0321] In an embodiment, the method, wherein determining the size of the payload of the D2R message may include determining the size of the payload of the D2R message based on the type of D2R message or an explicit indication provided in the PRDCH.

[0322] In an embodiment, the method, wherein determining the transmission timing of the PDRCH may include determining the transmission timing of the PDRCH based on a predefined time interval from the reception of the PRDCH or an explicit timing indication provided in the PRDCH.

[0323] In an embodiment, the method, wherein the PRDCH or the PDRCH may include one or more block-wise repetitions of entire bits transmitted in the PRDCH or the PDRCH.

[0324] In an embodiment, the method, wherein determining the transmission of the PDRCH to the reader based on reception of the PRDCH may include determining to shorten the length of PDRCH transmission or transmit the PDRCH providing an energy status report in case that an energy level of the IoT device is insufficient to execute an entirety of the PDRCH transmission.

[0325] In an embodiment, an Internet of Things (IoT) device including a transceiver and processing circuitry connected to the transceiver is provided.

[0326] In an embodiment, the IoT device, wherein the type of R2D message may include at least one of a message type triggering random access, a message type providing R2D data, or a message type providing a command. The IoT device, wherein the type of D2R message may include at least one of a message type for random access or a message type providing D2R data.

[0327] In an embodiment, the IoT device, wherein the processing circuitry may be configured to receive the PRDCH based on a determination of the size of the payload of the PRDCH. The IoT device, wherein the determination of the size of the payload of the PRDCH is based on the type of R2D message, an explicit indication provided in the PRDCH, or a reception of a postamble immediately following the PRDCH.

[0328] In an embodiment, the IoT device, wherein the processing circuitry may be configured to determine the size of the payload of the D2R message based on the type of D2R message or an explicit indication provided in the PRDCH.

[0329] In an embodiment, the IoT device, wherein the processing circuitry may be configured to determine the transmission timing of the PDRCH based on a predefined time interval from the reception of the PRDCH or an explicit timing indication provided in the PRDCH.

[0330] In an embodiment, the IoT device, wherein the PRDCH or the PDRCH may include one or more block-wise repetitions of entire bits transmitted in the PRDCH or the PDRCH.

[0331] In an embodiment, the IoT device, wherein the processing circuitry may be configured to determine to shorten the length of PDRCH transmission or transmit the PDRCH providing an energy status report when an energy level of the IoT device is insufficient to execute an entirety of the PDRCH transmission.

[0332] In an embodiment, a reader including a transceiver and processing circuitry connected to the transceiver is provided.

[0333] In an embodiment, the reader, wherein the type of R2D message may include at least one of a message type triggering random access, a message type providing R2D data, or a message type providing a command. The reader, wherein the type of D2R message may include at least one of a message type for random access or a message type providing D2R data.

[0334] In an embodiment, the reader, wherein the processing circuitry may be configured to transmit the PRDCH based on a determination of the size of the payload of the PRDCH. The reader, wherein the determination of the size of the payload of the PRDCH is based on the type of R2D message, an explicit indication in the PRDCH, or a postamble transmitted immediately following the PRDCH.

[0335] In an embodiment, the reader, wherein the processing circuitry may be configured to determine the size of the payload of the D2R message based on the type of D2R message or an explicit indication in the PRDCH.

[0336] In an embodiment, the reader, wherein the processing circuitry may be configured to determine the reception timing of the PDRCH based on a predefined time interval from the transmission of the PRDCH or an explicit timing indication in the PRDCH.

[0337] In an embodiment, the reader, wherein the PRDCH or the PDRCH may include one or more block-wise repetitions of entire bits transmitted in the PRDCH or the PDRCH.

[0338] Any of the above variation embodiments can be utilized independently or in combination with at least one other variation embodiment. The above flowchart(s) illustrate example methods that can be implemented in accordance with the principles of the present disclosure and various changes could be made to the methods illustrated in the flowcharts herein. For example, while shown as a series of steps, various steps in each figure could overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps.

[0339] Although the figures illustrate different examples of user equipment, various changes may be made to the figures. For example, the user equipment can include any number of each component in any suitable arrangement. In general, the figures do not limit the scope of the present disclosure to any particular configuration(s). Moreover, while figures illustrate operational environments in which various user equipment features disclosed in this patent document can be used, these features can be used in any other suitable system.

[0340] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims. None of the descriptions in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claims scope. The scope of patented subject matter is defined by the claims.

Claims

1.A method for an Internet of Things (IoT) device to communicate with a reader, the method comprising:receiving a physical reader-to-device channel (PRDCH) from the reader, wherein:the PRDCH includes a medium access control (MAC) header and a payload,the MAC header indicates a type of reader-to-device (R2D) message and information related to determining a size of the payload, andthe MAC header and the payload are jointly attached with a single set of cyclic redundancy check (CRC) bits;determining, based on reception of the PRDCH, a transmission of a physical device-to-reader channel (PDRCH) to the reader, including determining:a type of device-to-reader (D2R) message,a size of a payload of the D2R message,a length of the PDRCH transmission, anda transmission timing of the PDRCH; andtransmitting the PDRCH to the reader.2.The method of claim 1, wherein:the type of R2D message includes at least one of a message type triggering random access, a message type providing R2D data, or a message type providing a command, andthe type of D2R message includes at least one of a message type for random access or a message type providing D2R data.3.The method of claim 1, wherein:receiving the PRDCH further comprises receiving the PRDCH based on a determination of the size of the payload of the PRDCH, andthe determination of the size of the payload of the PRDCH is based on the type of R2D message or an explicit indication provided in the PRDCH.4.The method of claim 1, wherein determining the size of the payload of the D2R message further comprises determining the size of the payload of the D2R message based on the type of D2R message or an explicit indication provided in the PRDCH.5.The method of claim 1, wherein determining the transmission timing of the PDRCH further comprises determining the transmission timing of the PDRCH based on a predefined time interval from the reception of the PRDCH or an explicit timing indication provided in the PRDCH.6.The method of claim 1, wherein the PRDCH or the PDRCH includes one or more block-wise repetitions of entire bits transmitted in the PRDCH or the PDRCH.7.The method of claim 1, wherein determining the transmission of the PDRCH to the reader based on reception of the PRDCH further comprises:determining to shorten the length of PDRCH transmission or transmit the PDRCH providing an energy status report in case that an energy level of the IoT device is insufficient to execute an entirety of the PDRCH transmission.8.An Internet of Things (IoT) device, comprising:a transceiver; andprocessing circuitry connected to the transceiver, wherein the processing circuitry is configured to:receive a physical reader-to-device channel (PRDCH) from a reader, wherein:the PRDCH includes a medium access control (MAC) header and a payload,the MAC header indicates a type of reader-to-device (R2D) message and information related to determining a size of the payload, andthe MAC header and the payload are jointly attached with a single set of cyclic redundancy check (CRC) bits;determine, based on reception of the PRDCH, a transmission of a physical device-to-reader channel (PDRCH) to the reader, including to determine:a type of device-to-reader (D2R) message,a size of a payload of the D2R message,a length of the PDRCH transmission, anda transmission timing of the PDRCH; andtransmit the PDRCH to the reader.9.The IoT device of claim 8, wherein:the type of R2D message includes at least one of a message type triggering random access, a message type providing R2D data, or a message type providing a command, andthe type of D2R message includes at least one of a message type for random access or a message type providing D2R data.10.The IoT device of claim 8, wherein:the processing circuitry is further configured to receive the PRDCH based on a determination of the size of the payload of the PRDCH, andthe determination of the size of the payload of the PRDCH is based on the type of R2D message, an explicit indication provided in the PRDCH, or a reception of a postamble immediately following the PRDCH.11.The IoT device of claim 8, wherein the processing circuitry is further configured to determine the size of the payload of the D2R message based on the type of D2R message or an explicit indication provided in the PRDCH.12.The IoT device of claim 8, wherein the processing circuitry is further configured to determine the transmission timing of the PDRCH based on a predefined time interval from the reception of the PRDCH or an explicit timing indication provided in the PRDCH.13.The IoT device of claim 8, wherein the PRDCH or the PDRCH includes one or more block-wise repetitions of entire bits transmitted in the PRDCH or the PDRCH.14.The IoT device of claim 8, wherein the processing circuitry is further configured to determine to shorten the length of PDRCH transmission or transmit the PDRCH providing an energy status report when an energy level of the IoT device is insufficient to execute an entirety of the PDRCH transmission.15.A reader comprising:a transceiver; andprocessing circuitry connected to the transceiver, wherein the processing circuitry is configured to:transmit a physical reader-to-device channel (PRDCH) to an Internet of Things (IoT) device, wherein:the PRDCH includes a medium access control (MAC) header and a payload,the MAC header indicates a type of reader-to-device (R2D) message and information related to determining a size of the payload, andthe MAC header and the payload are jointly attached with a single set of cyclic redundancy check (CRC) bits;determine, based on transmission of the PRDCH, a reception of a physical device-to-reader channel (PDRCH) to the reader, including to determine:a type of device-to-reader (D2R) message,a size of a payload of the D2R message,a length of the PDRCH reception, anda reception timing of the PDRCH; andreceive the PDRCH from the IoT device.

Images