Frequency reporting for carrier reception and backscatter transmission

Abstract

Various aspects of the disclosure relate to an apparatus for frequency reporting for carrier reception and backscatter transmission, a processor for wireless communication, a network entity, a method, and a computer readable medium. A UE transmits, to a wireless device, a report message indicating one or more of at least one frequency point or at least one frequency offset for one or more of carrier reception or backscatter transmission of the UE. In this way, the UE is able to report carrier transmission frequency point(s) and / or frequency offset value(s) to the BS side.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to user equipment (UE), wireless device, processor, method, and computer-readable medium for wireless communication, including frequency reporting for carrier reception and backscatter transmission. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may otherwise be referred to as eNodeB (eNB), next-generation node B (gNB), or other suitable terms. Each network wireless device, such as a base station, may support wireless communication for one or more user wireless devices, which may otherwise be referred to as user equipment (UE) or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). In addition, the wireless communication system may also support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)).

[0003] In recent years, the Internet of Things (IoT) has attracted considerable attention in the field of wireless communication. More "things" are expected to be interconnected to improve productivity and enhance quality of life. Further reductions in the size, complexity, and power consumption of IoT devices will enable the deployment of hundreds of billions or even trillions of IoT devices for a wide range of applications, providing added value throughout the value chain. Powering all IoT devices with batteries that require manual replacement or charging is impractical, leading to high maintenance costs, serious environmental problems, and even security risks for certain use cases, such as wireless sensors in the power and oil industries.

[0004] Most existing wireless devices are powered by batteries that need to be manually replaced or recharged. Automation and digitalization across industries have opened up many new markets, requiring new IoT technologies that support battery-free devices with no energy storage capability or devices with energy storage that does not require manual replacement or recharging. An uplink (UL) transmission for such a device is proposed, where the transmission is backscattered on an externally provided carrier. Research is needed on the frequencies used for carrier reception and the corresponding backscattered transmission to enhance IoT technologies. Summary of the Invention

[0005] This disclosure relates to a UE for wireless communication, a wireless device, a processor for wireless communication, a method for wireless communication, and a computer-readable medium for frequency reporting of carrier reception and backscatter transmission.

[0006] In a first aspect, a user equipment (UE) for wireless communication is provided, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the UE: sends a report message to a wireless device, the report message indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or at least one frequency offset being used for one or more of the UE's carrier reception or backscatter transmission.

[0007] In a second aspect, a wireless device is provided, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the wireless device: receives a report message from a user equipment (UE) indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or at least one frequency offset being used for one or more of the UE's carrier reception or backscatter transmission.

[0008] In a third aspect, a processor for wireless communication is provided, comprising: at least one memory; and a controller coupled to the at least one memory and configured such that the controller: sends a report message to a wireless device, the report message indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or at least one frequency offset being used for one or more of carrier reception or backscatter transmission of the UE.

[0009] In a fourth aspect, a method is provided performed by a user equipment (UE), the method comprising: sending a report message to a radio device, the report message indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or at least one frequency offset being used for one or more of the UE’s carrier reception or backscatter transmission.

[0010] In a fifth aspect, a method performed by a wireless device is provided, the method comprising: receiving a report message from a user equipment (UE) indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or at least one frequency offset being used for one or more of the UE’s carrier reception or backscatter transmission.

[0011] In a sixth aspect, a computer-readable medium is provided having instructions stored thereon that, when executed by a processor of a device, cause the device to perform the method according to the fourth or fifth aspect of this disclosure.

[0012] In some implementations of the methods, UEs, and wireless devices described herein, the UE can transmit reports via backscatter and at transmission frequency points.

[0013] In some implementations of the methods, UEs, and wireless devices described herein, the configuration may include one or more of the following: one or more sets of frequency point indices; the default frequency point of the UE; the frequency point associated with the configuration; or one or more sets of offset values ​​for the frequency point associated with the configuration (and wherein one or more sets of frequency point indices are at least partially based on one or more sets of frequency point indices), the default frequency point of the UE, and one or more sets of offset values ​​for the frequency point associated with the configuration.

[0014] In some implementations of the methods, UEs, and wireless devices described herein, the set of one or more frequency offsets may be based on one or more of the following: at least one frequency point in a set of one or more frequency points, or a reference frequency index.

[0015] In some implementations of the methods, UEs, and wireless devices described herein, the UE may determine at least one frequency point from a set of one or more frequency points for carrier reception; and determine a frequency offset value based on a set of one or more frequency offsets or one or more of the UE's capabilities.

[0016] In some implementations of the methods described herein, the UE, and the radio device, the configuration may further include at least one of the following: a first indication of whether carrier reception is allocated in the downlink (DL) spectrum or the uplink (UL) spectrum; or a second indication of whether backscatter transmission is allocated in the DL spectrum or the UL spectrum.

[0017] In some implementations of the methods described herein, the UE, and the wireless device, the UE may receive a configured index.

[0018] In some implementations of the methods described herein, the UE, and the wireless device, the reporting message may include a frequency offset value that indicates the threshold frequency offset value of the UE.

[0019] In some implementations of the methods, UEs, and wireless devices described herein, the UE may receive an indication of a frequency offset value, wherein the frequency offset value is at least partially based on a threshold frequency offset value; and perform backscatter transmission of the UE at least partially based on the frequency offset value.

[0020] In some implementations of the methods described herein, UEs, and wireless devices, the reporting message may indicate one or more of the UE's type or capabilities.

[0021] In some implementations of the methods described herein, the UE, and the wireless device, the reporting message may include the UE's identification information.

[0022] In some implementations of the methods described herein, the UE, and the wireless device, the UE may perform uplink or sidelink transmissions including reporting messages.

[0023] In some implementations of the methods, UEs, and wireless devices described herein, one or more of the carrier reception or backscatter transmission may satisfy at least one of the following: the carrier reception is allocated in the DL spectrum and the corresponding backscatter transmission is allocated in the UL spectrum; the carrier reception is allocated in the DL spectrum and the corresponding backscatter transmission is allocated in the DL spectrum; the carrier reception is allocated in the UL spectrum and the corresponding backscatter transmission is allocated in the UL spectrum; or the carrier reception is allocated in the UL spectrum and the corresponding backscatter transmission is allocated in the DL spectrum.

