Auxiliary signal-based envelope tracking

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a first network entity may receive, from a second network entity, an indication of a first frequency offset associated with the second network entity. In some aspects, a first network entity may receive a first transmission from a second network entity, the first transmission including a first communication and a first assistance signal separated in a frequency domain based on a first frequency offset. In some aspects, a first network entity may decode a first transmission via envelope tracking to obtain a first communication from the first transmission. Numerous other aspects are provided.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 323,807, filed May 25, 2023, entitled “HELPER SIGNAL BASEDENVELOPE TRACKING,” which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication and to techniques and apparatus for envelope tracking based on auxiliary signals. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0004] A wireless network may include one or more network nodes that support communication for one or more user equipment (UE) devices. The UE may communicate with network entities via downlink and uplink communication. "Downlink" (or "DL") refers to the communication link from the network entity to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node.

[0005] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0006] Some aspects described herein relate to a first network entity for wireless communication. The first network entity may include one or more communication interfaces and one or more processors coupled to the one or more communication interfaces. The first network entity may be configured to receive, via the one or more communication interfaces and from the second network entity, an indication of a first frequency offset associated with the second network entity. The first network entity may be configured to receive, via the one or more communication interfaces and from the second network entity, a first transmission comprising a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset. The first network entity may be configured to decode the first transmission via envelope tracking to obtain the first communication from the first transmission.

[0007] Some aspects described herein relate to a first network entity for wireless communication. The first network entity may include one or more communication interfaces and one or more processors coupled to the one or more communication interfaces. The first network entity may be configured to enable the one or more communication interfaces to communicate with a second network entity to negotiate a first frequency offset and a first frequency domain positioning for communication associated with the first network entity, and a second frequency offset and second frequency domain positioning for communication associated with the second network entity. The first network entity may be configured to enable the one or more communication interfaces to transmit an indication of the first frequency offset to a third network entity. The first network entity may be configured to enable the one or more communication interfaces to transmit a communication and auxiliary signal, separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain positioning.

[0008] Some aspects described herein relate to a method of wireless communication performed by a first network entity. The method may include receiving from a second network entity an indication of a first frequency offset associated with the second network entity. The method may include receiving from the second network entity a first transmission, the first transmission including a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset. The method may include decoding the first transmission via envelope tracking to obtain the first communication from the first transmission.

[0009] Some aspects described herein relate to a method of wireless communication performed by a first network entity. The method may include communicating with a second network entity to negotiate a first frequency offset and a first frequency domain positioning for communication associated with the first network entity, and a second frequency offset and second frequency domain positioning for communication associated with the second network entity. The method may include sending an indication of the first frequency offset to a third network entity. The method may include transmitting communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain positioning.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing instructions thereon for wireless communication. When executed by a first network entity, these instructions cause the first network entity to receive from a second network entity an indication of a first frequency offset associated with the second network entity. When executed by the first network entity, these instructions cause the first network entity to receive from the second network entity a first transmission, the first transmission comprising a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset. When executed by the first network entity, these instructions cause the first network entity to decode the first transmission via envelope tracking to obtain the first communication from the first transmission.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing instructions thereon for wireless communication. These instructions, when executed by a first network entity, enable the first network entity to communicate with a second network entity to negotiate a first frequency offset and a first frequency domain positioning for communication associated with the first network entity, and a second frequency offset and a second frequency domain positioning for communication associated with the second network entity. These instructions, when executed by the first network entity, enable the first network entity to send an indication of the first frequency offset to a third network entity. These instructions, when executed by the first network entity, enable the first network entity to send the transmission of communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain positioning.

[0012] Some aspects described herein relate to a first apparatus for wireless communication. The first apparatus may include components for receiving from a second apparatus an indication of a first frequency offset associated with a second network entity. The first apparatus may include components for receiving from the second apparatus a first transmission, the first transmission including a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset. The first apparatus may include components for decoding the first transmission via envelope tracking to obtain the first communication from the first transmission.

[0013] Some aspects described herein relate to a first apparatus for wireless communication. The first apparatus may include means for communicating with a second apparatus to negotiate a first frequency offset and a first frequency domain positioning for communication associated with the apparatus, and a second frequency offset and a second frequency domain positioning for communication associated with the second apparatus. The first apparatus may include means for transmitting an indication of the first frequency offset to a third apparatus. The first apparatus may include means for transmitting a transmission including communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain positioning.

[0014] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0015] The foregoing provides a broad overview of the exemplary features and technical advantages of the examples according to this disclosure. Additional exemplary features and advantages are described below. Attached Figure Description

[0016] The accompanying drawings illustrate certain exemplary aspects of this disclosure and are therefore not limiting in scope. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 These are illustrations of example environments in which the apparatus and / or methods described herein may be implemented according to this disclosure.

[0018] Figure 2 This is a diagram illustrating example components of a device according to the present disclosure.

[0019] Figure 3 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 4 This is a diagram illustrating an environment that includes wireless communication between a first network entity and a second network entity according to this disclosure.

[0021] Figure 5This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0022] Figure 6 This is a diagram illustrating an example of backscatter communication according to this disclosure.

[0023] Figure 7 This is a diagram illustrating an example of envelope tracking according to this disclosure.

[0024] Figure 8 This is a diagram illustrating an example of operation associated with envelope tracking based on auxiliary signals, according to this disclosure.

[0025] Figure 9 This is a diagram illustrating an example of the transmission of communication and auxiliary signals in accordance with this disclosure.

[0026] Figure 10 This is a diagram illustrating an example of envelope tracking decoding associated with multiple signals according to this disclosure.

[0027] Figure 11 This is a diagram illustrating an example process performed, for example, by a first network node according to this disclosure.

[0028] Figure 12 This is a diagram illustrating an example process performed, for example, by a first network node according to this disclosure.

[0029] Figure 13 This is a diagram of an example device for wireless communication according to the present disclosure.

[0030] Figure 14 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0031] In some examples, envelope tracking can be used by network entities to decode wireless signals. For instance, envelope tracking can be used as a technique for detecting and extracting information from modulated signals. Envelope tracking can also be used by network entities as a form of signal demodulation, which can recover baseband signals from modulated radio frequency (RF) signals. For example, a network entity can receive signals with a received voltage that varies over time. The amplitude of the signal can vary over time.

[0032] Network entities can provide signals (or information associated with signals) to envelope detectors. Envelope detectors can be configured to detect the envelope associated with a signal. As used herein, the “envelope” of a signal can refer to the amplitude or magnitude of the signal, as amplitude or magnitude varies over time. The envelope can be a function of modulation applied to the signal. The envelope can be associated with an envelope voltage, which indicates the voltage of the envelope over time. Network entities can determine information about the signal (e.g., bit values) based on, according to, or otherwise associated with the envelope voltage. For example, a network entity can be configured to determine whether the voltage of a signal at a given time will be associated with “1” or “0” (e.g., for information bits of the signal) based on, according to, or otherwise associated with the envelope voltage at a given time. For example, a network entity can compare the voltage of the envelope to one or more thresholds. As an example, if the value of the voltage at a given time meets a threshold, the network entity can determine that the bit corresponding to the given time is associated with “1”. If the voltage value at a given time does not meet the threshold, the network entity can determine that the bit corresponding to the given time is associated with "0".

[0033] Therefore, the decoding operation performed by the network entity can be simplified and / or associated with reduced complexity. For example, it enables the network entity to obtain the value of the information bits of a signal without using one or more active RF components. Additionally, it enables the network entity to obtain the value of the information bits of a signal without down-converting the signal to a baseband signal. As another example, envelope tracking decoding operations enable the network entity to obtain the value of the information bits of a signal without performing carrier frequency offset and / or frequency synchronization. Thus, less complex circuitry or components (or fewer components) can be included in the network entity, and the network entity can still decode modulated signals by using envelope tracking.

[0034] However, in some examples, more than one transmitter may send signals toward the network entity in a spatial direction at a given time. For example, a first transmitter may send a first signal toward the network entity. The first signal may be a signal intended for use by the network entity. Another transmitter may send a second signal toward the network entity in a spatial direction, such that the network entity receives the second signal. The second signal may or may not be intended for use by the network entity. The first and second signals may at least partially overlap in the time domain. For example, the second signal may interfere with the first signal, resulting in the amplitude of the signal received at the network entity being different from the amplitude of the first signal. Therefore, the second signal may affect or modify the envelope of the first signal, causing the network entity to be unable to accurately decode the first signal using the envelope tracking decoding operation described herein. For example, the received signal may be the sum of data sent via the first and second signals. Therefore, the network entity may be unable to use envelope tracking to extract or recover the individual signals (e.g., because the envelope includes items as the sum of data sent via the first and second signals). Therefore, the communication performance and / or decoding performance associated with a network entity may be degraded because the network entity may incorrectly use envelope tracking to decode a signal when it receives one or more other signals at a time that at least partially overlaps with the time when the signal was received by the network entity.

[0035] Various aspects generally relate to wireless communication, and more specifically to decoding wireless communication signals via envelope tracking. Some aspects more specifically relate to decoding based on auxiliary signals via envelope tracking. In some aspects, the signal to be decoded via envelope tracking may include communication (e.g., data or control information) and auxiliary signals. In some aspects, a network entity may decode a signal via envelope tracking to obtain communication. As used herein, an auxiliary signal may refer to a single tone included in a signal. A tone may be a subcarrier or a resource element. Communication and auxiliary signals may be separated in the frequency domain by a frequency offset. Auxiliary signals enable the separation of information (e.g., items) of a received signal in the frequency domain, allowing the network entity receiving the signal to isolate information associated with a particular communication. For example, a network entity may modify the received signal (or the envelope of the received signal) based on, according to, or otherwise associated with a frequency offset to isolate information associated with a particular communication. A network entity may use envelope tracking to decode the communication after isolating the information associated with the communication.

[0036] For example, the signal received at a network entity can be the sum of multiple transmissions. Auxiliary signals included in the respective transmissions of the multiple transmissions can cause information in the received signal (e.g., for the respective transmissions of the multiple transmissions) to be separated in the frequency domain. For example, the first item may include information indicating the sum of the multiple transmissions, the second item may include information indicating the first transmission among the multiple transmissions, the third item may include information indicating the second transmission among the multiple transmissions, and the fourth item may include information indicating interference caused by the multiple transmissions, and so on. Data communications and auxiliary signals can be placed in the frequency domain within the respective transmissions to separate different items in the frequency domain, such that different items can be isolated by the network entity receiving the multiple transmissions. In some aspects, the frequency domain positions of data communications and auxiliary signals can be determined and / or negotiated based on one or more conditions, according to one or more conditions, or otherwise associated with one or more conditions.

[0037] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some aspects, by including an auxiliary signal in the transmission, the described techniques can be used to enable a network entity to decode the transmission using envelope tracking to obtain communication. By using envelope tracking, the complexity associated with decoding the transmission can be reduced. Additionally, by using envelope tracking, a network entity can include fewer (or less complex) RF components, thereby reducing the cost and / or complexity associated with the network entity. In some aspects, the auxiliary signal can isolate an item indicating communication from a given transmitter in the frequency domain from an item indicating information associated with other communication from other transmitters. This enables a network entity to modify the received signal and / or the envelope of the received signal to isolate the item indicating communication and to decode that item using envelope tracking to obtain communication.

[0038] In some aspects, the value of the frequency offset used for a corresponding transmission can be determined, selected, or negotiated based on, according to, or otherwise associated with one or more conditions. One or more conditions can ensure that items of the received signal are sufficiently separated in the frequency domain, enabling network entities to isolate and / or separate information associated with a particular communication or data when the received signal is the sum of multiple transmissions. Additionally, one or more conditions can ensure that interference caused by multiple transmissions occurs in frequency domain locations that do not overlap with other items of the received signal.

[0039] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and is not limited to any particular structure, function, example, aspect, etc., presented throughout this disclosure. For example, this disclosure includes any aspect disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure includes such apparatus or methods implemented using structures, functionalities, or structures and functionalities other than or different from the various aspects of the disclosure set forth herein. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0040] Aspects and examples generally include methods, apparatus, network nodes, network entities, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as described or fully described herein with reference to the accompanying drawings and description and illustrated as such.

[0041] This disclosure can be readily used as the basis for modifying or designing other structures for performing the same purposes as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. In the following description, and in conjunction with the accompanying drawings, the characteristics (both their organization and operation) of the exemplary concepts disclosed herein, as well as their associated exemplary advantages, are described. Each figure in the accompanying drawings is for illustrative and descriptive purposes and not as a limitation of the claims.

[0042] While aspects have been described in this disclosure by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described example aspects and example features may include additional example components and example features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of different sizes, shapes, and configurations.

[0043] Various devices and technologies are used to illustrate several aspects of a telecommunications system. These devices and technologies are described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0044] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0045] Figure 1 This is a diagram illustrating an example environment 100 in which the apparatus and / or methods described herein may be implemented according to this disclosure. Figure 1 As shown, environment 100 may include network entities 102, 104, and 106 that can communicate with each other via network 108. Network entities 102, 104, and 106 may be distributed throughout network 108, and each network entity 102, 104, and 106 may be stationary and / or mobile. Network 108 may include wired communication connections, wireless communication connections, or a combination of wired and wireless communication connections.

[0046] Network 108 may include, for example, cellular networks (e.g., Long Term Evolution (LTE) networks, Code Division Multiple Access (CDMA) networks, 4G networks, 5G networks, 6G networks, another type of next-generation network, etc.), Public Land Mobile Network (PLMN), Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), Telephone Network (e.g., Public Switched Telephone Network (PSTN)), Private Network, Ad Hoc Network, Intranet, Internet, Fiber-based Network, Cloud Computing Network, etc., and / or combinations of these or other types of networks.

[0047] Generally, any number of networks 108 can be deployed in a given geographical area. Each network 108 can support a specific RAT and can operate on one or more frequencies. A RAT can be referred to as a radio technology, air interface, etc. A frequency can be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, open RAT, NR, or 5G RAT networks can be deployed.

[0048] In some aspects, environment 100 may include one or more non-terrestrial network (NTN) deployments, wherein non-terrestrial wireless communication equipment may include non-terrestrial network entities (e.g., network entities 102, 104, and 106). Non-terrestrial network entities may include network entities such as, for example, user equipment (UE) (which are interchangeably referred to herein as “non-terrestrial UE”), base stations (which are interchangeably referred to herein as “non-terrestrial BS” and “non-terrestrial base stations”) and / or relay stations (which are interchangeably referred to herein as “non-terrestrial relay stations”), etc. As used herein, “NTN” may refer to a network to which access is facilitated by non-terrestrial network entities (such as non-terrestrial UEs, non-terrestrial base stations, and / or non-terrestrial relay stations, etc.).

[0049] One or more of network entities 102, 104, and 106 can be any number of non-terrestrial wireless communication devices, include any number of non-terrestrial wireless communication devices, or be included in any number of non-terrestrial wireless communication devices. Non-terrestrial wireless communication devices can include satellites, manned aircraft systems, unmanned aircraft system (UAS) platforms, etc. Satellites can include low Earth orbit (LEO) satellites, medium Earth orbit (MEO) satellites, geostationary orbit (GEO) satellites, highly elliptical orbit (HEO) satellites, etc. Manned aircraft systems can include aircraft, helicopters, spacecraft, etc. UAS platforms can include high-altitude platform stations (HAPS) and can include balloons, spacecraft, aircraft, etc. Satellites can use satellite communications to communicate directly and / or indirectly with other entities in the environment. Other entities can include UEs (e.g., terrestrial UEs and / or non-terrestrial UEs), one or more other satellites in one or more NTN deployments, other types of base stations (e.g., stationary and / or terrestrial base stations), relay stations, and / or one or more components and / or devices included in the core network, etc.

