Method and apparatus for controlling a reader in communication with a device in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. An apparatus and method for controlling a reader communicating with a device. A method for an Internet of Things (IoT) reader communicating with a device includes receiving, from a base station (BS), first information related to downlink (DL) reception or uplink (UL) transmission between the IoT reader and the BS, receiving, from the BS, second information related to reader-to-device (R2D) transmission or device-to-reader (D2R) reception between the IoT reader and one or more devices, receiving, from the BS, third information related to execution of a command, and transmitting, to the device, a physical reader-to-device channel (PRDCH). The PRDCH indicates information related to execution of the command. The PRDCH is device-specific for the device among the one or more devices, device-group-specific for the one or more devices, or common for all devices receiving the PRDCH. The method further includes transmitting, to the BS, fourth information related to execution of the command.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to apparatus and methods for controlling a reader communicating with a device in a wireless communication system. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, including 28GHz and 39GHz, known as millimeter wave (mmWave). Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz (THz) bands (e.g., the 95GHz to 3THz band) to achieve transmission rates 50 times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] In the early stages of 5G mobile communication technology development, to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization has been ongoing for the following technologies: beamforming and massive MIMO for reducing radio wave path loss and increasing radio wave transmission distance in millimeter waves; support parameter sets for dynamic operation (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and time slot formats; initial access technologies for supporting multi-beam transmission and broadband; definition and operation of BWP (bandwidth portion); new channel coding methods such as LDPC (low-density parity-check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing for providing dedicated networks for specific services.

[0004] Currently, regarding the services supported by 5G mobile communication technology, discussions are underway regarding improvements and performance enhancements to the initial 5G mobile communication technology. Physical layer standardization has been completed for technologies such as: V2X (vehicle-to-everything) for assisting autonomous vehicle driving decisions based on information transmitted by the vehicle regarding its location and status, and for improving user convenience; NR-U (New Radio Unlicensed) designed to comply with various regulatory requirements for system operation in unlicensed frequency bands; NR UE power saving; non-terrestrial networks (NTNs) for direct satellite communication between UEs to provide coverage in areas where communication with terrestrial networks is not possible; and positioning.

[0005] Furthermore, standardization of air interface architectures / protocols for technologies such as: Industrial Internet of Things (IIoT) for supporting new services through interoperability and integration with other industries; IAB (Integrated Access and Backhaul) for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Stack) handover; and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization of system architectures / services for technologies such as: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Virtual Network Functions (NFV) and Software-Defined Networking (SDN) technologies; and mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, an exponential increase in connected devices will be added to communication networks, thus necessitating enhanced functionality and performance of 5G mobile communication systems as well as integrated operation of connected devices. To this end, new research is planned related to the following technologies: Extended Reality (XR) for efficient support of AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; 5G performance improvements and complexity reduction through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication. Summary of the Invention

[0007] [Technical Issues]

[0008] This disclosure generally relates to wireless communication systems, and more specifically, to apparatus and methods for controlling a reader communicating with a device in a wireless communication system.

[0009] [Solution to the problem]

[0010] According to one aspect of an exemplary embodiment, a communication method in a wireless communication system is provided.

[0011] [Beneficial effects of the invention]

[0012] This disclosure provides efficient communication methods in wireless communication systems.

[0013] This disclosure relates to a reader for controlling and communicating with devices.

[0014] In one embodiment, a method for an Internet of Things (IoT) reader to communicate with a device is provided. The method includes: receiving from a base station (BS) first information related to a downlink (DL) reception or uplink (UL) transmission between the IoT reader and the BS; receiving from the BS second information related to a reader-to-device (R2D) transmission or device-to-reader (D2R) reception between the IoT reader and one or more devices; receiving from the BS third information related to executing a command; and sending a Physical Reader-to-Device Channel (PRDCH) to the device. The PRDCH indicates information related to executing the command. The PRDCH may be device-specific for one or more devices, device group-specific for one or more devices, or common to all devices receiving the PRDCH. The method also includes sending to the BS fourth information related to the execution of the command.

[0015] In another embodiment, an IoT reader is provided. The IoT reader includes a processor and a transceiver operatively coupled to the processor. The transceiver is configured to: receive from a BS first information related to DL reception or UL transmission between the IoT reader and the BS; receive from the BS second information related to R2D transmission or D2R reception between the IoT reader and one or more devices; receive from the BS third information related to executing a command; and send a PRDCH to the devices. The PRDCH indicates information related to executing a command. The PRDCH may be device-specific for one or more devices, device group-specific for one or more devices, or common to all devices receiving the PRDCH.

[0016] In yet another embodiment, a base station (BS) is provided. The BS includes a processor and a transceiver operatively coupled to the processor. The transceiver is configured to: transmit first information to an IoT reader relating to DL reception or UL transmission between the IoT reader and the BS; receive from the IoT reader second information relating to R2D transmission or D2R reception between the IoT reader and one or more devices; transmit third information to the IoT device relating to command execution; and receive from the IoT reader fourth information relating to command execution. The information relating to command execution is indicated via a PRDCH. The PRDCH may be device-specific for one or more devices, device group-specific for one or more devices, or common to all devices receiving the PRDCH.

[0017] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “comprise” and “include,” and their derivatives mean non-restrictive inclusion. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives mean including, being included within, interconnected with, containing, being contained within, connected to or connected with, coupled to or coupled with, capable of communicating with, cooperating with, intertwined, juxtaposed, proximate, bound to or bound with, having, possessing the attributes of, related to, or similar meanings. 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 in a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, local or remote. When the phrase "at least one" is used with a list of items, it means that different combinations of one or more of the listed items can be used, and only one item in the list may be required. For example, "at least one of the following: 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.

[0018] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, flows, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in 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 accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and subsequently rewrite it (such as rewritable optical discs or erasable storage devices).

[0019] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many (if not all) instances, such definitions apply to the prior and future use of these defined words and phrases. Attached Figure Description

[0020] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals denote like parts: Figure 1 An example wireless network according to an embodiment of this disclosure is shown; Figure 2 An example gNodeB (gNB) according to an embodiment of this disclosure is shown; Figure 3 An example user equipment (UE) according to an embodiment of this disclosure is shown; Figure 4A and Figure 4B An example of a wireless transmission and reception path according to an embodiment of this disclosure is shown; Figure 5 An example of a transmitter structure using orthogonal frequency division multiplexing (OFDM) according to an embodiment of this disclosure is shown; Figure 6 An example of a receiver structure using OFDM according to an embodiment of this disclosure is shown; Figure 7 An example encoding structure for downlink control information (DCI) format according to an embodiment of this disclosure is shown; Figure 8 An example decoding structure for downlink control information (DCI) format according to an embodiment of this disclosure is shown; Figure 9 A diagram of an example type 1 backscattering structure for an Internet of Things (IoT) device according to an embodiment of the present disclosure is shown; Figure 10 A diagram of an example impedance matching circuit according to an embodiment of the present disclosure is shown; Figure 11 A diagram of an example type 2a backscattering structure for an IoT device according to an embodiment of the present disclosure is shown; Figure 12 A diagram showing an example type 2b active device structure for an IoT device according to an embodiment of the present disclosure is illustrated; Figure 13 A diagram showing an example type 2b active device structure for an IoT device according to an embodiment of the present disclosure is illustrated; Figure 14 A diagram showing an example type 2b active device structure for an IoT device according to an embodiment of the present disclosure is illustrated; Figure 15 An example system for device-to-reader (D2R) / reader-to-device (R2D) transmission including an intermediate node, according to an embodiment of this disclosure, is shown; Figure 16 A flowchart illustrating an example reader process for transmitting information between a BS and a device according to an embodiment of this disclosure is shown; Figure 17 A flowchart illustrating an example reader process for selecting resources according to an embodiment of this disclosure is shown; Figure 18 Block diagrams of a UE according to various embodiments of the present disclosure are shown; and Figure 19 Block diagrams of base station or network entities according to various embodiments of the present disclosure are shown. Detailed Implementation

[0021] This application claims priority to U.S. Provisional Patent Application No. 63 / 575,272, filed April 5, 2024, and U.S. Non-Provisional Patent Application No. 19 / 089,289, filed March 21, 2025, pursuant to 35 USC § 119(e), the entire contents of which are incorporated herein by reference.

[0022] Wireless communication has become one of the most successful innovations in modern history. In recent years, the number of users of wireless communication services has exceeded five billion and continues to grow rapidly. Due to the increasing prevalence of smartphones and other mobile data devices (such as tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and businesses, the demand for wireless data traffic is increasing rapidly. To meet the high-speed growth of mobile data traffic and support new applications and deployments, improving the efficiency and coverage of wireless interfaces is crucial. To meet the increased demand for wireless data traffic since the deployment of 4G communication systems and to enable various vertical applications, 5G communication systems have been developed and are being deployed.

[0023] This disclosure relates to a reader for controlling and communicating with devices.

[0024] In one embodiment, a method for an Internet of Things (IoT) reader to communicate with a device is provided. The method includes: receiving from a base station (BS) first information related to a downlink (DL) reception or uplink (UL) transmission between the IoT reader and the BS; receiving from the BS second information related to a reader-to-device (R2D) transmission or device-to-reader (D2R) reception between the IoT reader and one or more devices; receiving from the BS third information related to executing a command; and sending a Physical Reader-to-Device Channel (PRDCH) to the device. The PRDCH indicates information related to executing the command. The PRDCH may be device-specific for one or more devices, device group-specific for one or more devices, or common to all devices receiving the PRDCH. The method also includes sending to the BS fourth information related to the execution of the command.

[0025] In another embodiment, an IoT reader is provided. The IoT reader includes a processor and a transceiver operatively coupled to the processor. The transceiver is configured to: receive from a BS first information related to DL reception or UL transmission between the IoT reader and the BS; receive from the BS second information related to R2D transmission or D2R reception between the IoT reader and one or more devices; receive from the BS third information related to executing a command; and send a PRDCH to the devices. The PRDCH indicates information related to executing a command. The PRDCH may be device-specific for one or more devices, device group-specific for one or more devices, or common to all devices receiving the PRDCH.

[0026] In yet another embodiment, a base station (BS) is provided. The BS includes a processor and a transceiver operatively coupled to the processor. The transceiver is configured to: transmit first information to an IoT reader relating to DL reception or UL transmission between the IoT reader and the BS; receive from the IoT reader second information relating to R2D transmission or D2R reception between the IoT reader and one or more devices; transmit third information to the IoT device relating to command execution; and receive from the IoT reader fourth information relating to command execution. The information relating to command execution is indicated via a PRDCH. The PRDCH may be device-specific for one or more devices, device group-specific for one or more devices, or common to all devices receiving the PRDCH.

[0027] Before making this disclosure, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “comprising” and “including,” and their derivatives mean non-limiting inclusion. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives mean including, being included within, interconnected with, containing, being contained within, connected to or connected with, coupled to or coupled with, capable of communicating with, cooperating with, intertwined, juxtaposed, proximate, bound to or bound with, having, possessing the attributes of, related to, or similar meanings. 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 in a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, local or remote. When the phrase "at least one" is used with a list of items, it means that different combinations of one or more of the listed items can be used, and only one item in the list may be required. For example, "at least one of the following: 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.

[0028] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, flows, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in 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 accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and subsequently rewrite it (such as rewritable optical discs or erasable storage devices).

[0029] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that, in many (if not all) instances, such definitions apply to the prior and future use of these defined words and phrases.

[0030] The following discussion Figures 1 to 19 The various non-limiting embodiments used to describe the principles of this disclosure in this patent document are illustrative only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0031] To meet the increased demand for wireless data services since the deployment of 4G communication systems and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are implemented in higher frequency (mmWave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (e.g., 6 GHz) to achieve robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems.

[0032] In addition, in 5G / NR communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), receiver interference cancellation, and location based on radio access technology (RAT).

[0033] The discussion of 5G systems and their associated frequency bands is for reference only, as some embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be used in conjunction with any frequency band. For example, aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G, or even subsequent versions that may use terahertz (THz) frequency bands.

[0034] The following documents and standards are incorporated herein by reference, as if fully set forth herein: [Reference 1] 3GPP TS 38.211 v18.1.0, "NR; Physical channels and modulation"; [Reference 2] 3GPP TS 38.212 v18.1.0, "NR; Multiplexing and channel coding"; [Reference 3] 3GPP TS 38.213 v18.1.0, "NR; Physical layer procedures for control"; [Reference 4] 3GPP TS 38.214 v18.1.0, "NR; Physical layer procedures for data"; [Reference 5] 3GPP TS 38.331 v18.0.0, "NR; Radio Resource Control (RRC) protocol". "NR; Medium Access Control (MAC) protocol specification"; and [Reference 6] 3GPP TS38.321 v18.0.0, "NR; Medium Access Control (MAC) protocol specification".

[0035] the following Figures 1 to 3 Various embodiments of communication technologies, such as orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA), are described in wireless communication systems. Figures 1 to 3 The description herein does not imply any physical or architectural limitation on the implementation of the different embodiments. The different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0036] Figure 1 An example wireless network 100 according to an embodiment of this disclosure is shown. Figure 1 The illustrated embodiment of the wireless network 100 is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0037] like Figure 1As shown, the wireless network 100 includes gNB 101 (e.g., a base station BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network).