[0024] In some implementations of the methods, UEs, and wireless devices described herein, the UE may include an environmental Internet of Things (IoT) device.

[0025] In some implementations of the methods, UEs, and wireless devices described herein, the wireless device may send a configuration to the UE indicating one or more of a set of one or more frequency points or a set of one or more frequency offsets, which are used for one or more of the UE's carrier reception or backscatter transmission.

[0026] In the methods described herein, and in some implementations of the UE and the wireless device, the wireless device may send a configured index.

[0027] In some implementations of the methods, UEs, and wireless devices described herein, the wireless device may send an indication of a frequency offset value, wherein the frequency offset value is at least partially based on a threshold frequency offset value.

[0028] In some implementations of the methods, UEs, and radio devices described herein, the radio device may perform uplink or sidelink reception, including reporting messages.

[0029] In some implementations of the methods, UEs, and wireless devices described herein, the wireless device may perform one or more carrier transmissions at one or more corresponding carrier frequencies, wherein each of the carrier transmissions is performed separately within a corresponding duration.

[0030] In some implementations of the methods, UEs, and wireless devices described herein, the wireless device may include one of the following: a base station, an auxiliary node, an intermediate node, a relay node or repeater, or a UE. Attached Figure Description

[0031] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure can be implemented are illustrated.

[0032] Figures 2A to 2E The illustration shows an example of a connectivity topology for environmental IoT networks and devices.

[0033] Figure 3 The illustration shows the process flow of frequency reporting steps according to some example embodiments of the present disclosure.

[0034] Figures 4A to 4H Examples of carrier reception and backscatter transmission frequency(s) and frequency(s) offsets according to some exemplary embodiments of the present disclosure are illustrated.

[0035] Figure 5 The illustration shows a schematic diagram of carrier transmission at multiple frequency points according to some example embodiments of the present disclosure.

[0036] Figure 6 Examples of devices suitable for implementing some embodiments of this disclosure are illustrated.

[0037] Figure 7 Examples of processors suitable for implementing some embodiments of this disclosure are illustrated.

[0038] Figure 8 The diagram illustrates a flowchart of a method performed by a UE according to aspects of this disclosure.

[0039] Figure 9 A flowchart illustrating a method performed by a wireless device according to aspects of this disclosure is shown.

[0040] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0041] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. This disclosure described herein can be implemented in various ways other than those described below. In the following specification and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0042] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments may include a particular feature, structure, or characteristic, but not every implementation includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiments. Moreover, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, those skilled in the art will understand that, whether explicitly described or not, in combination with other implementations, affecting such a feature, structure, or characteristic is within the scope of their knowledge.

[0043] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, steps, or devices are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate the ability to select from a number of functional alternatives that are not necessarily better, smaller, higher, or otherwise preferred than other options.

[0044] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that, when used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and variations thereof should be understood as open-ended terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “an embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can refer to “A only,” “B only,” or “A and B.” Other explicit or implicit definitions may be included below.

[0045] As mentioned above, most existing wireless devices are powered by batteries that require manual replacement or charging. Automation and digitalization across industries have opened up numerous new markets, necessitating new IoT technologies that support battery-free devices with no energy storage capabilities or devices with energy storage that does not require manual replacement or charging. Such devices must be small enough to effectively communicate the target use case.

[0046] As proposed by 3GPP, uplink (UL) transmissions of IoT devices can be backscattered on an externally provided carrier. For devices with peak power consumption of less than 1 µW, UL transmissions are backscattered on an externally provided carrier; while for devices with peak power consumption of less than several hundred µW, UL transmissions can be generated internally by the device or backscattered on an externally provided carrier.

[0047] For battery-free devices (e.g., environmental IoT devices), UL transmission is backscattered on an externally provided carrier. The device can be configured with a default frequency point (e.g., f0) or configurable frequency points (e.g., f0, f1, f2, f3) to receive the carrier. Additionally, the device can be configured with one or more frequency offset values ​​(e.g., fs1, fs2, fs3, fs4), or the maximum value of the configurable frequency offset corresponding to the carrier transmission frequency point. This capability information is unknown on the BS side (e.g., base station, auxiliary node, intermediate node, relay node or repeater, or UE).

[0048] In view of this, steps and related signals are proposed to support reporting (multiple) carrier frequency transmission points and / or (multiple) frequency offset values ​​to the BS side (e.g., base station, auxiliary node, intermediate node, relay node, or repeater, or UE) to enhance carrier reception and backscatter transmission of low-power devices (such as environmental IoT devices).

[0049] The aspects of this disclosure are described in the context of wireless communication systems. Figure 1Examples of wireless communication systems 100 that can be implemented according to some embodiments of this disclosure are illustrated. Wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. Wireless communication system 100 may support various radio access technologies. In some implementations, wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. Wireless communication system 100 may support radio access technologies beyond 5G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0050] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface. In a 3GPP non-terrestrial network (NTN), network entity 102 in satellite form can communicate directly with UE 104 using an NR / LTE Uu interface. The satellite may be a transparent satellite or a regenerated satellite. For an NTN utilizing a transparent satellite, the terrestrial base station can communicate with the UE via the satellite. For an NTN utilizing a regenerated satellite, the base station may be located on the satellite and communicate directly with the UE.

[0051] Network entity 102 can provide a geographic coverage area 112, for which network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within that geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced in the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0052] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or concurrently, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a Machine Type Communication (MTC) device, an Ambient IoT device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0053] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1 Some examples of UE 104 are shown. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Alternatively, UE 104 can support communication with other network entities 102 or UE 104, which can be used as relays in the wireless communication system 100.