[0050] As described herein, a network entity (which may alternatively be referred to as an entity, node, network node, or wireless entity) can be, resemble, include, or be a component of, the following: a base station (e.g., any base station described herein, including a decomposed base station), a UE (e.g., any UE described herein), a RedCap device, an enhanced RedCap device, an ambient Internet of Things (IoT) device, an energy harvesting (EH) capable device, a network controller, apparatus, device, computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network entity can be a UE. As another example, a network entity can be a base station. As used herein, “network entity” can mean an entity configured to operate in a network (such as network entity 108). For example, “network entity” is not limited to entities currently located in and / or currently operating in a network. Instead, a network entity can be any entity capable of communicating and / or operating within a network.

[0051] The adjectives "first," "second," "third," etc., are used to distinguish between two or more modified nouns in context, and do not imply absolute modifiers applicable only to a specific corresponding entity throughout the document. For example, a network entity may be referred to as "first network entity" in one discussion and as "second network entity" in another, and vice versa. As an example, the first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different from these examples.

[0052] Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network entities. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, a first processing entity, etc., configured to receive information; and the second network entity may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, a second processing entity, etc.

[0053] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to send information to a second network entity. In this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the first network entity is configured to provide, transmit, output, communicate, or send information to the second network entity. Similarly, in this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the second network entity is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network entity.

[0054] As shown in the figure, network entity 102 may include a communication manager 110 and one or more communication interfaces 112. The communication manager 110 may be configured to perform one or more communication tasks as described herein. In some aspects, the communication manager 110 may direct the communication interface 112 to perform one or more communication tasks as described herein. Similarly, network entity 106 may include a communication manager 114 and one or more communication interfaces 116. The communication manager 114 may be configured to perform one or more communication tasks as described herein. In some aspects, the communication manager 114 may direct the communication interface 116 to perform one or more communication tasks as described herein. Although network entities 102 and 104 have been depicted with reference only to clarity of description, any or more of network entities 102, 104, and 106 may also include a communication manager and a communication interface.

[0055] As used herein, "communication interface" refers to an interface that enables communication (e.g., wireless or wired communication) between a first network entity and a second network entity. A communication interface may include electronic circuitry that enables network entities to send, receive, or otherwise perform communication. A communication interface may include one or more components configured to enable communication between the first and second network entities. For example, a communication interface may include transmitting components, receiving components, and / or transceivers, etc. Communication interfaces are described in more detail elsewhere herein, such as in conjunction with... Figure 2 .

[0056] As described in more detail elsewhere herein, network entity 102 may (e.g., communication manager 110 may, or communication interface 112 may) receive from a second network entity an indication of a first frequency offset associated with the second network entity; receive from the second network entity a first transmission comprising a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset; and / or decode the first transmission via envelope tracking to obtain the first communication from the first transmission. Additionally or alternatively, network entity 102 and / or communication manager 110 may perform one or more other operations described herein.

[0057] As described in more detail elsewhere herein, network entity 106 may (e.g., communication manager 114 may, or communication interface 116 may) communicate with a second network entity to negotiate a first frequency offset and a first frequency domain location for communication associated with the first network entity, and a second frequency offset and a second frequency domain location for communication associated with the second network entity; send an indication of the first frequency offset to a third network entity; and / or send the transmission of communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain location. Additionally or alternatively, network entity 106 and / or communication manager 114 may perform one or more other operations described herein.

[0058] Figure 1 The number and arrangement of entities shown are provided as one or more examples. In practice, they may exist in... Figure 1 The network entities and / or networks shown are compared to additional network entities and / or networks, fewer network entities and / or networks, different network entities and / or networks, or network entities and / or networks arranged in a different manner. Furthermore, network entities 102, 104, and 106 can be implemented using a single device or multiple devices.

[0059] Figure 2 This is a diagram illustrating example components of apparatus 200 according to the present disclosure. Apparatus 200 may correspond to any or more of network entities 102, 104, and 106 or another network entity described herein. Additionally or alternatively, any or more of network entities 102, 104, and 106 or another network entity described herein may include one or more apparatuses 200 and / or one or more components of apparatus 200. For example, in some aspects, apparatus 200 may include means configured to perform wireless communication methods (e.g., devices, device components, modems, chips, and / or a set of device components, etc.), as described herein. Figure 2 As shown, device 200 may include components such as bus 205, processor 210, memory 215, input component 220, output component 225, communication interface 230, communication manager 235, and decoding component 240. One or more of components 205, 210, 215, 220, 225, 230, 235, and / or 240 may be implemented in hardware, software, or a combination of hardware and software.

[0060] Bus 205 includes components that enable communication between the various components of device 200. Processor 210 includes a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), digital signal processor (DSP), microprocessor, microcontroller, field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and / or another type of processing component. In some aspects, processor 210 includes one or more processors that can be programmed to perform functions.

[0061] Memory 215 includes random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, and / or optical storage) that stores information and / or instructions for use by processor 210. Memory 215 may store other information and / or software related to the operation and use of device 200. For example, memory 215 may include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, and / or solid-state disks), compact discs (CDs), digital multi-purpose discs (DVDs), floppy disks, cassettes, magnetic tapes, and / or another type of non-transitory computer-readable media.

[0062] Input component 220 includes components that allow device 200 to receive information, such as via user input. For example, input component 220 may be associated with a user interface as described herein (e.g., to allow a user to interact with one or more features of device 200). Input component 220 may include a capacitive touchscreen display capable of receiving user input. Input component 220 may include a keyboard, keypad, mouse, buttons, switches, and / or microphone, etc. Additionally or alternatively, input component 220 may include sensors for sensing information (e.g., a vision sensor, position sensor, accelerometer, gyroscope, and / or actuator, etc.). In some aspects, input component 220 may include a camera (e.g., a high-resolution camera and / or a low-resolution camera, etc.). Output component 225 may include components that provide output from device 200 (e.g., a display, speaker, and / or one or more light-emitting diodes (LEDs, etc.).

[0063] Communication interface 230 may include transmitting and / or receiving components. For example, communication interface 230 may include a transceiver and / or one or more separate receivers and / or transmitters, enabling device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. In some aspects, the communication interface may include one or more radio frequency reflective elements and / or one or more radio frequency refractive elements. Communication interface 230 may permit device 200 to receive information from and / or provide information to another device. For example, communication interface 230 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, an RF interface, a Universal Serial Bus (USB) interface, a Wi-Fi interface, a cellular network interface, a wireless modem, or an internal integrated circuit (I / O). 2 C) and / or Serial Peripheral Interface (SPI), etc.

[0064] Communication manager 235 may include hardware, software, or a combination of hardware and software configured to cause device 200 to perform one or more communication tasks associated with communication manager 110 and / or communication interface 112 or communication interface 230. Similarly, communication manager 235 may include hardware, software, or a combination of hardware and software configured to cause device 200 to perform one or more communication tasks associated with communication manager 114 and / or communication interface 116 or communication interface 230. In some aspects, communication manager 235 may be... Figure 1 The communication manager 110 and / or communication manager 114 depicted herein may be similar to, include, or be included in the communication manager. In some aspects, the communication manager 235 may include a processor 210, a memory 215, an input component 220, an output component 225, a communication interface 230, and / or a decoding component 240, and / or one or more aspects thereof.

[0065] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0066] As described above, in some respects, Figure 1 The network 108 depicted herein may include a cellular network containing a RAT. While some aspects may be described herein using terms commonly associated with 5G or NR RATs, aspects of this disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or 5G and later (e.g., 6G) RATs.

[0067] Figure 3This is a diagram illustrating an example of a wireless network 300 according to the present disclosure. The wireless network 300 may be or may include elements of a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and / or a 6G network, etc. The wireless network 300 may include one or more network nodes 310 (shown as network node 310a, network node 310b, network node 310c, and network node 310d), one or more UEs 320 (shown as UE 320a, UE 320b, UE 320c, UE 320d, and UE 320e), and / or other entities. Network node 310 is a network node that communicates with UE 320. As shown, network node 310 may include one or more network nodes. For example, network node 310 may be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, network node 310 can be a decomposed network node (sometimes referred to as a decomposed base station), which means that network node 310 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more CUs, one or more DUs, or one or more RUs).

[0068] In some examples, network node 310 is or includes network nodes (such as RU) that communicate with UE 320 via a radio access link. In some examples, network node 310 is or includes network nodes (such as DU) that communicate with other network nodes 310 via a fronthaul link or a midhaul link. In some examples, network node 310 is or includes network nodes (such as CU) that communicate with other network nodes 310 via a midhaul link or with the core network via a backhaul link. In some examples, network node 310 (such as aggregated network node 310 or decomposed network node 310) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 310 may include, for example, NR base stations, LTE base stations, Node B, eNB (e.g., in 4G), gNB (e.g., in 5G), access points, transmit / receive points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 310 can interconnect with each other or with one or more other network nodes 310 in the wireless network 300 using any suitable transport network through various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0069] In some examples, network node 310 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context of terminology use, the term "cell" may refer to the coverage area of ​​network node 310 and / or the network node subsystem serving that coverage area. Network node 310 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 320 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 320 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 320 associated with the femtocell (e.g., UE 320 in a Closed Subscriber Group (CSG)). Network node 310 used for macrocells may be referred to as a macro network node. Network node 310 used for picocells may be referred to as a pico network node. The network node 310 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 3 In the example shown, network node 310a can be a macro network node for macro cell 302a, network node 310b can be a pico network node for pico cell 302b, and network node 310c can be a femto network node for femto cell 302c. Network nodes can support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 310 (e.g., a mobile network node).

[0070] In some aspects, the term "base station" or "network entity" may refer to an aggregated base station, a decomposed base station, an IAB node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network entity" may refer to a CU, DU, RU, a near real-time (near RT) RAN Intelligent Controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 310). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeat the performance of at least a portion of that function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some respects, the term "base station" or "network entity" may refer to one base station function within a base station functionality, rather than another. In this way, a single device may include more than one base station.

[0071] The wireless network 300 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 310 or UE 320) and transmit data to downstream nodes (e.g., UE 320 or network node 310). A relay station may be a UE 320 that can relay transmissions to other UE 320s. Figure 3 In the example shown, network node 310d (e.g., a relay network node) can communicate with network node 310a (e.g., a macro network node) and UE 320d to facilitate communication between network node 310a and UE 320d. The network node 310 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

[0072] The wireless network 300 can be a heterogeneous network, comprising different types of network nodes 310, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 310 may have different transmit power levels, different coverage areas, and / or different effects on interference in the wireless network 300. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0073] Network controller 330 may be coupled to or communicate with a group of network nodes 310, and may provide coordination and control for these network nodes 310. Network controller 330 may communicate with network nodes 310 via a backhaul or midhaul communication link. Network nodes 310 may also communicate directly with each other, or indirectly via a wireless or wired backhaul communication link. In some aspects, network controller 330 may be a CU or a core network device, or may include a CU or a core network device.

[0074] For example, in some aspects, wireless network 300 may be, include, or be included in a wireless backhaul network (sometimes referred to as an IAB network). In an IAB network, at least one network entity (e.g., network node 310) may be an anchor base station communicating with the core network via a wired backhaul link (such as a fiber optic connection). Anchor base stations may also be referred to as IAB donors (or IAB-donors), central entities, central units, etc. An IAB network may include one or more non-anchor base stations (sometimes referred to as relay base stations or IAB nodes (or IAB-nodes)). Non-anchor base stations may communicate directly or indirectly with anchor base stations via one or more backhaul links (e.g., via one or more non-anchor base stations) to form a backhaul path to the core network for carrying backhaul services. The backhaul link may be a wireless link. Anchor base stations and / or non-anchor base stations may communicate with one or more UEs (e.g., UE 320) via an access link, which may be a wireless link for carrying access services.

[0075] In some aspects, radio access networks, including IAB networks, can utilize millimeter-wave technology and / or directional communication (e.g., beamforming, pre-decoding, etc.) for communication between base stations and / or UEs (e.g., between two base stations, between two UEs, and / or between a base station and a UE). For example, radio backhaul links between base stations can use millimeter waves to carry information and / or can use beamforming, pre-decoding, etc., to be directed toward a target base station. Similarly, radio access links between UEs and base stations can use millimeter waves and / or be directed toward a target network entity (e.g., the UE and / or the base station). In this way, inter-link interference can be reduced.

[0076] An IAB network may include IAB donors connected to a core network via a wired connection (e.g., wired backhaul). For example, the Ng interface of an IAB donor may terminate at the core network. Additionally or alternatively, an IAB donor may connect to one or more devices in the core network that provide core access and mobility management functions (AMF). In some aspects, an IAB donor may include network node 310, such as an anchor base station. An IAB donor may include a CU capable of performing access node controller (ANC) functions and / or AMF functions. The CU may configure the DU of the IAB donor and / or may configure one or more IAB nodes (e.g., mobile terminal (MT) functions and / or DU functions of the IAB nodes) connected to the core network via the IAB donor. Thus, the CU of the IAB donor may control and / or configure the entire IAB network (or a portion thereof) connected to the core network via the IAB donor, for example, by using control messages and / or configuration messages (e.g., Radio Resource Control (RRC) configuration messages or F1 Application Protocol (F1AP) messages).

[0077] The MT (Mediator Function) of an IAB node (e.g., a child node) may be controlled and / or scheduled by another IAB node (e.g., the parent node of the child node) and / or by an IAB donor. The DU (Distribution Function) of an IAB node (e.g., a parent node) may control and / or schedule other IAB nodes (e.g., child nodes of the parent node) and / or UE 320. Therefore, a DU may be referred to as a scheduling node or scheduling component, and an MT may be referred to as a scheduled node or scheduled component. In some aspects, an IAB donor may include DU functionality but not MT functionality. That is, an IAB donor may configure, control, and / or schedule communication between IAB nodes and / or UE 320. UE 320 may include only MT functionality and not DU functionality. That is, communication of UE 320 may be controlled and / or scheduled by an IAB donor and / or an IAB node (e.g., the parent node of UE 320).