[0038] gNB 102 provides wireless broadband access to network 130 to a plurality of first user equipments (UEs) within its coverage area 120. The plurality of first UEs includes: UE 111, which may be located in a small business; UE 112, which may be located in an enterprise; UE 113, which may be a WiFi hotspot; UE 114, which may be located in a first residence; UE 115, which may be located in a second residence; and UE 116, which may be a mobile device such as a cellular phone, wireless laptop, wireless PDA, or similar device. gNB 103 provides wireless broadband access to network 130 to a plurality of second UEs within its coverage area 125. The plurality of second UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, Long Term Evolution (LTE), LTE-A Advanced, WiMAX, WiFi, or other wireless communication technologies.

[0039] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmitting point (TP), a transmitting-receiving point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femtocell, a WiFi access point (AP), or other wireless enabling devices. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3rd Generation 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 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. Furthermore, depending on the network type, the term "user equipment" or "UE" can refer to any component such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user device." For convenience, the terms “user equipment” and “UE” are used in this patent document to refer to a remote wireless device that wirelessly accesses the BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

[0040] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas (such as coverage areas 120 and 125) associated with the BS may have other shapes (including irregular shapes) depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0041] As described in more detail below, one or more of UEs 111-116 include circuitry, software, or a combination thereof for supporting control of a reader communicating with a device. In some embodiments, one or more of gNBs 101-103 include circuitry, software, or a combination thereof to provide control over a reader communicating with a device.

[0042] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1Various modifications can be made. For example, wireless network 100 can include any number of gNBs and any number of UEs. Furthermore, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each gNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Additionally, gNBs 101, 102, and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0043] Figure 2 An example gNB 102 according to an embodiment of this disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 gNBs 101 and 103 can have the same or similar configurations. However, gNBs have multiple configurations, and Figure 2 The scope of this disclosure is not limited to any particular implementation of gNB.

[0044] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

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

[0046] The transmit (TX) processing circuitry in transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. Transceivers 210a-210n up-convert the baseband or IF signal into an RF signal transmitted via antennas 205a-205n.

[0047] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the transceivers 210a-210n to receive uplink (UL) channel signals and transmit downlink (DL) channel signals according to known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 225 may support beamforming or directional routing operations, wherein the output / input signals from / to multiple antennas 205a-205n are weighted differently to efficiently guide the output signals in a desired direction. The controller / processor 225 may support any of a variety of other functions in the gNB 102.

[0048] The controller / processor 225 is also capable of executing programs and other processes residing in the memory 230, such as providing control over a reader that communicates with the device. The controller / processor 225 can move data into or out of the memory 230 as needed for the execution process.

[0049] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. The backhaul or network interface 235 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., a system supporting 5G / NR, LTE, or LTE-A), the backhaul or network interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the backhaul or network interface 235 can allow the gNB 102 to communicate with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. The backhaul or network interface 235 includes any suitable structure that supports communication via wired or wireless connections (such as Ethernet or transceivers).

[0050] The memory 230 is coupled to the controller / processor 225. A portion of the memory 230 may include RAM, and another portion of the memory 230 may include flash memory or other ROM.

[0051] although Figure 2 An example of gNB 102 is shown, but it is possible to compare it with other models. Figure 2 Various changes can be made. For example, gNB 102 can include any number of Figure 2 Each component shown. Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0052] Figure 3 An example UE 116 according to an embodiment of this disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have multiple configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0053] like Figure 3 As shown, UE 116 includes an antenna 305, a transceiver 310, and a microphone 320. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0054] Transceiver 310 receives an input RF signal transmitted by a gNB of wireless network 100 from antenna 305. Transceiver 310 down-converts the input RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in transceiver 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 sends the processed baseband signal to speaker 330 (e.g., for voice data) or to processor 340 (e.g., for web browsing data).

[0055] The TX processing circuitry in transceiver 310 and / or processor 340 receives analog or digital voice data from microphone 320 or other output baseband data (such as network data, email, or interactive video game data) from processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband or IF signal. Transceiver 310 up-converts the baseband or IF signal into an RF signal transmitted via antenna 305.

[0056] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control transceiver 310 to receive DL channel signals and transmit UL channel signals according to known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0057] Processor 340 is also capable of executing other processes and programs residing in memory 360. For example, processor 340 can execute processes for supporting communication between the reader and the control device, as described in embodiments of this disclosure. Processor 340 can move data into or out of memory 360 as needed during execution. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from a gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices such as laptops and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0058] The processor 340 is also coupled to input 350 and display 355. Input 350 includes, for example, a touchscreen, a keypad, etc. The operator of UE 116 can use input 350 to input data into UE 116. Display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text and / or at least limited graphics (such as from a website).

[0059] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), and another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0060] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 can include any number of transceivers and signal processing chains, and can be connected to any number of antennas. Furthermore, although... Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile or fixed devices.

[0061] Figure 4A and Figure 4BExamples of wireless transmit and receive paths 400 and 450 according to embodiments of the present disclosure are shown respectively. For example, transmit path 400 may be described as being implemented in a gNB (such as gNB 102), while receive path 450 may be described as being implemented in a UE (such as UE 116). However, it will be understood that receive path 450 may be implemented in a gNB, and transmit path 400 may be implemented in a UE. In some embodiments, transmit path 400 and / or receive path 450 perform or utilize a reader that communicates with the device as described in embodiments of the present disclosure.

[0062] like Figure 4A As shown, the transmit path 400 includes a channel coding and modulation block 405, a serial-to-parallel (S to P) block 410, an N-size inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (P to S) block 420, a cyclic prefix addition block 425, and an up-converter (UC) 430. The receive path 450 includes a down-converter (DC) 455, a cyclic prefix removal block 460, a serial-to-parallel (S to P) block 465, an N-size fast Fourier transform (FFT) block 470, a parallel-to-serial (P to S) block 475, and a channel decoding and demodulation block 480.

[0063] In transmit path 400, channel coding and modulation block 405 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (such as with quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a frequency-domain modulated symbol sequence. Serial-to-parallel block 410 converts the serial data through modulated symbols (such as demultiplexing) into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 420 converts (such as multiplexing) the parallel time-domain output symbols from IFFT block 415 of size N to generate a serial time-domain signal. Cyclic prefix addition block 425 inserts a cyclic prefix into the time-domain signal. Upconverter 430 modulates (e.g., upconverts) the output of cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal can also be filtered at baseband before conversion to the RF frequency.

[0064] like Figure 4BAs shown, downconverter 455 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 465 converts the time-domain baseband signal into a parallel time-domain signal. FFT block 470 of size N performs an FFT algorithm to generate N parallel frequency-domain signals. (P to S) block 475 converts the parallel frequency-domain signals into a modulated data symbol sequence. Channel decoding and demodulation block 480 demodulates and decodes the modulated symbols to recover the original input data stream.

[0065] Each of gNBs 101-103 can implement a transmission path 400 similar to that used for sending to UEs 111-116 in the downlink, and a reception path 450 similar to that used for receiving from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 can implement a transmission path 400 for sending to gNBs 101-103 in the uplink, and a reception path 450 for receiving from gNBs 101-103 in the downlink.

[0066] Figure 4A and Figure 4B Each component can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 4A and Figure 4B At least some of the components can be implemented in software, while others can be implemented in configurable hardware or a hybrid of software and configurable hardware. For example, FFT block 470 and IFFT block 415 can be implemented as configurable software algorithms, where the value of size N can be modified according to the implementation.

[0067] Furthermore, although described as using FFT and IFFT, this is merely an example and should not be construed as limiting the scope of this disclosure. Other types of transforms, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, can be used. It will be understood that for the DFT and IDFT functions, the value of the variable N can be any integer (such as 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of the variable N can be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

[0068] although Figure 4A and Figure 4B Examples of wireless transmit and receive paths 400 and 450 are shown respectively, but more details can be found on the other side. Figure 4A and Figure 4B Make various changes. For example, Figure 4A and Figure 4B The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. Furthermore, Figure 4A and Figure 4B This is intended to illustrate examples of transmit and receive path types that can be used in wireless networks. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0069] Internet of Things (IoT) devices include ambient-powered IoT (A-IoT) devices, which are ultra-low-complexity devices with very small form factors and low-cost designs that operate without the need for conventional batteries that can be manually replaced or recharged. Conversely, A-IoT devices can be battery-free or have small batteries (such as small capacitors) that operate based on energy harvested from RF waveforms or other ambient energy sources. For practical applications requiring limited size and complexity, such as battery-free devices without energy storage capabilities or devices with limited energy storage that does not require manual replacement or recharging, the output power of the energy harvester is typically from 1µW to several hundred µW.

[0070] Throughout the various embodiments of this disclosure, a UE (e.g., UE 116) or device may be referred to as an energy harvesting-based A-IoT device or A-IoT UE, characterized by ultra-low complexity and power consumption, and intended for low-end IoT applications. For example, the UE may have limited (or no) energy storage or battery capabilities (e.g., capacitors), such as for amplifying reception or transmission at the UE, or for other UE operations (e.g., power-on, warm-up, memory, internal processing, etc.), or for energy storage units operating using backscatter communication.

[0071] An A-IoT device can be an IoT device that meets one or more of the following criteria (or variations thereof): - Powered by energy harvesting, without batteries or with limited energy storage capacity (e.g., using capacitors), and the energy is provided by harvesting radio waves (including RF waveforms), light (including sunlight or indoor light), motion, pressure, heat, or any other energy source deemed suitable; - Compared to previously defined 3GPP IoT devices (e.g., NB-IoT / enhanced machine-type communication (eMTC) devices), it features low complexity, small size, low capability, and low power consumption; - Maintenance-free and can have a long lifespan (e.g., more than 10 years).

[0072] A-IoT can communicate directly with a base station / gNB (e.g., BS 102) (e.g., operating as a reader), or indirectly with a reader through intermediate / auxiliary nodes (such as handheld devices / UEs (e.g., "reader" UEs scanning A-IoT devices), relays, integrated access and backhaul (IAB) nodes, repeaters (e.g., network control repeaters (NCRs)), etc.). Communication can be mono-static, where the transmitter node to the A-IoT UE is the same as the receiver node from the A-IoT UE, or bi-static (or multi-static), where the transmitter node to the A-IoT UE can be different from the receiver node from the A-IoT UE.

[0073] In various embodiments, A-IoT devices operate using energy storage and power management capabilities. These devices are characterized by ultra-low power consumption and employ energy harvesting mechanisms such as solar, RF, and kinetic energy, thus eliminating the need for frequent battery replacements. In various embodiments, A-IoT devices operate using energy harvesting (EH) or with limited (or no) energy storage / battery capabilities (such as capacitors), for example, to amplify reception or transmission at the UE, or for other UE operations (such as power-on, warm-up, memory, internal processing, etc.), or with energy storage units operating using backscatter communication.

[0074] In various embodiments, A-IoT devices operate using RF envelope detection to receive signals modulated by amplitude shift keying (ASK) (e.g., OOK). RF envelope detection is a key function enabling ambient IoT devices to filter and analyze RF signals. This technique is applied to receive modulated RF signals to extract information from them, thereby enabling efficient and low-power communication between devices. RF envelope detection is one of the most important techniques used in many low-power wireless communication protocols employed in ambient IoT systems.

[0075] In various embodiments, A-IoT devices can operate using impedance matching. Impedance matching can be used in passive environment IoT devices that backscatter an externally provided carrier (CW) signal.

[0076] This disclosure relates to defining the functions and processes of a reader that performs control and communicates with an A-IoT device. DL and UL are also referred to as reader-to-device (R2D) and device-to-reader (D2R), respectively, and vice versa.

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

[0078] Information bits, such as DCI bits or data bits 510, are encoded by encoder 520, rate-matched by rate matcher 530 for allocated time / frequency resources, and modulated by modulator 540. Subsequently, the modulated coded symbols and demodulation reference signal (DM-RS) or channel state information reference signal (CSI-RS) 550 are mapped to RE 560, and filter 570 performs inverse fast Fourier transform (IFFT). Also included are bandwidth (BW) selector unit 565, filter 580, radio frequency (RF) amplifier 590, and transmit signal 595.

[0079] Figure 6 An example of a receiver structure 600 using OFDM according to an embodiment of this disclosure is shown. For example, the receiver structure 600 using OFDM can be constructed by... Figure 1 This can be implemented using any of UEs 111-116. This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0080] The received signal 610 is filtered by filter 620, CP removal unit removes CP 630, filter 640 applies Fast Fourier Transform (FFT), RE demapping unit 650 demaps the RE selected by BW selector unit 655, the received symbols are demodulated by channel estimator and demodulator unit 660, rate dematcher 670 restores rate matching, and decoder 680 decodes the obtained bits to provide information bit 690.