[0054] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0055] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0056] In some implementations, network entity 102 can be configured in a decoupled architecture that utilizes protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-Real-Time RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0057] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decoupled RAN architecture, one or more components of network entity 102 may be co-located, or one or more components of network entity 102 may be located in different locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decoupled RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0058] The functional division among CU, DU, and RU can be flexible and can depend on the different functions supported by the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio functions, and any combination thereof). For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host higher-layer protocol (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer) functions and signaling, and each can be at least partially controlled by the CU 160.

[0059] Alternatively, the functional partitioning of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional partitioning between CU and DU, or between DU and RU, can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by different ones of CU, DU, or RU).

[0060] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1c, F1u), while the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the mid-range or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, where each layer is supported by a corresponding network entity 102 communicating via such a communication link.

[0061] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)). In some implementations, control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0062] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. PDU session can serve as an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0063] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multi-frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0064] One or more parameter sets can be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefix. The first parameter set (e.g.) =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the normal cyclic prefix. In some implementations, the first parameter set associated with the first subcarrier spacing (e.g., 15 kHz) is... =0) allows each subframe to utilize one time slot. The second parameter set (e.g., =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third parameter set (e.g., =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth parameter set (e.g., =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0065] Time intervals for resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0066] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., ...) associated with the corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. =0、 =1、 =2、 =3、 =4) Each subframe may utilize a single time slot, two time slots per subframe, four time slots per subframe, eight time slots per subframe, or 16 time slots per subframe. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot may include 12 symbols. The relationship between the number of symbols per time slot for normal and extended cyclic prefixes, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that the first parameter set (e.g., 15 kHz) associated with the first parameter set (e.g., =0) can be used interchangeably between subframes and time slots.

[0067] In wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, wireless communication system 100 can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410 MHz – 7.125 GHz), FR2 (24.25 GHz – 52.6 GHz), FR3 (7.125 GHz – 24.25 GHz), FR4 (52.6 GHz – 114.25 GHz), FR4a or FR4-1 (52.6 GHz – 71 GHz), and FR5 (114.25 GHz – 300 GHz). In some implementations, NE 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by NE 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0068] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the first parameter set (e.g., =0) is associated with, including a 15 kHz subcarrier spacing; the second parameter set (e.g., =1), including a 30kHz subcarrier spacing; and a third parameter set (e.g., =2), including a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with a third parameter set (e.g., =2) associated with, including a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., =3), including a 120 kHz subcarrier spacing.

[0069] Figures 2A to 2E The diagram illustrates an example of a connectivity topology for environmental IoT networks and devices. In all these topologies, environmental IoT devices can be supplied with carriers from (multiple) other nodes inside or outside the topology. Links in each topology can be bidirectional or unidirectional. Figures 2A to 2E In this network topology, base stations (BS), user units (UEs), auxiliary nodes, or intermediate nodes can be multiple BSs or UEs. The hybrid indoor and outdoor deployment of these nodes can be considered a network implementation choice. The potential impact on device or node complexity needs to be considered. In these connection topologies, this does not imply the presence of multi-hop auxiliary or intermediate nodes.

[0070] Figure 2A The diagram illustrates Topology 1, in which the environmental IoT device communicates directly and bidirectionally with the base station. Communication between the base station and the environmental IoT device includes environmental IoT data and / or signaling. This topology involves a different base station (BS) sending data to the environmental IoT device and a different BS receiving data from the environmental IoT device.

[0071] Figure 2B The diagram illustrates Topology 2, in which an environmental IoT device communicates bidirectionally with an intermediate node located between the device and the base station. In this topology, the intermediate node can be a relay, integrated access and backhaul (IAB) node, UE, repeater, etc., and possesses environmental IoT capabilities. The intermediate node can transmit environmental IoT data and / or signaling between the base station and the environmental IoT device.