[0078] When a first node controls and / or schedules the communication of a second node (e.g., when the first node provides DU functionality for the MT function of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Therefore, the DU functionality of the parent node can control and / or schedule the communication of the child node for that parent node. The parent node may be an IAB donor or an IAB node, and the child node may be an IAB node or UE 320. The communication of the MT function of the child node may be controlled and / or scheduled by the parent node of that child node.

[0079] The link between UE 320 and the IAB donor, or between UE 320 and an IAB node, can be referred to as an access link. An access link can be a radio access link that provides radio access to the core network to UE 320 via the IAB donor and optionally via one or more IAB nodes. Therefore, the radio network 300 can be referred to as a multi-hop network or a wireless multi-hop network.

[0080] A link between an IAB donor and an IAB node, or between two IAB nodes, can be referred to as a backhaul link. A backhaul link can be a wireless backhaul link that provides radio access to the core network to an IAB node via an IAB donor and optionally via one or more other IAB nodes. In an IAB network, network resources used for wireless communication (e.g., time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link. In some aspects, a backhaul link can be a primary backhaul link or a secondary backhaul link (e.g., a backup backhaul link). In some aspects, a secondary backhaul link can be used if the primary backhaul link fails, becomes congested, and / or becomes overloaded, etc.

[0081] UE 320 may be distributed throughout the wireless network 300, and each UE 320 may be stationary or mobile. UE 320 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 320 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

[0082] Some UEs 320 may be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 320 may be considered Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 320 may be considered customer premises equipment. UEs 320 may be contained within a housing that houses components of the UE 320, such as processor components and / or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0083] Some network nodes may have a reduced feature set compared to other network nodes. Network nodes with a reduced feature set may be referred to as RedCap nodes, low-level nodes, NR-Lite nodes, IoT nodes, environmental IoT nodes, passive nodes, terminals (e.g., RFID devices, tags, or similar devices), and / or nodes with energy harvesting capabilities, etc. For example, compared to other nodes (e.g., Quadrature Phase Shift Keying (QPSK) versus 256-Quadrature Amplitude Modulation (QAM), nodes with a reduced feature set may support a lower maximum modulation and decoding scheme (MCS), support a lower maximum transmit power, have less advanced beamforming capabilities (e.g., may not be able to form as many beams as other nodes), require longer processing times, may include less hardware (e.g., fewer antennas, fewer RF components, fewer transmit antennas, and / or fewer receive antennas), and / or may not be able to communicate over the same maximum bandwidth, etc.

[0084] For example, some network nodes may not include batteries, and nodes may accumulate energy from radio signaling. Network nodes can be passive network nodes. Passive network nodes may have no energy storage or have energy storage. Passive network nodes without energy storage may include capacitors to provide energy from the RF to the passive network node momentarily (or near momentarily). Passive network nodes with energy storage may have some limited energy storage capacity. In some examples, network nodes (e.g., RedCap network nodes, low-level network nodes, passive network nodes, RFID devices, tags, or network nodes with energy harvesting capabilities) may include a streamlined set of RF components. For example, some network nodes may not include oscillators, power amplifiers, and / or other active RF components.

[0085] Generally, any number of wireless networks 300 can be deployed in a given geographical area. Each wireless network 300 can support a specific RAT and can operate on one or more frequencies. A RAT may be referred to as a radio technology, air interface, etc. A frequency may be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0086] In some examples, two or more UEs 320 (e.g., shown as UE 320a and UE 320e) may communicate directly using one or more sidelink channels (e.g., without using network node 310 as an intermediary device to communicate with each other). For example, UEs 320 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols) and / or mesh networks. In such examples, UEs 320 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 310.

[0087] Devices in Wireless Network 300 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in Wireless Network 300 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to in documents and articles as the “millimeter wave” band, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0088] The frequencies between FR1 and FR2 can be referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0089] Considering the examples above, unless otherwise specifically stated, the use of terms such as "below 6 GHz" herein can broadly refer to frequencies less than 6 GHz, within FR1, or that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, the use of terms such as "millimeter wave" herein can broadly refer to frequencies that may include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or that may be within the EHF band. Frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0090] As described above, in some respects, network entities (e.g., Figure 1 The network entities 102, 104, and / or 106 depicted can be implemented in a wireless communication environment. For example, in some aspects, the network node can be implemented as a UE, a base station, a relay device, and / or a TRP, etc. In some such aspects, such as Figure 3 As shown, UE 320a may include a communication manager 340 and / or a transceiver, and network node 310a may include a communication manager 350 and / or a transceiver. In some aspects, the communication manager 340 and / or 350 may be... Figure 1 The communication manager 110 and / or communication manager 114 and / or described in the text Figure 2 The communication manager 235 depicted herein, similar to the communication manager, including the communication manager, or included in the communication manager, may be... In some aspects, the transceiver may be... Figure 1 The communication interface 112 and / or communication interface 116 depicted herein may be similar to, include, or be incorporated within the communication interface. In some aspects, the transceiver may include... Figure 2The communication interface 230 depicted in the diagram may be included in the communication interface.

[0091] In some aspects, UE 320 may include a communication manager 340. As described in more detail elsewhere herein, the communication manager 340 may receive from a second network entity an indication of a first frequency offset associated with the second network entity; receive from the second network entity a first transmission, the first transmission including a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset; and / or decode the first transmission via envelope tracking to obtain the first communication from the first transmission. Additionally or alternatively, the communication manager 340 may perform one or more other operations described herein.

[0092] In some aspects, network node 310 may include communication manager 350. As described in more detail elsewhere herein, communication manager 350 may communicate with a second network entity to negotiate a first frequency offset and a first frequency domain location for communication associated with a first network entity, and a second frequency offset and a second frequency domain location for communication associated with the second network entity; send an indication of the first frequency offset to a third network entity; and / or send transmissions including communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain location. Additionally or alternatively, communication manager 350 may perform one or more other operations described herein.

[0093] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0094] Figure 4 This illustrates, according to this disclosure, the inclusion of wireless communication with network entity 404 (e.g., via a network such as...) Figure 1 Network 108 and / or depicted in Figure 3 The diagram illustrates the environment 400 of network entity 402 (of a wireless network 300) depicted in the image. Network entity 402 may be equipped with a set of antennas 406a to 406t, such as... T One antenna ( T ≥ 1). Network entity 404 may be equipped with a set of antennas 408a to 408r, such as R One antenna ( R ≥ 1).

[0095] At network entity 402, transmitting processor 410 may receive data from data source 412 intended for or otherwise specified for network entity 404 (or a set of network entities 404). Transmitting processor 410 may select one or more MCSs for network entity 404 based on one or more Channel Quality Indicators (CQIs) received from network entity 404. Network entity 402 may process (e.g., encode and modulate) the data for network entity 404 based on the MCS selected for network entity 404 and may provide data symbols for network entity 404. Transmitting processor 410 may process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 410 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 414 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can process a collection of output symbol streams (e.g., T Each output symbol stream is provided to the corresponding set of modems 416a to 416t (e.g., ...). T Each modem in the set of modems 416a to 416t can be provided to the modulator component (shown as MOD) of the modems in the set of modems 416a to 416t. Each modem in the set of modems 416a to 416t can use the corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem in the set of modems 416a to 416t can further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a signal. One or more modems in the set of modems 416a to 416t can transmit a set of signals (e.g., via corresponding antennas in the set of antennas 406a to 406t) T (Signals). These signals may include, for example, downlink signals.

[0096] At network entity 404, one or more antennas from the set of antennas 408a to 408r can receive signals from network entity 402 and / or network nodes, and can transmit signals to the set of modems 418a to 418r (e.g., R One or more modems (of a set of modems) provide a collection of received signals (e.g., modems). REach received signal may be provided to the demodulator component (shown as DEMOD) of the corresponding modem in the set of modems 418a to 418r. Each modem in the set of modems 418a to 418r may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem in the set of modems 418a to 418r may use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. The MIMO detector 420 may obtain the received symbols from one or more modems in the set of modems 418a to 418r, may perform MIMO detection on these received symbols where applicable, and may provide the detected symbols.

[0097] The receiver processor 422 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for network entity 404 to data sink 424, and provide decoded control information and system information to controller / processor 426. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. Controller / processor 426 can be, similar to, include, or be included in... Figure 2 In the processor 210 depicted, the controller / processor 426 can determine parameters such as the received reference signal power (RSRP), received signal strength indicator (RSSI), received reference signal quality (RSRQ), and / or CQI.

[0098] Network controller 428 may include communication unit 430, controller / processor 432, and memory 434. Network controller 428 may be, similar to, include, or be included in... Figure 3 The network controller 330 is depicted in the diagram. The network controller 428 may include one or more devices, such as those in the core network. The network controller 428 may communicate with the network entity 402 via the communication unit 430.

[0099] One or more antennas (e.g., antennas 406a to 406t and / or antennas 408a to 408r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings (such as housing 484)), a set of coplanar antenna elements, a set of non-coplanar antenna elements and / or coupled to one or more transmitting and / or receiving components (such as...) Figure 4 One or more antenna elements (one or more components).

[0100] Similarly, at network entity 404, transmit processor 436 may receive and process data from data source 438 and control information from controller / processor 426 (e.g., reports including RSRP, RSSI, RSRQ, and / or CQI). Transmit processor 436 may generate reference symbols for one or more reference signals. Symbols from transmit processor 436 may be pre-decoded by TX MIMO processor 440 where applicable, and further processed by one or more modems from the set of modems 418a to 418r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network entity 402. In some examples, each modem from the set of modems 418a to 418r of network entity 404 may include a modulator and a demodulator. Network entity 404 may include communication manager 458. Communication manager 458 may be, or may be similar to, communication manager 110, communication manager 114, communication manager 235, communication manager 340, and / or communication manager 350. In some examples, network entity 404 includes a transceiver. The transceiver may include any combination of antennas 408a to 408r, modems 418a to 418r, MIMO detector 420, receive processor 422, transmit processor 436, and / or TX MIMO processor 440. The transceiver may be... Figure 1 The communication interface 112 and / or communication interface 116 and / or described in the figure Figure 2 The communication interface 230 depicted herein, similar to this communication interface, including this communication interface, or included in this communication interface. The transceiver may be used by a processor (e.g., controller / processor 426) and / or memory 442 to execute this document (e.g., reference 442). Figures 8 to 14 ( ) any aspect of the method described in the method.

[0101] At network entity 402, signals from network entity 404 and / or other network nodes may be received by one or more antennas from the set of antennas 406a to 406t, processed by one or more modems (e.g., demodulator components, shown as DEMOD) from the set of modems 416a to 416t, detected by MIMO detector 444 where applicable, and further processed by receiver processor 446 to obtain decoded data and control information transmitted by network entity 404. Receiver processor 446 may provide the decoded data to data sink 448 and the decoded control information to controller / processor 450. Network entity 402 may include communication unit 452 and may communicate with network controller 428 via communication unit 452. Network entity 402 may include communication manager 460. Communication manager 460 may be, or may be similar to, communication manager 110, communication manager 114, communication manager 235, communication manager 340, and / or communication manager 350. Network entity 402 may include a scheduler 454 to schedule one or more network entities 404 for downlink and / or uplink communication. In some examples, one or more modems from the set of modems 416a to 416t of network entity 402 may include a modulator and a demodulator. In some examples, network entity 402 includes a transceiver. The transceiver may include any combination of antennas 406a to 406t, modems 416a to 416t, MIMO detector 444, receive processor 446, transmit processor 410, and / or TXMIMO processor 414. The transceiver may be... Figure 1 The communication interface 112 and / or communication interface 116 and / or described in the figure Figure 2 The communication interface 230 depicted herein, similar to this communication interface, including this communication interface, or included in this communication interface. The transceiver may be used by a processor (e.g., controller / processor 450) and memory 456 to execute this document (e.g., reference 450). Figures 8 to 14 ( ) any aspect of the method described in the method.

[0102] When referring to one or more elements that perform functions (e.g., steps of a method), one element may perform all functions, or more than one element may jointly perform these functions. When more than one element jointly performs these functions, each function does not need to be performed by every single element (e.g., different functions may be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements may perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform functions, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions.

[0103] The controller / processor 450 of network entity 402, the controller / processor 426 of network entity 404 and / or Figure 4 Any other component may perform one or more techniques associated with envelope tracking based on auxiliary signals, as described in more detail elsewhere herein. For example, the controller / processor 450 of network entity 402, the controller / processor 426 of network entity 404, and / or Figure 4 Any other component that can execute or direct, for example Figure 11 Process 1100 Figure 12 The operation of process 1200 and / or other processes as described herein. Memory 442 and memory 456 may store data and program code for network entity 402 and network entity 404, respectively. In some examples, memory 442 and / or memory 456 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions may cause one or more processors, network entity 404 and / or network entity 402 to perform or direct, for example, when executed by one or more corresponding processors of network entity 402 and / or network entity 404 (e.g., direct execution, or execution after compilation, transformation, and / or interpretation). Figure 11 Process 1100 Figure 12 The operation of process 1200 and / or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions and / or interpret instructions, etc.

[0104] In some aspects, the first network entity (e.g., network entity 402 or network entity 404) includes components for receiving from the second network entity an indication of a first frequency offset associated with the second network entity; components for receiving from the second network entity a first transmission, the first transmission including a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset; and / or components for decoding the first transmission via envelope tracking to obtain the first communication from the first transmission. In some aspects, components for the first network entity to perform the operations described herein may include, for example, one or more of the following: a communication manager 460, a transmit processor 410, a TX MIMO processor 414, a modem 416, an antenna 406, a MIMO detector 444, a receive processor 446, a controller / processor 450, a memory 456, a scheduler 454, a communication interface 112, a communication interface 116, and / or a communication interface 230, etc. In some aspects, components for enabling the first network entity to perform the operations described herein may include one or more of, for example, a communication manager 458, an antenna 408, a modem 418, a MIMO detector 420, a receive processor 422, a transmit processor 436, a TX MIMO processor 440, a controller / processor 426, a memory 442, a communication interface 112, a communication interface 116, and / or a communication interface 230, etc.

[0105] In some aspects, a first network entity (e.g., network entity 402 or network entity 404) includes components for communicating with a second network entity to negotiate a first frequency offset and a first frequency domain positioning for communications associated with the first network entity, and a second frequency offset and a second frequency domain positioning for communications associated with the second network entity; components for sending an indication of the first frequency offset to a third network entity; and / or components for sending transmissions including communications and auxiliary signals separated in the frequency domain by the first frequency offset, the communications being associated with frequency domain resources in the first frequency domain positioning. In some aspects, components for enabling the first network entity to perform the operations described herein may include, for example, one or more of the following: a communications manager 460, a transmit processor 410, a TX MIMO processor 414, a modem 416, an antenna 406, a MIMO detector 444, a receive processor 446, a controller / processor 450, a memory 456, a scheduler 454, a communications interface 112, a communications interface 116, and / or a communications interface 230, etc. In some aspects, components for enabling the first network entity to perform the operations described herein may include one or more of, for example, a communication manager 458, an antenna 408, a modem 418, a MIMO detector 420, a receive processor 422, a transmit processor 436, a TX MIMO processor 440, a controller / processor 426, a memory 442, a communication interface 112, a communication interface 116, and / or a communication interface 230, etc.

[0106] Although Figure 4 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 436, receive processor 422, and / or TX MIMO processor 440 may be performed by or under the control of controller / processor 426. Figure 4 Any number of other combinations of the various combinations of components described herein may be considered within the scope of this disclosure.

[0107] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0108] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functions can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0109] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network entities. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0110] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0111] As used herein, "outputting" or "transmitting" communication from a first network entity to a second network entity can refer to direct transmission (e.g., from the first network entity to the second network entity) or indirect transmission via one or more other network entities or devices. For example, if the first network entity is a DU, indirect transmission to the second network entity can include the DU outputting or transmitting communication to an RU and the RU transmitting communication to the second network entity, or it can include causing the RU to transmit communication (e.g., triggering the transmission of a physical layer reference signal). Similarly, "transmitting" communication from a second network entity to a first network entity can refer to direct transmission (e.g., from the second network entity to the first network entity) or indirect transmission via one or more other network entities or devices. For example, if the first network entity is a DU, indirect transmission to the first network entity can include the second network entity transmitting communication to an RU and the RU transmitting communication to the DU. Similarly, "receiving" communication by a first network entity can refer to directly receiving a transmission carrying communication (e.g., from the second network entity to the first network entity) or receiving communication (or information deduced from the reception of communication) via one or more other network entities or devices.

