Frequency-dependent residual sideband (FDRSB) aware precoding

Abstract

In some aspects, an apparatus for wireless communication includes a receiver and a transmitter. The transmitter is configured to transmit a capability message including an indication of whether the receiver supports frequency-dependent residual sideband (FDRSB) distortion reduction for a received signal. The receiver is configured to receive a signal precoded with one of a first precoder or a second precoder different from the first precoder in accordance with at least the indication of whether the receiver supports FDRSB distortion reduction.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of Israel Patent Application No. 310424, filed on January 26, 2024, entitled “FREQUENCY-DEPENDENT RESIDUALSIDE BAND (FDRSB) AWARE PRECODING”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate generally to wireless communication systems, and more specifically to frequency-dependent residual sideband (FDRSB) sensing pre-decoding for wireless communication systems. Background Technology

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, message sending and receiving, and broadcasting. These wireless networks can be multiple access networks capable of supporting multiple users by sharing available network resources. Such networks can be multiple access networks that support communication for multiple users by sharing available network resources.

[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as a base station (or node B) that can support communication between multiple user equipments (UEs). UEs may communicate with the base station via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the base station to the UE, and an uplink (or reverse link) refers to the communication link from the UE to the base station.

[0006] The base station can transmit data and control information to the UE on the downlink or receive data and control information from the UE on the uplink. On the downlink, transmissions from the base station may encounter interference originating from transmissions from neighboring base stations or other radio frequency (RF) transmitters. On the uplink, transmissions from the UE may encounter interference from uplink transmissions from other UEs communicating with neighboring base stations or from other RF transmitters. This interference can degrade performance on both the downlink and uplink.

[0007] For example, frequency-dependent vestigial sideband (FDRSB) distortion can degrade performance in wireless communication systems. In some devices, such FDRSB distortion can cause, or be associated with, a mismatch or imbalance between a transmitter component associated with an in-phase (I) signal component and another transmitter component associated with a quadrature (Q) signal component. To compensate for the effects of FDRSB distortion, some wireless communication systems may reduce or limit one or more of the following: data transmission rate, carrier frequency, or the number of transmit antennas used to transmit the signal. Such techniques may increase latency and may reduce communication throughput or quality in the wireless communication system. Other techniques may compensate for FDRSB distortion by increasing the transmit power associated with the transmitted signal, thereby increasing energy consumption. Summary of the Invention

[0008] In some aspects of this disclosure, an apparatus for wireless communication includes a receiver and a transmitter. The transmitter is configured to transmit a capability message including an indication of whether the receiver supports frequency-dependent vestigial sideband (FDRSB) distortion reduction for a received signal. The receiver is configured to receive a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on the indication of whether the receiver supports FDRSB distortion reduction.

[0009] In some other aspects, a method of wireless communication performed by a device includes transmitting a capability message that includes an indication of whether the device supports FDRSB distortion reduction for a received signal. The method also includes receiving a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, at least based on the indication of whether the device supports FDRSB distortion reduction.

[0010] In some other aspects, an apparatus for wireless communication includes a receiver configured to receive a capability message including an indication of whether the device supports FDRSB distortion reduction for the received signal. The apparatus also includes a transmitter configured to transmit a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on the indication of whether the device supports FDRSB distortion reduction.

[0011] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. One or more features described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations may include integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, artificial intelligence (AI) enabled devices, etc.). While some examples may or may not point to a use case or application, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, as well as aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals involve multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). One or more features described herein can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., of varying sizes, shapes, and constructions. Attached Figure Description

[0012] A further understanding of the nature and advantages of this disclosure can be achieved by referring to the following figures. In the figures, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numerals.

[0013] Figure 1 This is a block diagram illustrating example details of an example wireless communication system that supports frequency-dependent residual sideband (FDRSB) sensing pre-decoding based on one or more aspects.

[0014] Figure 2 This is a block diagram illustrating examples of base stations and user equipment (UEs) that support FDRSB-aware pre-decoding according to one or more aspects.

[0015] Figure 3 This is a block diagram illustrating an example wireless communication system that supports FDRSB-aware pre-decoding based on some aspects.

[0016] Figure 4 Examples of graphs illustrating some aspects of FDRSB-aware pre-decoding are shown.

[0017] Figure 5 This is a flowchart illustrating an example process of supporting FDRSB-aware pre-decoding based on one or more aspects.

[0018] Figure 6 This is a flowchart illustrating another example process of supporting FDRSB-aware pre-decoding based on one or more aspects.

[0019] Figure 7 This is a block diagram of an example UE that supports FDRSB-aware pre-decoding based on one or more aspects.

[0020] Figure 8 It is a block diagram of an example network node that supports FDRSB-aware pre-decoding based on one or more aspects. Detailed Implementation

[0021] In some aspects of this disclosure, network nodes (such as base stations) can select a predecoder from a plurality of predecoders for transmitting signals. The plurality of predecoders may include a first predecoder, such as a frequency-dependent vestigial sideband (FDRSB)-aware predecoder, and may also include a second predecoder, such as a non-FDRSB-aware predecoder. In some specific implementations, using an FDRSB-aware predecoder can reduce the amount of FDRSB distortion associated with the signal compared to using a non-FDRSB-aware predecoder, can balance the signal-to-FDRSB noise ratio (SFNR) associated with the signal (e.g., by reducing the variability of SFNR over the frequency range), or both.

[0022] In some implementations, network nodes can select a predecoder based on one or more criteria. In some examples, the user equipment (UE) can indicate whether the UE supports UE-side FDRSB reduction (e.g., based on whether the UE includes FDRSB reduction circuitry). In some such examples, the network node can select a non-FDRSB-aware predecoder based on an indication that the UE supports UE-side FDRSB reduction, or it can select an FDRSB-aware predecoder based on an indication that the UE does not support UE-side FDRSB reduction.

[0023] Alternatively or in addition, one or more criteria may include the battery state associated with the UE. For example, a network node may select an FDRSB-aware predecoder based on a relatively high battery level indicated by the UE, or it may select a non-FDRSB-aware predecoder based on a relatively low battery level indicated by the UE. By selecting a non-FDRSB-aware predecoder based on a relatively low battery level indicated by the UE, the network node can enable the UE to avoid using FDRSB reduction circuitry, which may be associated with relatively high power consumption.

[0024] Alternatively or in addition, one or more criteria may include the amount (or estimate) of FDRSB, such as the FDRSB basis compared to the amount of thermal noise in the wireless communication system. In some examples, if the FDRSB basis is relatively low compared to the amount of thermal noise, the network node may select a non-FDRSB-aware predecoder. In some other examples, if the FDRSB basis is relatively high compared to the amount of thermal noise, the network node may select an FDRSB-aware predecoder.

[0025] One or more features described herein can improve performance within a wireless communication system. For example, by selecting from multiple pre-decoders, a network node can achieve FDRSB reduction while also promoting enhanced performance in the wireless communication system (e.g., by saving power at the network node, the UE, or both). For example, in some scenarios, a network node can use an FDRSB-aware pre-decoder to perform FDRSB reduction at the network node, such as in response to one or more of the following: the UE does not support UE-side FDRSB reduction, the UE is associated with relatively low battery power, or the FDRSB distortion is relatively high. In some other scenarios, the network node can choose a non-FDRSB-aware pre-decoder and can “offload” or “delegate” the decision of whether to use FDRSB distortion reduction to the UE, such as in response to one or more of the following: the UE supports UE-side FDRSB reduction, the UE is associated with relatively high battery power, or the FDRSB distortion is relatively low. Therefore, FDRSB distortion reduction is enabled for various situations, including for UEs that support UE-side FDRSB reduction and for UEs that do not support UE-side FDRSB reduction.

[0026] To further illustrate, performance in wireless communication systems can be improved by reducing the variability of the SFNR. For example, in some wireless communication protocols, the modulation and decoding scheme (MCS) may be based on, or be affected by, the "worst-case" SFNR. In such cases, significant SFNR variability can limit the MCS or the range of MCSs available for data transmission. By reducing the SFNR variability (e.g., by balancing, smoothing, or flattening the SFNR over a frequency range), instances of such "worst-case" SFNR can be reduced or eliminated, which can facilitate the use of a wider range of MCSs for data transmission.