[0072] Figure 2C and Figure 2D The diagram illustrates topology 3, in which environmental IoT devices send data / signaling to the base station and receive data / signaling from auxiliary nodes. Figure 2C ); or environmental IoT devices receive data / signaling from the base station and send data / signaling to auxiliary nodes ( Figure 2DIn this topology, auxiliary nodes can be relays, IAB nodes, UEs, repeaters, etc., and they have environmental IoT capabilities.

[0073] Figure 2E Topology 4 is illustrated, in which the environmental IoT device and the UE communicate bidirectionally. The communication between the UE and the environmental IoT device includes environmental IoT data and / or signaling.

[0074] Figure 3 The illustration shows a process flow 300 for frequency reporting steps according to some example embodiments of the present disclosure. Process flow 300 may include a wireless device 301 and a UE 302. Wireless device 301 may be a network entity 102 or a UE 104 capable of providing a carrier, while UE 302 may be a UE 104 capable of harvesting energy via the carrier from wireless device 301 and using the harvested energy to perform a corresponding backscatter transmission. It should be understood that process flow 300 can be applied to other communication scenarios.

[0075] refer to Figures 2A to 2E Wireless device 301 may include a base station. Alternatively or additionally, wireless device 301 may include intermediate nodes, such as access points, IAB nodes, relays, or repeaters. Alternatively or additionally, wireless device 301 may include a UE. UE 302 may include IoT devices, such as environmental IoT devices or tags.

[0076] At 310, UE 302 may send a report message 315 to radio device 301, which indicates at least one frequency point and / or at least one frequency offset in carrier reception and / or backscatter transmission for UE 302. Accordingly, at 320, radio device 301 receives report message 315 from UE 302.

[0077] Report message 315 may be physical layer control information, or may be sent via higher-layer signaling, such as Media Access Control (MAC) Control Element (MAC CE) or Radio Resource Control (RRC) signaling. In some embodiments, the transmission of report message 315 may be an uplink or sidelink transmission for reporting. Report message 315 may be sent via backscatter transmission of UE 302.

[0078] Report message 315 may implicitly indicate (multiple) frequency points and / or (multiple) frequency offsets. In some embodiments, report message 315 may include information about the device type and / or device capabilities of UE 302. In this way, wireless device 301 may derive (multiple) frequency points and / or (multiple) frequency offsets based on device type and / or device capabilities. Additionally, report message 315 may carry the identification (ID) information of UE 302.

[0079] Upon receiving report message 315, wireless device 301 obtains capability information from UE 302 regarding the frequencies used for carrier reception and backscatter transmission. Therefore, wireless device 301 can perform carrier transmission at the frequency(s) specified in report message 315 and expects to receive backscatter transmission (e.g., data transmission) at the frequency(s) specified in report message 315.

[0080] In some embodiments, the report message 315 may indicate a frequency point f0 and a frequency offset fs. In this case, the wireless device 301 can determine the carrier transmission frequency point based on the reported frequency point f0. The wireless device 301 can then perform carrier transmission at frequency point f0 and expect to receive additional transmissions at frequency point f0+fs. If the frequency point and frequency offset are implicitly indicated, the wireless device 301 can determine the carrier transmission frequency point based on the reported device type or device capability.

[0081] In some embodiments, the report message 315 may indicate one or more frequency points (e.g., {f1,f2,f3,f4}) and / or one or more frequency offset values ​​(e.g., {fs1,fs2,fs3,fs4}). It should be understood that different numbers of frequency points or frequency offset values ​​are possible. In this case, the wireless device 301 receives the report message 315 and determines the carrier transmission frequency point based on the reported one or more frequency points {f1,f2,f3,f4} and / or one or more frequency offset values ​​{fs1,fs2,fs3,fs4}. Alternatively, the wireless device 301 may determine the carrier transmission frequency point based on the reported device type or device capability.

[0082] In some embodiments, the reporting message 315 may include a frequency offset value indicating a threshold frequency offset value for the UE. The threshold frequency offset value may be, for example, the maximum frequency offset value supported by the UE 302, such as fs4. In this case, the wireless device 301 may determine a frequency offset value not greater than the threshold, such as fs1, fs2, or fs3, and indicate it to the UE 302. The wireless device may anticipate receiving additional backscatter transmissions at frequency points f0+fs1, f0+fs2, or f0+f3.

[0083] At 330, radio device 301 may send configuration 335 to UE 302, which indicates one or more frequency points and / or one or more frequency offsets for carrier reception and / or backscatter transmission for UE 302. Accordingly, at 340, UE 302 may receive configuration 335 from radio device 301. Configuration 335 may be physical layer control information or sent via higher-layer signaling (e.g., MAC CE or RRC signaling). Note that the transmission of configuration 335 is optional and may be omitted in some embodiments.

[0084] Configuration 335 indicates the carrier transmission's frequency(s) and / or frequency offset(s). Here, "or" means that the carrier transmission's frequency(s) or frequency offset(s) values ​​may not exist. That is, the indicated frequency(s) for carrier transmission are default to the UE, for example, the default frequency(s) or the same as the transmission frequency(s) in configuration 335. The indicated frequency(s) for carrier transmission may be the same as or different from the transmission frequency(s) in configuration 335. In some embodiments, configuration 335 may be based at least in part on reporting message 315. That is, the indicated frequency(s) and frequency offset(s) values ​​are supported by UE 302.

[0085] To indicate one or more frequency points used for carrier reception, configuration 335 may include one or more frequency point indices. Alternatively, configuration 335 may include a default frequency point for carrier reception by the UE. Alternatively, configuration 335 may include the same frequency point for transmissions of configuration 335 used for carrier reception. Alternatively, configuration 335 may include one or more offset value indices to the configured transmission frequency points. In this case, UE 302 can derive the multiple frequency points used for carrier reception by applying the offset values(s) to the indices of the same frequency points used for the configured transmissions.

[0086] The frequency offsets indicated in Configuration 335 may be associated with a base frequency, i.e., the offsets are based on the frequencies from which they are calculated or derived. The base frequency may be one of one or more frequency points indicated in Configuration 335. Alternatively, the base frequency may be associated with a reference frequency index. For example, the base frequency may be a band frequency, such as 900 MHz.

[0087] Using configuration 335, UE 302 can perform carrier reception at (multiple) indicated frequency points and perform corresponding backscatter transmissions for data transmission and frequency reporting. To perform backscatter transmissions, UE 302 can determine the transmission frequency point for backscatter transmissions based on (multiple) indicated frequency points and / or (multiple) frequency offsets.

[0088] Note that in configuration 335, the indication of (multiple) frequency offsets can be optional. If (multiple) frequency offset indications exist, UE 302 can determine the transmission frequency point by applying (multiple) frequency offsets to the base frequency (e.g., one of the indicated frequency points). For example, if configuration 335 indicates frequency point f0 and frequency offset fs 1, UE 302 can perform carrier reception at frequency point f0 and perform the corresponding backscatter transmission at transmission frequency point f0+fs1. If (multiple) frequency offsets do not exist, UE 302 can determine the transmission frequency for backscatter transmission based on the UE's capabilities, for example, by applying one of the UE 302's supported frequency offset values ​​or the default frequency offset value to (multiple) indicated frequency points of (multiple) carriers.

[0089] In some embodiments, configuration 335 may include indications regarding spectrum allocation for carrier reception and corresponding backscatter transmission. Wireless device 301 may include in configuration 335: a first indication indicating whether carrier reception is allocated in downlink (DL) spectrum or uplink (UL) spectrum; and / or a second indication indicating whether backscatter transmission is allocated in downlink (DL) spectrum or uplink (UL) spectrum.

[0090] Figure 4A Examples of frequency points and frequency offsets for carrier reception and backscatter transmission according to some exemplary embodiments of this disclosure are illustrated. Figure 4A In this context, carrier reception is allocated in the DL spectrum, while the corresponding backscatter transmission is allocated in the UL spectrum.

[0091] refer to Figure 4A The wireless device 301 transmits a configuration indicating a frequency point for carrier transmission in the DL spectrum; and / or indicating one or more frequency offset values. Here, "or" means that there may be no indication of a carrier transmission frequency point or frequency offset value. That is, the indicated frequency point for carrier transmission is default to the UE, for example, a default frequency point, or the same as the frequency point configured for transmission. The indicated frequency point for carrier transmission may be the same as or different from the configured transmission frequency point. In addition, the configuration may carry a first indication that carrier reception is allocated in the DL spectrum; and / or a second indication that backscatter transmission is allocated in the UL spectrum.

[0092] Frequency point f0 can be explicitly indicated by a frequency point index, or it can be indicated by an offset value corresponding to the frequency point configured for transmission. One or more indicated frequency offset values ​​(e.g., fs1, fs2, fs3, and fs4) can be indicated based on the indicated f0, or based on the frequency point of the first transmission, or based on a reference frequency index in the UL spectrum. Alternatively, UE 301 can determine the frequency offset value based on device capabilities (i.e., an indication of the frequency offset may not be required).

[0093] After receiving configuration 335, UE 302 determines a frequency point f0 for carrier reception. UE 302 also determines frequency offset values, i.e., one or more of fs1, fs2, fs3, and fs4, based on an indicated frequency offset value and / or device capability. UE 302 then reports the frequency point f0 and one or more of fs1, fs2, fs3, and fs4 to radio device 301. Accordingly, after receiving the report message, radio device 301 can perform carrier transmission at the determined frequency point (e.g., f0 in the DL spectrum) and expects to receive backscatter transmissions at frequency points f0+fs1, f0+fs2, f0+fs3, and f0+fs4 in the UL spectrum, as... Figure 4A As shown in the image.

[0094] As an example, wireless device 301 transmits a configuration indicating a frequency point (e.g., f0) for carrier transmission in the DL spectrum and indicating multiple available frequency offset values ​​(e.g., fs1, fs2, and fs3), while UE 302 has the capability to support frequency offset values ​​fs1 and fs2. UE 302 can determine fs1 as the frequency offset value. UE 302 receives the carrier at frequency point f0 and performs multiple corresponding backscatter transmissions at frequency point f0+fs1.

[0095] As another example, wireless device 301 transmits a configuration indicating a frequency point (e.g., f0) for carrier transmission in the DL spectrum, but does not indicate the available frequency offset values(s). UE 302 has the capability to support frequency offset values ​​fs1, fs2, and fs3. UE 302 can determine offset fs2 as the frequency offset value. UE 302 receives the carrier at frequency point f0 and performs the corresponding backscatter transmission(s) at frequency point f0+fs2.

[0096] Figure 4B Examples of frequency points and frequency offsets for carrier reception and backscatter transmission according to some exemplary embodiments of this disclosure are illustrated. Figure 4B In this process, carrier reception is allocated in the DL spectrum, and the corresponding backscatter transmission is allocated in the UL spectrum.

[0097] Wireless device 301 transmits a configuration (e.g., configuration 335) to indicate one or more frequency points for carrier transmission in the DL spectrum, and / or to indicate a frequency offset value. Here, "or" indicates that the frequency offset value may not be present. That is, the frequency offset value is default for UE 302, such as fs. The indicated frequency points for carrier transmission may be the same as or different from the frequency points configured for transmission. Additionally, the configuration may carry a first indication that carrier reception is allocated in the DL spectrum, and / or a second indication that backscatter transmission is allocated in the UL spectrum.

[0098] Frequency points f0, f1, f2, and f3 can be explicitly indicated by one or more frequency point indices, or they can be indicated by one or more offset values ​​corresponding to the frequency points configured for transmission. The indicated frequency offset value fs can be indicated by a frequency offset value index, or it can be based on device capabilities (i.e., it may not need to be indicated).

[0099] After receiving configuration 335, UE 302 determines one or more frequency points from frequency points f0, f1, f2, and f3 for carrier reception. UE 302 also determines the frequency offset value based on the indicated frequency offset value and / or device capability (i.e., fs). UE 302 then reports one or more of f0, f1, f2, and f3, along with the frequency offset fs, to radio device 301. Correspondingly, upon receiving the report message, radio device 301 can perform carrier transmission at the reported frequency points(multiple) according to the report, and expects to receive backscatter transmissions at frequency points f0+fs1, f0+fs2, f0+fs3, or f0+fs4 in the UL spectrum, such as... Figure 4B As shown in the image.

[0100] As an example, wireless device 301 transmits a configuration indicating the frequency points (e.g., f0, f1, f2, and f3) for carrier transmission in the DL spectrum and indicating the available frequency offset values ​​(e.g., fs). UE 302 can determine f1 as the frequency(s) for carrier transmission. UE 302 receives the carrier at frequency point f1 and performs (multiple) corresponding backscatter transmissions at frequency point f1+fs.

[0101] As another example, wireless device 301 sends a configuration indicating only the frequency points (e.g., f0, f1, f2, and f3) for carrier transmission in the DL spectrum. UE 302 can determine f1 as the carrier transmission frequency(s) and determine fs based on default values. UE 302 receives the carrier at frequency point f1 and performs the corresponding backscatter transmissions at frequency point f1+fs.

[0102] Reference Figure 4A and Figure 4BIn the described embodiments, carrier reception is allocated in the DL spectrum, while the corresponding backscatter transmission is allocated in the UL spectrum. It should be understood that different DL or UL spectrum allocations are also applicable. Instructions regarding spectrum allocation can be configured or indicated to UE 302, for example via configuration 335. In some embodiments, a first indication can be included in the configuration to indicate whether carrier reception is allocated in the DL spectrum or the UL spectrum; and / or a second indication can be included to indicate whether backscatter transmission is allocated in the DL spectrum or the UL spectrum.

[0103] Figure 4C The illustration shows an example of multiple frequency points and frequency offsets used for carrier reception and backscatter, where both carrier reception and the corresponding backscatter transmission are allocated in the UL spectrum. Figure 4C In this process, the carrier reception has one frequency point, and the backscatter propagation has multiple frequency offsets. The corresponding process flow and reference... Figure 4A Similar to what is described in the text, except for the indication of spectrum allocation.

[0104] Figure 4D The illustration shows an example of multiple frequency points and frequency offsets used for carrier reception and backscatter, where both carrier reception and the corresponding backscatter transmission are allocated in the UL spectrum. Figure 4D In this process, the carrier reception has multiple frequency points, and the backscatter transmission has a frequency offset. The corresponding process flow and reference... Figure 4B Similar to what is described in the text, except for the indication of spectrum allocation.

[0105] Figure 4E The illustration shows an example of multiple frequency points and frequency offsets used for carrier reception and backscatter, where both carrier reception and the corresponding backscatter transmission are allocated in the DL spectrum. Figure 4E In this process, the carrier reception has one frequency point, and the backscatter propagation has multiple frequency offsets. The corresponding process flow and reference... Figure 4A Similar to what is described in the text, except for the indication of spectrum allocation.

[0106] Figure 4F The illustration shows an example of multiple frequency points and frequency offsets used for carrier reception and backscatter, where both carrier reception and the corresponding backscatter transmission are allocated in the DL spectrum. Figure 4F In this process, the carrier reception has multiple frequency points, and the backscatter transmission has a frequency offset. The corresponding process flow and reference... Figure 4B Similar to what is described in the text, except for the indication of spectrum allocation.

[0107] Figure 4GThe illustration shows an example of multiple frequency points and frequency offsets used for carrier reception and backscatter, where carrier reception is allocated in the UL spectrum and the corresponding backscatter transmission is allocated in the DL spectrum. Figure 4G In this process, the carrier reception has one frequency point, and the backscatter propagation has multiple frequency offsets. The corresponding process flow and reference... Figure 4A Similar to what is described in the text, except for the indication of spectrum allocation.

[0108] Figure 4H The illustration shows an example of multiple frequency points and frequency offsets used for carrier reception and backscatter, where carrier reception is allocated in the UL spectrum and the corresponding backscatter transmission is allocated in the DL spectrum. Figure 4H In this process, the carrier reception has one frequency point, and the backscatter propagation has multiple frequency offsets. The corresponding process flow and reference... Figure 4B The description is similar, except for the indication of spectrum allocation.

[0109] In some embodiments, UE 302 may report threshold values ​​for multiple frequency offset values, such as a maximum frequency offset value (e.g., fs4), to radio device 301. Radio device 301 may determine a frequency offset value equal to or less than the maximum frequency offset value, such as fs2, and indicate it to UE 302. Radio device 301 may perform carrier transmission at frequency point f0 and expect to receive backscatter transmission at frequency point f0+fs2.

[0110] To simplify configuration signaling, the indication information can be (pre)configuration information for both radio device 301 and UE 302, and a configuration index can be used to indicate or configure steps. In some embodiments, a configuration set can be (pre)configured for radio device 301 and UE 302, as shown in Table 1 below. Each configuration is associated with one or more frequency points and one or more frequency offsets. Radio device 301 can indicate a configuration index to UE 302, such as configuration #1. UE 302 can determine DL f0 for carrier reception and DL f0+UL fs2 for backscatter transmission. Additionally, the pre-configured Table 1 can be associated with frequency value configurations that specify the frequency values ​​used for the parameters in the table. For example, DL f0 = x MHz, UL f0 = y MHz, DL f1 = a MHz, DL f2 = b MHz, and so on. Table 1: Pre-configuration of frequency points and frequency offsets

[0111] In an environment with a large number of UEs deployed, the wireless device 301 can perform carrier scanning via the proposed reporting scheme to collect UE capability information. The wireless device 301 can perform one or more carrier transmissions at one or more corresponding frequency points (e.g., f0, f1, f2, f3) to trigger the UE to send a reporting message. Carrier transmissions at multiple frequency points can be performed within corresponding durations.

[0112] While performing carrier transmission, the wireless device 301 may instruct the UE 302 to report its carrier frequency point (e.g., f0) and / or frequency offset (e.g., fs). Here, the frequency offset fs may be one or more of the indicated frequency offset values ​​(fs1, fs2, fs3, fs4), or it may be the maximum frequency offset, such as fs4. In some embodiments, the wireless device 301 may include the ID information of (multiple) UEs in the indication.

[0113] UE 302 receives carrier transmission at a frequency point (e.g., f0) and performs backscatter transmission at frequency point f0+fs. Here, fs can be one or more frequency offsets (fs1, fs2, fs3, fs4), or fs can be the maximum frequency offset, such as fs4. UE 302 can perform backscatter transmission based on indicated ID information. In some embodiments, UE 302 can perform backscatter transmission by including its ID information.

[0114] Figure 5 The illustration shows a schematic diagram of carrier transmission at multiple frequency points according to some exemplary embodiments of the present disclosure. For example, such as Figure 5 As shown, during duration t1, the wireless device performs carrier transmission at frequency point f0, while the environmental IoT device performs backscatter transmission at frequency points (f0+fs1, f0+fs2, f0+fs3). This backscatter transmission may include environmental IoT device ID information. This means that the environmental IoT device with this ID information has the capability to receive signals at frequency point f0 with a frequency offset of (fs1, fs2, fs3).

[0115] At duration t2, if by default or instructed to report the maximum frequency offset value, the ambient IoT device can perform backscatter transmission at frequency point (f1+fs3). This means that the ambient IoT device has the ability to receive frequencies offset (fs1, fs2, and fs3) at frequency point f1.

[0116] At duration t3, if the default or indicated frequency offset values ​​for ID1 and ID2 are reported, an environment IoT device with ID1 can perform backscatter transmission at frequency point (f2+fs2), and an environment IoT device with ID2 can perform backscatter transmission at frequency point (f2+fs3).

[0117] At duration t4, if the maximum value of the frequency offset is reported by default or as instructed, an environment IoT device with ID 3 can perform backscatter transmission at frequency point (f3+fs2) using the ID 3 information. This means that an environment IoT device including ID information 3 has the ability to receive signals with frequency offsets (fs1 and fs2) at frequency point f3.

[0118] Figure 6 Examples of devices suitable for implementing some embodiments of this disclosure are illustrated. Device 600 may be an example of UE 104 or network entity 102 as described herein. Device 600 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 600 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 602, memory 604, transceiver 606, and optional I / O controller 608. These components may be electronically or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0119] Processor 602, memory 604, transceiver 606, or various combinations thereof or components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, processor 602, memory 604, transceiver 606, or various combinations thereof or components thereof may support methods for performing one or more operations described herein.