[0112] Figure 5This is a diagram illustrating an example disaggregated base station architecture 500 according to this disclosure. The disaggregated base station architecture 500 may include a CU 510, which may communicate directly with the core network 520 via a backhaul link, or indirectly with the core network 520 via one or more disaggregated control units (such as a near-RT RIC 525 via an E2 link, or a non-RT RIC 515 associated with a Service Management and Orchestration (SMO) framework 505, or both). The CU 510 may communicate with one or more DUs 530 via a corresponding midhaul link (such as via an F1 interface). Each DU 530 may communicate with one or more RUs 540 via a corresponding fronthaul link. Each RU 540 may communicate with one or more UEs 320 via a corresponding RF access link. In some implementations, a UE 320 may be served simultaneously by multiple RUs 540.

[0113] Each unit in the clusters (including CU 510, DU 530, RU 540), as well as the near-RT RIC 525, non-RT RIC 515, and SMO frame 505, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cluster, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other clusters via transmission media. In some examples, each unit in the cluster may include a wired interface and a wireless interface configured to receive signals via a wired transmission media or transmit signals to one or more units in other clusters, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals via a wireless transmission media or transmit signals to one or more units in other clusters, or both.

[0114] In some aspects, the CU 510 can host one or more higher-level control functions. Such control functions may include RRC functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions managed by the CU 510. The CU 510 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 510 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 510 can be implemented to communicate with the DU530 for network control and signaling purposes, as needed.

[0115] Each DU 530 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 540s. In some aspects, the DU 530 may, at least in part, host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, depending on functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 530 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 530 or with control functions hosted by the CU 510.

[0116] Each RU 540 can implement lower-layer functionality. In some deployments, an RU 540 controlled by a DU 530 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splits (e.g., function splits defined by 3GPP) (such as lower-layer function splits). In such architectures, each RU 540 can be operated to handle over-the-air (OTA) communications with one or more UEs 320. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 540 can be controlled by the corresponding DU 530. In some scenarios, this configuration allows each DU 530 and CU 510 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0117] The SMO framework 505 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 505 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 505 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 590 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 510, DU 530, RU 540, non-RT RIC 515, and near-RT RIC 525. In some specific implementations, the SMO framework 505 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 511) via the O1 interface. Additionally, in some implementations, the SMO framework 505 can communicate directly with each of one or more RUs 540 via a corresponding O1 interface. The SMO framework 505 may also include a non-RTRIC 515 configured to support the functionality of the SMO framework 505.

[0118] The non-RT RIC 515 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 525. The non-RT RIC 515 can be coupled to or communicate with the near-RT RIC 525, such as via an A1 interface. The near-RT RIC 525 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 510s, one or more DU 530s, or both, and O-eNBs to the near-RT RIC 525.

[0119] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 525, the non-RT RIC 515 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 525 and may be received from non-network data sources or network functions at the SMO framework 505 or the non-RT RIC 515. In some examples, the non-RT RIC 515 or near-RT RIC 525 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 515 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the creation of the SMO framework 505 (such as reconfiguration via the O1 interface) or via RAN management policies (such as A1 interface policies).

[0120] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0121] Figure 6 This is a diagram illustrating example 600 associated with backscatter communication according to this disclosure.

[0122] Some network entities can be considered Internet of Things (IoT) devices, such as environmental IoT devices (sometimes referred to as ultralight IoT devices) or similar IoT devices. IoT technologies can include passive IoT (e.g., NR passive IoT for 5G advanced), semi-passive IoT, ultralight IoT, or environmental IoT, etc. In passive IoT, the terminal (e.g., RFID device, tag, or similar device) may not include a battery, and the terminal can accumulate energy from RF signaling. Additionally, the terminal can accumulate solar energy to supplement the accumulated energy from radio signaling. In passive IoT, the communication distance can be up to 30 meters (or longer) to facilitate feasible network coverage of large areas (e.g., 5000 square meters) such as in a warehouse. Furthermore, the power consumption of passive IoT terminals can be less than 0.1 milliwatts (mW) to support battery-free operation, and the terminals can be relatively inexpensive to facilitate cost-sensitive uses. The positioning accuracy of passive IoT terminals can be approximately 3 to 5 meters in both the horizontal and vertical directions.

[0123] Passive IoT combined with industrial sensors can be useful, for which battery replacement can be very difficult or undesirable (e.g., for security monitoring or fault detection in smart factories, infrastructure, or environments). Additionally, the characteristics of passive IoT devices, such as low cost, small size, maintenance-free operation, durability, and long lifespan, can facilitate smart logistics / warehousing (e.g., combined with automated asset management via RFID tag replacement). Furthermore, passive IoT can be combined with smart home networks for home appliance management, wearable devices (e.g., wearables for medical monitoring of patients that do not require battery replacement), and / or environmental monitoring. To achieve further cost reductions and zero-power communication, 5G and / or 6G wireless networks can utilize a type of passive IoT device known as an "ambient backscatter device" or "backscatter device."

[0124] Network entity 605 includes devices (e.g., tags, sensors, passive devices such as passive IoT devices, semi-passive devices, active devices, UEs, etc.) that are powered at least partially by receiving RF signals (e.g., from transmitter 610). In some examples, network entity 605 may be network entity 102, network entity 104, network entity 106, device 200, UE 320, network entity 402, and / or network entity 404. In some examples, network entity 605 may employ a simplified hardware design (e.g., including a power divider, energy harvester, and microcontroller) that does not include a battery and / or oscillator, allowing network entity 605 to be powered by energy harvesting, and that does not include radio wave generation circuitry, enabling network entity 605 to transmit information solely by reflecting radio waves. In some examples, network entity 605 may include a battery, capacitor, or another form of energy storage device. In some examples, network entity 605 may include a communication module, such as a Bluetooth Low Energy (BLE) module, a WiFi module, etc. The communication module may be at least partially powered by RF signals transmitted by transmitter 610, enabling network entity 605 to communicate with transmitter 610 or another device using a communication module powered by RF signals. In some examples, network entity 605 may include a radio wave generation circuit that can be powered by receiving RF signals and / or by the energy storage of network entity 605. Transmitter 610 may be network entity 102, network entity 104, network entity 106, device 200, UE 320, network node 310, network entity 402, and / or network entity 404.

[0125] In some examples, network entity 605 can communicate with reader 608 (e.g., which may include a UE, network node, base station, or other network device) by modulating reflected radio signals from transmitter 610 (referred to herein as a transmitter (e.g., a network node or another network device)). In some examples, transmitter 610 and reader 608 may be the same device and / or co-located. In some examples, transmitter may be referred to as exciter. In some examples, network entity 605 may not communicate with reader 608. For example, network entity 605 may communicate with another device (e.g., transmitter 610, RF energy harvesting device, or another network node). Reader 608 may be optional.

[0126] To facilitate communication with network entity 605, transmitter 610 may transmit an RF signal (e.g., an energy harvesting wave) to network entity 605. When facilitating communication with reader 608, the energy harvesting wave may be transmitted for a sufficient duration to achieve a communication phase within a target range between reader 608 and network entity 605. Additionally or alternatively, in some cases, the range between transmitter 610 and network entity 605 may be limited by a minimum received power (such as -20 dBm) required to trigger energy harvesting at network entity 605.

[0127] Once sufficient energy has been accumulated at network entity 605, network entity 605 can initiate communication or store energy. As an example, network entity 605 can reflect radio waves radiated onto itself via backscatter link 615. For instance, transmitter 610 can initiate a communication session with a query (sometimes referred to as query-response communication), which can be a modulated envelope of continuous wave (CW). Network entity 605 can respond via backscattering of the CW. The communication session can include multiple rounds, such as for contention resolution purposes when multiple backscattering devices respond to a query. The channel between transmitter 610 and network entity 605 via backscatter link 615 can be correlated with a first backscatter link channel response value (sometimes referred to as a first backscatter link channel coefficient or a first backscatter link gain value). h BD Associated with, as described below, network entity 605 may have a reflection on and reflection off period that follows at least in part based on the pattern of information bits transmitted by network entity 605. Reader 608 may detect the reflection pattern of network entity 605 and obtain backscatter communication information via backscatter link 615. The channel between reader 608 and network entity 605 of backscatter link 615 may be correlated with a second backscatter link channel response value (sometimes referred to as the second backscatter link channel coefficient or second backscatter link channel gain value). h DU Associated with each other. Furthermore, transmitter 610 and reader 608 may communicate (e.g., reference signals and / or data signals) via direct link 620. The channel between transmitter 610 and reader 608 on direct link 620 may be correlated with direct link channel response values ​​(sometimes referred to as direct link channel coefficients or direct link channel gain values). h BU Related. In some examples, network entity 605 may use the received energy to power active transmission (e.g., using an amplifier) ​​or other operations.

[0128] In some examples, transmitter 610 may include a power source (e.g., a portable power source, such as a battery or hardwired power supply). Transmitter 610 may include transmitting components, such as an RF chain including a power amplifier and one or more antennas. In some examples, the one or more antennas may be capable of some degree of beamforming (either based on a hardware configuration of the antenna array or via a dynamic beamforming method such as analog or digital beamforming) such that the RF signal transmitted by transmitter 610 is directed to a coverage area (e.g., an area such as a portion of a sphere, an azimuth angle, etc.) in which network entity 605 may be excited by the RF signal. In some examples, transmitter 610 may include one or more sensors, such as RF sensors, light sensors, motion sensors, etc. In some examples, transmitter 610 may be associated with (e.g., including, connected to, or communicating with) a BLE module, which is a module capable of transmitting and / or receiving BLE signaling (such as BLE communication). In some examples, the BLE module may include an RF sensor. As shown in the figure, transmitter 610 may include one or more processors that can perform the operations described herein, or be configured to perform the operations described herein.

[0129] If backscatter communication is performed, network entity 605 can use an information modulation scheme, such as amplitude shift keying (ASK) modulation, phase shift keying (PSK) modulation, or on / off keying (OOK) modulation. For the information modulation scheme, network entity 605 can enable reflection when transmitting an information bit "1" and disable reflection when transmitting an information bit "0". In backscatter communication, transmitter 610 can transmit specific radio waves (e.g., reference signals or data signals, such as the Physical Downlink Shared Channel (PDSCH)) (which can be represented as...). The reader 608 can receive the radio waves directly from the transmitter 610 via a direct link 620, and from the network entity 605 that modulates and reflects the radio waves to the reader 608 via a backscatter link 615. The signal received at reader 608 via direct link 620 (represented as...) (and indicated by reference numeral 625) are radio waves transmitted by transmitter 610. Multiply by the direct link channel response value h BU The product of the product and any signal noise. The information bit signal of network entity 605 can be represented as... ,in Therefore, the signal received at reader 608 via backscatter link 615 (denoted as...) (and indicated by reference numeral 630) is a signal transmitted by transmitter 610. Multiply by the first backscatter link channel response value h BD Second backscatter link channel response value h DU Information bit signal from network entity 605 and the reflection coefficient associated with network entity 605 The product plus any noise.

[0130] Therefore, if backscatter communication is performed, the signal received at reader 608 (which is the superposition of the signal received via direct link 620 and the signal received via backscatter link 615) can be represented as: ,in This signal As shown by reference numeral 635 in the attached figure. As illustrated, when (As indicated by reference numeral 640 in the graph shown at reference numeral 630) when network entity 605 can turn off reflection, such that the signal components It equals zero, and therefore reader 608 only receives signals from direct link 620 (e.g., ).when (As indicated by reference numeral 645 in the graph shown at reference numeral 630) when network entity 605 can enable reflection, such that the signal components equal Therefore, reader 608 receives the superposition of the direct link 620 signal and the backscatter link 615 signal (e.g., In order to receive information bits sent by network entity 605, reader 608 may first treat the backscattered link 615 signal as interference, at least in part based on the direct link channel response value. To decode Then, reader 608 can access the data from... minus To detect signal components The existence of [something]. In some cases, apart from the contents stored in the memory of network entity 605 (such as the electronic product code (EPC) or similar information associated with network entity 605), network entity 605 may not maintain the state from communication session to communication session.

[0131] Network entity 605 can detect or decode radio waves (e.g., reference signals or data signals, such as PDSCH) transmitted by transmitter 610. Network entity 605 can detect or decode radio waves via envelope tracker 650. Envelope tracker 650 can be a component or module of network entity 605 associated with decoding wireless signals via envelope tracking. As used herein, the “envelope” of a signal can refer to the amplitude or magnitude of the signal, since the amplitude or magnitude varies over time. The envelope can be a function of modulation applied to the signal. The envelope can be represented as a waveform that captures the change in signal amplitude over time. When a modulation scheme is applied to the signal, the envelope of the signal varies according to the modulated waveform. Envelope tracking can be used as a technique for detecting and extracting modulated signals in a wireless communication system. For example, envelope tracking can be used by network entity 605 as a form of signal demodulation, which can recover the baseband signal from the modulated RF signal, as described in more detail elsewhere herein.

[0132] Some IoT devices can be referred to as semi-passive IoT devices because communication between the reader and the IoT device does not require an energy harvesting waveform as a precondition. For example, a semi-passive IoT device may include a battery or similar energy source that can power the receiver and / or logic circuitry. For such devices, energy harvesting can still be triggered in some cases, such as for long-range communication. In such examples, the rectifier circuitry of the IoT device may have a hot start from a battery or other energy source and can therefore be associated with a lower minimum receive power requirement than that of a passive IoT device (e.g., -30dBm instead of -20dBm). However, long-range communication may require battery power consumption to incentivize each decoding. More specifically, for long-range communication where the energy harvesting rate is lower than required by the decoding circuitry, such as when the energy harvesting rate is below -30dBm, a semi-passive IoT device may consume battery power to incentivize each decoding. Therefore, continuous IoT device monitoring (such as for receiving long-range query communications) can lead to excessive battery consumption at the IoT device.

[0133] In this respect, passive and semi-passive IoT devices can inherently limit their applications. For example, passive IoT devices can be associated with low cost and low form factor because no RF chain is required at the IoT device level. However, these devices require an energy harvesting waveform, thus limiting the application of such passive IoT devices to short-range communication. While semi-passive IoT devices can eliminate the need for an energy harvesting waveform and / or enable long-range communication, such devices increase cost and complexity because they require the use of batteries or similar power sources. Furthermore, because passive and semi-passive devices can be associated with communication sessions initiated by RF sources, these devices may inherently limit their use in sensing scenarios or similar latency-critical applications requiring non-periodic business, and these devices may not scale well for high IoT density applications.

[0134] In some cases, ambient IoT devices (sometimes called ultralight IoT devices) can be employed to overcome some of the limitations of passive and semi-passive IoT devices. Ambient IoT devices can be devices capable of transmitting uplink triggers and thus initiating communication sessions from the IoT device side. For example, an ambient IoT device may be associated with uplink transmissions that do not utilize a PA (e.g., transmissions in the 0dBm to 5dBm range), and for such uplink transmissions, there are limited transmission capabilities, such as the ability to simply send a preamble to indicate uplink traffic. Ambient IoT devices, passive devices, and semi-passive devices are referred to herein as RF energy harvesting devices (although RF energy harvesting devices may include another form of device capable of harvesting RF energy from RF signals to power the operation of the device).

[0135] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0136] Figure 7 This is a diagram illustrating example 700 associated with envelope tracking according to this disclosure. (Combined) Figure 7 The operations described and depicted can be performed by network nodes such as network entity 605, network entity 102, network entity 104, network entity 106, device 200, UE 320, network entity 402 and / or network entity 404, etc. In some examples, network entities can be tags associated with reduced RF capabilities (e.g., RFID tags), sensors, passive devices, passive IoT devices, semi-passive devices, active devices, RedCap network nodes, low-level network nodes, NR-Lite network nodes, and / or UEs, etc. For example, network entities may not include active RF components such as oscillators, power amplifiers, low-noise amplifiers, mixers, and / or other RF components.