[0027] For further illustration, some aspects of this disclosure relate to wireless communication networks, including Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth-generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems, or devices), and other communication networks. As described herein, the terms "network" and "system" are used interchangeably.

[0028] For example, CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.

[0029] For example, TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standard for the GSM EDGE (Enhanced Data Rate GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network connecting GSM / EDGE base stations (e.g., Ater and Abis interfaces) and base station controllers (A interface, etc.). The radio access network represents a component of the GSM network through which telephone calls and packet data are routed from the Public Switched Telephone Network (PSTN) and the Internet to subscriber handsets (also known as user terminals or user equipment (UEs)) and from subscriber handsets to the PSTN and the Internet. A mobile phone operator's network may include one or more GERANs, which may be coupled with UTRAN in the case of UMTS / GSM networks. Additionally, the operator's network may also include one or more LTE networks, or one or more other networks. Different network types may use different radio access technologies (RATs) and RANs.

[0030] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, LTE, and NR are described in documents provided by an organization called the 3rd Generation Partnership Project (3GPP), and cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration among telecommunications associations aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP initiative aimed at improving the UMTS mobile phone standard. 3GPP defines specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may refer to LTE, 4G, or 5G NR technologies to describe certain aspects; however, this description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of this disclosure may relate to shared access to radio spectrum between networks using different radio access technologies or radio air interfaces.

[0031] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be achieved using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to (1) provide coverage to large-scale Internet of Things (IoT) with ultra-high density (e.g., about 1M nodes / km^2), ultra-low complexity (e.g., about 10 bits / second), ultra-low power consumption (e.g., about 10+ years of battery life), and deep coverage to reach challenging locations; (2) include mission-critical controls with strong security to protect sensitive personal, financial or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with wide range of mobility or lack of mobility; and (3) provide coverage with enhanced mobile broadband (including extremely high capacity (e.g., about 10Tbps / km^2), extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates)) and with deep awareness with advanced discovery and optimization.

[0032] Devices, networks, and systems can be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise for FR2, which is often (interchangeably) referred to as the “millimeter wave” (mmWave) band in documents and articles, although this is different from the extremely high frequency (EHF) band (30GHz-300GHz) designated as “mmWave” by the International Telecommunication Union (ITU).

[0033] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the terms "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the terms "mmWave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0034] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform characteristics. These characteristics may include scalable parameter sets and transmission time intervals (TTIs); a common flexible framework for efficiently multiplexing services and characteristics using dynamic, low-latency time-division duplex (TDD) or frequency-division duplex (FDD) designs; and advanced radio technologies such as massive MIMO, robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR efficiently addresses the operation of diverse services across different spectrums and deployments through subcarrier spacing scaling. For example, in various outdoor and macro coverage deployments implementing FDD or TDD below 3 GHz, subcarrier spacing may occur at 15 kHz, such as bandwidths exceeding 1 MHz, 5 MHz, 10 MHz, 20 MHz, etc. For other various outdoor and small cell coverage deployments with TDD above 3 GHz, subcarrier spacing may occur at 30 kHz over an 80 MHz / 100 MHz bandwidth. For various other indoor broadband implementations using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting via mmWave components under 28 GHz TDD, subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.

[0035] 5G NR's scalable parameter set facilitates scalable TTIs for diverse latency and Quality of Service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to begin at symbol boundaries. 5G NR also anticipates self-contained integrated subframe designs, where uplink or downlink scheduling information, data, and reception are contained within the same subframe. Self-contained integrated subframes support communication in unlicensed or contention-based shared spectrum, with adaptive uplink or downlink that can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current service demands.

[0036] For clarity, certain aspects of the apparatus and technology may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in the sections described below; however, this description is not intended to be limited to 5G applications.

[0037] Furthermore, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, apparatuses, and methods described herein can be applied to other communication systems and applications besides the specific examples provided.

[0038] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, package arrangements, etc. For example, implementations or uses may arise via integrated chip implementations or other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail or purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the described aspects. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. The innovations described herein are intended to be implemented in a wide variety of specific implementations of varying sizes, shapes, and constructions, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed deployments, aggregated or decomposed deployments, end-user devices, and the like.

[0039] Figure 1 This is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. Wireless network 100 may, for example, include a 5G wireless network. As those skilled in the art will recognize, Figure 1 The components appearing in this network are likely to have corresponding components in other network arrangements (including, for example, cellular network arrangements and non-cellular network arrangements (e.g., device-to-device, peer-to-peer, or self-organizing network arrangements)).

[0040] Figure 1The wireless network 100 illustrated herein includes multiple base stations 105 and other network entities. A base station can be a station communicating with one or more UEs and may also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving that coverage area, depending on the context in which the term is used. In the specific implementation of the wireless network 100 herein, base stations 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in the specific implementation of the wireless network 100 herein, base station 105 may use one or more frequencies (e.g., one or more bands of licensed spectrum, unlicensed spectrum, or combinations thereof) from the same frequencies as neighboring cells to provide wireless communication. In some examples, a single base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0041] Base stations can provide communication coverage for macro cells, small cells (such as pico cells or femto cells), or other types of cells. Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as pico cells) typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femto cells) also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, provide restricted access by UEs associated with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, pico base station, femto base station, or home base station. Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a to 105c are macro base stations implemented using one of 3D, full-dimensional (FD), or massive MIMO. Base stations 105a to 105c utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base stations can support one or more (e.g., two, three, and four cells, etc.) cells.

[0042] Wireless Network 100 can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timings, and transmissions from different base stations can be roughly aligned in time. For asynchronous operation, base stations can have different frame timings, and transmissions from different base stations may not be aligned in time. In some scenarios, the network can be enabled or configured to handle dynamic switching between synchronous and asynchronous operations.

[0043] UE 115 is distributed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that although mobile devices are generally referred to as UEs in standards and specifications issued by 3GPP, such devices may additionally or otherwise be referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handphone, terminal, user agent, mobile client, client, gaming device, augmented reality device, vehicle component, vehicle equipment or vehicle module, or some other suitable term. In this document, a “mobile” device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices include specific implementations of one or more UEs in UE 115, including mobile phones, cellular phones (cell phones), smartphones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebook computers, netbooks, smartbooks, tablets, and personal digital assistants (PDAs). Mobile devices may additionally be IoT or “Internet of Everything” (IoE) devices, such as automobiles or other transportation vehicles, satellite broadcasting, Global Positioning System (GPS) devices, Global Navigation Satellite System (GNSS) devices, logistics controllers, drones, multi-rotor helicopters, quadcopter helicopters, smart energy or security devices, solar panels or solar arrays, urban lighting, water meters or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, posture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia equipment, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a-115d illustrated herein are examples of mobile smartphone-type devices accessing the wireless network 100. The UE may also be a machine specifically configured for connecting communications, including machine-type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The UE 115e-115k illustrated herein is an example of various machines configured for communication that access the wireless network 100.

[0044] Mobile devices (such as UE 115) can communicate with any type of base station (whether macro base station, pico base station, femto base station, or relay station). Figure 1 In this context, the communication link (represented by a lightning bolt) indicates radio transmissions between the UE and a serving base station (which is designated to serve the UE on the downlink or uplink), or expected transmissions between base stations, and backhaul transmissions between base stations. The UE may operate as a base station or other network node in some scenarios. Backhaul communication between base stations of the wireless network 100 can be performed using wired or wireless communication links.

[0045] In operation, at wireless network 100, base stations 105a to 105c use 3D beamforming and cooperative spatial technologies such as Cooperative Multipoint (CoMP) or Multi-Connection to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a to 105c and the small cell (base station 105f). Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber Alerts or Grey Alerts.

[0046] The implemented wireless network 100 supports mission-critical communication with highly reliable and redundant links for mission-critical devices such as UE 115e as a drone. Redundant communication links with UE 115e include links from macro base stations 105d and 105e, as well as small cell base station 105f. Other machine-type devices such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device) can communicate directly with base stations such as small cell base station 105f and macro base station 105e via the wireless network 100, or in a multi-hop configuration by communicating with another user device relaying its information to the network, such as UE 115f transmitting temperature measurement information to smart meter UE 115g, which then reports it to the network via small cell base station 105f. Wireless network 100 can also provide additional network efficiency through dynamic, low-latency TDD or low-latency FDD communication, such as in vehicle-to-vehicle (V2V) mesh networks between UEs 115i to 115k communicating with macro base station 105e.