[0081] refer to Figure 5 An example transmitter structure using OFDM according to this disclosure is shown.

[0082] refer to Figure 6 An example receiver structure using OFDM according to this disclosure is shown.

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

[0084] The gNB encodes and transmits each DCI format separately in the corresponding Physical Downlink Control Channel (PDCCH). Where applicable, the DCI format is designed to mask the Cyclic Redundancy Check (CRC) of the DCI format codewords to the Radio Network Temporary Identifier (RNTI) for the UE (e.g., UE 116) so that the UE can recognize the DCI format. For example, the CRC may include 24 bits, and the RNTI may include 16 or 24 bits. The CRC calculation unit 720 determines the CRC of the (unencoded) DCI format bits 710, and the CRC is masked using an XOR operation unit 730 between the CRC bits and the RNTI bits 740. The XOR operation is defined as XOR(0,0)=0, XOR(0,1)=1, XOR(1,0)=1, XOR(1,1)=0. The masked CRC bits are appended to the DCI format information bits using a CRC appending unit 750. Encoder 760 performs channel coding, such as polar coding, which is then rate-matched by rate matcher 770 for the allocated resources. Interleaving and modulation unit 780 applies interleaving and modulation (such as QPSK), and transmits output control signals 790.

[0085] Figure 8 An example decoding structure 800 for the DCI format is shown according to an embodiment of this disclosure. For example, the decoding structure 800 for the DCI format can be derived from... Figure 1 This can be implemented using any of UEs 111-116. This example is for illustrative purposes only, and other embodiments may be used without departing from the scope of this disclosure.

[0086] The received control signal 810 is demodulated and deinterleaved by the demodulator and deinterleaver 820. The rate match applied at the gNB transmitter is recovered by the rate matcher 830, and the resulting bits are decoded by the decoder 840. After decoding, the CRC extractor 850 extracts the CRC bits and provides DCI format information bits 860. The DCI format information bits are demasked by an XOR operation with RNTI 880 (where applicable), and a CRC check is performed by unit 890. When the CRC check is successful (checksum is zero), the DCI format information bits are considered valid. When the CRC check fails, the DCI format information bits are considered invalid.

[0087] refer to Figure 7 This illustrates an example encoding process for the DCI format according to this disclosure.

[0088] refer to Figure 8 This illustrates an example decoding process for a DCI format used with a UE, according to this disclosure.

[0089] It is conceivable that the number of connected devices will reach approximately 50 billion by 2030, roughly 59 times the projected world population at that time (approximately 8.5 billion). Mobile devices will take on various form factors, such as augmented reality (AR) glasses, virtual reality (VR) headsets, and holographic devices, while the majority of devices will be Internet of Things (IoT) devices designed to improve productivity and enhance quality of life. With the number of IoT devices growing exponentially, they will dominate next-generation wireless communication systems, such as fifth-generation (5G) enhanced systems and sixth-generation (6G) systems.

[0090] With the explosive growth in the number of IoT devices, powering them with batteries that require manual replacement or recharging can be challenging, leading to high maintenance costs. Automation and digitalization across various industries necessitate new IoT technologies that support battery-free devices without energy storage capabilities or devices with energy storage that does not require manual replacement or recharging. In this disclosure, this type of device is collectively referred to as Ambient IoT (A-IoT), which is powered by various renewable energy sources, such as radio waves, light, motion, or heat. Use cases for A-IoT devices include asset inventory / tracking and remote environmental monitoring. The following list provides example use cases for A-IoT devices: -Indoor Inventory --Automated warehousing --Medical instrument inventory management and positioning --Dedicated non-public logistics network --Automobile manufacturing --Airport Terminals / Shipping Ports --Smart Laundry --Automated supply chain distribution --Fresh food supply chain --End-to-end logistics --Flower Auction --Electronic shelf label -Indoor sensor --Smart Home --Base station equipment room environment monitoring --Smart Laundry --Smart Agriculture --Smart Pig Farm --Cowshed -Indoor positioning --Find lost items remotely --Location services --Home Distance Measurement --Personal Items Search --Location within the shopping mall --Museum Guide -Indoor Command --Online modification of medical instrument status --Device activation and deactivation --Health care for the elderly --Permanently deactivate the device --Electronic shelf label -Outdoor Inventory --Medical instrument inventory management and positioning --Dedicated non-public logistics network --Airport Terminals / Shipping Ports --Automated supply chain distribution -Outdoor sensor --Smart Grid --Forest fire monitoring --Dairy farming --Intelligent manhole cover safety monitoring --Intelligent Bridge Health Monitoring -Outdoor positioning --Find lost items remotely --Location services --Personal Items Search -Outdoor Command --Online modification of medical instrument status --Device activation and deactivation --Health care for the elderly --Intelligent agricultural controller Given the limited size and low complexity required for practical applications of A-IoT devices, the output power of energy harvested from ambient power sources is typically from 1µW to several hundredµW, which is several orders of magnitude lower than that of typical user equipment (UE) devices with peak power consumption exceeding 10mW. This necessitates new wireless access technologies for A-IoT devices that cannot be implemented by existing cellular systems, including low-power IoT technologies such as NB-IoT and eMTC.

[0091] In the following text, italicized names of parameters indicate that the parameter is provided by a higher level.

[0092] DL (e.g., Physical Reader to Device Channel (PRDCH)) transmissions or UL (e.g., Physical Device to Reader Channel (PDRCH)) transmissions can be based on OFDM waveforms, which include variants using DFT precoding, and these variants are referred to as DFT-extended OFDM, which is typically used for UL transmissions.

[0093] In the following text, a subframe (SF) refers to a transmission time unit used for LTE RAT, while a time slot refers to a transmission time unit used for NR RAT. For example, the time slot duration may be an approximation of the SF duration. NR may use DL or UL time slot structures different from the LTE SF structure. Differences may include the structure for transmitting the Physical Downlink Control Channel (PDCCH), the location and structure of the Demodulation Reference Signal (DM-RS), transmission duration, etc. Furthermore, eNB refers to a base station serving a UE operating using LTE RAT, and gNB refers to a base station serving a UE operating using NR RAT. Exemplary embodiments provide the same set of parameters (numerology) for transmissions using LTE RAT and NR RAT, including the subcarrier spacing (SCS) configuration and cyclic prefix (CP) length for OFDM symbols. In this case, the OFDM symbols used for LTE RAT are the same as those used for NR RAT, the subframes are the same as the time slots, and for brevity, the term time slot will be used subsequently in the remainder of this disclosure.

[0094] The unit used for DL ​​or UL signaling on a cell is called a time slot and may include one or more symbols. The bandwidth (BW) unit is called a resource block (RB). An RB includes multiple subcarriers (SCs). For example, a time slot may have a duration of 1 millisecond, and an RB may have a bandwidth of 180 kHz and include 12 SCs with an inter-SC spacing of 15 kHz. The subcarrier spacing (SCS) can be configured via the SCS. Determined as kHz. A cell of a subcarrier on a symbol is called a resource element (RE). A cell of an RB on a symbol is called a physical RB (PRB).

[0095] DL signaling includes the Physical Downlink Shared Channel (PDSCH) for transmitting information content, the PDCCH for transmitting DL control information (DCI), and the Reference Signal (RS). The PDCCH can be transmitted using a variable number of time slot symbols (including one time slot symbol) and can be transmitted using multiple control channel elements (CCEs) from a predetermined set of CCE numbers (called CCE aggregation levels) within the control resource set (CORESET), as described in v17.6.0 of [Reference 1] and v17.6.0 of [Reference 3].

[0096] DCI can be used for a variety of purposes. The DCI format includes multiple fields or information elements (IEs) and is typically used to schedule PDSCH (DL DCI format) or PUSCH (UL DCI format) transmissions. The DCI format includes Cyclic Redundancy Check (CRC) bits to allow the UE (e.g., UE 116) to confirm correct detection. The DCI format type is identified by a Radio Network Temporary Identifier (RNTI) that scrambles the CRC bits. For a DCI format that schedules a Physical Downlink Shared Channel (PDSCH) or PUSCH for a single UE with an RRC connection to a gNB (e.g., BS 102), the RNTI is either a Cell RNTI (C-RNTI) or another RNTI type, such as a Modulation and Coding Scheme-Cell RNTI (MCS-C-RNTI). For a DCI format that schedules a PDSCH that transmits System Information (SI) to a group of UEs, the RNTI is a System Information RNTI (SI-RNTI). For a DCI format that schedules a PDSCH that provides a response to Random Access (RA) from a group of UEs, the RNTI is a Random Access (RA-RNTI). For the DCI format of PDSCH that provides contention resolution in Msg4 of the RA procedure, the RNTI is the Temporary C-RNTI (TC-RNTI). For the DCI format of PDSCH that paging a group of UEs, the RNTI is the Paging RNTI (P-RNTI). For the DCI format that provides Transmit Power Control (TPC) commands to a group of UEs, the RNTI is the Transmit Power Control Radio Network Temporary Identifier (TPC-RNTI), and so on. Each RNTI type is configured to the UE via higher-layer signaling. The UE typically decodes at multiple candidate locations for PDCCH reception determined by the associated search space set.

[0097] For each DL bandwidth portion (BWP) indicated to the UE in the serving cell, it can be provided to the UE via higher-layer signaling. Each control resource set (CORESET). For each CORESET, the UE is provided with: a CORESET index. , ; DM-RS scrambling sequence initialization value; precoder granularity for multiple resource element groups (REGs) in the frequency domain for which the UE can expect to use the same DM-RS precoder; multiple consecutive symbols for CORESET; resource block (RB) set for CORESET; control channel element to resource element group (CCE to REG) mapping parameters; an antenna port quasi-co-address from the antenna port quasi-co-address set, the antenna port quasi-co-address indicating the quasi-co-address information of the DM-RS antenna port received by the PDCCH in the corresponding CORESET; and by CORESET The presence or absence of the Transmission Configuration Indicator (TCI) field in DCI format 1_1 transmitted by the PDCCH.