[0137] Envelope tracking can be used by network entities to decode wireless signals. For example, envelope tracking can be used as a technique for detecting and extracting modulated signals. Envelope tracking can also be used by network entities as a form of signal demodulation, which can recover the baseband signal from the modulated RF signal. For example, a network entity can receive a received voltage (V) with time. R The signal 705. For example, the amplitude of the signal may vary over time, such as... Figure 7 As shown.

[0138] A network entity may provide a signal (or information associated with the signal) to an envelope detector 710 (e.g., which may resemble an envelope tracker 650). The envelope detector 710 may be configured to detect the envelope 715 associated with the signal 705. In some examples, the envelope detector 710 may be configured to detect the upper envelope of the signal 705. The upper envelope may be a waveform indicating the upper limit of the amplitude of the signal 705 over time. For example, the envelope of the signal 705 may be derived from... Figure 7 The bold waveform shown is illustrated. Envelope 715 can be associated with an envelope voltage (V) indicating the voltage across envelope 715 over time. E (related to)

[0139] The network entity can provide the envelope 715 and / or envelope voltage (V) to the low-pass filter 720. E The low-pass filter 720 can be associated with a filtering frequency above a frequency threshold. For example, the low-pass filter 720 can allow signals with lower frequencies to pass through while blocking signals with higher frequencies (e.g., above a frequency threshold). The network entity can provide the low-pass filter 720 with an envelope 715 and / or an envelope voltage (V). E The baseband signal associated with signal 705 is extracted. Low-pass filter 720 removes high-frequency components of signal 705, leaving only the filtered signal 725 at the output of low-pass filter 720. Then, as described herein, the voltage (V) with time can be further processed. LP The filtered signal 725.

[0140] For example, a network entity can provide comparator 730 with a voltage (V) that varies with time. LP The filtered signal 725. Comparator 730 can be configured to determine the voltage (V) of a signal at a given time. O This is a component that will be associated with either "1" or "0" (e.g., for the information bits of signal 705). For example, comparator 730 can compare the voltage of filtered signal 725 to one or more thresholds. As an example, if the voltage value at a given time meets a threshold, comparator 730 can determine that filtered signal 725 is associated with "1" at that time. If the voltage value at a given time does not meet a threshold, comparator 730 can determine that filtered signal 725 is associated with "0" at that time. Comparator 730 can provide a voltage (V O The output 735 indicates a "1" or "0" for the corresponding information bit of signal 705.

[0141] like Figure 7As shown, a network entity can decode information bits (e.g., a series of "1"s and / or "0"s) based on the output of comparator 730. For example, for a time window (e.g., a given amount of time), the network entity can determine whether the comparator's output 735 indicates "0" or "1". The network entity can determine, based on the output 735 of comparator 730, according to that output, or otherwise associated with that output (e.g., associated with a time window), whether a bit is associated with "0" or "1". Therefore, the decoding operation performed by the network entity can be simplified and / or associated with reduced complexity. For example, it enables the network entity to obtain the value of the information bits of signal 705 without using one or more active RF components. Additionally, it enables the network entity to obtain the value of the information bits of signal 705 without downconverting signal 705 to a baseband signal. As another example, envelope tracking decoding operation enables the network entity to obtain the value of the information bits of signal 705 without performing carrier frequency offset and / or frequency synchronization.

[0142] However, in some cases, more than one transmitter may send signals toward a network entity in a spatial direction at a given time. For example, a first transmitter may send a first signal (s1) toward a network node. The first signal may be a signal intended for use by the network node. Another transmitter may send a second signal (s2) toward the network node in a spatial direction, causing the network entity to receive the second signal. The second signal may or may not be intended for use by the network node. The first and second signals may at least partially overlap in the time domain. For example, the second signal may interfere with the first signal, causing the amplitude of the signal received at the network entity to differ from the amplitude of the first signal. Therefore, the second signal may affect or modify the envelope of the first signal, preventing the network entity from accurately decoding the first signal using the envelope tracking decoding operation described herein.

[0143] For example, the first signal can be represented as ,in It is necessary to be in time t The data (e.g., information bits) conveyed for the first signal, and This is the frequency associated with the first signal. The second signal can be represented as... ,in It is necessary to be in time t The data (e.g., information bits) conveyed for the second signal, and It is the frequency associated with the second signal. The signal received at the network entity can be the sum of the first and second signals, such as... The envelope of the received signal can be associated with the square of the received signal. For example, the envelope of the received signal can be represented as... After removing the higher frequency terms of the envelope (e.g., after performing a low-pass filter), the DC voltage of the envelope can be expressed as: Furthermore, the low-frequency term of the envelope can be expressed as Because the DC voltage of the received signal (e.g., the DC term of the envelope) is the sum of the data transmitted via the first and second signals, the network entity may be unable to use envelope tracking to extract or recover the individual signals (e.g., because the envelope includes terms that are the sum of the data transmitted via the first and second signals). Therefore, the communication performance and / or decoding performance associated with the network entity may be degraded because the network entity may incorrectly use envelope tracking to decode a signal when it receives one or more other signals at a time that at least partially overlaps with the time when the signal is received by the network node.

[0144] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0145] Figure 8 This is a diagram illustrating an example of an operation 800 associated with envelope tracking based on auxiliary signals, according to this disclosure. Figure 8 As shown, the first network entity 805, the second network entity 810, and the third network entity 815 can communicate with each other. In some aspects, the first network entity 805, the second network entity 810, and the third network entity 815 can be part of a wireless network (e.g., wireless network 300). The first network entity 805 and / or the second network entity 810 can be network entity 102, network entity 104, network entity 106, device 200, network node 310, UE 320, network entity 402, network entity 404, transmitter 610, base station, CU, DU, and / or RU, etc. The third network entity 815 may be network entity 102, network entity 104, network entity 106, device 200, network node 310, UE 320, network entity 402, network entity 404, network entity 605, tag (e.g., RFID tag), sensor, passive device, passive IoT device, semi-passive device, RedCap network node, low-level network node and / or NR-Lite network node, etc.

[0146] As indicated by reference numeral 820 in the accompanying drawings, the first network entity 805 and the second network entity 810 may negotiate frequency domain allocations for data and auxiliary signals. In some aspects, the first network entity 805 and the second network entity 810 may negotiate frequency domain allocations for data and auxiliary signals used for communication intended for use with network nodes or devices performing envelope tracing decoding (such as the third network entity 815) or otherwise associated with such network nodes or devices (e.g., in conjunction with...) Figure 7 (Similar to the described manner). Communication (e.g., including data and auxiliary signals) can be downlink data communication. In some aspects, communication can be IoT communication (e.g., transmitted via IoT channels).

[0147] First network entity 805 and second network entity 810 may communicate one or more signals or information to determine a first frequency offset, a first frequency domain location, a second frequency offset, and / or a second frequency domain location, etc. For example, first network entity 805 may send and second network entity 810 may receive information associated with negotiating the first frequency offset, the first frequency domain location, the second frequency offset, and / or the second frequency domain location, etc. Additionally or alternatively, second network entity 810 may send and first network entity 805 may receive information associated with negotiating the first frequency offset, the first frequency domain location, the second frequency offset, and / or the second frequency domain location, etc.