[0047] Figure 2 This is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 can be... Figure 1 This refers to any one of the base stations and one of the UEs in the system. For restricted association scenarios (as mentioned above), base station 105 can be... Figure 1 The base station 105 is a small cell base station, and UE 115 can be UE 115c or 115d operating within the service area of ​​base station 105f. UE 115 will be included in the list of accessible UEs of small cell base station 105f in order to access it. Base station 105 can also be some other type of base station. For example... Figure 2 As shown, base station 105 may be equipped with antennas 234a to 234t, and UE 115 may be equipped with antennas 252a to 252r for facilitating wireless communication.

[0048] At base station 105, transmitting processor 220 can receive data from data source 212 and control information from controller 240 (such as a processor). The control information may be for physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), physical downlink control channel (PDCCH), enhanced physical downlink control channel (EPDCCH), MTC physical downlink control channel (MPDCCH), etc. The data may be for physical downlink shared channel (PDSCH), etc. Additionally, transmitting processor 220 can process (e.g., encoding and symbol mapping) the data and control information separately to obtain data symbols and control symbols. Transmitting processor 220 can also generate, for example, reference symbols for primary synchronization signal (PSS) and secondary synchronization signal (SSS), as well as cell-specific reference signals. The transmit (TX) MIMO processor 230 can perform spatial processing (e.g., pre-decoding, where applicable) on data symbols, control symbols, or reference symbols, and can provide an output symbol stream to modulators (MODs) 232a to 232t. For example, spatial processing performed on data symbols, control symbols, or reference symbols may include pre-decoding. Each modulator 232 can (e.g., for OFDM, etc.) process its respective output symbol stream to obtain an output sample stream. Additionally or alternatively, each modulator 232 can process the output sample stream (e.g., perform analog-to-analog conversion, amplification, filtering, and up-conversion) to obtain a downlink signal. The downlink signal from modulators 232a to 232t can be transmitted via antennas 234a to 234t, respectively.

[0049] At UE 115, antennas 252a to 252r can receive downlink signals from base station 105 and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 can obtain the received symbols from demodulators 254a to 254r, perform MIMO detection on the received symbols when necessary, and provide the detected symbols. Receiver processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide the decoded data for UE 115 to data sink 260, and provide the decoded control information to controller 280, such as a processor.

[0050] On the uplink, at UE 115, the transmitting processor 264 can receive and process data from data source 262 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller 280 (e.g., for the Physical Uplink Control Channel (PUCCH)). Additionally, the transmitting processor 264 can also generate reference symbols for reference signals. Symbols from the transmitting processor 264 can be pre-decoded by the TX MIMO processor 266 when needed, further processed by modulators 254a to 254r (e.g., for SC-FDM, etc.), and transmitted to base station 105. At base station 105, the uplink signal from UE 115 can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 when needed, and further processed by receiving processor 238 to obtain the decoded data and control information transmitted by UE 115. Receiving processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller 240. Controllers 240 and 280 can respectively direct operations at base station 105 and UE 115. Controller 240 or other processors and modules at base station 105 or controller 280 or other processors and modules at UE 115 can initiate, execute, or control one or more operations described herein. Memory 242 and memory 282 can respectively store data and program code for base station 105 and UE 115. Scheduler 244 can schedule the UE to perform downlink or uplink data transmission.

[0051] In some cases, UE 115 and base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, UE 115 or base station 105 may conventionally perform a medium sensing procedure to compete for spectrum access. For example, UE 115 or base station 105 may perform a Listen-Before-Speak or Listen-Before-Transmit (LBT) procedure (such as Clear Channel Assessment (CCA)) before communication to determine if a shared channel is available. In some implementations, CCA may include an energy detection procedure to determine if any other active transmission is present. For example, the device may infer that a change in the Received Signal Strength Indicator (RSSI) of the power meter indicates that the channel is occupied. In particular, signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another radio transmitter. CCA may also include the detection of a specific sequence indicating channel usage. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or on ACK / NACK feedback of its own transmitted packets (as a manifestation of a collision).

[0052] Figure 3 This is a block diagram illustrating an example wireless communication system 300 supporting FDRSB-aware pre-decoding according to some aspects. Wireless communication system 300 may include a UE 315 (such as UE 115). Wireless communication system 300 may also include one or more network nodes, such as network node 305. In some examples, network node 305 may be implemented as a base station, such as base station 105. For further illustration, network node 305 may be implemented as a base station, network controller, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), or remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), as illustrative examples. A network node may also be referred to as a network entity.

[0053] Network node 305 may include one or more processors 302 (such as controller 240), memory 304 (such as memory 242), transmitter 306, and receiver 308. One or more processors 302 may be coupled to memory 304, transmitter 306, and receiver 308. In some examples, transmitter 306 and receiver 308 may include references. Figure 2 The described components include one or more of the modulator / demodulator 232a-t, MIMO detector 236, receiver processor 238, transmitter processor 220, or TXMIMO processor 230. In some examples, one or more processors 302 may be configured to perform one or more of the operations described herein, individually or jointly.

[0054] Transmitter 306 can transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 308 can receive reference signals, control information, and data from one or more other devices. For example, in some implementations, transmitter 306 can transmit signaling, control information, and data to UE 315, and receiver 308 can receive signaling, control information, and data from UE 315.

[0055] UE 315 may include one or more processors 352 (such as controller 280), memory 354 (such as memory 282), transmitter 356, and receiver 358. One or more processors 352 may be coupled to memory 354, transmitter 356, and receiver 358. In some examples, transmitter 356 and receiver 358 may include references. Figure 2The described components include one or more of the modulator / demodulator 254a-r, MIMO detector 256, receiver processor 258, transmitter processor 264, or TX MIMO processor 266. In some embodiments, transmitter 356 and receiver 358 may be integrated into one or more transceivers of UE 315. In some examples, one or more processors 352 may be configured to perform one or more of the operations described herein, individually or jointly.

[0056] Transmitter 356 can send reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 358 can receive reference signals, control information, and data from one or more other devices. For example, in some implementations, transmitter 356 can send signaling, control information, and data to network node 305, and receiver 358 can receive signaling, control information, and data from network node 305.

[0057] The wireless communication system 300 may use wireless communication channels, which may be specified by one or more wireless communication protocols, such as the 5G NR wireless communication protocol. For example, network node 305 may use one or more downlink wireless communication channels (such as via one or more of PDSCH or PDCCH) to communicate with UE 315. UE 315 may use one or more uplink wireless communication channels (such as via one or more of PUSCH or PUCCH) to communicate with network node 305. Alternatively or otherwise, UE 315 may communicate with one or more other UEs, such as via sidelink wireless communication channels.

[0058] In some implementations, UE 315 may support reduction of FDRSB distortion in the received signal. For example, UE 315 may include FDRSB distortion reduction circuitry 362 that supports the elimination or reduction of FDRSB distortion in the received signal. For example, FDRSB distortion reduction circuitry 362 may be configured to measure the amount of FDRSB distortion associated with the received signal (such as measuring the amount of signal components within the sideband frequencies of the received signal) and reduce or eliminate FDRSB distortion from the received signal (such as by attenuating or eliminating signal components within the sideband frequencies of the received signal).

[0059] In some other implementations, UE 315 may not support FDRSB distortion reduction. In such examples, UE 315 may not include FDRSB distortion reduction circuitry 362. To further illustrate, in some implementations, a UE associated with a first communication type may support FDRSB distortion reduction, while a UE of another communication type may not support it. As an illustrative example, a UE supporting Reduced Capability (RedCap) communication may not support FDRSB distortion reduction to reduce power consumption. As another illustrative example, another type of UE (such as a "full-capability" or "enhanced-capability" UE) may support FDRSB distortion reduction to improve communication reliability. Alternatively or otherwise, the UE may support another communication type.