[0098] For each DL BWP configured for a UE in the serving cell, it is provided to the UE by the higher layers. A search space set. For those from For each search space set, the UE is provided with: a search space set index. , Search space set With CORESET The relationship between them; The PDCCH monitoring cycle for each time slot and The PDCCH monitoring offset for each time slot; the PDCCH monitoring mode within the time slot, indicating the first symbol of the CORESET within the time slot used for PDCCH monitoring; indicating the search space set. The duration of the number of existing time slots ( (per time slot); per CCE aggregation level Number of PDCCH candidates ; and search space set This indicates whether it is a common search space (CSS) set or a UE-specific search space (USS) set. When the search space set is a CSS set, the UE monitors the PDCCH for the following: detecting DCI format 2_x (where x ranges from 0 to 7 as described in v17.6.0 of [Reference 2]) or the DCI format associated with scheduling broadcast / multicast PDSCH reception; and DCI format 0_0 and DCI format 1_0.

[0099] The UE determines the PDCCH monitoring timing on the active DLBWP based on the PDCCH monitoring period, PDCCH monitoring offset, and PDCCH monitoring mode within the time slot. For the search space set... ,if Then the UE determines that in the number The frame number is There are one or more PDCCH monitoring opportunities within the time slot. The UE starts from the time slot. Start at Monitoring search space set within consecutive time slots The PDCCH candidate, and in the following The search space set is not monitored within a consecutive time slot. The UE determines the CCE for monitoring the PDCCH based on the search space formula described in v17.6.0 as in [Reference 3].

[0100] The UE anticipates monitoring PDCCH candidates for up to four DCI formats per cell, including up to three DCI formats with CRC scrambled by C-RNTI. The UE calculates the number of DCI format sizes for each serving / scheduled cell based on the number of PDCCH candidates in the corresponding search space set of the relevant active DL BWP. For brevity, the limitation on the number of DCI format sizes will be referred to as the DCI size limit in the following text. When the configuration of DCI formats monitored by the UE would exceed the UE's DCI size limit, the UE aligns some DCI format sizes as described in v17.6.0 of [Reference 2] to avoid exceeding the DCI size limit.

[0101] For each scheduled cell, the UE does not need to have an SCS configuration in the scheduled cell. The activity on the DL BWP monitors more than [number] times per time slot. PDCCH candidates or more There are non-overlapping CCEs, where, and and These are the maximum number of PDCCH candidates and non-overlapping CCEs in the scheduled cell, respectively. and These are the total number of PDCCH candidates and non-overlapping CCEs of the scheduled cell, as described in v17.6.0 of [Reference 3].

[0102] In addition to the CSS set used for multicast PDSCH scheduling, the UE does not expect to be configured with a CSS set, which results in the corresponding total number of PDCCH candidates and non-overlapping CCEs monitored per slot on the primary cell or the number of PDCCH candidates and non-overlapping CCEs monitored per slot for each scheduled cell exceeding the corresponding maximum number per slot. For the USS set or for the CSS set associated with multicast PDSCH scheduling, when the number of PDCCH candidates or non-overlapping CCEs in a slot would exceed the limit / maximum number used for scheduling per slot on the primary cell as described herein, the UE selects the USS set or CSS set to monitor the corresponding PDCCH in ascending order of the corresponding search space set index until PDCCH monitoring would result in exceeding the maximum number of PDCCH candidates or non-overlapping CCEs used for scheduling per slot on the PCell, as described in v17.6.0 of [Reference 3].

[0103] For scheduling within the same cell, or for scheduling cells and scheduled cells that have the same SCS configuration For cross-carrier scheduling of DLBWP, the UE does not expect the number of PDCCH candidates and the corresponding number of non-overlapping CCEs per time slot on the secondary cell to be greater than the corresponding number that the UE can monitor per time slot on that secondary cell. For cross-carrier scheduling, the number of PDCCH candidates used for monitoring and the number of non-overlapping CCEs per time slot are counted separately for each scheduled cell.

[0104] The UE can be configured to operate using carrier aggregation (CA) to perform PDSCH reception (DLCA) on multiple cells or PUSCH transmission (ULCA) on multiple cells. The UE can also operate via CORESET (where the UE receives PDCCH / PDSCH from the corresponding TRP). coresetPoolIndex The indication (or absence of indication) is configured in multiple transmit-receive points (TRPs) for each cell, as described in v17.6.0 of [Reference 3] and v17.6.0 of [Reference 4].

[0105] MIMO technology plays a crucial role in improving the system throughput of NR and LTE, and this role will continue and expand in future generations of wireless technologies. For MIMO operation, an antenna port is defined such that the channel through which symbols are transmitted on that antenna port can be inferred from the channel through which other symbols are transmitted on the same antenna port. There is not necessarily a one-to-one correspondence between antenna ports and antenna elements, and multiple antenna elements can be mapped to a single antenna port.

[0106] Figure 9 A diagram illustrates an example Type 1 backscattering structure 900 for an IoT device according to an embodiment of the present disclosure. For example, the Type 1 backscattering structure 900 can be constructed from... Figure 1 It can be implemented by any of the UEs 111-116, or it can be a device with fewer components and functions than a UE. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0107] like Figure 9 As shown, the Type 1 backscatter structure 900 for IoT devices includes an antenna 905, a matching network 910, an RF energy harvester 915, a phasor measurement unit (PMU) 920, an energy storage device 925, an RF bandpass filter (BPF) 930, an RF envelope detector 935, a baseband (BB) low-pass filter (LPF) 940, a comparator 945, a clock generator 950, a BB stream 955, a memory 960, a backscatter (imp matching) 965, and a processing circuit 913.

[0108] In various embodiments, processing circuitry 913 may be a full-power processor (such as included in UE 116), a low-power microprocessor or microcontroller, an application-specific integrated circuit (ASIC), or logic circuitry. Processing circuitry 913 may control the overall operation of the IoT device, including determining receive and / or transmit timing. Processing circuitry 913 may be powered via an energy storage device and power management 905. Signal receiving and transmitting processing circuitry included in the IoT device, such as RF BPF 906, RF envelope detector 908, comparator / analog-to-digital converter (ADC) 910, baseband 912, LO 918, mixer 920, modulator (impedance matching) 922, may be referred to as transceivers, which may receive and transmit using separate antennas, or may transmit and receive using a common antenna such as antenna 905. One or more implementations described herein also include other implementation variations, such as separate Tx-Rx antennas versus a common Tx-Rx antenna, the use of sensors, etc. These implementations should be understood as examples and not limitations.

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

[0110] Figure 11 A diagram illustrates an example type 2a backscattering structure 1100 for an IoT device according to an embodiment of this disclosure. For example, the backscattering structure 1100 may be composed of... Figure 1 It can be implemented by any of UEs 111-116, such as UE 111, or it can be a device with fewer components and functions than a UE. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0111] like Figure 11 As shown, the type 2a backscattering structure 1100 includes an antenna 905, a matching network 910, an RF energy harvester 915, a PMU 920, an energy storage device 925, an energy harvester (excluding RF) 1122, an RF BPF 930, a low-noise amplifier (LNA) 1132, an RF envelope detector 935, a BB amplifier (amp) 1137, a BB LPF 940, a comparator / ADC 1142, a clock generator 950, a BB stream 955, a memory 960, a frequency shifter 1162, a backscattering (imp matching) 965, a reflection amplifier (amp) 1167, and a processing circuit 913.

[0112] Figure 12A diagram illustrates an example type 2b active device structure 1200 for an IoT device according to an embodiment of this disclosure. For example, the backscattering structure 1200 may be composed of... Figure 1 It can be implemented by any of UEs 111-116, such as UE 112, or it can be a device with fewer components and functions than a UE. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0113] like Figure 12 As shown, the Type 2b active device structure 1200 includes an antenna 905, a matching network 910, an RF energy harvester 915, a PMU 920, an energy storage device 925, an energy harvester (excluding RF) 1122, an RF BPF 930, an LNA 1132, an RF envelope detector 935, a BB amp 1137, a BB LPF 940, a comparator / ADC 1142, a clock generator 950, a BB stream 955, a memory 960, a modulator 1265, a digital-to-analog converter (DAC) 1270, a local oscillator (LO) 1275, a mixer 1280, a PA 1285, and processing circuitry 913.

[0114] Figure 13 A diagram is shown of an example type 2b active device structure 1300 for an IoT device according to an embodiment of the present disclosure. For example, structure 1300 may be composed of... Figure 1 It can be implemented by any of UEs 111-116, such as UE 113, or it can be a device with fewer components and functions than a UE. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0115] like Figure 13 As shown, the Type 2b active device structure 1300 includes an antenna 905, a matching network 910, an RF energy harvester 915, a PMU 920, an energy storage device 925, an energy harvester (excluding RF) 1122, an RF BPF 930, an LNA 1132, a mixer 1334, an IF Amp / BPF 1336, an IF envelope detector (ED) 1338, an a BB amp / LPF 1340, a comparator / ADC 1142, a clock generator 950, a BB stream 955, a memory 960, a modulator 1265, a DAC 1270, an LO 1275, a mixer 1280, a PA 1285, and a processing circuit 913.

[0116] Figure 14 A diagram illustrates an example type 2b active device structure 1400 for an IoT device according to an embodiment of this disclosure. For example, the backscattering structure 1400 may be composed of... Figure 1 It can be implemented by any of UEs 111-116, such as UE 114, or it can be a device with fewer components and functions than a UE. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0117] like Figure 14 As shown, the Type 2b active device structure 1400 includes an antenna 905, a matching network 910, an RF energy harvester 915, a PMU 920, an energy storage device 925, an energy harvester (excluding RF) 1122, an RF BPF 930, an LNA 1132, a mixer 1334, a BB amp 1137, a BB LPF 940, a comparator / ADC 1142, a clock generator 950, a BB stream 955, a memory 960, a modulator 1265, a DAC 1270, a LO 1275, a mixer 1280, a PA 1285, and a processing circuit 913.

[0118] Several different types of A-IoT devices can be considered as follows.

[0119] - Device 1: Peak power consumption of approximately 1µW, with an energy storage device, initial sampling frequency offset (SFO) up to 10Xppm, and no R2D or D2R amplification in the device. The device's D2R transmission is backscattered on an externally provided carrier.

[0120] - Device 2a: Peak power consumption ≤ several hundred µW, with energy storage, initial sampling frequency offset (SFO) up to 10X ppm, and R2D and / or D2R amplification in the device. The device's D2R transmission is backscattered on an externally provided carrier.

[0121] - Device 2b: Peak power consumption ≤ several hundred µW, with energy storage, initial sampling frequency offset (SFO) up to 10X ppm, and R2D and / or D2R amplification within the device. The device's D2R transmission is generated internally.

[0122] The device can operate in either frequency division duplex (FDD) or time division duplex (TDD) spectrum, and can be licensed or unlicensed.

[0123] In the following text, reference architectures for the device types used in this article are provided, which should be understood as examples rather than limitations.

[0124] refer to Figure 9 The following is an example of a backscattering device structure of type 1 according to this disclosure.

[0125] RF energy harvester 915 converts RF signals into DC power and supplies it to the device. R2D signals or externally provided CW signals for backscattering can be used for RF energy harvesting. The CW is provided externally by a gNB or a dedicated source. The CW signal source (e.g., a gNB or dedicated node) may or may not be known to the A-IoT device. The harvested energy (e.g., using a rectifier) ​​can be stored using capacitors, supercapacitors, or generally, energy storage devices. For the RF energy harvester and receiver / transmitter, the antennas can be shared or separate. Matching network 910 is used to match the impedance between the antenna and other components. Power management unit (PMU) 920 manages the storage of energy from the energy harvester to the energy storage device and the supply of power to active component blocks that require power. Clock generator 950 provides the required clock signal.

[0126] The R2D signal is demodulated using a low-complexity envelope detector and comparator, and its output is provided as the input to the baseband circuitry. Given the low power and low complexity requirements of Type 1 backscattering devices, RF envelope detection can be a viable solution for receiver architectures compared to heterodyne architectures utilizing IF envelope detection or null-difference architectures utilizing baseband envelope detection (both of which require a LO and a mixer for down-conversion). The input RF signal passes through an RF bandpass filter (BPF) 930 for adjacent channel interference suppression, then the filtered RF signal is directly converted to 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.

[0127] For D2R backscatter transmission, any of the following can be used: -Case 1) Provide CW in the DL spectrum and perform backscattering, i.e., CW@DL spectrum, D2R backscattering@DL spectrum.

[0128] -Case 2) Provide CW in the UL spectrum and perform backscattering, i.e., CW@UL spectrum, D2R backscattering@UL spectrum.

[0129] -Case 3) Provide CW in the DL spectrum, shift the frequency to the UL spectrum, and then perform backscattering, i.e., CW@DL spectrum, D2R backscattering@UL spectrum.

[0130] In one instance, for device 1, either case 1) or case 2) is evaluated, i.e., CW and D2R backscattering at the same frequency, therefore, a frequency shifter (FS) is not required.

[0131] refer to Figure 10An exemplary impedance matching circuit for D2R modulation of a backscattering device is shown according to the present disclosure.

[0132] Here is a simple example of impedance matching operation: - Open circuit: In-phase total reflection of the received CW signal. This can be used for modulation using on-off keying (OOK) of the matching circuit.

[0133] - Short circuit: Total internal reflection of the received CW signal. This can be used for phase shift keying (PSK) modulation.

[0134] - Matching circuit: No reflection because the impedance matches the load, i.e., absorption. This can be used for energy harvesting, Rx mode, or modulation utilizing other matching states.

[0135] - Multi-stage matching circuits: such as Figure 10 As shown, multi-stage impedance matching is applied to Z1, Z2, ..., Z... L , used for ASK modulation of log2(L) bits per symbol.

[0136] Depending on the matched load impedance, the matching circuit can backscatter input CW signals with different reflection coefficients in amplitude and phase. Typically, impedance matching circuits can be used to support ASK / PSK / Frequency Shift Keying (FSK). OOK can be evaluated as the simplest modulation scheme. The device can indicate its modulation capability or impedance matching capability to the network (e.g., network 130), or certain requirements can be predefined in the system operation specifications.

[0137] refer to Figure 11 An example device 2a architecture based on RF envelope detection according to this disclosure is shown.

[0138] Device 2a can share a similar structure with device 1 because D2R transmission is still based on backscattering of an externally provided CW, while device 2a can differ from device 1 in the following ways.

[0139] Device 2a has a peak power consumption of ≤ several hundred µW and incorporates R2D and / or D2R amplification. In this case, alternatives to RF energy harvesting from an R2D signal or an externally supplied CW signal can be provided, along with other renewable energy sources such as solar, thermal, and kinetic energy. From a system design perspective, some form of energy harvesting capability from a renewable energy source is anticipated. The use of an energy harvester (e.g., RF energy harvester only, other energy harvesters only, or both) can be an implementation choice.