[0148] In some other respects, another network entity ( Figure 8 (Not shown) (such as a control entity or CU) can determine the frequency domain allocation for data and auxiliary signals (e.g., in a manner similar to that described herein). In such an example, another network entity can send and a first network entity 805 and a second network entity 810 can receive instructions on the frequency domain allocation for data and auxiliary signals.

[0149] In some aspects, the first network entity 805 and / or the second network entity 810 may determine the frequency domain allocation for data and auxiliary signals based on one or more conditions. One or more conditions may be associated with mitigating interference (e.g., between communications transmitted via different network nodes, such as the first network entity 805 and the second network entity 810). For example, one or more conditions may ensure that the third network entity 815 is able to isolate the intended signal from interference caused by simultaneous transmission by the first network entity 805 and the second network entity 810 (e.g., towards the third network entity 815 in a spatial direction), as described in more detail elsewhere herein. In some aspects, one or more conditions may be associated with the bandwidth of the channel used to transmit the communication (e.g., an IoT channel or an environmental IoT channel). For example, the conditions may be defined relative to the bandwidth of the channel. In some aspects, the bandwidth of the channel may be the bandwidth (or a portion of the bandwidth) associated with the communication.

[0150] In some aspects, one or more conditions may be associated with the amount or quantity of frequency domain resources between the frequency domain locations of the data transmitted by the first network entity 805 and the second network entity 810. For example, the conditions may be... ,in It is the frequency domain location of the data to be sent by the second network entity 810. It is the frequency domain location of the data to be sent by the first network entity 805. It is the frequency offset associated with the first network entity 805 (e.g., between data and auxiliary signals). It is the frequency offset associated with the second network entity 810 (e.g., between data and auxiliary signals), and This refers to the bandwidth of the channel (e.g., an IoT channel) or the bandwidth of the data being transmitted. More generally, it refers to the bandwidth of data transmitted via the channel. m A network node, the condition can be .

[0151] Additionally or alternatively, conditions may be defined for determining the values ​​of corresponding frequency offsets of network nodes transmitting via a channel (e.g., via an IoT channel). For example, the conditions for a given network entity may be based on the channel bandwidth and the frequency offset of another network node, or otherwise associated with the channel bandwidth and the frequency offset of another network node. As an example, the conditions could be... More generally, for transmissions via a channel... m A network node, the condition can be The conditions described herein ensure that interference generated as a result of transmissions (e.g., including data and auxiliary signals) from the respective network nodes via the channel occurs in a frequency domain location that does not overlap with the data (e.g., in the frequency domain) and / or enables the third network entity 815 to filter out or otherwise remove the interference (e.g., via a low-pass filter).

[0152] Communication (which includes data and auxiliary signals) can be transmitted via channels such as IoT channels. An IoT channel can be a channel associated with communication between devices in an IoT network.

[0153] In some respects, the first network entity 805 and the second network entity 810 may exchange communications indicating corresponding frequency domain allocations for data and auxiliary signals. For example, the first network entity 805 and the second network entity 810 may communicate to negotiate a first frequency offset for communications associated with the first network entity 805. ) and first frequency domain positioning ( ) and a second frequency offset for communication associated with the second network entity 810 ( ) ) and second frequency domain positioning ( For example, the first frequency offset can be an offset between data (e.g., transmitted at a first frequency domain location) and an auxiliary signal transmitted by the first network entity 805 (e.g., in the frequency domain). The second frequency offset can be an offset between data (e.g., transmitted at a second frequency domain location) and an auxiliary signal transmitted by the second network entity 810 (e.g., in the frequency domain).

[0154] As an example, the first network entity 805 can send and the second network entity 810 can receive a first frequency offset ( ) and first frequency domain positioning ( The first network entity 805 may determine the first frequency offset based on the bandwidth of the channel or otherwise associated with the bandwidth of the channel. The value of ). For example, the first network entity 805 can determine the first frequency offset ( The value of ) is greater than or equal to the bandwidth of the channel. The second network entity 810 may determine the second frequency offset based on one or more conditions, according to one or more conditions, or otherwise associated with one or more conditions. ) and second frequency domain positioning ( For example, the second network entity 810 can be based on the first frequency offset ( ), first frequency domain positioning ( The second frequency offset is calculated in association with one or more conditions or otherwise related to the first frequency offset, the first frequency domain location, and one or more conditions. ) and second frequency domain positioning ( The second network entity 810 can send and the first network entity 805 can receive the second frequency offset. ) and second frequency domain positioning ( (instructions).

[0155] In other respects, another network entity (e.g., CU) can transmit and the first network entity 805 can receive a first frequency offset ( ) and first frequency domain positioning ( Instructions for a second frequency offset ( ). Another network entity may send and a second network entity 810 may receive instructions for a second frequency offset ( ). ) and second frequency domain positioning ( The instructions are as follows. In such examples, another network entity can determine the frequency offset and frequency domain location in a similar manner to that described herein.

[0156] As an example, the channel bandwidth could be 180 kHz. The first network entity 805 can determine that the first frequency offset is 180 kHz. The second network entity 810 can determine that the second frequency offset is a value greater than 360 kHz (e.g., Additionally, the second network entity 810 can determine whether the second frequency domain positioning satisfies... (Assuming the second frequency offset is 360kHz) value.

[0157] In some respects, the first network entity 805 and / or the second network entity 810 may determine or select the first frequency offset based on, according to, or otherwise associated with the capabilities of the third network entity 815. ) and second frequency offset ( The value of ). For example, as described in more detail elsewhere herein, a third network entity 815 may send a capability report indicating one or more supporting values ​​for the frequency offset used by other network nodes. A first network entity 805 and / or a second network entity 810 may determine or select a first frequency offset () from one or more supporting values ​​of the frequency offset indicated by the third network entity 815. ) and second frequency offset ( The value of ).

[0158] In some respects, the first network entity 805 and / or the second network entity 810 may determine or select a first frequency offset based on, according to, or otherwise associated with the size or bandwidth of a downlink data channel (such as PDSCH). ) and second frequency offset ( The value of ). For example, the bandwidth of PDSCH can be H A resource block (RB). The first network entity 805 and / or the second network entity 810 can determine or select a first frequency offset ( ) and second frequency offset ( The value of ) is greater than or equal to H One RB. This allows the third network entity 815 to mitigate interference caused by transmissions via PDSCH.

[0159] As indicated by reference numeral 825 in the accompanying drawings, a third network entity 815 can send a capability report, and a first network entity 805 (and / or a second network entity 810) can receive it. The third network entity 815 can send the capability report via UE capability signaling, UE Assistance Information (UAI) communication, RRC communication, Physical Uplink Shared Channel (PUSCH) and / or Physical Uplink Control Channel (PUCCH), etc. The capability report can indicate support for one or more operations described herein. For example, the capability report can indicate whether the third network entity 815 supports envelope tracking-based decoding for modulated signals (e.g., as in combination with...). Figure 7 (Described envelope tracking). The capability report may indicate whether the third network entity 815 supports envelope tracking decoding based on auxiliary signals (or auxiliary tones), as described in more detail elsewhere herein. In some aspects, the capability report may indicate one or more frequency offsets supported by the third network entity 815. For example, the capability report may indicate one or more supported values ​​of frequency offsets associated with envelope tracking decoding based on auxiliary signals (or auxiliary tones), as described in more detail elsewhere herein.

[0160] First network entity 805 and / or second network entity 810 (or another network node) may configure third network entity 815 based on a capability report. For example, network node 805 may configure or trigger third network entity 815 to perform one or more operations based on, in response to, or otherwise associated with a capability report, a capability report instructing third network entity 815 to support one or more operations. As an example, first network entity 805 may configure or trigger third network entity 815 to perform envelope tracking decoding based on auxiliary signals based on a capability report instructing third network entity 815 to support envelope tracking decoding based on auxiliary signals, in response to, or otherwise associated with a capability report. As another example, first network entity 805 may determine or select a value of frequency offset to be used by first network entity 805 based on, in response to, a capability report instructing third network entity 815 to support a value of frequency offset for envelope tracking decoding based on auxiliary signals, in response to, or otherwise associated with a capability report.

[0161] As indicated by reference numeral 830 in the accompanying drawings, a first network entity 805 may transmit and a third network entity 815 may receive an indication of a frequency offset associated with the transmission from the first network entity 805 (e.g., for a first frequency offset). The first frequency offset can be an indication of the value of the signal to be transmitted by the first network entity 805 (e.g., the signal to be transmitted by the first network entity 805 may include communication and auxiliary signals separated in the frequency domain based on the first frequency offset). In some aspects, the indication of the first frequency offset can be first information, and the first frequency offset can be second information. For example, the first information can be a first value, and the second information can be a second value, wherein the first value indicates the second value. As another example, the indication of the first frequency offset may include information indicating the value of the first frequency offset. As another example, the indication of the first frequency offset may include the value of the first frequency offset. For example, the first network entity 805 may transmit and the third network entity 815 may receive an indication of the amount (e.g., in kHz or RB) of frequency domain resources between data and auxiliary signals transmitted by the first network entity 805 (e.g., via an IoT channel). The frequency offset may indicate that the first network entity 805 wants to transmit a signal or transmission that includes communication (e.g., data communication or control communication) and auxiliary signals separated in the frequency domain by the frequency offset.

[0162] A first network entity 805 may send, and a third network entity 815 may receive, an indication of a first frequency offset via configuration information. In some aspects, the indication of the frequency offset may be included in broadcast communications. For example, the first network entity 805 may broadcast information indicating the value of the first frequency offset to be used by the first network entity 805. In some aspects, the indication of the first frequency offset may be included in system information communications (e.g., in a System Information Block (SIB) or Master Information Block (MIB)). As another example, the indication of the first frequency offset may be included in another communication (such as RRC communication). In some aspects, the indication of the first frequency offset may be included in broadcast communications.

[0163] The third network entity 815 can receive and decode an indication of the frequency offset associated with the first network entity 805. The third network entity 815 can communicate based on the frequency offset associated with the first network entity 805. (or otherwise configure itself in association with a frequency offset. For example, the third network entity 815 can use a frequency offset ( The value of ) is used to configure the decoder or decoding component of the third network entity 815 so that the third network entity 815 can decode the transmitted or signaled from the first network entity 805, as described in more detail elsewhere in this document.

[0164] In some respects, as indicated by reference numeral 835, the second network entity 810 may transmit and the third network entity 815 may receive an indication of a second frequency offset associated with the transmission from the second network entity 810 (e.g., for the second frequency offset ( The second frequency offset can be an indication of the value of the second frequency offset. For example, the second network entity 810 may use the second network entity 810 for signals transmitted by the second network entity 810 (e.g., the signals to be transmitted by the second network entity 810 may include communication and auxiliary signals separated in the frequency domain based on the second frequency offset). In some aspects, the indication of the second frequency offset may be first information, and the first frequency offset may be second information. For example, the first information may be a first value, and the second information may be a second value, wherein the first value indicates the second value. As another example, the indication of the second frequency offset may include information indicating the value of the second frequency offset. As another example, the indication of the second frequency offset may include the value of the second frequency offset. The second network entity 810 may transmit the indication of the second frequency offset in a manner similar to that described in conjunction with the first network entity 805. For example, the third network entity 815 may receive indications of the corresponding frequency offsets of transmitters (e.g., the first network entity 805 and the second network entity 810) in or near the geographical area surrounding the third network entity 815. This enables the third network entity 815 to isolate signals transmitted by a particular network entity when multiple network nodes transmit simultaneously (e.g., at times that at least partially overlap in the time domain) in a geographical area around or near the third network entity 815 (e.g., by performing envelope tracking decoding using a frequency offset associated with a particular network node).

[0165] As described elsewhere in this document, an auxiliary signal can be a single tone. A tone can also be referred to as a subcarrier or a resource element (RE). For example, time-frequency resources in a radio access network can be divided into resource blocks (RBs). An RB can include a set of subcarriers (e.g., 12 subcarriers) and a set of symbols (e.g., 14 symbols). In some aspects, an RB can include a set of subcarriers in a single time slot. A single time-frequency resource included in an RB can be referred to as an RE. An RE can include a single subcarrier (e.g., in frequency) and a single symbol (e.g., in time). A symbol can be referred to as an OFDM symbol. An RE can be used to transmit a modulation symbol, which can be a real value or a complex value. An auxiliary signal can occupy a single tone (e.g., a single subcarrier) and can have a fixed or known value or amplitude. In some aspects, an auxiliary signal can be or can occupy a single RE. In some aspects, an auxiliary signal can be associated with a fixed frequency.

[0166] As shown by reference numeral 840 in the accompanying drawings, a first network entity 805 can transmit and a third network entity 815 can receive a first signal, which includes data and auxiliary signals separated based on a first frequency offset or otherwise associated with the first frequency offset (e.g., separated by the first frequency offset or separated by a frequency value separated based on the first frequency offset or otherwise associated with the first frequency offset). The first signal can be a modulated signal. For example, the first network entity 805 can modulate the first signal using ASK modulation, PSK modulation, or OOK modulation, etc. For example, transmission from the first network entity 805 may include communication (e.g., data communication or control communication) and auxiliary signals. The communication and auxiliary signals may be offset in the frequency domain by the first frequency ( The communication may occupy one or more subcarriers and / or REs. The first network entity 805 may transmit a first signal (e.g., a modulated signal including communication and auxiliary signals) via a channel associated with IoT (e.g., an IoT channel).

[0167] For example, the first signal sent by the first network entity 805 can be represented as ,in The first signal in time t The value of the communication information (e.g., information bits), It is a frequency associated with communication. It is the value of the auxiliary signal (e.g., a known or fixed value, such as "1"), and It is the frequency associated with the auxiliary signal. In some respects, This could be the center frequency associated with the communication (e.g., where the communication occupies multiple frequency domain resources). As described elsewhere in this document, the difference between the frequency associated with the communication and the frequency associated with the auxiliary signal could be a first frequency offset (e.g., ).

[0168] In some aspects, as indicated by reference numeral 845, a second network entity 810 may transmit and a third network entity 815 may receive a second signal, which includes data and auxiliary signals separated based on or otherwise associated with a second frequency offset (e.g., separated by the second frequency offset or by a frequency value separated based on or otherwise associated with the second frequency offset). In some aspects, the second signal may be intended for use by the third network entity 815 (e.g., the second network entity 810 may transmit the second signal to the third network entity 815). In other aspects, the second signal may not be intended for use by the third network entity 815. For example, the second network entity 810 may transmit the second signal to another network node, but the second signal may be transmitted spatially toward the third network entity 815, such as the third network entity 815 receiving the second signal. The first and second signals may at least partially overlap in the time domain. For example, a first network entity 805 may transmit the first signal, and the second network entity 810 may simultaneously transmit the second signal.

[0169] The second signal can be a modulated signal (e.g., modulated via ASK modulation, PSK modulation, or OOK modulation). For example, transmissions from the second network entity 810 may include communication (e.g., data communication or control communication) and auxiliary signals. The communication and auxiliary signals may be offset in the frequency domain by a second frequency ( The communication may occupy one or more subcarriers and / or REs. The second network entity 810 may transmit a second signal (e.g., a modulated signal including communication and auxiliary signals) via a channel associated with IoT (e.g., an IoT channel). The IoT channel may be a different channel from the channel used to transmit the first signal.

[0170] For example, the second signal sent by the second network entity 810 can be represented as ,in The second signal in time t The value of the communication information (e.g., information bits), It is a frequency associated with communication. It is the value of the auxiliary signal (e.g., a known or fixed value, such as "1"), and It is the frequency associated with the auxiliary signal. In some respects, This could be the center frequency associated with the communication (e.g., where the communication occupies multiple frequency domain resources). As described elsewhere in this document, the difference between the frequency associated with the communication and the frequency associated with the auxiliary signal could be a second frequency offset (e.g., ).

[0171] As indicated by reference numeral 850 in the accompanying drawings, the third network entity 815 may use envelope tracking to decode the first signal. For example, the third network entity 815 may determine that the first signal is intended for use by the third network entity 815. As an example, the first network entity 805 may send and the third network entity 815 may receive scheduling information indicating that the first signal is to be sent to the third network entity 815. In some aspects, the third network entity 815 may (e.g., by the first network entity 805 or another network node) be configured with information indicating that the third network entity 815 wants to receive communications from the first network entity 805 (e.g., the third network entity 815 may be configured to always decode communications from the first network entity 805).

[0172] The third network entity 815 can be based on the first frequency offset ( The third network entity 815 decodes the first signal based on or otherwise associated with a first frequency offset. For example, the third network entity 815 may decode the transmission (e.g., the first signal) via envelope tracking to obtain communication (e.g., data communication or control communication). In some aspects, the third network entity may decode the first signal in association with a first frequency offset between communication and auxiliary signals. For example, the third network entity 815 may detect the envelope of the first signal (e.g., detect or determine the amplitude of the first signal over time). For example, the envelope of the first signal may be the square of the first signal received by the third network entity 815. The envelope of the first signal may be represented as... Because the value of the first frequency offset is determined or selected based on one or more conditions described elsewhere in this document, the value of the first frequency offset may be greater than the following frequency spans. In other words, frequency domain location. and They can not overlap in the frequency domain. Therefore, the third network entity 815 can be isolated from... Information or values ​​in the associated envelope.

[0173] For example, the third network entity 815 may perform operations associated with frequency domain resources of the first signal based on a first frequency offset. In some aspects, the third network entity 815 may offset the transmitted frequency domain resources by the value of the first frequency offset. For example, the third network entity 815 may offset the detected envelope in the frequency domain by the first frequency offset ( As another example, a bandpass filter can be applied to the third network entity 815 to isolate it from... Information or values ​​in the associated envelope, wherein the bandpass filter is configured to filter out information or values ​​outside a given frequency range (e.g., where the given frequency range is based on a first frequency offset). ) and frequencies associated with communication ( (or otherwise associated with the first frequency offset and the frequency associated with communication).

[0174] Therefore, the modified envelope of the first signal can indicate the relationship with... Related information (e.g., after passing the envelope through a low-pass filter to remove high-frequency terms). Because The value is fixed or known and The value is indicated to the third network entity 815, thus enabling the third network entity 815 to obtain communication via envelope tracking. For example, a third network entity 815 may compare the voltage of a modified envelope (e.g., after passing the modified envelope through a low-pass filter) with one or more thresholds. As an example, if the voltage value at a given time meets a threshold, the third network entity 815 may determine communication. At a given time t Associated with "1". If the voltage value at a given time does not meet the threshold, then the third network entity 815 can determine communication ( () is associated with "0" at a given time.

[0175] The auxiliary signal can facilitate the isolation of the first signal by the third network entity 815 when multiple signals that at least partially overlap in time are present (e.g., (Item). For example, assuming multiple signals are a first signal (e.g., sent by a first network entity 805) and a second signal (e.g., sent by a second network entity 810), the envelope of the signal received at the third network entity 815 could be: in This is a DC term (e.g., which would originally be used by a third network entity 815 to perform envelope tracking of the received signal). It is a term to be used for decoding the first signal via envelope tracking. It is a term to be used for decoding the second signal via envelope tracking, and This refers to interference generated due to the transmission of the first and second signals at at least partially overlapping times. The first network entity 805 and the second network entity 810 determine or select values ​​for the frequency offset and frequency domain location of the communication according to one or more conditions described herein (e.g., , , and The values ​​of each item described above can be separated in the frequency domain (e.g., they can not overlap in the frequency domain), so that the third network entity 815 can isolate and / or filter out other items in the received signal.

[0176] For example, in order to decode the first signal, the third network entity 815 can be based on the first frequency offset. Modify the envelope of the received signal according to or otherwise associated with the first frequency offset to isolate the term. (For example, the third network entity 815 can offset the envelope by a first frequency offset) The value). Then, the third network entity 815 can decode and obtain the communication by performing envelope tracing. As described in more detail elsewhere in this document. As another example, to decode the second signal, the third network entity 815 can be based on the second frequency offset. Modify the envelope of the received signal according to or otherwise associated with the second frequency offset to isolate the term. (For example, the third network entity 815 can offset the envelope by a second frequency offset) The value). Then, the third network entity 815 can decode and obtain the communication by performing envelope tracing. As described in more detail elsewhere in this document. This is because the frequency offset and frequency domain location of the communication (e.g., , , and The value is determined or selected based on one or more conditions described herein, so the generated interference may occur at a frequency domain location that can be filtered out by a low-pass filter (e.g., it may occur in a frequency domain that is not in the same frequency domain as the low-pass filter). or (At overlapping frequency domain locations). In other words, the generated interference can occur at locations related to the term. and item Bandwidth of the channel (e.g., IoT channel) At the separated frequency domain locations. This allows the third network entity 815 to filter out interference and the sum of the two signals (e.g., ), to isolate the intended communication used for decoding.

[0177] As indicated by reference numeral 855, the third network entity 815 may perform actions associated with data or information obtained via the first signal. For example, the third network entity 815 decodes the first signal and obtains information (e.g., one or more information bits) associated with the communication sent by the first network entity 805. The third network entity 815 may use an information modulation scheme (such as ASK modulation, PSK modulation, or OOK modulation) to combine with... Figure 6 The described method reflects and / or forwards communications to another network entity (e.g., Figure 8 (Not shown in the image). As another example, the third network entity 815 may store data or information obtained via the first signal. As another example, the third network entity 815 may configure itself to perform one or more operations or actions based on the data or information obtained via the first signal.

[0178] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0179] Figure 9 This is a diagram illustrating an example of transmission 900, including communication and auxiliary signals, according to this disclosure. Figure 9 As shown, transmission 900 may include data 905 and auxiliary signal 910.

[0180] Data 905 can be associated with data communication or control communication. Data 905 can be associated with IoT communication. For example, transmission 900 can be transmitted via an IoT channel. Transmission 900 can be similar to the combination of the above. Figure 8 The first signal and / or second signal are described. Data 905 may occupy one or more frequency domain resources (e.g., one or more subcarriers or REs). Data 905 may be associated with frequency locations. Related. Frequency location The auxiliary signal 910 may be the center frequency of one or more frequency domain resources associated with data 905. The auxiliary signal 910 may be a single tone, a single subcarrier, and / or a single RE in the frequency domain. The auxiliary signal 910 may not be associated with transmitted information. For example, the auxiliary signal 910 may be a tone with a fixed value or fixed amplitude. The auxiliary signal 910 may be associated with an item that sufficiently separates the received signal (e.g., the envelope of the received signal) in the frequency domain (e.g., at the receiver, such as third network entity 815) to enable the receiver to isolate information associated with data 905 (e.g., indicated by the envelope) in the presence of multiple transmissions occurring simultaneously or partially overlapping at different times.

[0181] like Figure 6 As shown, data 905 and auxiliary signal 910 can be separated in the frequency domain by a frequency offset 915. For example, auxiliary signal 910 can be separated by a frequency... Related. and The difference can be a frequency offset of 915. The value of the frequency offset of 915 can be selected and / or determined by the network entity transmitting transmission 900. For example, as described in more detail elsewhere herein, the network entity can determine and / or negotiate the value of the frequency offset of 915 based on one or more conditions, according to one or more conditions, or otherwise associated with one or more conditions. One or more conditions can ensure that the value of the frequency offset of 915 is sufficient to separate (e.g., at the receiver (such as third network entity 815)) items of the received signal (e.g., the envelope of the received signal) in the frequency domain, so that the receiver can isolate information associated with data 905 (e.g., indicated by the envelope) in the presence of multiple transmissions that occur simultaneously or partially overlap in time.

[0182] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0183] Figure 10 This is a diagram of Example 1000 associated with envelope tracking decoding from multiple signals according to this disclosure. Example 1000 depicts signals received at the receiver when the receiver (e.g., a third network entity 815) receives multiple signals (e.g., when multiple transmitters (such as a first network entity 805 and a second network entity 810) transmit signals simultaneously or at least partially overlapping times). Figure 10 An example of a receiver receiving two signals is depicted. However, the techniques and operations described herein can be similarly applied to examples where the receiver receives more than two signals.

[0184] As described in more detail elsewhere herein, each signal can be transmitted with the communication and auxiliary signals separated by a frequency offset in the frequency domain. For example, a received signal can be associated with a first signal (e.g., comprising a first communication (e.g., first data) and a first auxiliary signal separated by a first frequency offset in the frequency domain) and a second signal (e.g., comprising a second communication (e.g., second data) and a second auxiliary signal separated by a second frequency offset in the frequency domain). For example, the first signal can be represented as... ,in The first signal in time t The value of the first communication information (e.g., information bits). It is the frequency associated with the first communication. It is the value of the first auxiliary signal (e.g., a known or fixed value, such as "1"), and It is the frequency associated with the first auxiliary signal. The second signal can be represented as... ,in The second signal in time t The value of the second communication information (e.g., information bits), It is the frequency associated with the second communication. It is the value of the second auxiliary signal (e.g., a known or fixed value, such as "1"), and It is the frequency associated with the second auxiliary signal.

[0185] As described elsewhere in this article, , First frequency offset (For example, where) ) and second frequency offset (For example, where) The value of can be determined, selected, or negotiated based on, according to, or otherwise associated with one or more conditions. One or more conditions can ensure that the received signal (e.g., in...) Figure 10 The items (described in the text) are sufficiently separated in the frequency domain so that the receiver (e.g., the third network entity 815) is able to isolate and / or separate information associated with a particular communication or data when the received signal is the sum of multiple signals.

[0186] For example, such as Figure 10 As shown, the received signal may include signals at a first frequency domain position (e.g., in the frequency domain). Figure 10 The first term associated with the summation signal 1005, shown as "0" in the table. For example, the summation signal 1005 could be... Because the receiver may not know about the first communication ( ) or second communication The received signal may include a second item associated with the first signal information 1010, such as information or values ​​associated with the first signal information 1010. Therefore, the receiver may not be able to use the summation signal 1005 to decode the first or second communication via envelope tracking. Information. The first signal information 1010 can be used by the receiver to decode the first communication ( ),because The value is known and / or fixed, and because the receiver can receive the value... Indicator of value. For example... Figure 10 As shown, the first signal information 1010 can be associated with a frequency domain position, which is offset by a first frequency. The value is separated from the summation signal 1005.

[0187] To decode the first communication, the receiver may modify the envelope of the received signal to isolate the first signal information 1010. For example, the receiver may offset the envelope and / or the received signal by a first frequency offset. This causes the first signal information 1010 to be located at a reference frequency (e.g., DC frequency, in...). Figure 10 (This is shown as "0"). As another example, the receiver may apply a bandpass filter to isolate the first signal information 1010. The receiver can obtain the first communication by applying envelope tracking decoding using the first signal information 1010, as described in more detail elsewhere herein.

[0188] The received signal may include a third item associated with the second signal information 1015. The second signal information 1015 may include, for example, The second signal information 1015 can be used by the receiver to decode the second communication ( ),because The value is known and / or fixed, and because the receiver can receive the value... Indicator of value. For example... Figure 10 As shown, the second signal information 1015 can be associated with a frequency domain position offset by a second frequency. The value is separated from the summation signal 1005. To decode the second communication, the receiver can modify the envelope of the received signal to isolate the second signal information 1015. For example, the receiver can offset the envelope and / or the received signal by a second frequency offset. This causes the second signal information 1015 to be located at a reference frequency (e.g., DC frequency, in...). Figure 10 (This is shown as "0"). As another example, the receiver can apply a bandpass filter to isolate the second signal information 1015. The receiver can obtain the second communication by applying envelope tracking decoding using the second signal information 1015, as described in more detail elsewhere in this document.

[0189] The received signal may include one or more items associated with interference 1020. For example, interference 1020 may be caused by a first signal and a second signal. , First frequency offset (For example, where) ) and second frequency offset (For example, where) The value of ) can be determined, selected, or negotiated based on one or more conditions, according to one or more conditions, or otherwise associated with one or more conditions, such that the interference 1020 produces a frequency domain position that does not overlap with the summation signal 1005, the first signal information 1010, and the second signal information 1015. Additionally, , First frequency offset (For example, where) ) and second frequency offset (For example, where) The value of ) can be determined, selected, or negotiated based on, according to, or otherwise associated with one or more conditions, such that interference 1020 occurs at a frequency domain location having a frequency value higher than the frequency value associated with the summation signal 1005, the first signal information 1010, and the second signal information 1015. Therefore, interference 1020 can be removed or filtered by a low-pass filter applied by the receiver when decoding the received signal.

[0190] For example, interference 1020 can be removed or mitigated because > And because = This could cause interference 1020 to occur. Outside and Outside of the frequency range. In other words, these conditions ensure that interference 1020 occurs at least at a channel bandwidth (or data bandwidth) away from the first signal information 1010 and the second signal information 1015. This ensures that the receiver can filter and / or remove interference 1020 (e.g., via a low-pass filter) when decoding the first or second signal.

[0191] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0192] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, by a first network node according to this disclosure. Example process 1100 is an example of a first network entity (e.g., third network entity 815, network entity 102, network entity 104, network entity 106, device 200, network node 310, UE 320, network entity 402, network entity 404) performing operations associated with envelope tracking based on auxiliary signals.

[0193] like Figure 11 As shown, in some aspects, process 1100 may include receiving an indication from a second network entity of a first frequency offset associated with the second network entity (block 1110). For example, the first network entity (e.g., using...) Figure 13 The receiving component 1302 and / or communication manager 1308 depicted herein may receive an indication of a first frequency offset associated with the second network entity from the second network entity, as described above.

[0194] like Figure 11 Further shown, in some aspects, process 1100 may include receiving a first transmission from a second network entity, the first transmission including a first communication and a first auxiliary signal separated in the frequency domain based on a first frequency offset (block 1120). For example, the first network entity (e.g., using...) Figure 13 The receiving component 1302 and / or communication manager 1308 depicted herein may receive a first transmission from a second network entity, the first transmission comprising a first communication and a first auxiliary signal separated in the frequency domain based on a first frequency offset, as described above.

[0195] like Figure 11 As further shown, in some aspects, process 1100 may include decoding the first transmission via envelope tracking to obtain the first communication from the first transmission (block 1130). For example, the first network entity (e.g., using...) Figure 13 The communication manager 1308 depicted above can decode the first transmission via envelope tracking to obtain the first communication from the first transmission.

[0196] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0197] In a first aspect, receiving an indication of a first frequency offset includes receiving system information signaling that includes an indication of the first frequency offset.

[0198] In the second aspect, either alone or in combination with the first aspect, the first frequency offset is associated with the bandwidth of the first communication.

[0199] In a third aspect, either alone or in combination with one or more of the first and second aspects, process 1100 includes sending a capability report to a second network entity, the capability report indicating one or more frequency offsets supported by the first network entity, wherein the first frequency offset is included in the one or more frequency offsets.

[0200] In the fourth aspect, decoding the first transmission, either alone or in combination with one or more of the first to third aspects, includes performing operations associated with the frequency domain resources of the first transmission based on a first frequency offset.

[0201] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, decoding the first transmission includes offsetting the frequency domain resources of the first transmission by a value based on a first frequency offset.

[0202] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, decoding the first transmission includes detecting the envelope of the first transmission in the frequency domain via envelope tracking; shifting the envelope by a first frequency offset in the frequency domain to obtain a modified envelope; applying a low-pass filter to the modified envelope; and obtaining the values ​​of a first communication and a first auxiliary signal associated with the modified envelope.

[0203] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 1100 includes receiving from a third network entity an indication of a second frequency offset associated with the third network entity, wherein the first frequency offset is different from the second frequency offset; and receiving from the third network entity a second transmission, the second transmission including a second communication and a second auxiliary signal separated in the frequency domain based on the second frequency offset.

[0204] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the first communication is ASK modulation communication or PSK modulation communication.

[0205] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the first auxiliary signal is a single tone of fixed frequency.

[0206] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 1100 may be executed in parallel.

[0207] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, by a first network node according to this disclosure. Example process 1200 is an example of a first network entity (e.g., first network entity 805, second network entity 810, network entity 102, network entity 104, network entity 106, device 200, network node 310, UE 320, network entity 402, network entity 404) performing operations associated with envelope tracking based on auxiliary signals.

[0208] like Figure 12 As shown, in some aspects, process 1200 may include communicating with a second network entity to negotiate a first frequency offset and a first frequency domain positioning for communication associated with the first network entity, and a second frequency offset and a second frequency domain positioning for communication associated with the second network entity (block 1210). For example, the first network entity (e.g., using...) Figure 14 The receiving component 1402, transmitting component 1404, and / or communication manager 1408 depicted herein can communicate with a second network entity to negotiate a first frequency offset and a first frequency domain positioning for communication associated with the first network entity, and a second frequency offset and a second frequency domain positioning for communication associated with the second network entity, as described above.

[0209] like Figure 12 As further shown, in some aspects, process 1200 may include sending an indication of a first frequency offset to a third network entity (box 1220). For example, the first network entity (e.g., using...) Figure 14 The transmitting component 1404 and / or the communication manager 1408 depicted herein can transmit an indication of a first frequency offset to a third network entity, as described above.

[0210] like Figure 12 Further shown, in some aspects, process 1200 may include the transmission of communication and auxiliary signals separated in the frequency domain by a first frequency offset, the communication being associated with frequency domain resources in a first frequency domain location (box 1230). For example, a first network entity (e.g., using...) Figure 14 The transmitting component 1404 and / or the communication manager 1408 depicted herein can transmit communication and auxiliary signals separated in the frequency domain by a first frequency offset, the communication being associated with a frequency domain resource located in the first frequency domain, as described above.

[0211] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0212] In the first aspect, the first frequency offset, the first frequency domain positioning, the second frequency offset, and the second frequency domain positioning are associated with one or more conditions.

[0213] In the second aspect, either alone or in combination with the first aspect, one or more conditions include a second frequency domain location value being greater than or equal to the sum of the first frequency domain location, the first frequency offset, the second frequency offset, and the communication bandwidth.

[0214] In the third aspect, either alone or in combination with one or more of the first and second aspects, one or more conditions include a second frequency offset being greater than or equal to the sum of the first frequency offset and the bandwidth of the communication.

[0215] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, one or more conditions are associated with the number of network entities communicating in a geographic area, including the first network entity and the second network entity.

[0216] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1200 includes determining at least one of the following based on one or more conditions: a first frequency offset and a first frequency domain location, or a second frequency offset and a second frequency domain location.

[0217] In the sixth aspect, sending an indication of the first frequency offset, either alone or in combination with one or more of the first to fifth aspects, includes sending an indication of the first frequency offset via system information signaling.

[0218] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the first frequency offset is associated with the bandwidth of the communication.

[0219] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1200 includes a reception capability report indicating one or more frequency offsets supported by a third network entity, wherein a first frequency offset is included in one or more frequency offsets.

[0220] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the communication is ASK modulation communication or PSK modulation communication.

[0221] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the auxiliary signal is a single tone of fixed frequency.

[0222] In the eleventh aspect, communication with the second network entity, either alone or in combination with one or more of the first to tenth aspects, includes at least one of the following: sending information associated with at least one of negotiating a first frequency offset, a first frequency domain location, a second frequency offset, or a second frequency domain location; or receiving information associated with at least one of negotiating a first frequency offset, a first frequency domain location, a second frequency offset, or a second frequency domain location.

[0223] although Figure 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... Figure 12 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 1200 may be executed in parallel.

[0224] Figure 13 This is a diagram of an example device 1300 for wireless communication according to the present disclosure. Device 1300 may be a first network entity, or a first network entity may include device 1300. In some aspects, device 1300 includes a receiving component 1302 and a transmitting component 1304, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1300 may use the receiving component 1302 and the transmitting component 1304 to communicate with another device 1306 (such as a UE, a base station, or another wireless communication device). As further shown, device 1300 may include a communication manager 1308. Communication manager 1308 may be or be similar to communication manager 110, communication manager 114, communication manager 235, communication manager 340, communication manager 350, communication manager 458, and / or communication manager 460. Communication manager 1308 may include a decoding component 1310, etc.

[0225] In some respects, device 1300 can be configured to perform the functions described herein. Figures 8 to 10 One or more operations described herein. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein (such as...). Figure 11 The process 1100) or a combination thereof. In some respects, Figure 13 The device 1300 and / or one or more components shown may include a combination Figure 4 One or more components of the first network entity described. Additionally or alternatively, Figure 13 One or more components shown can be combined Figure 4Implementation within one or more components described. Additionally or alternatively, one or more of the components in a set may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0226] Receiver 1302 may receive communications from device 1306, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signal to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 4 The first network entity described includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0227] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1306. In some aspects, transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmitting component 1304 may include combinations of... Figure 4 The first network entity described includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1304 may be co-located with the receive component 1302 in a transceiver.