[0060] During operation, UE 315 may send a capability message 320 to network node 305. As an illustrative example, UE 315 may send the capability message 320 via a Media Access Control (MAC) control element (MAC-CE), Radio Resource Control (RRC) signaling, or other signaling. The capability message 320 may include an indication 322 of whether UE 315 (or receiver 358) supports FDRSB distortion reduction of the received signal. For example, if UE 315 includes FDRSB distortion reduction circuitry 362, the indication 322 may specify that UE 315 supports FDRSB distortion reduction. As another example, if UE 315 does not include FDRSB distortion reduction circuitry 362, the indication 322 may specify that UE 315 does not support FDRSB distortion reduction. In some examples, the indication 322 may include or correspond to a flag (e.g., a bit) that can be set to a first or second value. The first value can indicate that UE 315 supports FDRSB distortion reduction, and the second value can indicate that UE 315 does not support FDRSB distortion reduction.

[0061] In some other implementations, UE 315 may send capability message 320 only if UE 315 supports (or does not support) FDRSB distortion reduction of the received signal. For example, UE 315 and network node 305 may operate according to a wireless communication protocol that specifies that UE 315 will only provide indication 322 to network node 305 if UE 315 supports FDRSB distortion reduction. In another example, the wireless communication protocol specifies that UE 315 will only provide indication 322 to network node 305 if UE 315 does not support FDRSB distortion reduction.

[0062] In some implementations, UE 315 may send a power state message 324 to network node 305 indicating a power state 326 associated with UE 315. For example, power state 326 may indicate an estimated battery level associated with UE 315's battery. For further illustration, in some examples, power state 326 may have one of a first value (e.g., indicating a low battery level), a second value (e.g., indicating an intermediate battery level), or a third value (e.g., indicating a high battery level). In some other examples, power state 326 may indicate a percentage battery level associated with UE 315 (e.g., a 50% battery level may indicate that UE 315's battery is charged to approximately half its capacity). In some examples, UE 315 may send power state message 324 via a PUCCH signal or via another signal. Furthermore, although... Figure 3 The example illustrates that UE 315 can send indication 322 and power status 326 via separate messages, but in some other examples, UE 315 can send indication 322 and power status 326 via a common message.

[0063] In some implementations, UE 315 may send one or more of capability message 320 or power status message 324 to network node 305 based on one or more triggering events. For example, in some implementations, UE 315 may send one or more of capability message 320 or power status message 324 to network node 305 during session establishment with network node 305 (e.g., during attachment) or upon handover to network node 305. Alternatively or otherwise, UE 315 may send power status message 324 based on a change in power status associated with UE 315 (e.g., due to battery usage or due to battery charging).

[0064] Network node 305 may perform predecoder selection 332 to select a predecoder from a plurality of predecoders 310. The plurality of predecoders 310 may include a first predecoder, such as an FDRSB-aware predecoder 312, and may also include a second predecoder, such as a predecoder 314 (e.g., a non-FDRSB-aware predecoder). Network node 305 may perform predecoder selection 332 according to one or more criteria. For example, network node 305 may perform predecoder selection 332 according to indication 322. In some examples, indication 322 may specify that UE 315 does not support FDRSB distortion reduction, and network node 305 may select FDRSB-aware predecoder 312 according to indication 322 specifying that UE 315 supports FDRSB distortion reduction. In some such examples, network node 305 may select FDRSB-aware predecoder 312 to compensate for UE 315's lack of support for FDRSB distortion reduction. In some other examples, instruction 322 may specify that UE 315 supports FDRSB distortion reduction, and network node 305 may select pre-decoder 314 based on instruction 322 specifying that UE 315 supports FDRSB distortion reduction. In some such examples, UE 315 may use FDRSB distortion reduction circuitry 362 to perform FDRSB distortion reduction (e.g., instead of relying on the use of FDRSB-aware pre-decoder 312 to reduce FDRSB distortion).

[0065] In some implementations, if indication 322 specifies that UE 315 supports FDRSB distortion reduction, network node 305 can perform predecoder selection 332 based on one or more auxiliary criteria. For example, in some scenarios, network node 305 can select FDRSB-aware predecoder 312 (instead of predecoder 314) to enable UE 315 to avoid power consumption associated with the operation of FDRSB distortion reduction circuitry 362 (even if UE 315 supports FDRSB distortion reduction). For example, network node 305 can perform predecoder selection 332 based on power state 326. For example, in some examples, UE 315 can (e.g., via indication 322) indicate support for FDRSB distortion reduction and can also (e.g., via power state 326) indicate a relatively low battery level, such as a first battery level that fails to exceed a battery level threshold. In some such examples, network node 305 may select FDRSB-aware pre-decoder 312 (e.g., instead of pre-decoder 314) to avoid increasing power consumption associated with the operation of FDRSB distortion reduction circuitry 362. In some other examples, UE 315 may (e.g., via indication 322) indicate support for FDRSB distortion reduction and may also (e.g., via power state 326) indicate a larger battery level, such as a second battery level exceeding a battery level threshold. In some such examples, network node 305 may select pre-decoder 314 (e.g., instead of FDRSB-aware pre-decoder 312) to facilitate enhanced signal reception associated with FDRSB distortion reduction performed by UE 315.

[0066] Alternatively, or in addition to power state 326, one or more auxiliary criteria may include one or more other criteria. For example, network node 305 may perform pre-decoder selection 332 based on FDRSB distortion measurement 301 associated with network node 305. FDRSB distortion measurement 301 may indicate the amount of FDRSB distortion associated with network node 305, such as the amount of FDRSB distortion generated by the circuitry of transmitter 306 during signal transmission. Depending on the specific implementation, FDRSB distortion measurement 301 may be performed using the hardware of network node 305 (such as a feedback chain or a comparator comparing the inputs and outputs of the frequency converter), using external equipment (such as a spectrum analyzer), using one or more other techniques, or a combination thereof.

[0067] In some examples, network node 305 may select (or is more likely to select) FDRSB-aware predecoder 312 (instead of predecoder 314) based on a relatively large FDRSB distortion measurement 301 (e.g., exceeding an FDRSB distortion threshold). For illustration, in some examples, UE 315 may (e.g., via indication 322) indicate support for FDRSB distortion reduction, and FDRSB distortion measurement 301 may indicate a relatively low amount of FDRSB distortion, such as a first FDRSB distortion that fails to exceed an FDRSB distortion threshold. In some such examples, network node 305 may select predecoder 314 (instead of FDRSB-aware predecoder 312) to avoid power consumption associated with the operation of FDRSB distortion reduction circuitry 362, which may be unnecessary or undesirable when the amount of FDRSB distortion is relatively low. In some other examples, UE 315 may (e.g., via indication 322) indicate support for FDRSB distortion reduction, and FDRSB distortion measurement 301 may indicate a larger amount of FDRSB distortion, such as a second FDRSB distortion exceeding an FDRSB distortion threshold. In some such examples, network node 305 may select FDRSB-aware pre-decoder 312 (e.g., instead of pre-decoder 314) to facilitate enhanced signal reception associated with FDRSB distortion reduction performed by UE 315.

[0068] Although the previous examples have been described with reference to FDRSB distortion measurement 301, other examples are also within the scope of this disclosure. For example, network node 305 may determine a metric based on FDRSB distortion measurement 301 and may perform predecoder selection 332 based on that metric. In some examples, the metric may correspond to an FDRSB basis metric. The FDRSB basis metric may be determined based on subtracting FDRSB distortion measurement 301 from a thermal noise level, which may be indicated to network node 305 by UE 315, such as via channel state information (CSI) reporting. In some specific implementations, network node 305 may select an FDRSB-aware predecoder 312 if the FDRSB basis metric exceeds an FDRSB basis threshold, or select a predecoder 314 if the FDRSB basis metric fails to exceed the FDRSB basis threshold.

[0069] In some examples, network node 305 may perform (or re-perform) FDRSB distortion measurement 301 based on the detection that one or more FDRSB distortion measurement criteria 303 are met. In some examples, network node 305 may perform (or re-perform) FDRSB distortion measurement 301 during a factory calibration phase, during a session establishment process with UE 315, based on a temperature or temperature change associated with the network node, based on a hardware reconfiguration associated with the network node (e.g., a change in one or more transmit antennas), based on a time interval expiring (e.g., where the time interval corresponds to a specific number of time slots), or during an offline learning phase (e.g., where the offline learning phase includes determining one or more of the following: temperature, temperature change, or number of time slots). As an illustrative example, a change in ambient temperature (e.g., since the previous FDRSB distortion measurement 301 was performed) may be associated with a change in FDRSB distortion measurement 301. Therefore, network node 305 may monitor the ambient temperature and may re-perform FDRSB distortion measurement 301 based on the detection that the change in ambient temperature exceeds a temperature change threshold. In such examples, one or more FDRSB distortion measurement criteria 303 may include detecting a change in ambient temperature exceeding a temperature change threshold. Other examples are also within the scope of this disclosure.