[0120] In some implementations, processor 602, memory 604, transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting means for performing the functions described herein. In some implementations, processor 602 and memory 604 coupled to processor 602 may be configured to perform one or more functions described herein (e.g., instructions stored in memory 604 are executed by processor 602).

[0121] For example, processor 602 may support wireless communication at device 600 according to an example disclosed herein. Device 600 may be an example of UE 104, such as an environmental IoT device. In this case, processor 602 may be configured to operate to support means for sending a report message to a wireless device, the report message indicating one or more of at least one frequency point or at least one frequency offset, which is used for one or more of the UE's carrier reception or backscatter transmission.

[0122] Device 600 may be a network entity or an example of UE 104. In this case, processor 602 may be configured to operate to support means for receiving a report message from the UE, the report message indicating one or more of at least one frequency point or at least one frequency offset, which is used for one or more of the UE's carrier reception or backscatter transmission.

[0123] Processor 602 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 602 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into processor 602. Processor 602 may be configured to execute computer-readable instructions stored in memory (e.g., memory 604) to cause device 600 to perform various functions of this disclosure.

[0124] Memory 604 may include random access memory (RAM) and read-only memory (ROM). Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 602, cause device 600 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, this code may not be directly executable by processor 602, but may cause a computer (e.g., at compile and execution time) to perform the functions described herein. In some implementations, memory 604 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0125] I / O controller 608 can manage input and output signals for device 600. I / O controller 608 can also manage peripheral devices not integrated into device 600. In some implementations, I / O controller 608 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 608 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 608 can be implemented as part of a processor (such as processor 406). In some implementations, a user can interact with device 600 via I / O controller 608 or via hardware components controlled by I / O controller 608.