[0228] The receiving component 1302 can receive an indication of a first frequency offset associated with the second network entity from the second network entity. The receiving component 1302 can also receive a first transmission from the second network entity, the first transmission including a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset. The decoding component 1310 can decode the first transmission via envelope tracking to obtain the first communication from the first transmission.

[0229] The transmitting component 1304 can send a capability report to a second network entity, the capability report indicating one or more frequency offsets supported by the first network entity, wherein the first frequency offset is included in the one or more frequency offsets.

[0230] The receiving component 1302 can receive from the third network entity an indication of a second frequency offset associated with the third network entity, wherein the first frequency offset is different from the second frequency offset.

[0231] The receiving component 1302 can receive a second transmission from a third network entity, the second transmission including a second communication and a second auxiliary signal separated in the frequency domain based on a second frequency offset.

[0232] Figure 13 The number and arrangement of components shown are provided as an example. In reality, they can exist in combination with... Figure 13 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 13 The two or more components shown can be implemented within a single component, or Figure 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The set (one or more) components shown are executable and described as being composed of Figure 13 The other set of components shown in the diagram performs one or more functions.

[0233] Figure 14 This is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a first network entity, or a first network entity may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a transmitting component 1404, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 can use the receiving component 1402 and the transmitting component 1404 to communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device). As further shown, apparatus 1400 may include a communication manager 1408. Communication manager 1408 may be or be similar to communication manager 110, communication manager 114, communication manager 235, communication manager 340, communication manager 350, communication manager 458, and / or communication manager 460. Communication manager 1408 may include a determining component 1410, etc.