[0070] Network node 305 may send one or more configuration messages 330 to UE 315 indicative of predecoder selection 332 (or the result of predecoder selection 332). UE 315 may receive one or more configuration messages 330. In some specific implementations, UE 315 may perform one or more operations based on predecoder selection 332. For example, based on the selection of FDRSB-aware predecoder 312 indicated by predecoder selection 332, UE 315 may deactivate (e.g., power off) FDRSB distortion reduction circuitry 362 if FDRSB distortion reduction circuitry is active (e.g., powered on). In another example, based on the selection of predecoder 314 indicated by predecoder selection 332, UE 315 may activate (e.g., power on) FDRSB distortion reduction circuitry 362 if FDRSB distortion reduction circuitry is inactive (e.g., standby mode).

[0071] Network node 305 can transmit signal 340 (e.g., a downlink signal) to UE 315 according to pre-decoder selection 332. For example, by instructing FDRSB-aware pre-decoder 312 according to pre-decoder selection 332, network node 305 can use FDRSB-aware pre-decoder 312 to pre-decode signal 340. As another example, by instructing pre-decoder 314 according to pre-decoder selection 332, network node 305 can use pre-decoder 314 to pre-decode signal 340.

[0072] UE 315 can receive signal 340 according to pre-decoder selection 332. In some examples, UE 315 can receive signal 340 without performing FDRSB distortion reduction. For illustration, UE 315 may not support FDRSB distortion reduction (e.g., where UE 315 does not include FDRSB distortion reduction circuitry 362). In such examples, network node 305 can pre-decode signal 340 using FDRSB-aware pre-decoder 312, and UE 315 can receive signal 340 without performing FDRSB distortion reduction. In some other examples, UE 315 may support FDRSB distortion reduction, network node 305 can pre-decode signal 340 using pre-decoder 314, and UE 315 can use FDRSB distortion reduction (e.g., via FDRSB distortion reduction circuitry 362) to receive signal 340. In some additional examples, UE 315 may support FDRSB distortion reduction, network node 305 may pre-decode signal 340 using FDRSB-aware pre-decoder 312 (e.g., based on one or more of power state 326 or FDRSB distortion measurement 301 as described above), and UE 315 may receive signal 340 without performing FDRSB distortion reduction (e.g., to avoid power consumption associated with the operation of FDRSB distortion reduction circuitry 362).

[0073] UE 315 can determine whether to use (or not use) the FDRSB distortion reduction circuitry 362 to receive signal 340 based on one or more criteria. For example, after sending capability message 320 and before receiving signal 340, UE 315 can receive an FDRSB power estimation message 334 from network node 305 indicating an estimate 336 of the FDRSB power associated with signal 340. UE 315 can perform a determination of whether the estimated FDRSB power 336 exceeds an FDRSB power threshold 360, and can receive signal 340 based on this determination. For example, if the estimated FDRSB power 336 exceeds the FDRSB power threshold 360, UE 315 can use FDRSB distortion reduction to receive signal 340, such as by demodulating signal 340 using the FDRSB distortion reduction circuitry 362. As another example, if the estimated FDRSB power 336 fails to exceed the FDRSB power threshold 360, the UE 315 may receive the signal 340 without using FDRSB distortion reduction, such as by operating the FDRSB distortion reduction circuitry 362 in standby or inactive mode when receiving the signal 340.

[0074] In some examples, network node 305 can report an estimate 336 of FDRSB power based on pre-decoder selection 332. For example, if pre-decoder 314 is used to pre-decode signal 340, the estimate 336 of FDRSB power can be reported frequency-wise for multiple frequencies (because, for example, when pre-decoder 314 is used to pre-decode signal 340, the FDRSB power can vary based on frequency, as referenced). Figure 4 (Further description). As another example, if the signal 340 is to be pre-decoded using the FDRSB-aware pre-decoder 312, a single value can be used to report an estimate 336 of the FDRSB power (because, for example, when the signal 340 is pre-decoded using the FDRSB-aware pre-decoder 312, the FDRSB power can be constant or substantially constant for different frequencies, as described in reference). Figure 4 (Further description).

[0075] Alternatively, or in addition to using the FDRSB power estimate 336, UE 315 may determine whether to use the FDRSB distortion reduction circuitry 362 to receive signal 340 based on one or more other metrics. For example, in some scenarios, UE 315 may use the FDRSB distortion reduction circuitry 362 to receive signal 340 based on determining that an error metric (e.g., error magnitude vector) associated with signal 340 exceeds an error threshold. In some other scenarios, UE 315 may receive signal 340 without using the FDRSB distortion reduction circuitry 362 based on determining that the error metric fails to exceed the error threshold. Alternatively, or in addition, UE 315 may use the FDRSB distortion reduction circuitry 362 to receive signal 340 based on determining that an FDRSB base metric exceeds an FDRSB base threshold. In some other scenarios, UE 315 may receive signal 340 without using the FDRSB distortion reduction circuitry 362 based on determining that the FDRSB base metric fails to exceed the FDRSB base threshold.

[0076] In some cases, network node 305 may switch between multiple predecoders 310 during a communication session with UE 315, such as in response to a change in power state 326 reported by UE 315 or in response to one or more other events. For example, after transmitting signal 340 using one of the multiple predecoders 310, network node 305 may transmit another signal using another of the multiple predecoders 310. In such cases, network node 305 may send an update of predecoder selection 332 to UE 315 to indicate the change of predecoder.

[0077] In some examples, signal 340 may include or correspond to a downlink signal, such as a Physical Downlink Shared Channel (PDSCH) signal or a Physical Downlink Control Channel (PDCCH) signal. Other examples are also within the scope of this disclosure. For example, in some implementations, UE 315 may use an FDRSB-aware pre-decoder to pre-decode an uplink signal, and network node 305 may use FDRSB distortion reduction to receive the uplink signal. As an illustrative example, the uplink signal may correspond to a Physical Uplink Shared Channel (PUSCH) signal or a Physical Uplink Control Channel (PUCCH) signal. Furthermore, in some implementations, UE 315 may use an FDRSB-aware pre-decoder to pre-decode a sidelink signal, and another UE may use FDRSB distortion reduction to receive the sidelink signal. As an illustrative example, the sidelink signal may correspond to a Physical Sidelink Shared Channel (PSSCH) signal, a Physical Sidelink Control Channel (PSCCH) signal, or a Physical Sidelink Feedback Channel (PSFCH) signal. Therefore, although this document has described some examples with reference to signaling from network node 305 to UE 315 (or vice versa), such examples also apply to signaling from UE 315 to network node 305 (or vice versa) and to signaling from UE 315 to another UE (or vice versa).

[0078] In some implementations, UE 315 may send a request to network node 305 to use FDRSB-aware pre-decoder 312. For example, instead of sending capability message 320 and power status message 324, UE 315 may send this request to network node 305 to request the use of FDRSB-aware pre-decoder 312. In some examples, the request may include or correspond to a flag (e.g., a bit) having either a first value requesting FDRSB-aware pre-decoder 312 or a second value requesting pre-decoder 314. Furthermore, in some examples, UE 315 may set this flag based on one or more of UE 315's FDRSB distortion reduction capability, power status 326, or an estimate of FDRSB power 336.

[0079] Figure 4 Example graph 400 illustrates some aspects of FDRSB-aware pre-decoding. Figure 4 In the example, the horizontal axis can indicate the frequency of signal 340, which can be measured in megahertz (MHz), and the vertical axis can indicate the signal-to-FDRSB noise ratio (SFNR) associated with the received version of signal 340, which can be measured in decibels (dB). Note that the provided... Figure 4 The examples provided are for illustrative purposes, and other examples are also within the scope of this disclosure. Therefore, Figure 4 The examples depicted are illustrative rather than limiting.