[0126] In some implementations, device 600 may include a single antenna 610. However, in other implementations, device 600 may have more than one antenna 610 (i.e., multiple antennas), including multiple antenna panels or antenna arrays that may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 606 may communicate bidirectionally via one or more antennas 610, wired or wireless links, as described herein. For example, transceiver 606 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 606 may also include a modem for modulating packets to provide modulated packets to one or more antennas 610 for transmission, and for demodulating packets received from one or more antennas 610. Transceiver 606 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0127] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 610 for transmitting the amplified signal over the air or wireless medium.

[0128] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 610 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0129] Figure 7 An example of a processor 700 for implementing some embodiments of the present disclosure is illustrated. Processor 700 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 700 may include a controller 702 configured to perform various operations according to the examples described herein. Processor 700 may optionally include at least one memory 704. Additionally or alternatively, processor 700 may optionally include one or more arithmetic logic units (ALUs) 706. One or more of these components may be electronically or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0130] Processor 700 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 700)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0131] The controller 702 can be configured to manage and coordinate various operations of the processor 700 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable the processor 700 to support various operations as described herein. For example, the controller 702 can operate as a control unit of the processor 700 to generate control signals that manage the operation of the various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0132] Controller 702 can be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 704 and determine subsequent instructions(s) to be executed, enabling processor 700 to support various operations as described herein. Controller 702 can be configured to track memory addresses of instructions associated with memory 604. Controller 702 can be configured to decode instructions to determine the operation to be performed and its operands. For example, controller 702 can be configured to interpret instructions and determine control signals to be output to other components of processor 700, enabling processor 700 to support various operations as described herein. Alternatively or additionally, controller 702 can be configured to manage data flow within processor 700. Controller 702 can be configured to control data transfer between registers, arithmetic logic unit (ALU), and other functional units of processor 700.