[0234] In some respects, device 1400 can be configured to perform the functions described herein. Figures 8 to 10 One or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein (such as...). Figure 12The process 1200) or a combination thereof. In some respects, Figure 14 The device 1400 and / or one or more components shown may include a combination Figure 4 One or more components of the first network entity described. Additionally or alternatively, Figure 14 One or more components shown can be combined Figure 4 Implementation within one or more components described. Additionally or alternatively, one or more of the components in a set may be implemented at least partially as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0235] Receiver 1402 may receive communications from device 1406, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1400. In some aspects, receiver 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signal to one or more other components of device 1400. In some aspects, receiver 1402 may include combinations of... Figure 4 The first network entity described includes one or more antennas, modems, demodulators, MIMO detectors, receiver processors, controllers / processors, memory, or combinations thereof.

[0236] Transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1406. In some aspects, one or more other components of device 1400 may generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1406. In some aspects, transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1406. In some aspects, transmitting component 1404 may include combinations of... Figure 4 The first network entity described includes one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1404 may be co-located with the receive component 1402 in a transceiver.

[0237] Transmitting component 1404 and / or receiving component 1402 may communicate with a second network entity to negotiate a first frequency offset and first frequency domain positioning for communication associated with the first network entity, and a second frequency offset and second frequency domain positioning for communication associated with the second network entity. Transmitting component 1404 may transmit an indication of the first frequency offset to a third network entity. Transmitting component 1404 may transmit communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain positioning.

[0238] The determining component 1410 can determine at least one of the following based on one or more conditions: a first frequency offset and a first frequency domain location, or a second frequency offset and a second frequency domain location.

[0239] The receiving component 1402 can receive a capability report indicating one or more frequency offsets supported by a third network entity, wherein a first frequency offset is included in one or more frequency offsets.

[0240] Figure 14 The number and arrangement of components shown are provided as an example. In reality, they can exist in combination with... Figure 14 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The set (one or more) components shown are executable and described as being composed of Figure 14 The other set of components shown in the diagram performs one or more functions.

[0241] The following provides an overview of some aspects of this disclosure:

[0242] Aspect 1: A method of wireless communication performed by a first network entity, the method comprising: receiving from a second network entity an indication of a first frequency offset associated with the second network entity; receiving from the second network entity a first transmission, the first transmission comprising a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset; and decoding the first transmission via envelope tracking to obtain the first communication from the first transmission.

[0243] Aspect 2: According to the method of aspect 1, receiving the indication of the first frequency offset includes receiving system information signaling including the indication of the first frequency offset.

[0244] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the first frequency offset is associated with the bandwidth of the first communication.

[0245] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: sending a capability report to the second network entity, the capability report indicating one or more frequency offsets supported by the first network entity, wherein the first frequency offset is included in the one or more frequency offsets.

[0246] Aspect 5: The method according to any one of Aspects 1 to 4, wherein decoding the first transmission includes: performing an operation associated with the frequency domain resources of the first transmission based on the first frequency offset.

[0247] Aspect 6: The method according to any one of Aspects 1 to 5, wherein decoding the first transmission includes: offsetting the frequency domain resources of the first transmission by the value of the first frequency offset based on the first frequency offset.

[0248] Aspect 7: The method according to any one of Aspects 1 to 6, wherein decoding the first transmission comprises: detecting the envelope of the first transmission in the frequency domain via the envelope tracking; offsetting the envelope by the first frequency offset in the frequency domain to obtain a modified envelope; applying a low-pass filter to the modified envelope; and obtaining values ​​of the first communication and the first auxiliary signal associated with the modified envelope.

[0249] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: receiving from a third network entity an indication of a second frequency offset associated with the third network entity, wherein the first frequency offset is different from the second frequency offset; and receiving from the third network entity a second transmission, the second transmission comprising a second communication and a second auxiliary signal separated in the frequency domain based on the second frequency offset.

[0250] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the first communication is amplitude shift keying (ASK) modulation communication or phase shift keying (PSK) modulation communication.

[0251] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the first auxiliary signal is a single tone of a fixed frequency.

[0252] Aspect 11: A method of wireless communication performed by a first network entity, the method comprising: communicating with a second network entity to negotiate a first frequency offset and a first frequency domain location for communication associated with the first network entity, and a second frequency offset and a second frequency domain location for communication associated with the second network entity; sending an indication of the first frequency offset to a third network entity; and sending a transmission including communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources in the first frequency domain location.

[0253] Aspect 12: According to the method of aspect 11, wherein the first frequency offset, the first frequency domain positioning, the second frequency offset and the second frequency domain positioning are associated with one or more conditions.

[0254] Aspect 13: According to the method of aspect 12, wherein one or more conditions include the sum of the value of the second frequency domain positioning being greater than or equal to the first frequency domain positioning, the first frequency offset, the second frequency offset, and the bandwidth of the communication.

[0255] Aspect 14: The method according to any one of Aspects 12 to 13, wherein one or more conditions include the second frequency offset being greater than or equal to the sum of the first frequency offset and the bandwidth of the communication.

[0256] Aspect 15: The method according to any one of Aspects 12 to 14, wherein the one or more conditions are associated with the number of network entities communicating in a geographic area, the network entities including the first network entity and the second network entity.

[0257] Aspect 16: The method according to any one of aspects 12 to 15, the method further comprising: determining at least one of the following based on the one or more conditions: the first frequency offset and the first frequency domain location, or the second frequency offset and the second frequency domain location.

[0258] Aspect 17: The method according to any one of Aspects 11 to 16, wherein sending the indication of the first frequency offset comprises: sending the indication of the first frequency offset via system information signaling.

[0259] Aspect 18: The method according to any one of aspects 11 to 17, wherein the first frequency offset is associated with the bandwidth of the communication.

[0260] Aspect 19: The method according to any one of Aspects 11 to 18, the method further comprising: receiving a capability report, the capability report indicating one or more frequency offsets supported by the third network entity, wherein the first frequency offset is included in the one or more frequency offsets.

[0261] Aspect 20: The method according to any one of aspects 11 to 19, wherein the communication is amplitude shift keying (ASK) modulation communication or phase shift keying (PSK) modulation communication.

[0262] Aspect 21: The method according to any one of aspects 11 to 20, wherein the auxiliary signal is a single tone of a fixed frequency.

[0263] Aspect 22: The method according to any one of Aspects 11 to 21, wherein communicating with the second network entity includes at least one of: sending information associated with negotiating at least one of the first frequency offset, the first frequency domain positioning, the second frequency offset, or the second frequency domain positioning; or receiving information associated with negotiating at least one of the first frequency offset, the first frequency domain positioning, the second frequency offset, or the second frequency domain positioning.

[0264] Aspect 23: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; a memory coupled to the processors; and instructions stored in the memory and executable by the processors to cause the apparatus to perform the method according to one or more of aspects 1 to 22.

[0265] Aspect 24: An apparatus for wireless communication, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to perform the method according to one or more of aspects 1 to 22.

[0266] Aspect 25: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 22.

[0267] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 22.

[0268] Aspect 27: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 22.

[0269] Aspect 28: A device for wireless communication, the device comprising: one or more communication interfaces; and one or more processors coupled to the one or more communication interfaces, the device being configured to perform the method according to one or more of aspects 1 to 22.

[0270] The foregoing disclosure provides examples and descriptions, but is neither exhaustive nor a limitation on the scope of this disclosure. For example, various aspects and examples are disclosed herein, but this disclosure is not limited to the precise form used to describe such aspects and examples. Modifications and variations can be made based on the foregoing disclosure, or from practice in various aspects.

[0271] As used herein, the term "component" should be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. The systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, this document does not refer to specific software code to describe the operation and behavior of systems and / or methods, as those skilled in the art will understand that software and hardware can be designed to implement systems and / or methods, at least in part, based on the descriptions herein.

[0272] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0273] As used herein, the term "determine" encompasses a wide variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), reasoning, ascertainment, and / or measurement, etc. Additionally, "determine" can include receiving (such as receiving information), accessing (such as accessing data stored in memory), and / or sending (such as sending information), etc. As another example, "determine" can include parsing, selecting, obtaining, choosing, building, and other similar actions.

[0274] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations do not limit the scope of this disclosure. Many of these features may be combined in ways not specifically recited in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set. As used herein, the phrase referring to “at least one of” the list of items means any combination of these items, including a single member. As an example, “at least one of a, b, or c” covers: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0275] The elements, actions, or instructions used herein are not critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “one” include one or more items and are used interchangeably with “one or more.” Additionally, as used herein, the article “described” includes one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having,” etc., are open-ended terms that do not limit the elements they modify (e.g., an element that “has” A may also have B). Additionally, as used herein, “based on” has an inclusive meaning unless otherwise explicitly indicated. For example, unless otherwise explicitly indicated, “based on” is used interchangeably with “at least partially based on,” “associated with,” or “according to.” The phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. Specifically, unless the phrase in the context refers to "based on 'one' only" or an equivalent, it can be based solely on "one" or on a combination of "one" and one or more other factors, conditions, or information, whether it is "based on 'one'" or "at least partially based on 'one'". Furthermore, as used herein, the term "or" is inclusive when used in a series and can be used interchangeably with "and / or" unless otherwise explicitly stated (e.g., if used in conjunction with "any" or "only one").

Claims

1. A first network entity for wireless communication, the first network entity comprising: One or more communication interfaces; and One or more processors coupled to one or more communication interfaces, wherein the first network entity is configured to: Receive an indication of a first frequency offset associated with the second network entity via the one or more communication interfaces and from the second network entity; Receive a first transmission via the one or more communication interfaces and from the second network entity, the first transmission comprising a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset; as well as The first transmission is decoded via envelope tracking to obtain the first communication from the first transmission.

2. The first network entity according to claim 1, wherein, In order to receive the indication of the first frequency offset, the first network entity is configured to receive system information signaling including the indication of the first frequency offset via the one or more communication interfaces.

3. The first network entity of claim 1, wherein the first frequency offset is associated with the bandwidth of the first communication.

4. The first network entity according to claim 1, wherein the first network entity is configured as follows: The one or more communication interfaces are configured to send a capability report to the second network entity, the capability report indicating one or more frequency offsets supported by the first network entity. The first frequency offset is included in the one or more frequency offsets.

5. The first network entity according to claim 1, wherein, In order to decode the first transmission, the first network entity is configured as follows: The operation associated with the frequency domain resource transmitted first is performed based on the first frequency offset.

6. The first network entity according to claim 1, wherein, In order to decode the first transmission, the first network entity is configured as follows: The frequency domain resources of the first transmission are offset by the value of the first frequency offset based on the first frequency offset.

7. The first network entity according to claim 1, wherein, In order to decode the first transmission, the first network entity is configured as follows: The envelope of the first transmission in the frequency domain is detected via the envelope tracking. In the frequency domain, the envelope is shifted by the first frequency shift to obtain a modified envelope; Apply a low-pass filter to the modified envelope; as well as Obtain the values ​​of the first communication and the first auxiliary signal associated with the modified envelope.

8. The first network entity according to claim 1, wherein the first network entity is configured as: Receive, via the one or more communication interfaces and from a third network entity, an indication of a second frequency offset associated with the third network entity, wherein the first frequency offset is different from the second frequency offset; and The second transmission is received via the one or more communication interfaces and from the third network entity, the second transmission including a second communication and a second auxiliary signal separated in the frequency domain based on the second frequency offset.

9. The first network entity according to claim 1, wherein the first communication is amplitude shift keying (ASK) modulation communication or phase shift keying (PSK) modulation communication.

10. The first network entity of claim 1, wherein the first auxiliary signal is a single tone of a fixed frequency.

11. A first network entity for wireless communication, the first network entity comprising: One or more communication interfaces; and One or more processors coupled to one or more communication interfaces, wherein the first network entity is configured to: The one or more communication interfaces are made to communicate with a second network entity to negotiate a first frequency offset and a first frequency domain location for communication associated with the first network entity, and a second frequency offset and a second frequency domain location for communication associated with the second network entity. The one or more communication interfaces are configured to send an indication of the first frequency offset to a third network entity. as well as The one or more communication interfaces are configured to transmit communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources located in the first frequency domain.

12. The first network entity of claim 11, wherein the first frequency offset, the first frequency domain location, the second frequency offset, and the second frequency domain location are associated with one or more conditions.

13. The first network entity of claim 12, wherein one or more conditions include the sum of the value of the second frequency domain location being greater than or equal to the first frequency domain location, the first frequency offset, the second frequency offset, and the bandwidth of the communication.

14. The first network entity of claim 12, wherein one or more conditions include the second frequency offset being greater than or equal to the sum of the first frequency offset and the bandwidth of the communication.

15. The first network entity of claim 12, wherein one or more conditions are associated with the number of network entities communicating in a geographic area, the network entity comprising the first network entity and the second network entity.

16. The first network entity according to claim 12, wherein the first network entity is configured to: Determine at least one of the following based on one or more of the stated conditions: The first frequency offset and the first frequency domain positioning, or The second frequency offset and the second frequency domain positioning.

17. A method for wireless communication performed by a first network entity, the method comprising: Receive an indication of a first frequency offset associated with the second network entity from the second network entity; Receive a first transmission from the second network entity, the first transmission including a first communication and a first auxiliary signal separated in the frequency domain based on the first frequency offset; as well as The first transmission is decoded via envelope tracking to obtain the first communication from the first transmission.

18. The method of claim 17, wherein receiving the indication of the first frequency offset includes receiving system information signaling including the indication of the first frequency offset.

19. The method of claim 17, wherein the first frequency offset is associated with the bandwidth of the first communication.

20. The method of claim 17, further comprising: A capability report is sent to the second network entity, the capability report indicating one or more frequency offsets supported by the first network entity. The first frequency offset is included in the one or more frequency offsets.

21. The method of claim 17, wherein decoding the first transmission comprises: The operation associated with the frequency domain resource transmitted first is performed based on the first frequency offset.

22. The method of claim 17, wherein decoding the first transmission comprises: The frequency domain resources of the first transmission are offset by the value of the first frequency offset based on the first frequency offset.

23. The method of claim 17, wherein decoding the first transmission comprises: The envelope of the first transmission in the frequency domain is detected via the envelope tracking. In the frequency domain, the envelope is shifted by the first frequency shift to obtain a modified envelope; Apply a low-pass filter to the modified envelope; as well as Obtain the values ​​of the first communication and the first auxiliary signal associated with the modified envelope.

24. The method of claim 17, wherein the first auxiliary signal is a single tone of a fixed frequency.

25. A method for wireless communication performed by a first network entity, the method comprising: Communicate with a second network entity to negotiate a first frequency offset and a first frequency domain location for communication associated with the first network entity, and a second frequency offset and a second frequency domain location for communication associated with the second network entity. Send an indication of the first frequency offset to the third network entity; as well as The transmission includes the transmission of communication and auxiliary signals separated in the frequency domain by the first frequency offset, the communication being associated with frequency domain resources located in the first frequency domain.

26. The method of claim 25, wherein sending the indication of the first frequency offset comprises: The indication of the first frequency offset is sent via system information signaling.

27. The method of claim 25, wherein the first frequency offset is associated with the bandwidth of the communication.

28. The method of claim 25, further comprising: A reception capability report, which indicates one or more frequency offsets supported by the third network entity. The first frequency offset is included in the one or more frequency offsets.

29. The method of claim 25, wherein the communication is amplitude shift keying (ASK) modulation communication or phase shift keying (PSK) modulation communication.

30. The method of claim 25, wherein communicating with the second network entity comprises at least one of the following: Send information associated with at least one of the negotiated first frequency offset, first frequency domain positioning, second frequency offset, or second frequency domain positioning; or Receive information associated with at least one of the negotiated first frequency offset, first frequency domain positioning, second frequency offset, or second frequency domain positioning.

Images