[0140] Device 2a may be equipped with R2D and / or D2R amplification. Given the power consumption requirement of ≤ several hundred µW, the R2D / D2R amplification for device 2a can be based on an architecture different from typical power amplifiers (PAs) and low-noise amplifiers (LNAs). In some example low-power / complexity architectures for the forward amplifier for reader-to-device (R2D) reception and the reflective amplifier for device-to-reader (D2R) transmission, a single bipolar transistor terminated in a microstrip pattern can be used. Receiver amplification can be RF amplification before the envelope detector, baseband amplification after the envelope detector, or both, depending on the implementation choice. In one example, the reflective amplifier is used for both R2D reception and D2R transmission, and the LNA may or may not be present. In another example, the reflective amplifier is used only for D2R transmission, and the LNA is used for R2D reception amplification.

[0141] Another difference between device 2a and device 1 could be the use of FS. With peak power consumption of a few hundred µW, some low-power LO architectures with mixers can be evaluated for case 3). Utilizing FS, CW can be expected to be provided at frequencies different from the UL carrier frequency. Considering that A-IoT devices aim for low complexity and low power consumption, the following options can be evaluated as example methods for frequency shifting: - An ultra-low power local oscillator (LO) whose output frequency is multiplied by a frequency multiplier in one or more stages to obtain the desired frequency shift.

[0142] - A calibrated RC (resistor-capacitor) oscillator that uses the CW frequency as the input to an RC oscillator with a phase-locked loop (PLL) circuit.

[0143] - The CW signal is provided at the UL carrier frequency; in this case, a frequency shifter is not required.

[0144] - Use the harmonic frequency of the CW signal or the intermodulation frequency of the two-tone CW signal.

[0145] The receiver architecture of device 2a can be based on an RF envelope detector, an intermediate frequency (IF) envelope detector (i.e., a heterodyne receiver), or a zero-IF zero-differential receiver, as illustrated for device 2b.

[0146] refer to Figure 12 The example device 2b architecture based on RF envelope detection according to this disclosure is shown.

[0147] refer to Figure 13 An example device 2b architecture based on a heterodyne / IF-ED receiver according to this disclosure is shown.

[0148] refer to Figure 14An example device 2b architecture based on a zero-difference / zero-IF receiver according to this disclosure is shown.

[0149] Except that the D2R signal is generated internally using the LO instead of being backscattered from an externally provided CW, device 2b shares a largely similar structure with device 2a. Figures 12 to 14 The example architecture shown is based on a typical active transmitter chain, where D2R data is modulated, converted to an analog signal using a digital-to-analog converter (DAC), then upconverted to the UL carrier frequency using an LO and mixer, followed by an amplifier.

[0150] exist Figure 12 In this architecture, the R2D receiver chain remains based on an RF envelope detector, as in the previous architecture. Figure 13 In this R2D receiver chain, a heterodyne receiver with an IF envelope detector is used. In the heterodyne structure, the RF signal is down-converted to an intermediate frequency (IF) and then detected using the envelope detector. Figure 14 In this R2D receiver, the receiver is based on a zero-difference receiver, i.e., zero IF. In the zero-difference / zero IF structure, the RF signal is directly down-converted to a baseband signal, and then detected using a comparator / ADC.

[0151] Figures 9 to 14 This should be understood as being for illustrative purposes only. Other components not explicitly shown in the figures may be present, such as switches, duplexers, and filters, or some components may be replaced with different options. Furthermore, the device can operate in both TDD and FDD spectrum, whether licensed or unlicensed, and the actual architecture may differ from the conceptual illustrations in the figures depending on the operating spectrum.

[0152] When deploying A-IoT devices, different topology options can be evaluated. Examples of topology options are provided below: -Topology 1: BS A-IoT devices --A-IoT devices communicate directly and bidirectionally with the base station. Communication between the base station and the A-IoT devices includes A-IoT data and / or signaling. This topology includes the option of sending a different base station (BS) to the A-IoT devices than sending a different BS to the A-IoT devices.

[0153] -Topology 2: BS intermediate nodes Environmental IoT devices

[0154] --Bidirectional communication between A-IoT devices and intermediate nodes between devices and base stations. In this topology, intermediate nodes can be A-IoT relays, IAB nodes, UEs, repeaters, etc. Intermediate nodes transmit A-IoT data and / or signaling between the BS and A-IoT devices. In this disclosure, intermediate nodes are referred to as I nodes.

[0155] Topology 3: BS auxiliary nodes Environmental IoT devices BS

[0156] --A-IoT devices send data / signaling to the BS and receive data / signaling from auxiliary nodes; or A-IoT devices receive data / signaling from the base station and send data / signaling to auxiliary nodes. In this topology, auxiliary nodes can be A-IoT relays, IABs, UEs, repeaters, etc.

[0157] Topology 4: UE Environmental IoT devices

[0158] -- Bidirectional communication between A-IoT devices and UEs. Communication between the UE (e.g., UE 116) and A-IoT devices includes A-IoT data and / or signaling.

[0159] This disclosure applies to at least the following deployment scenarios: Scenario 1: Device is indoors, BS is indoors Scenario 2: Equipment is indoors, BS is outdoors -Scenario 3: Indoor device, UE-based reader Scenario 4: Equipment is outdoors, BS is outdoors -Scenario 5: Outdoor device, UE-based reader A-IoT deployments can be carried out at the same sites as existing 3GPP deployments corresponding to the BS type (e.g., macro cells, micro cells, pico cells, etc.). In some embodiments, A-IoT deployments may be anticipated at new sites, rather than existing 3GPP deployments. Deployment can be based on licensed or unlicensed TDD or FDD spectrum, which may be within the frequency band of existing deployments, within the guard band of existing deployments, or within a separate frequency band. Different service types can be supported, including device-terminating (DT) and device-initiated (DO) services, where DO services can be further subdivided into DO autonomous (DO-A) and DO device-termination-triggered (DO-DTT) types.

[0160] A-IoT devices are a type of UE. The embodiments in this disclosure are generally applicable to other types of UEs, such as smartphones, AR / VR devices, or any other type of IoT device.

[0161] Figure 15 An example system 1500 for D2R / R2D transmission, including an intermediate node, is illustrated according to an embodiment of this disclosure. For example, system 1500 can... Figure 1 This is implemented in a wireless network 100. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0162] refer to Figure 15 The diagram illustrates a topology involving intermediate nodes, where an intermediate node (I-node) can be any of a UE, relay, repeater, dedicated node, or gNB (e.g., BS 102). Any operation performed by the BS can also be performed by the I-node instead of the BS, and each or part of the interface is transparent to A-IoT devices.

[0163] Entities that communicate directly with devices or tags are collectively referred to as readers, which can be such as... Figure 15 The intermediate nodes, auxiliary nodes, UEs, or BSs that communicate directly with the device are shown.

[0164] This disclosure applies to any of the following spectrum options, wherein the reader can be any of the BS, intermediate node, auxiliary node, or UE in any of the topologies or scenarios disclosed herein: - Scenarios where the reader is an intermediate node, auxiliary node, or UE --CW is transmitted on the DL spectrum, and D2R is transmitted on the DL spectrum or shifted to the UL spectrum.

[0165] --CW is transmitted on the UL spectrum, and D2R is transmitted on the UL spectrum or shifted to the DL spectrum.

[0166] --The reader's R2D transmission is on the DL spectrum or UL spectrum.

[0167] --The node sending CW can be a node inside the topology, such as a BS, intermediate node, auxiliary node or UE, or a node outside the topology, such as a dedicated CW source.

[0168] --The reader receiving D2R transmissions and the reader sending R2D transmissions can be the same or different.

[0169] --As an example, CW is transmitted on the DL spectrum and D2R transmission is shifted to the UL spectrum, where the node transmitting CW is either inside or outside the topology, and the reader transmitting R2D and the reader receiving D2R can be the same or different.

[0170] --As another example, CW is transmitted on the DL or UL spectrum, and D2R transmission is on the same spectrum as the CW transmission, wherein the node transmitting CW is either inside or outside the topology, and the reader transmitting R2D and the reader receiving D2R can be the same or different.

[0171] In this disclosure, the physical channel used for reader-to-device transmission is referred to as the Physical Reader-to-Device (R2D) Channel (PRDCH), and the physical channel used for device-to-reader transmission is referred to as the Physical Device-to-Reader (D2R) Channel (PDRCH).

[0172] For PRDCH and PDRCH transmissions, timing acquisition signals (e.g., preambles) are included, at least for timing acquisition and for indicating the start of transmission in the time domain, respectively.

[0173] The following timing relationships can exist between transmissions: -T R2D_min T R2D_max Minimum / maximum time between R2D transmission and the corresponding D2R transmission thereafter.

[0174] -T D2R_min T D2R_max Minimum / maximum time between a D2R transmission and its corresponding R2D transmission.

[0175] -T R2D_R2D_min T R2D_R2D_max Minimum / maximum time between two different consecutive R2D transmissions to the same A-IoT device.

[0176] -T D2R_D2R_min T D2R_D2R_max Minimum / maximum time between two distinct consecutive D2R transmissions from the same A-IoT device.

[0177] Given the low complexity and low power consumption requirements of A-IoT devices, it's clear that oscillators equipped with A-IoT devices will be significantly less powerful than those equipped with ordinary NR UEs. Therefore, expecting A-IoT devices to have the same precise timing capabilities as ordinary NR UEs is unrealistic. Furthermore, since A-IoT devices are powered by harvested energy, they may occasionally run out of power, resulting in a loss of timing—that is, a lack of timing maintenance capability.

[0178] When the reader is not a BS (Browser / Base Station), for example, when the reader is an intermediate node, auxiliary node, or UE (User Equipment), the reader may need to be under network control regarding transmissions or receptions between the reader and the BS, and between the reader and one or more devices. Therefore, embodiments of this disclosure recognize the need to define processes and methods for providing the reader with parameters related to transmissions or receptions between the reader and the BS, and between the reader and one or more devices.

[0179] When the reader is not a BS (Browser / Base Station), for example, when the reader is an intermediate node, auxiliary node, or UE (User Equipment), the reader may need to provide a function to execute commands received from the BS to one or more devices and to forward information between the BS and one or more devices. Therefore, embodiments of this disclosure also recognize the need to define processes and methods for the reader to execute commands received from the BS and to pass information received from the BS to one or more devices, and vice versa.

[0180] When the reader is not a BS, for example, when the reader is an intermediate node, auxiliary node, or UE, the reader may need to receive commands from the BS in order to execute them on one or more devices in a timely manner. Therefore, embodiments of this disclosure also recognize the need to define procedures and methods for the reader to receive commands from the BS via a DCI format or MAC CE that provides the commands.

[0181] When the reader is not a BS (Browser / Base Station), for example, when the reader is an intermediate node, auxiliary node, or UE (User Equipment), the reader's transmissions may cause interference to other ongoing communications beyond the tolerance level. The reader's transmissions include R2D transmissions and possible CW (Content-Wave) transmissions (if not provided by nodes outside the topology). Therefore, embodiments of this disclosure also recognize the need to define processes and methods for controlling the reader's R2D or CW transmit power or other transmission-related parameters.

[0182] When the reader is not a BS (Browser / Server), for example, when the reader is an intermediate node, auxiliary node, or UE (User Equipment), the BS may not be fully aware of the channel conditions at the reader for transmitting R2D or receiving D2R, or may not be able to allocate channels in an instantaneous manner. Therefore, embodiments of this disclosure also recognize the need to define processes and methods for allocating a set of resources to the reader and for the reader to select resources from that set to communicate with one or more devices.

[0183] This disclosure relates to communication systems. Specifically, it relates to defining functions and procedures for an A-IoT reader, which may be an intermediate node (auxiliary node, UE, relay, BS, dedicated CW source, or repeater) facilitating communication between a BS and one or more devices.

[0184] This disclosure relates to defining functions and processes for providing a reader with parameters related to the transmission or reception between the reader and the BS, and between the reader and one or more devices.

[0185] This disclosure also relates to defining functions and procedures for a reader to execute commands received from a BS and to transmit information received from the BS to one or more devices, and vice versa.

[0186] This disclosure also relates to defining functions and procedures for a reader to receive commands from a BS via a DCI format or MAC CE that provides the commands.

[0187] This disclosure also relates to defining functions and processes for controlling the R2D or CW transmit power or other transmission-related parameters of a reader.

[0188] This disclosure also relates to defining functions and procedures for allocating a set of resources to a reader and for a reader to select resources from that set of resources to communicate with one or more devices.

[0189] Embodiments of this disclosure relating to an A-IoT reader are summarized below and described in further detail herein, wherein the A-IoT reader may be an intermediate node (auxiliary node, UE, relay, BS, dedicated CW source or repeater) that facilitates communication between a BS and one or more devices.