[0080] exist Figure 4 In this configuration, the FDRSB-aware pre-decoder 312 may be associated with a flat or nearly flat average SFNR, and the pre-decoder 314 may be associated with a substantially non-flat SFNR. For example, the average SFNR 402 of signal 340 when pre-decoded using the FDRSB-aware pre-decoder 312 may have a first slope, and the average SFNR 404 of signal 340 when pre-decoded using the pre-decoder 314 may have a second slope less than the first slope. In some examples, the first slope may be zero or nearly zero, and the second slope may be negative. Therefore, using the FDRSB-aware pre-decoder 312 can achieve an improved (e.g., more balanced) SFNR compared to using the pre-decoder 314.

[0081] To further illustrate some aspects of this disclosure, in some specific embodiments, the FDRSB impaired signal can be represented as And it can be expressed using Equation 1: (Equation 1).

[0082] The FDRSB impaired signal can correspond to signal 340 before pre-decoding using the FDRSB-aware pre-decoder 312 (or without pre-decoding using the FDRSB-aware pre-decoder 312). In some examples, the FDRSB impaired signal... This corresponds to signal 340 after pre-decoding. Furthermore, It can represent frequency. This can represent the amount of FDRSB damage associated with signal 340, and ( )= ( ) ( ) can represent the pre-decoded signal 340, where ( ) can represent a pre-decoder, and where ( This can represent the data to be transmitted via signal 340. Furthermore, It can represent the complex conjugate operator.

[0083] The FDRSB damage quantity can also be expressed as = ,in A first parameter (e.g., phase) may be indicated as associated with the in-phase (I) component of signal 340, and wherein A second parameter (e.g., phase) may be indicated as associated with the quadrature (Q) component of signal 340. In some cases, the first parameter may differ from the second parameter, resulting in FDRSB impairment. For example, the modulator of transmitter 306 may include an I-mixer and a Q-mixer. A lack of synchronization between the I-mixer and the Q-mixer may cause the first parameter to differ from the second parameter, resulting in FDRSB impairment.

[0084] Equation 1 can also be expressed as Equation 2: (Equation 2).

[0085] The SFNR associated with the FDRSB impaired signal can be expressed as: And it can be expressed using Equation 3: (Equation 3).

[0086] In equation 3, It can represent and ( The associated variance. To reduce FDRSB impairment, pre-decoding of signal 340 can be used to balance the SFNR at the frequency and its mirror frequency (e.g., the frequency multiplied by negative one), such as according to Equation 4: (Equation 4).

[0087] Therefore, pre-decoding of signal 340 can be performed according to Equation 5: (Equation 5).

[0088] After pre-decoding signal 340 according to Equation 5, each pair of frequencies can be balanced (e.g., the frequency and its mirror frequency, such as the frequency multiplied by negative one), and each pair of pre-decoder frequency gradations. and This can produce equation 6: (Equation 6)

[0089] In equation 6, It can be symmetrical (or approximately symmetrical) for different frequencies, but it can be non-constant for different frequencies. In some specific implementations, the gain stage can be used to increase... For balancing at different frequencies (e.g., by achieving a constant or near-constant SFNR over a frequency range). In some other implementations, the gain stage can be omitted. The gain stage can be calculated according to Equation 7: (Equation 7).

[0090] In equation 7, c(f) Gain levels can represent (e.g., the set of coefficients for a gain level). Alternatively, or in addition to using gain levels, the transmitter can operate according to Equation 8, where each pre-decoder frequency grid can be multiplied by a value. This value can be a real scalar value common to each pre-decoder frequency grid. This value can be indicated as... Using this value can increase Balance in the frequency domain (e.g., by achieving a constant or near-constant SFNR over a frequency range), such as that indicated by Equation 8: (Equation 8)

[0091] The pre-decoder described with reference to Equation 8 can correspond to FDRSB-sensing pre-decoder 312. For example, when multiplying each pre-decoder frequency by a value ( Afterwards, the pre-decoder can increase the balance of FDRSB across frequency ranges, such as... Figure 4 As illustrated in the examples (e.g., as described by the average SFNR 402 when the reference signal 340 is pre-decoded using the FDRSB-aware pre-decoder 312). Therefore, when the signal 340 is pre-decoded using the FDRSB-aware pre-decoder 312, implementing the FDRSB-aware pre-decoder 312 according to Equations 1 to 8 can improve the performance within the wireless communication system 300.

[0092] Furthermore, the FDRSB distortion reduction circuit 362 can be implemented using one or more techniques to enable the UE 315 to reduce FDRSB distortion that may be associated with the signal 340. In some specific implementations, the received version of the signal 340 received by the UE 315 can be indicated as And it can be expressed using Equation 9: (Equation 9)

[0093] In equation 9, ... It can represent the Hadamard multiplication operator (also known as the element-wise multiplication operator). This can represent the channel used to transmit signal 340. Equation 9 can also be expressed as Equation 10: , in

[0094] and (Equation 10).

[0095] In equation 9, This can indicate the noise component or other parameters associated with the received version of signal 340. UE 315 can estimate the amount of FDRSB impairment, such as according to Equation 11: (Equation 11).

[0096] also, For a given number N subcarriers (SC), they can remain constant or approximately constant, which can be expressed using equations 12 and 13: (Equation 12).

[0097] (Equation 13).

[0098] After averaging, interpolation can be performed on the SCs to estimate the FDRSB curve in each SC. After estimating the FDRSB curve, UE 315 can use the estimated curves... To remove the effects of FDRSB (correction steps), such as according to Equation 14: (Equation 14).

[0099] In equation 14, It can indicate the first received version of signal 340 before performing FDRSB distortion reduction, and This can indicate a second received version of signal 340 after FDRSB distortion reduction is performed. In Equation 14, estimation_error can indicate an error metric associated with one or more operations, such as channel estimation, FDRSB distortion reduction, one or more other operations, or a combination thereof. Therefore, in some specific implementations, the FDRSB distortion reduction circuit 362 can be configured to remove (or reduce) distortion in signal 340 by means of, for example, removing (or reducing) distortion in signal 340 according to Equation 14. To reduce or eliminate FDRSB distortion in signal 340.

[0100] One or more features described herein can improve performance within the wireless communication system 300. For example, by selecting from multiple pre-decoders 310, network node 305 can achieve FDRSB reduction while also promoting enhanced performance within the wireless communication system 300 (e.g., by saving power at network node 305, UE 315, or both). For example, in some scenarios, network node 305 can use an FDRSB-aware pre-decoder 312 to perform FDRSB reduction at network node 305, such as in response to one or more of the following: UE 315 does not support UE-side FDRSB reduction, UE 315 is associated with relatively low battery power, or the amount of FDRSB distortion is relatively large. In some other scenarios, network node 305 can select pre-decoder 314 and can "offload" or "delegate" the decision on whether to use FDRSB distortion reduction to UE 315, such as in response to one or more of the following: UE 315 supports UE-side FDRSB reduction, UE 315 is associated with relatively high battery power, or the amount of FDRSB distortion is relatively low. Therefore, FDRSB distortion reduction can be enabled for various situations, including for UEs that support UE-side FDRSB reduction and for UEs that do not support UE-side FDRSB reduction.

[0101] To further illustrate, by reducing the variability of SFNR (such as...) Figure 4 As illustrated in the examples, performance can be improved in wireless communication system 300. For instance, in some wireless communication protocols, the modulation and decoding scheme (MCS) may be based on, or may be affected by, the "worst-case" SFNR. In such cases, greater variability in the SFNR may limit the MCS or the range of MCSs available for data transmission. By reducing the variability of the SFNR (e.g., by balancing, smoothing, or flattening the SFNR over a frequency range), instances of such "worst-case" SFNRs can be reduced or eliminated, which can facilitate the use of a wider range of MCSs for data transmission.

[0102] Figure 5 This is a flowchart illustrating an example process 500 for supporting FDRSB-aware pre-decoding according to one or more aspects. In some examples, a UE (e.g., UE 315) may perform process 500 to communicate with a network node (such as network node 305). In some other examples, a network node may perform process 500 to communicate with a UE. In some additional examples, a UE may perform process 500 to communicate with another UE.

[0103] Procedure 500 includes sending a capability message at 502, which includes an indication of whether the device supports reduction of frequency-dependent vestigial sideband (FDRSB) distortion for the received signal. For example, UE 315 may send capability message 320, which includes an indication 322 of whether UE 315 supports reduction of FDRSB distortion. In such examples, the device described with reference to procedure 500 may correspond to UE 315. In some other examples, the device may correspond to another entity, such as network node 305 (e.g., where network node 305 performs procedure 500).

[0104] Process 500 also includes receiving a signal at 504 that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on an indication of whether the device supports FDRSB distortion reduction. For example, UE 315 may receive signal 340, and signal 340 may be pre-decoded using either FDRSB-aware pre-decoder 312 or pre-decoder 314, based on indication 322.

[0105] Figure 6 This is a flowchart illustrating another example process 600 for supporting FDRSB-aware pre-decoding according to one or more aspects. In some examples, a network node (e.g., network node 305) may perform process 600 to communicate with a UE (e.g., UE 315). In some other examples, a UE may perform process 600 to communicate with a network node or with another UE.

[0106] Procedure 600 includes receiving a capability message at 602, which includes an indication of whether the device supports reduction of frequency-dependent vestigial sideband (FDRSB) distortion for the received signal. For example, network node 305 may receive capability message 320, which includes an indication 322 of whether UE 315 supports FDRSB distortion reduction. In such examples, the device described with reference to procedure 600 may correspond to UE 315. In some other examples, the device may correspond to another entity, such as network node 305 (e.g., where UE 315 performs procedure 600).

[0107] Process 600 also includes transmitting a signal at 604 that pre-decodes using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on an indication of whether the device supports FDRSB distortion reduction. For example, network node 305 may transmit signal 340, and signal 340 may pre-decode using either FDRSB-aware pre-decoder 312 or pre-decoder 314, based on indication 322.

[0108] Figure 7This is a block diagram of an example UE 315 that supports FDRSB-aware pre-decoding based on one or more aspects. UE 315 may include Figure 2 , Figure 3 Or the structures, hardware, or components illustrated herein. For example, UE 315 may include controller 280, which can execute instructions stored in memory 282. Using controller 280, UE 315 can transmit and receive signals via wireless radio components 701a-r and antennas 252a-r. Wireless radio components 701a-r may include one or more components or devices described herein, such as modulator / demodulator 254a-r, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, transmitter 356, receiver 358, one or more other components or devices, or combinations thereof.

[0109] In some examples, memory 282 may store instructions executable by one or more processors (e.g., controller 280) to initiate, perform, or control one or more operations described herein. For example, memory 282 may store FDRSB distortion reduction mode selection instructions 702, which can be executed by controller 280 to determine whether to use FDRSB distortion reduction circuitry 362 to perform FDRSB distortion reduction on one or more received signals (such as signal 340). In some examples, UE 315 may perform this determination based on a comparison of an estimated FDRSB power 336 with an FDRSB power threshold 360. As another example, memory 282 may store FDRSB distortion reduction instructions 704, which can be executed by controller 280 to initiate, perform, or control FDRSB distortion reduction, such as by setting the value of a control signal destined for FDRSB distortion reduction circuitry 362. The control signal may have a first value for activating the FDRSB distortion reduction circuit 362 (e.g., to receive signal 340 using FDRSB distortion reduction) or a second value for deactivating the FDRSB distortion reduction circuit 362 (e.g., to receive signal 340 without FDRSB distortion reduction).

[0110] Figure 8 This is a block diagram of an example network node 305 supporting FDRSB-aware pre-decoding according to one or more aspects. Network node 305 may include... Figure 2 , Figure 3Or the structures, hardware, and components exemplified herein. For example, network node 305 may include controller 240, which can execute instructions stored in memory 242. Under the control of controller 240, network node 305 may transmit and receive signals via wireless radio components 801a-t and antenna 234a-t. Wireless radio components 801a-t may include one or more components or devices described herein, such as modulator / demodulator 232a-t, MIMO detector 236, receive processor 238, transmit processor 220, TX MIMO processor 230, one or more other components or devices, or combinations thereof.

[0111] In some examples, memory 242 may store instructions executable by one or more processors (e.g., controller 240) to initiate, perform, or control one or more operations described herein. For example, memory 242 may store predecoder selection instructions 802, which can be executed by controller 240 to, for example, according to... Figure 3 Instruction 322 selects from a plurality of pre-decoders 310. As another example, memory 242 may store FDRSB distortion measurement instructions 804, which can be executed by controller 240 to, for example, according to... Figure 3 One or more FDRSB distortion measurement criteria 303 are used to initiate, execute, or control the execution of FDRSB distortion measurement 301.

[0112] According to some other examples, in a first aspect, an apparatus for wireless communication includes a receiver and a transmitter. The transmitter is configured to transmit a capability message including an indication of whether the receiver supports frequency-dependent vestigial sideband (FDRSB) distortion reduction for a received signal. The receiver is configured to receive a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, at least based on the indication of whether the receiver supports FDRSB distortion reduction.

[0113] In a second aspect, in conjunction with the first aspect, the first predecoder corresponds to an FDRSB-aware predecoder, and the second predecoder corresponds to a non-FDRSB-aware predecoder.

[0114] In a third aspect, in combination with one or more of the first or second aspects, a designated receiver is indicated to support FDRSB distortion reduction, and the receiver includes FDRSB distortion reduction circuitry configured to apply FDRSB distortion reduction to a signal.

[0115] In a fourth aspect, in combination with one or more of the first to third aspects, it is indicated that the designated receiver does not support FDRSB distortion reduction, and the receiver is further configured to receive the signal without applying FDRSB distortion reduction to the signal.

[0116] In a fifth aspect, in combination with one or more of the first to fourth aspects, the receiver is further configured to receive a configuration message indicating the selection of one of the first or second pre-decoders after transmitting the capability message and before receiving the signal, and to receive the signal according to the pre-decoder selection.

[0117] In a sixth aspect, in combination with one or more of the first to fifth aspects, the transmitter is further configured to transmit a power status message indicating a power status associated with the device, and further pre-decode the signal using one of a first pre-decoder or a second pre-decoder based on the power status message.

[0118] In a seventh aspect, in combination with one or more of the first to sixth aspects, the receiver is further configured to receive an FDRSB power estimation message indicating an estimate of the FDRSB power associated with the signal after transmitting the capability message and before receiving the signal, and to receive the signal based on determining whether the estimate of the FDRSB power exceeds an FDRSB power threshold.

[0119] In the eighth aspect, in combination with one or more of the first to seventh aspects, the estimated amount of FDRSB power exceeds the FDRSB power threshold, and the receiver is further configured to receive the signal using FDRSB distortion reduction.

[0120] In the ninth aspect, in combination with one or more of the first to eighth aspects, the estimated amount of FDRSB power fails to exceed the FDRSB power threshold, and the receiver is further configured to receive the signal without using FDRSB distortion reduction.

[0121] In a tenth aspect, a method of wireless communication performed by a device includes transmitting a capability message including an indication of whether the device supports frequency-dependent vestigial sideband (FDRSB) distortion reduction for a received signal. The method also includes receiving a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, at least based on the indication of whether the device supports FDRSB distortion reduction.

[0122] In the eleventh aspect, in conjunction with the tenth aspect, the designated device is instructed to support FDRSB distortion reduction, and receiving the signal includes using the device's FDRSB distortion reduction circuitry to apply FDRSB distortion reduction to the signal.

[0123] In the twelfth aspect, in combination with one or more of the tenth to eleventh aspects, it is indicated that the designated device does not support FDRSB distortion reduction and receives the signal without applying FDRSB distortion reduction to the signal.

[0124] In the thirteenth aspect, in combination with one or more of the tenth to twelfth aspects, the method further includes receiving a configuration message indicating the selection of one of the first predecoders or the second predecoder after transmitting the capability message and before receiving the signal, and receiving the signal according to the predecoder selection.

[0125] In the fourteenth aspect, in combination with one or more of the tenth to thirteenth aspects, the method further includes sending a power status message indicating the power status of the device, and further pre-decoding the signal using one of a first pre-decoder or a second pre-decoder based on the power status message.

[0126] In a fifteenth aspect, in combination with one or more of aspects ten through fourteen, the method further includes receiving an FDRSB power estimation message indicating an estimated amount of FDRSB power associated with the signal after transmitting the capability message and before receiving the signal. The method further includes performing a determination of whether the estimated amount of FDRSB power exceeds an FDRSB power threshold. Based on the determination, the signal is received.

[0127] In the sixteenth aspect, in combination with one or more of the tenth to fifteenth aspects, the estimated FDRSB power exceeds the FDRSB power threshold, and FDRSB distortion reduction is used to receive the signal.

[0128] In the seventeenth aspect, in combination with one or more of the tenth to sixteenth aspects, the estimated amount of FDRSB power fails to exceed the FDRSB power threshold, and the signal is received without using FDRSB distortion reduction.

[0129] In an eighteenth aspect, an apparatus for wireless communication includes a receiver configured to receive a capability message including an indication of whether the device supports reduction of frequency-dependent vestigial sideband (FDRSB) distortion for a received signal. The apparatus also includes a transmitter configured to transmit a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on the indication of whether the device supports reduction of FDRSB distortion.

[0130] In the nineteenth aspect, in conjunction with the eighteenth aspect, the transmitter is further configured to transmit a configuration message indicating the selection of a predecoder for either the first or the second predecoder based on FDRSB distortion measurements.

[0131] In aspect 20, in combination with one or more of aspects 18 to 19, the FDRSB distortion measurement is associated with at least one of the following: factory calibration phase, session establishment process with the device, temperature associated with the device, temperature change, hardware reconfiguration associated with the device, time interval expiration, or offline learning phase.

[0132] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0133] The components, functional blocks, and modules described herein may include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, and any combination thereof. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, and other examples, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. Furthermore, the features discussed herein may be implemented via processor circuitry, via executable instructions, or a combination thereof.

[0134] Those skilled in the art will further appreciate that the various exemplary logic blocks, modules, circuits, and operations described herein can be implemented as electronic hardware, computer software, or a combination of both. For illustrative purposes, various exemplary components, blocks, modules, circuits, and operations have been generally described above in their functional form. Whether such functionality is implemented as hardware or software can depend on the specific application and design of the entire system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as causing a departure from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein is exemplary, and that components, methods, or interactions of various aspects of this disclosure can be combined or performed in ways other than those illustrated and described herein.

[0135] Hardware and data processing means for implementing the various exemplary logic units, logic blocks, modules, and circuits described herein can be implemented or executed using single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof designed to perform the functions described herein. The processor can be a microprocessor, controller, microcontroller, state machine, or other type of processor. In some embodiments, the processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some embodiments, specific processes and methods may be performed by circuitry specific to a given function.

[0136] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.

[0137] If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted through a computer-readable medium. The procedures of the methods or processes disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and accessible to a computer. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically reproduce data, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operation of a method or process may reside as one of codes and instructions, or any combination or set of codes and instructions, on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.

[0138] Various modifications to the specific embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other specific embodiments without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the specific embodiments shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features thereof.

[0139] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positioning on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0140] Certain features described in this specification in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as operating in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0141] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the indicated specific order or sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be combined with the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any illustrated operation. In some contexts, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems may be integrated together in a single software product or packaged into multiple software products. Additionally, some other embodiments also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