[0133] Memory 704 may include one or more caches (e.g., local to processor 500 or included in processor 700) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 704 may reside inside or on the processor chipset (e.g., local to processor 700). In other implementations, memory 704 may reside outside the processor chipset (e.g., remote from processor 700).

[0134] Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 700, cause processor 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 702 and / or processor 700 may be configured to execute computer-readable instructions stored in memory 704 to cause processor 700 to perform various functions. For example, processor 700 and / or controller 702 may be coupled to or coupled to memory 704, and processor 700, controller 702, and memory 704 may be configured to perform the various functions described herein. In some examples, processor 700 may include multiple processors, and memory 704 may include multiple memories. One or more processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0135] One or more ALU 706s can be configured to support various operations as described herein. In some implementations, one or more ALU 706s may reside inside or on a processor chipset (e.g., processor 700). In some other implementations, one or more ALU 706s may reside outside the processor chipset (e.g., processor 700). One or more ALU 706s can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 706s can receive input operands and an opcode, the opcode determining the operation to be performed. One or more ALU 706s can be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively or additionally, one or more ALU 706s can support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 706s to handle conditional operations, comparisons, and bitwise operations.

[0136] Processor 700 may be implemented at UE 104 (e.g., an environmental IoT device). In this case, processor 700 may be configured to support means for sending a report message to a wireless device, the report message indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or at least one frequency offset being used for one or more of the UE's carrier reception or backscatter transmission.

[0137] Processor 700 can support wireless communication according to examples disclosed herein. Processor 700 can be implemented at network entity 102 or UE 104. In this case, processor 700 can be configured to support means for receiving a report message from a user equipment (UE) indicating one or more of at least one frequency point or at least one frequency offset for one or more of the UE's carrier reception or backscatter transmission.

[0138] Figure 8 A flowchart illustrating method 800 performed by a UE according to aspects of this disclosure is shown. Operation of method 800 may be implemented by a device or component thereof as described herein. For example, operation of method 800 may be performed by a UE 104 as described herein. In some implementations, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions. Alternatively or additionally, the UE may use dedicated hardware to perform aspects of the described functions.

[0139] At 810, the method may include sending a report message to a wireless device indicating one or more of at least one frequency point or at least one frequency offset, which are used for one or more of the UE's carrier reception or backscatter transmission. Operation of 810 may be performed according to examples as described herein. In some implementations, aspects of operation of 810 may be performed by UE 104, as referenced... Figure 1 As described.