[0190] -Methods and apparatus for defining methods and apparatus for providing a reader with parameters related to transmission or reception between the reader and the BS, and between the reader and one or more devices.

[0191] - Used to define methods and apparatus for a reader to execute commands received from a BS and to transmit information received from a BS to one or more devices, and vice versa.

[0192] - Methods and apparatus for defining a reader for receiving commands from a BS via a DCI format or MAC CE that provides the commands.

[0193] - Methods and apparatus for defining R2D or CW transmit power or other transmission-related parameters for controlling a reader.

[0194] - This defines methods and apparatus for allocating a set of resources to a reader and for a reader to select resources from that set of resources to communicate with one or more devices.

[0195] Figure 16A flowchart of an example reader process 1600 for transmitting information between a BS and a device according to an embodiment of the present disclosure is shown. For example, process 1600 can be performed by any reader device described herein. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0196] The process begins in step 1610, where the reader receives parameters from the BS related to transmission or reception on the link between the reader and the BS. In step 1620, the reader receives parameters from the BS related to transmission or reception on the link between the reader and the device. In step 1630, the reader receives a command from the BS for one or more devices to execute, which may involve receiving parameters, data, or control information related to the command. In step 1640, the reader instructs one or more devices to execute the command, which may involve sending and receiving data or control information. In step 1650, the reader sends the data or control information received from one or more devices to the BS.

[0197] The entire process of controlling the reader includes: the reader receiving parameters related to sending or receiving on the link between the reader and the BS and the link between the reader and the device; the reader executing commands received from the BS to one or more devices; and the reader transmitting information between the BS and one or more devices.

[0198] refer to Figure 16 The present disclosure illustrates an example flowchart of a reader receiving configuration from a BS, communicating with a device, and transferring information between the BS and the device.

[0199] In step 1610, the reader receives parameters related to transmission or reception on the link between the reader and the BS via a PDCCH providing DCI format or a PDSCH providing MAC CE or RRC. The parameters related to transmission or reception on the link between the reader and the BS include one or more of the following: - A search space configuration in DCI format for monitoring from the BS to the reader, providing control information related to executing commands between the reader and one or more devices.

[0200] -SPS PDSCH configuration is used to receive R2D data / control information from the BS that will be sent to one or more devices.

[0201] - Configuration authorization (CG) PUSCH configuration used to send D2R data / control information received from one or more devices to the BS.

[0202] - Physical uplink control channel (PUCCH) resources used for transmitting D2R control information or for sending scheduling requests (SRs) for transmitting D2R data / control information received from one or more devices to the BS.

[0203] - When the PUCCH resource is unavailable, a dedicated RACH resource is used for the SR.

[0204] - Indication of the time slot format of the link between the reader and the BS.

[0205] --The time slot format can be any of DL, UL, or F (flexible).

[0206] --Dynamic indication of whether the F-slot is used for DL ​​and UL.

[0207] --If none of the DL, UL, or F resources are used, then dynamic instructions are given.

[0208] In step 1620, the reader receives parameters related to transmission or reception on the link between the reader and the device from the BS via a PDCCH providing DCI format or a PDSCH providing MAC CE or RRC. The parameters related to transmission or reception on the link between the reader and the device include one or more of the following: - Parameters related to R2D / D2R power control, including target received power, path loss scaling factor, etc.

[0209] --The transmit power of the PDRCH preamble can be explicitly indicated.

[0210] -- Allows D2R power amplification, for example, expressed as on / off or allowed amplification gain value (in dB).

[0211] --P used for R2D transmission CMAX

[0212] - Frequency domain parameters (BW, position, SCS) used for R2D transmission and D2R reception.

[0213] --D2R transmission allows for frequency shifts / channels.

[0214] - Dynamic R2D and / or D2R resource allocation or CG resource allocation in the time or frequency domain.

[0215] - Indication of the time slot format of the link between the reader and the device.

[0216] --The time slot format can be any of R2D, D2R, or F, and each resource can also be indicated as hard / soft / unavailable. Below is an example of how a reader identifies soft or soft resources: ---BS- The reader UL resource is configured, but there is no UL data or no valid scheduling authorization has been received.

[0217] ---The reader can simultaneously perform UL transmission to the BS and R2D transmission to the device.

[0218] ---The reader is full-duplex.

[0219] ---Receives explicit indication from the BS that a particular BS reader resource is not in use, thus allowing the reader to decide for itself how to use the resource.

[0220] - For PRDCH / PDRCH, the use of preamble format (e.g., long, short, or indexed from the supported preamble set), midamble, and postamble.

[0221] --In one example, a preamble sequence is provided from a set of sequences.

[0222] - Parameters related to random access resource configuration

[0223] -- Multiple time slots used for random access, the duration of which is predefined in the system operation specification or indicated in the trigger message.

[0224] --Frequency domain resources. In one example, it can be multiple frequency domain resources, where the resource can be a subcarrier, a PRB, a unit frequency quantity, or a frequency range. As an example, the device can randomly select a frequency resource from multiple resources. In another example, it can be multiple frequency shifts, where the frequency shift can be indicated by ±Δ Hz, ± integer multiples of a unit frequency quantity, or parameters of the line code (such as the number of subcarrier cycles per symbol).

[0225] --Indications may exist for available or prohibited time slots / frequency resources / frequency shifts for random access, for example, using a mask or bitmap of size equal to the number of time slots. Masks / bitmaps may be provided individually for each frequency resource / frequency shift, or uniformly.

[0226] -Parameters related to random access

[0227] --Media access probability, which can be applied to a given time slot, or applied individually to each time slot. In one example, the access probability could be 1.

[0228] --Maximum number of allowed random access transmissions

[0229] --Response monitoring window after sending random access

[0230] --Disable timers after a failed random access attempt

[0231] - Parameters associated with the identifier included in the PDRCH transmission. In one instance, the parameters relate to random number generation, such as the interval used to draw random numbers, for example, [0, 2]. N -1], where N is indicated. In another example, an indication of the identifier type is provided, such as a device product code, e.g., PC, XPC, Electronic Product Code (EPC), or a random number, and such as full format or shortened format.

[0232] -Parameters related to PDRCH

[0233] --Transmission duration, for example, expressed in the number of symbols or chips, payload size

[0234] --Frequency resources, such as specific subcarriers, PRBs, or frequency ranges used for transmission. In another example, a specific frequency shift amount used for UL transmission, such as ±Δ Hz, ± integer multiples of a unit quantity of frequency, or parameters of the line code (such as the number of subcarrier cycles per symbol).

[0235] --Parameters of the MCS or line code (such as the number of subcarrier cycles per symbol).

[0236] --If more than one format is supported, append the preamble, intermolecular, postmatrix and their format (e.g., long format or short format).

[0237] --Append CRC and / or CRC size.

[0238] --Modulation types, such as OOK-1, OOK-4, BPSK, QPSK, FSK, and multi-order ASK.

[0239] -- An indicator of the encoding type, such as Manchester encoding, FM0, or Miller encoding.

[0240] - Parameters related to D2R autonomous access, such as the number of time slots used for autonomous access, time slot duration, maximum payload size, etc.

[0241] -PRDCH controls the field format, for example, if a different set of PHY schemas is defined. For instance, it can be indicated as an index from a set of supported PHY schemas.

[0242] - Maximum transmission length for R2D and D2R, expressed in terms of symbol, duration, or payload size.

[0243] - Acknowledgment / non-acknowledgment mode used for communication between the reader and the device.

[0244] - Relative timing parameters used for communication between the reader and the device.

[0245] - Ranging Mode: If more than one ranging mode is supported, the reader can be indicated by an index from the set of supported ranging modes.

[0246] -Parameters related to CW transmission

[0247] --Indicates whether to send CW.

[0248] ---This may involve the reader reporting its ability to transmit CW to the BS, along with related parameters such as the ability to transmit single or multiple tones, CW transmission power, etc.

[0249] ---If instructed to send a CW, it may involve the time pattern used to send the CW. In one example, it may indicate or anticipate sending a CW.

[0250] --CW carrier frequency, DL or UL spectrum of FDD band, CW transmission BW, waveform-related information, etc.

[0251] ---Waveform-related information includes single-tone or multi-tone CW transmission. For multi-tone CW, it may also include power distribution on the tone and subcarrier spacing.

[0252] ---PRDCH to CW power offset.

[0253] - Parameters related to channel BW and parameter set, used for links between the reader and one or more devices, etc.

[0254] --BW can be a system, a channel, or an occupied BW.

[0255] In step 1630, the reader receives a command from the BS to execute on one or more devices, which may involve receiving parameters, data, or control information associated with the command. The following is an example list of commands that can be instructed from a reader to a device, and the parameters associated with those commands, according to this disclosure. The command may be received via a PDCCH providing DCI format or a PDSCH providing MAC CE or RRC.

[0256] - Read / Write: The device reads and returns specific data from or writes received data to the memory, including one or more of the following.

[0257] --All or part of the device product code --Country code --Version / Generation Information --Device ID, --Sensor data, --Or any data that can be read from or written to the device's memory.

[0258] - Request random number / set parameters: The device returns a random number or settings parameters related to random number generation, such as N used to set the range of values ​​to draw the random number, for example, [0, 2]. N -1].

[0259] - Status Reporting / Update: The device reads and returns a specific status or updates the status based on a received command, the status including one or more of the following: --Password status (e.g., protected, unprotected), current / new password, --Device status (e.g., identified, unidentified, arbitration / response / confirmation / open / secure / terminated, etc.) --or memory size.

[0260] - Lock / Unlock: The device may be permanently or temporarily locked / unlocked for one or more of the following: --password, --Specific storage, --or the entire memory.

[0261] - Access / Terminate: Device accesses or terminates a process, storage, or command.

[0262] Device activation / deactivation

[0263] -Reset: The device resets one or more of the following: --A specific or every counter in a set of counters used by the device, for example, a time slot counter. --Specific storage, --Or data from data stored in the device's memory.

[0264] - Get / Set Configuration: The device reports or sets a configuration parameter based on one or more of the following commands: --The device's transmit power level, for example, maximum equivalent isotropic radiated power (EIRP). --Equipment scaling level, --PRDCH receives parameters, or --PDRCH sends parameters, --The received or transmitted parameters include one or more of the following: ---Modulation schemes (OOK-N with N and number of chips per symbol duration, Double Side Band (DSB) / Synchronization Block (SSB) / Phase Inversion Amplitude Shift Keying (PR-ASK), PSK, FSK with modulation order), ---Encoding schemes (e.g., Manchester, FMO, PIE, Miller with chip count per symbol), ---Use scrambling, ---Operating frequency, bandwidth, operating channel index, single-tone and multi-tone, default frequency shift, frequency hopping sequence / rate ---The use of forward error correction (FEC), ---Use of CRC ---Use preamble / intro / postamble and related parameters, such as length, short or long format, waveform. ---Bit rate, --- Timing parameters, for example, T R2D_min T R2D_max T D2R_min T D2R_max T R2D_R2D_min T R2D_R2D_max T D2R_D2R_min T D2R_D2R_max .

[0265] When the reader receives a request from the BS, the reader executes one or more commands listed in this document on one or more devices.

[0266] The reader can also be instructed to perform ranging operations on one or more devices and parameters for performing ranging operations, such as: the ranging mode to be used, L1 measurements (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Received Signal Strength Indicator (RSSI), Signal-to-Interference-plus-Noise Ratio (SINR)) and thresholds to be used to determine the process.

[0267] The reader can also be instructed to perform an inventory process and the parameters used to perform the inventory process, such as random access configuration.

[0268] When the reader receives a command from the BS, the reader can also be directed to a specific target device based on that command. In one example, the reader is instructed to execute the command with a specific device ID. In another example, the reader is instructed to execute the command with a specific device group ID, where...

[0269] In addition to the device ID, a device can be assigned a unique device group ID.

[0270] A device ID can consist of two parts: the first part is the device group ID, and the second part is the device ID within that group. In this case, the first part of the device ID is indicated.

[0271] - Select a subset of devices by using mod(device ID, K) = L. In this case, both K and L are indicated. In one example, L is fixed (e.g., zero) and only K is indicated.

[0272] In another example, the reader is instructed to execute commands to any nearby anonymous devices.

[0273] In step 1640, the reader instructs one or more devices to execute commands, which may involve the sending and receiving of data or control information.

[0274] The principles for instructing and executing commands between a reader and a device include: a PRDCH transmission by the reader providing the command and related parameters, and a PDRCH transmission by the device providing an acknowledgment (ACK) after the received command has been executed. The ACK message from the device may include additional information for the reader, such as a temporary device ID (e.g., a random number) or the assigned device ID. In another example, the PRDCH transmission providing the command may also provide scheduling information for the PDRCH transmission, causing the device to send additional information as part of the command execution (such as a "read" command). In this case, the reader may send an ACK-providing PDRCH after receiving a PDRCH transmission from the device.