[0142] As used herein (including the claims), the term “or” in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing component A, B, or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Furthermore, as used herein (including the claims), “or” in a list of items beginning with “at least one of” indicates a separate list, such that a list such as “at least one of A, B, or C” refers to A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these items. The term “substantially” is defined as being substantially, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed specific implementation, the term “substantially” may be used in place of “[percentage]” for the specified content, where the percentage includes 0.1%, 1%, 5% or 10%.

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

Claims

1. An apparatus for wireless communication, the apparatus comprising: Receiver; and A transmitter configured to transmit a capability message including an indication of whether the receiver supports reduction of frequency-dependent vestigial sideband (FDRSB) distortion of the received signal. The receiver is configured to receive a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on the indication of whether the receiver supports the FDRSB distortion reduction.

2. The apparatus of claim 1, wherein the first predecoder corresponds to an FDRSB-aware predecoder, and wherein the second predecoder corresponds to a non-FDRSB-aware predecoder.

3. The apparatus of claim 1, wherein the indication specifies that the receiver supports the FDRSB distortion reduction, and wherein the receiver includes FDRSB distortion reduction circuitry configured to apply the FDRSB distortion reduction to the signal.

4. The apparatus of claim 1, wherein the indication specifies that the receiver does not support the FDRSB distortion reduction, and wherein the receiver is further configured to receive the signal without applying the FDRSB distortion reduction to the signal.