[0140] Figure 9 A flowchart illustrating a method 900 performed by a wireless device according to aspects of this disclosure is shown. The operation of method 900 can be implemented by a device or components thereof as described herein. For example, the operation of method 900 can be performed by a network entity 102 or UE 104 as described herein. In some implementations, the wireless device can execute a set of instructions to control functional elements of the wireless device to perform the described functions. Alternatively or additionally, the wireless device can use dedicated hardware to perform aspects of the described functions.

[0141] At 910, the method may include receiving a report message from a user equipment (UE) indicating one or more of at least one frequency point or at least one frequency offset, which is used for one or more of the UE's carrier reception or backscatter transmission. The operation at 810 can be performed according to the examples described herein. In some implementations, aspects of the operation at 810 may be performed by network entity 102 or UE 104, as referenced... Figure 1As described.

[0142] It should be noted that the methods described herein describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, two or more aspects from the methods can be combined.

[0143] The various exemplary blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, it may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0144] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, these functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the function are implemented at different physical locations.

[0145] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose computer or a special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose computer or a special-purpose computer or a general-purpose processor or a special-purpose processor.

[0146] As used herein, including in the claims, the article “a(a)” preceding an element is unrestricted and is understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a(a),” “at least one,” “one or more,” and “at least one of one or more” may be used interchangeably. As used herein, including in the claims, “or” is used in lists of items (e.g., lists of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) to indicate inclusive lists, such that, for example, a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as “at least partially based on.” Moreover, as used herein, including in the claims, “set” can include one or more elements.

[0147] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be applied within the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the UE: A report message is sent to the wireless device, the report message indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or the at least one frequency offset being used for one or more of the UE's carrier reception or backscatter transmission.

2. The UE of claim 1, wherein the at least one processor is further configured such that the UE: The system receives a configuration from the wireless device, the configuration indicating one or more of a set of one or more frequency points or a set of one or more frequency offsets, the set of one or more frequency points or the set of one or more frequency offsets being used for one or more of the carrier reception or the backscatter transmission of the UE. Based on the set of one or more frequency points or the set of one or more frequency offsets, the transmission frequency points for the backscatter transmission of the UE are determined.

3. The UE of claim 2, wherein, in order to send the report message to the wireless device, the at least one processor is configured to cause the UE to send the report message via the backscatter transmission and at the transmission frequency point.

4. The UE of claim 2, wherein the configuration comprises one or more of the following: a set of one or more frequency point indices; a default frequency point of the UE; a frequency point associated with the configuration; or a set of one or more offset value indices of the frequency point associated with the configuration, and The set of one or more frequency point indices is based at least in part on one or more of the following: the set of one or more frequency point indices, the default frequency point of the UE, and the set of one or more offset value indices for the frequency point associated with the configuration.

5. The UE of claim 2, wherein the set of one or more frequency offsets is based on one or more of the following: at least one frequency point in the set of one or more frequency points, or a reference frequency index.

6. The UE of claim 2, wherein, in order to determine the transmission frequency point for the backscatter transmission of the UE, the at least one processor is configured such that the UE: Determine at least one frequency point from the set of one or more frequency points for carrier reception; and The frequency offset value is determined based on one or more of the set of one or more frequency offsets or one or more of the capabilities of the UE.

7. The UE of claim 2, wherein the configuration further comprises at least one of the following: A first indication of whether the carrier reception is allocated in the downlink (DL) spectrum or the uplink (UL) spectrum; or A second indication regarding whether the backscatter transmission is allocated in the DL spectrum or the UL spectrum.

8. The UE of claim 2, wherein, in order to receive the configuration from the wireless device, the at least one processor is configured to cause the UE to receive an index of the configuration.

9. The UE of claim 1, wherein the reporting message includes a frequency offset value, the frequency offset value indicating a threshold frequency offset value of the UE.

10. The UE of claim 9, wherein the at least one processor is further configured such that the UE: An indication of receiving a frequency offset value, wherein the frequency offset value is at least partially based on the threshold frequency offset value; and The backscatter transmission of the UE is performed at least in part based on the frequency offset value.

11. The UE of claim 1, wherein the reporting message indicates one or more of the following: the type of the UE or the capabilities of the UE.

12. The UE according to claim 1, wherein the reporting message includes the identification information of the UE.

13. The UE of claim 1, wherein, in order to send the report message to the wireless device, the at least one processor is further configured to cause the UE to: Perform uplink or sidelink transmissions including the reported message.

14. The UE of claim 1, wherein one or more of the carrier reception or the backscatter transmission satisfies at least one of the following: The carrier reception is allocated in the DL spectrum, and the corresponding backscatter transmission is allocated in the UL spectrum; The carrier reception is allocated in the DL spectrum, and the corresponding backscatter transmission is allocated in the DL spectrum; The carrier reception is allocated in the UL spectrum, and the corresponding backscatter transmission is allocated in the UL spectrum; or The carrier reception is allocated in the UL spectrum, and the corresponding backscatter transmission is allocated in the DL spectrum.

15. The UE of claim 1, wherein the UE includes an environmental Internet of Things (IoT) device.

16. A wireless device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the wireless device: Receive a report message from a user equipment (UE) indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or the at least one frequency offset being used for one or more of the UE's carrier reception or backscatter transmission.

17. The wireless device of claim 16, wherein the at least one processor is further configured to cause the wireless device to: The configuration is sent to the UE, the configuration indicating one or more of a set of one or more frequency points or a set of one or more frequency offsets, the set of one or more frequency points or the set of one or more frequency offsets being used for one or more of the UE's carrier reception or backscatter transmission.

18. The wireless device of claim 16, wherein the wireless device comprises a base station, an auxiliary node, an intermediate node, a relay node, a repeater, or a UE.

19. A method performed by a user equipment (UE), the method comprising: A report message is sent to the wireless device, the report message indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or the at least one frequency offset being used for one or more of the UE's carrier reception or backscatter transmission.

20. A method performed by a wireless device, the method comprising: Receive a report message from a user equipment (UE) indicating one or more of at least one frequency point or at least one frequency offset, the at least one frequency point or the at least one frequency offset being used for one or more of the UE's carrier reception or backscatter transmission.

Images