[0275] In one example, the PRDCH providing the command is device-specific. The PRDCH provides a specific device ID, which can be an assigned ID (e.g., a handler identifier) ​​or a device product-related ID. In another example, the PRDCH providing the command is device group-specific. The PRDCH provides a specific device group ID, which can be a management ID or a group ID from the device product code. It can also be an assigned ID. For example, a device group can be defined as a group of devices whose IDs satisfy mod(device ID, K) = L, where K and / or L are indicated or predefined. In one example, L is fixed (e.g., zero) and only K is indicated. Or, in another example, K is fixed and L is indicated. In yet another example, the PRDCH providing the command is public to any device receiving the command. In this case, the PRDCH is addressed to NULL or a specific code point for broadcast purposes, which is predefined in the system operation specification.

[0276] In step 1650, the reader sends data or control information received from one or more devices to the BS. This step may involve CG PUSCH or PUCCH transmissions performed as configured. This step may also involve PUCCH or Physical Random Access Channel (PRACH) transmissions for the SR. This step may also involve BS buffer status report (BSR) transmissions, where the BSR may be provided separately for data forwarding from devices other than the reader's own data, or it may be provided as a report that does not distinguish between data forwarding from devices and the reader's own data. This step may also involve ACK / NACK (NACK) forwarding from one or more devices as a result of command execution.

[0277] The reader receives control information from the BS relating to executing commands to one or more devices via a PDCCH providing DCI format or a PDSCH providing MAC CE or RRC. The information elements disclosed herein may be indicated in either a PDCCH providing DCI format or a PDSCH providing MAC CE or RRC: - An index of commands from a set of commands and any associated parameters, as illustrated in this article.

[0278] - TPC commands for R2D transmission can be absolute power values ​​in dBm or as an index to a value from a set of predefined values; or differential values ​​of the current transmit power, indicated by ±dB or as an index to a value from a set of predefined differential values.

[0279] - Indicates R2D or R2D data forwarding and the data to be forwarded. In one example, R2D forwarding data is provided via PDSCH, and the DCI format provides scheduling information for PDSCH.

[0280] - Information related to configuring or activating / deactivating SPS PDSCH or CG PUSCH.

[0281] -Parameters related to equipment selection

[0282] --Specific Device ID

[0283] --Specific device group ID

[0284] ---In addition to the device ID, a unique device group ID can be assigned to the device.

[0285] ---A device ID can consist of two parts: the first part is the device group ID, and the second part is the device ID within that group. In this case, the first part of the device ID is indicated.

[0286] ---mod(device ID, K) = L. In this case, both K and L are indicated. In one example, L is fixed (e.g., zero) and only K is indicated.

[0287] --All devices, for example, address the target device or group of devices by indicating NULL or some predefined code points in the PRDCH transmission.

[0288] If a DCI format is used, referred to as DCI format A in this disclosure for simplicity, the PDCCH providing DCI format A can be received in a UE-specific or UE-group-specific manner according to the USS or CSS set, and scrambled by one or more of C-RNTI / Configured Scheduling RNTI (CS-RNTI) / MCS-C-RNTI or a new dedicated RNTI (which may be referred to as A-RNTI (A-IoT RNTI)). Considering the UE design constraints (e.g., UE 116) for maintaining the “3+1” limit on the size of the decoded DCI format that a UE can receive from the PDCCH of each cell, several options can be provided for DCI format A received on the PDCCH of the decoded cell, as disclosed herein.

[0289] In the first approach, the size of DCI format A can be separate from the sizes of other DCI formats of the corresponding PDCCH on the same cell monitored by the UE, for example, smaller. Then, to maintain the "3+1" constraint on the cell's DCI format size, the UE may need to perform additional size matching for the DCI format of the corresponding PDCCH of the cell the UE receives (where the UE receives the PDCCH providing DCI format A). This will result in an increase in the size of some DCI formats because size matching between the two DCI formats is achieved by padding zeros into one of the DCI formats with the smaller size.

[0290] In the second method, to avoid increasing the size of other DCI formats, the size of DCI format A can be defined by the system operation specifications to be the same as the size of one of the already defined DCI formats (e.g., DCI format 1_0). If the total size of DCI format A is less than the size of the selected DCI format among the already defined DCI formats, the UE can pad DCI format A with bits (e.g., bits with a value of 0) until the size of DCI format A is the same as the size of the selected DCI format among the already defined DCI formats.

[0291] In the third method, instead of being specified as having the same size as one of the already defined DCI formats, the size of DCI format A can be individually indicated to the UE by the serving gNB via higher-layer signaling (e.g., via SIB or via UE-specific RRC signaling). Compared to the second method, the third method provides flexibility to the serving gNB, but at the cost of a small amount of signaling overhead. The indication of the size of DCI format 2_8 can be optional. If provided, the UE appends zeros to the bits of the fields in DCI format A until the size is the same as the indicated size. If not provided, the UE determines the size of DCI format A based on the total number of bits in the fields of DCI format A.

[0292] Power control of the reader used for the link between the reader and the device can be based on open-loop power control.

[0293] For open-loop power control, in one example, the device measures the RSRP from the PRDCH received from the reader and reports the measured RSRP to the reader. Measurements can be performed on the PRDCH preamble. In this case, based on the reported RSRP, the reader calculates the PL by subtracting the RSRP from the PRDCH transmit power. R2D .

[0294] In another example, the reader measures the path loss from the backscattered signal from the device. In this case, the path loss is calculated as PL. R2D = (P) Tx – RSRP + R gain –R loss ) / 2, where

[0295] -P Tx It is the transmission power of the signal from the reader.

[0296] --If the reader is a CW source, then it can be the CW transmit power.

[0297] --If the reader is not the source of the CW, it can be the transmit power of any signal that can be detected by the reader itself when the signal returns to it, such as PRDCH, preamble / intermulet / postamble, or any signature sequence. In one example, the signal is transmitted at a frequency different from the CW transmission frequency, but still within the device's backscatter bandwidth. In this case, the reader measures the RSRP over the frequency range of the transmitted signal. In another example, the reader instructs the CW source to remain silent while transmitting a signal for reflection, allowing the reader to measure the RSRP of the returned signal it transmits.

[0298] -RSRP is the signal power measured at the reader.

[0299] -R gain This is the reflection amplification gain at the device. This value can be reported or set to a specific value. R loss It is the reflection loss at the equipment location.

[0300] --In one example, the two values ​​are reported by the device to the reader separately.

[0301] --In another example, the device reports a single result value to the reader, such as R. gain –R loss .

[0302] --In yet another example, the device sets its amplification gain such that R gain –R loss = L, where L is indicated by BS or is predefined, for example, L = 0.

[0303] --In yet another example, the reader has prior knowledge about these values, i.e., no signaling is required.

[0304] Using the exported PL R2D The transmit power of R2D for a specific device (used as a reference for path loss measurement) can be derived as P R2D = min(P) MAX , P 0, R2D +10 log 10 (BW) + α PL R2D ),in

[0305] -P MAX It is the maximum transmit power that the reader is allowed to transmit on the R2D link, which can be indicated to the reader by the BS or predefined, for example, by specification or UE power level.

[0306] -BW is the bandwidth for R2D transmission.

[0307] - P 0, R2D α and β are parameters related to power control and can be indicated by BS or predefined.

[0308] In one example, P is calculated. R2D The device determines and individually configures the reader's transmit power for each device. In another example, based on P calculated for one or more devices... R2D This allows for the joint determination and configuration of the reader's transmit power for the devices. In one example, a maximum P calculated for one or more devices is used. R2D In another example, using minimum or average P... R2D In yet another example, P using the reference device...R2D .

[0309] Use P R2B This represents the transmit power calculated for the reader's transmission to the BS. In one example, the reader's transmit power on the R2D or R2B link is determined to be P. R2D and P R2B The smaller of the two values. In another example, the reader's transmit power on the R2D link or R2B link is determined independently.

[0310] The transmit power control disclosed herein is applied to R2D transmissions that include at least PRDCH transmissions. If the reader is also a CW source, the transmit power control disclosed herein is also applied to CW transmissions.

[0311] Figure 17 A flowchart of an example reader process 1700 for selecting resources according to an embodiment of the present disclosure is shown. For example, process 1700 can be performed by any reader device described herein. This example is for illustration only, and other embodiments may be used without departing from the scope of this disclosure.

[0312] The process begins at step 1710, where the reader receives parameters from the BS related to selecting resources from the resource set. In step 1720, the reader performs sensing on the resource set and selects resources. In step 1730, the reader uses the selected resources to communicate with one or more devices.

[0313] The general process by which a reader selects resources for communication with one or more devices includes the reader receiving parameters related to resources from the BS and selecting resources from a resource set, and the reader sensing the resource set and selecting resources for communication. The resource set, or resource pool, can be any of time-domain, frequency-domain, or code-domain resources.

[0314] refer to Figure 17 This illustrates a sample flowchart of a reader selecting resources from a resource set according to this disclosure.

[0315] In step 1710, the reader receives parameters from the BS related to selecting resources from the resource set.

[0316] In one example, the resource is a frequency domain resource. A frequency domain resource can be a subchannel, which can be indicated to the reader by the number and starting position of PRBs, an index from the BWP set, an index of unit bandwidth within the carrier, or via frequency location and bandwidth. For example, a frequency resource is a contiguous and non-overlapping set of PRBs, where the number of PRBs is ≥ N. In one example, the frequency resource set is common to both R2D and D2R links, and the selection of frequencies from this common frequency resource set may be common or separate for both R2D and D2R links. In another example, frequency resource sets are provided separately for R2D and D2R communication, and the reader selects resources from the frequency resource set used for R2D and from the frequency resource set used for D2R.

[0317] In another example, the resource is a temporal resource. In one example, it is a symbol, time slot, subframe, or frame from the NRUu link between the reader and the BS. In another example, it can be a collection of temporal resources or patterns, such as every N symbols, time slots, subframes, or frames.

[0318] In yet another example, the resource is a code field resource. In one example, it is a collection of sequences or patterns used for preambles, intermezzos, or postcodes.

[0319] In step 1720, the reader performs sensing on the resource set and selects resources.

[0320] The reader can perform L1 measurements on a set of resources in any of the time, frequency, or code resources, such as RSRP, RSRQ, RSSI, SINR, etc. A time window may exist associated with the measurement to perform averaging of the L1 measurements. In one example, a measurement is performed on the detected preamble from a PRDCH or PDRCH transmission on a given resource.

[0321] In one example, the device is provided with a threshold to determine whether a resource is available. If the measured channel conditions are better than the threshold—for example, if the measured RSRP on the resource is below the threshold—the reader determines that the corresponding resource is available. Among the available resources, the reader randomly selects a resource. If no resource is available, the reader adjusts the threshold, for example, by increasing the threshold by X dB. In one example, if the percentage of available resources is less than a certain threshold, for example, N%, the reader continues to adjust the threshold and selects a resource from the set of available resources only when the availability is greater than or equal to N%. In another example, the reader randomly selects a resource whenever at least one or more available resources exist.

[0322] After the reader selects resources, it reports the selected resources to the BS, such as one or more indices from the resource set. If the resource sets are configured separately in one or more domains, the selected resources can be indicated separately for each of the time, frequency, or code domain resources. Other related reports, such as the threshold used for selection or the actual measured L1 value, can be provided by the reader to the BS.

[0323] In one example, the reader reports the Channel Busy Rate (CBR) to the BS. In one instance, CBR is defined as the percentage of time, frequency, or code resources for which an L1 measurement (e.g., any of RSRP, RSRQ, RSSI, SINR, etc.) is greater than a certain threshold. In another example, CBR is defined as the percentage of resources where a preamble signal is detected above a certain threshold. A specific time window may be associated with the measurement for averaging.

[0324] In step 1730, the reader uses the selected resources to communicate with one or more devices.

[0325] The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the individual steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps may be omitted or replaced with other steps.

[0326] Figure 18 Block diagrams of a UE according to various embodiments of the present disclosure are shown. Furthermore, Figure 18 The UE corresponds to Figure 1 and Figure 3 UE.

[0327] like Figure 18 As shown, the UE according to the embodiment may include a transceiver 1810, a memory 1820, and a processor 1830. The transceiver 1810, memory 1820, and processor 1830 of the UE can operate according to the communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. Furthermore, the processor 1830, transceiver 1810, and memory 1820 may be implemented as a single chip. Additionally, the processor 1830 may include at least one processor.

[0328] Transceiver 1810 generally refers to both UE receivers and UE transmitters, and can send / receive signals to / from base stations or network entities. Signals sent to or received from base stations or network entities may include control information and data. Transceiver 1810 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying low noise and down-converting the frequency of the received signal. However, this is merely an example of transceiver 1810, and the components of transceiver 1810 are not limited to RF transmitters and RF receivers.