5. The apparatus of claim 1, wherein the receiver is further configured to receive a configuration message indicating a predecoder selection of one of the first predecoder or the second predecoder after sending the capability message and before receiving the signal, and wherein the signal is received according to the predecoder selection.

6. The apparatus of claim 1, wherein the transmitter is further configured to transmit a power state message indicating a power state associated with the apparatus, and wherein the signal is further pre-decoded using one of the first pre-decoder or the second pre-decoder based on the power state message.

7. The apparatus of claim 1, wherein the receiver is further configured to: After sending the capability message and before receiving the signal, an FDRSB power estimation message indicating an estimate of the FDRSB power associated with the signal is received; and The signal is received based on whether the estimated FDRSB power exceeds the FDRSB power threshold.

8. The apparatus of claim 7, wherein the estimated amount of FDRSB power exceeds the FDRSB power threshold, and wherein the receiver is further configured to receive the signal using the FDRSB distortion reduction.

9. The apparatus of claim 7, wherein the estimated amount of FDRSB power fails to exceed the FDRSB power threshold, and wherein the receiver is further configured to receive the signal without using the FDRSB distortion reduction.

10. A method for wireless communication performed by a device, the method comprising: Send a capability message, the capability message including an indication of whether the device supports reduction of frequency-dependent vestigial sideband (FDRSB) distortion for the received signal; as well as A received signal is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on the indication of whether the device supports the FDRSB distortion reduction.

11. The method of claim 10, wherein the indication specifies that the device supports the FDRSB distortion reduction, and wherein receiving the signal includes using the FDRSB distortion reduction circuitry of the device to apply the FDRSB distortion reduction to the signal.

12. The method of claim 10, wherein the indication specifies that the device does not support the FDRSB distortion reduction, and wherein the signal is received without applying the FDRSB distortion reduction to the signal.

13. The method of claim 10, further comprising receiving a configuration message indicating a predecoder selection of either the first predecoder or the second predecoder after sending the capability message and before receiving the signal, wherein the signal is received according to the predecoder selection.

14. The method of claim 10, further comprising sending a power status message indicating the power status of the device, wherein the signal is further pre-decoded using one of the first pre-decoder or the second pre-decoder based on the power status message.

15. The method according to claim 10, further comprising: After sending the capability message and before receiving the signal, an FDRSB power estimation message indicating an estimate of the FDRSB power associated with the signal is received; as well as Perform the determination of whether the estimated FDRSB power exceeds the FDRSB power threshold. The signal is received according to the determination.

16. The method of claim 15, wherein the estimated amount of FDRSB power exceeds the FDRSB power threshold, and wherein the FDRSB distortion reduction is used to receive the signal.

17. The method of claim 15, wherein the estimated amount of FDRSB power fails to exceed the FDRSB power threshold, and wherein the signal is received without using the FDRSB distortion reduction.

18. An apparatus for wireless communication, the apparatus comprising: The receiver is configured to receive capability messages, the capability messages including an indication of whether the device supports reduction of frequency-dependent vestigial sideband (FDRSB) distortion for the received signal; and A transmitter configured to transmit a signal that is pre-decoded using either a first pre-decoder or a second pre-decoder other than the first pre-decoder, based at least on an indication of whether the device supports the FDRSB distortion reduction.

19. The apparatus of claim 18, wherein the transmitter is further configured to transmit a configuration message indicating predecoder selection for either the first predecoder or the second predecoder based on FDRSB distortion measurements.

20. The apparatus of claim 19, wherein the FDRSB distortion measurement is associated with at least one of the following: a factory calibration phase, a session establishment process with the device, a temperature associated with the device, a change in the temperature, a hardware reconfiguration associated with the device, an expiration of a time interval, or an offline learning phase.

Images