[0329] In addition, transceiver 1810 can receive signals via a wireless channel and output signals to processor 1830, and can also transmit signals output from processor 1830 via a wireless channel.

[0330] The memory 1820 can store programs and data required for the operation of the UE. Furthermore, the memory 1820 can store control information or data included in signals received by the UE. The memory 1820 can be a storage medium such as read-only memory (ROM), random access memory (RAM), hard disk, CD-ROM, and DVD, or a combination of storage media.

[0331] The processor 1830 can control a series of processes to enable the UE to operate as described above. For example, the transceiver 1810 can receive data signals, including control signals, transmitted by a base station or network entity, and the processor 1830 can determine the result of receiving the control signals and data signals transmitted by the base station or network entity.

[0332] Figure 19 Block diagrams of base station or network entities according to various embodiments of the present disclosure are shown. Furthermore, Figure 19 The base station or network entity corresponds to Figure 1 and Figure 2 gNB.

[0333] like Figure 19 As shown, a base station (or network entity receiver) according to an embodiment may include a transceiver 1910, a memory 1920, and a processor 1930. The transceiver 1910, memory 1920, and processor 1930 of the base station (or network entity receiver) can operate according to the communication method of the base station (or network entity receiver) described above. However, the components of the base station (or network entity receiver) are not limited thereto. For example, the base station may include more or fewer components than described above. Furthermore, the processor 1930, transceiver 1910, and memory 1920 may be implemented as a single chip. Additionally, the processor 1930 may include at least one processor.

[0334] Transceiver 1910 refers to both base station (or network entity receiver) and base station (or network entity) transmitter, and can send / receive signals to / from a terminal, network entity, or base station. Signals sent to or received from a terminal, network entity, or base station may include control information and data. Transceiver 1910 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying low noise and down-converting the frequency of the received signal. However, this is merely an example of transceiver 1910, and the components of transceiver 1910 are not limited to RF transmitters and RF receivers.

[0335] In addition, transceiver 1910 can receive signals via a wireless channel and output signals to processor 1930, and transmit signals output from processor 1930 via a wireless channel.

[0336] The memory 1920 can store programs and data required for the operation of the base station (or network entity receiver). Furthermore, the memory 1920 can store control information or data included in signals received by the base station. The memory 1920 can be a storage medium such as read-only memory (ROM), random access memory (RAM), hard disk, CD-ROM, and DVD, or a combination of storage media.

[0337] Processor 1930 can control a series of processes to cause the base station (or network entity receiver) to operate as described above. For example, transceiver 1910 can receive data signals, including control signals, transmitted by the terminal, network entity, or base station, and processor 1930 can determine the result of receiving the control signals and data signals transmitted by the terminal, network entity, or base station.

[0338] Although the accompanying drawings illustrate different examples of user equipment, various changes can be made to the drawings. For example, the user equipment can include any number of each component in any suitable arrangement. Generally, the drawings do not limit the scope of this disclosure to any particular configuration. Furthermore, while the drawings illustrate operating 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.

[0339] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications can be made by those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims. Nothing described in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. An Internet of Things (IoT) reader, comprising: processor; as well as A transceiver, operatively coupled to the processor, is configured to: Receive first information from the base station BS related to downlink DL reception or uplink UL transmission between the IoT reader and the BS; The BS receives second information related to reader-to-device R2D transmission or device-to-reader D2R reception between the IoT reader and one or more devices; Receive third information related to the execution command from the BS; Send the physical reader to the device channel PRDCH, wherein: The PRDCH indicates information related to the execution of the command, and The PRDCH is (i) device-specific for one or more devices, (ii) device-group-specific for the one or more devices, or (iii) common to all devices receiving the PRDCH; and Send fourth information related to the execution of the command to the BS.

2. The IoT reader according to claim 1, wherein: The transceiver is also configured to receive a physical device-to-reader channel (PDRCH) from the device, the PDRCH providing information related to the execution of the command. Information related to the execution of the command includes at least one of the following: Indications related to the success or failure of executing the command, and Additional data associated with executing the command, and The fourth information is based on the reception of the PDRCH.

3. The IoT reader according to claim 1, wherein: The first information indicates at least one of the following: A search space set for receiving the Physical Downlink Control Channel (PDCCH), which provides Downlink Control Information (DCI) format indicating control information related to executing the command; (i) Semi-persistent scheduling of SPS physical downlink shared channel (PDSCH) resources for receiving R2D data or control information, and (ii) activation or deactivation of the SPS PDSCH. (i) Configuration authorization for transmitting D2R data or control information using the Physical Uplink Shared Channel (PUSCH) resource, wherein the D2R data or control information includes at least the fourth information, and (ii) activation or deactivation of the CG PUSCH. (i) Physical uplink control channel (PUCCH) resources for transmitting D2R control information, wherein the D2R control information includes at least the fourth information, or (ii) a scheduling request (SR) for transmitting D2R data or control information. The dedicated physical random access channel (PRACH) resource is used to transmit the SR, which is used to transmit D2R data or control information, and The time slot format indication for communication between the IoT reader and the BS, and The first information is provided by (i) the DCI format received in the PDCCH or (ii) the Media Access Control (MAC) Control Element (MAC CE) or Radio Resource Control (RRC) message received in the Physical Downlink Shared Channel (PDSCH).

4. The IoT reader according to claim 1, wherein: The second information indicates at least one of the following: Parameters related to controlling R2D or D2R transmit power, Parameters related to R2D preamble, Parameters related to the D2R preamble or intermembrane, Parameters related to transmitting PRDCH or receiving from the physical device to the reader channel PDRCH. Parameters related to receiving D2R transmissions, which are used for autonomous DO-A services initiated by the sending device. Parameters related to D2R random access, Parameters related to setting the acknowledged or unacknowledged mode for communication between the IoT reader and the one or more devices. Parameters related to carrier CW transmission, and Channel information used for communication between the IoT reader and the one or more devices, and The second information is provided by (i) downlink control information in DCI format received in PDCCH or (ii) media access control (MAC) control element (MAC CE) or radio resource control (RRC) message received in Physical Downlink Shared Channel (PDSCH).

5. The IoT reader according to claim 1, wherein: The third information indicates at least one of the following: An index corresponding to a command from a set of commands, wherein the set of commands includes at least one of the following: Commands for writing data to or reading data from the memory of the device. Commands used to execute device identification for inventory checks. Commands used to set or retrieve one or more device states or parameters related to sending or receiving. Commands used to lock or unlock the storage of the device. Commands used to access or terminate a process or another command, and Commands used to activate, deactivate, or initialize the device. The parameters associated with the command, R2D data associated with the command, and Information related to the target device, and The third information is provided by (i) downlink control information in DCI format received in PDCCH or (ii) media access control (MAC) control element (MAC CE) or radio resource control (RRC) message received in Physical Downlink Shared Channel (PDSCH).

6. The IoT reader according to claim 1, wherein: The processor is configured to determine the PRDCH transmit power based on the path loss between the IoT reader and the one or more devices. The path loss is (i) measured by the one or more devices from the R2D signal and reported to the IoT reader, or (ii) calculated by the IoT reader based on the reception of the D2R signal. The transmission of the PRDCH to the device is based on the determined PRDCH transmit power.

7. The IoT reader according to claim 1, wherein: The processor is configured to receive information related to a resource pool used for communication between the IoT reader and the one or more devices. The processor is configured to determine resources from the resource pool based on measurement or random selection, and The transmission of the PRDCH to the device is based on resources determined from the resource pool.

8. A method for communicating with a device in a wireless communication system, executed by an Internet of Things (IoT) reader, comprising: Receive first information from the base station BS related to downlink DL reception or uplink UL transmission between the IoT reader and the BS; The BS receives second information related to reader-to-device R2D transmission or device-to-reader D2R reception between the IoT reader and one or more devices; Receive third information related to the execution command from the BS; Send the physical reader to the device channel PRDCH, wherein: The PRDCH indicates information related to the execution of the command, and The PRDCH is (i) device-specific for one or more devices, (ii) device-group-specific for one or more devices, or (iii) common to all devices receiving the PRDCH; and Send fourth information related to the execution of the command to the BS.

9. A base station (BS), comprising: processor; as well as A transceiver, operatively coupled to the processor, is configured to: Send first information to the IoT reader related to downlink DL reception or uplink UL transmission between the IoT reader and the BS; Receive second information from the IoT reader related to reader-to-device R2D transmission or device-to-reader D2R reception between the IoT reader and one or more devices; Send third information related to the execution command to the IoT device, wherein: Information related to the execution of the command is indicated via the physical reader to the device channel PRDCH, and The PRDCH is (i) device-specific for one or more devices, (ii) device-group-specific for the one or more devices, or (iii) common to all devices receiving the PRDCH; and Receive fourth information related to the execution of the command from the IoT reader.

10. The BS according to claim 9, wherein: The fourth information is based on the Physical Device to Reader Channel (PDRCH), which provides information related to the execution of the command. Information related to the execution of the command includes at least one of the following: Indications related to the success or failure of executing the command, and Additional data associated with executing the command.

11. The BS according to claim 9, wherein: The first information indicates at least one of the following: A search space set for transmitting the Physical Downlink Control Channel (PDCCH), wherein the PDCCH provides Downlink Control Information (DCI) format, the DCI format indicating control information related to the execution of the command; (i) Semi-persistent scheduling of SPS physical downlink shared channel (PDSCH) resources for R2D data or control information, and (ii) activation or deactivation of the SPS PDSCH. (i) Configuration authorization for D2R data or control information, including at least the fourth information, and (ii) activation or deactivation of the CG PUSCH. (i) Physical uplink control channel (PUCCH) resources for D2R control information, wherein the D2R control information includes at least the fourth information, or (ii) a scheduling request (SR) for D2R data or control information. The dedicated physical random access channel (PRACH) resource is used to transmit the SR, which is used to transmit D2R data or control information, and The time slot format indication for communication between the IoT reader and the BS, and The first information is provided by (i) the DCI format in the PDCCH transmission or (ii) the Media Access Control (MAC) Control Element (MAC CE) or Radio Resource Control (RRC) message in the Physical Downlink Shared Channel (PDSCH) transmission.

12. The BS according to claim 9, wherein: The second information indicates at least one of the following: Parameters related to controlling R2D or D2R transmit power, Parameters related to R2D preamble, Parameters related to the D2R preamble or intermembrane, Parameters related to the PRDCH or physical device-to-reader channel PDRCH. Parameters related to D2R transmissions used for device-initiated autonomous DO-A services. Parameters related to D2R random access, Parameters related to setting the acknowledged or unacknowledged mode for communication between the IoT reader and the one or more devices. Parameters related to carrier CW transmission, and Channel information used for communication between the IoT reader and the one or more devices, and The second information is provided by (i) downlink control information in DCI format transmitted in PDCCH or (ii) media access control MAC control element MAC CE or radio resource control RRC message transmitted in Physical downlink shared channel PDSCH.

13. The BS according to claim 9, wherein: The third information indicates at least one of the following: An index corresponding to a command from a set of commands, wherein the set of commands includes at least one of the following: Commands for writing data to or reading data from the memory of the device. Commands used to execute device identification for inventory checks. Commands used to set or retrieve one or more device states or parameters related to sending or receiving. Commands used to lock or unlock the storage of the device. Commands used to access or terminate a process or another command, and Commands used to activate, deactivate, or initialize the device. The parameters associated with the command, R2D data associated with the command, and Information related to the target device, and The third information is provided by (i) downlink control information in DCI format transmitted in PDCCH or (ii) media access control MAC control element MAC CE or radio resource control RRC message transmitted in physical downlink shared channel PDSCH.

14. The BS according to claim 9, wherein: PRDCH transmit power is based on the path loss between the IoT reader and the one or more devices. The path loss is (i) measured by the one or more devices from the R2D signal and reported to the IoT reader, or (ii) calculated by the IoT reader based on the D2R signal. The transmission of the PRDCH to the device is based on the determined PRDCH transmit power.

15. A method performed by a base station (BS) in a wireless communication system, the method comprising: Send first information to the IoT reader related to downlink DL reception or uplink UL transmission between the IoT reader and the BS; Receive second information from the IoT reader related to reader-to-device R2D transmission or device-to-reader D2R reception between the IoT reader and one or more devices; Send third information related to the execution command to the IoT device, wherein: Information related to the execution of the command is indicated via the physical reader to the device channel PRDCH, and The PRDCH is (i) device-specific for one or more devices, (ii) device-group-specific for the one or more devices, or (iii) common to all devices receiving the PRDCH; and Receive fourth information related to the execution of the command from the IoT reader.

Images