Improved power and spectral efficiency based on addition of odd order modulation

Abstract

Aspects are provided that allow a network entity, such as a base station, to configure odd modulation orders to be applied to downlink or uplink transmissions via signaling between the network entity and a UE. Initially, the network entity sends a configuration to the UE indicating network support for communications using odd order modulation. Thereafter, the UE transmits data in the signal using the odd order modulation, and the network entity receives the data. Thus, based on network support configured for such odd order modulation, improved SPEF, PAPR reduction, and phase noise mitigation associated with odd order modulation may be achieved by applying odd order modulation to data transmission or reception.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 931,019, filed on September 9, 2022, entitled “IMPROVED POWER AND SPECTRALEFFICIENCY BASED ON ADDING ODD ORDER MODULATIONS,” which is assigned to the assignee of the present invention and is incorporated herein by reference in its entirety. Background Art Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems between user equipment (UE) and network entities or devices such as base stations.

[0004] introduction

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0007] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE. The UE receives a configuration indicating network support for communications using odd-order modulation, and the UE sends data in a signal using odd-order modulation.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a network entity. The network entity sends a configuration indicating network support for communications using odd-order modulation, and the network entity receives data in a signal using odd-order modulation.

[0010] To achieve the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this specification is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1A is a diagram illustrating an example of a wireless communication system and an access network.

[0012] Figure 1B is a conceptual diagram of an example open radio access network architecture.

[0013] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0014] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0016] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0017] Figure 3 is a diagram illustrating an example of network devices such as a base station and a user equipment (UE) in an access network.

[0018] FIG. 4A to FIG. 4C An example of a non-square Quadrature Amplitude Modulation (QAM) constellation diagram is illustrated.

[0019] Figure 5 Examples of a modulation and coding scheme (MCS) table including an MCS having an even modulation order and various code rates and an extended MCS table including an MCS having an odd modulation order and various code rates are illustrated.

[0020] Figure 6 An example of a call flow between a UE and a network device such as a base station for an odd modulation order to be applied in downlink or uplink communication is illustrated.

[0021] Figure 7 An example of a graph showing spectral efficiency (SPEF) improvement due to odd modulation orders based on the relationship between signal-to-noise ratio (SNR) and block error rate (BLER) is illustrated.

[0022] Figure 8 An example of a graph showing SPEF improvement from odd modulation orders based on the relationship between SNR and throughput is illustrated.

[0023] Fig. 9 An example of a graph showing improvement in peak to average power ratio (PAPR) for an odd modulation order configuration relative to an even modulation order configuration is illustrated.

[0024] Fig.10 An example of a non-square QAM constellation diagram indicating phase noise resilience is illustrated.

[0025] Fig.11 An example of a graph showing the performance improvement achieved by odd modulation orders compared to even modulation orders in a single carrier waveform is illustrated.

[0026] Fig.12 An example of a graph showing the performance improvement achieved by odd modulation orders compared to even modulation orders in an Orthogonal Frequency Division Multiplexing (OFDM) waveform is illustrated.

[0027] Fig.13 is a flow chart of a method of performing wireless communication at a UE.

[0028] Fig.14 is a flow chart of a method of wireless communication at a network entity such as a base station.

[0029] Fig.15 is a diagram illustrating an example of a hardware implementation of an example apparatus.

[0030] Fig.16 is a diagram illustrating another example of a hardware implementation for another example apparatus. DETAILED DESCRIPTION

[0031] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0032] In general, a network device (such as a base station) modulates data intended to be sent to a UE using a modulation and coding scheme (MCS) associated with an even modulation order. For example, when modulating downlink data to be transmitted to a UE, the network device may apply quadrature phase shift keying (QPSK) (modulation order = 2) or square quadrature amplitude modulation (square QAM), such as 16QAM (modulation order = 4), 64QAM (modulation order = 6), or 256QAM (modulation order = 8). Currently, network devices are limited to applying even modulation orders rather than odd modulation orders (e.g., modulation orders 3, 5, 7, 9, etc., such as non-square QAM or amplitude and phase shift keying (APSK)), because demodulation of a signal including an even modulation order is relatively simple compared to a signal including an odd modulation order. However, methods have been developed to reduce the complexity in demodulation of odd-order modulated signals. For example, to achieve simplified soft demapping of non-square QAM, the geometric trend of non-square QAM constellations and the folding overlap method can be used to allow the nonlinear log-likelihood ratio (LLR) equation based on the maximum logarithm maximum a posteriori (MAP) algorithm to be approximated as a linear equation, thereby significantly reducing the computational complexity.

[0033] However, while the UE may have the ability to demodulate odd-order modulated signals to reduce complexity due to these methods, this capability may not be used without some coordination with network equipment (e.g., base station) to apply odd-order modulation. Since odd-order modulation may provide increased spectral efficiency granularity, improved peak-to-average power ratio (PAPR), and improved phase noise mitigation compared to even-order modulation, it would be helpful if more MCSs could be configured to allow odd-order modulation to be applied to downlink or uplink signaling.

[0034] Therefore, various aspects of the present disclosure allow a network device to configure an odd modulation order to be applied to a downlink or uplink transmission via signaling between the network device and the UE. For example, the network device may send configuration information indicating support for odd-order modulation to the UE. Then, the network device and the UE may communicate using odd-order modulation. In this way, odd-order modulation between the UE and the network device may be facilitated, thereby allowing increased spectral efficiency granularity, improved PAPR, and / or improved phase noise mitigation compared to even-order modulation. In one example, if the UE is currently communicating with the network device using even-order modulation in one MCS table, but the UE is capable of demodulating odd-order modulated signals, the UE may request the network device to switch from the MCS table to a different MCS table (extended MCS table) including MCS associated with odd-order modulation and even-order modulation. Therefore, a UE capable of receiving an odd-order modulated signal may benefit from an associated SPEF improvement with an odd modulation order. In another example, if the UE is also capable of correcting phase noise, the UE may transmit this request to the network device to apply an extended MCS table, thereby similarly benefiting from improved phase noise resilience. In another example, if the UE is located at the cell edge but includes the ability to demodulate odd-order modulated signals, the UE can request the network device to switch to an extended MCS table to result in a lower PAPR. This lower PAPR can in turn allow the UE's transmit power to be increased by 0.8 dB, thereby providing a significant improvement in signal quality at the cell edge.

[0035] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0036] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc.

[0037] Therefore, in one or more example embodiments, the described functions can be implemented with hardware, software or any combination thereof. If implemented in software, the function can be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), an optical disk storage device, a magnetic disk storage device, other magnetic storage devices, a combination of computer-readable media of the above type, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0038] Figure 1A 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0039] The base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (eg, via the EPC 160 or the core network 190) via the third backhaul link 134 (eg, an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0040] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between base station 102 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in the carrier aggregation for up to a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 can use spectrum with a bandwidth of up to Y megahertz (MHz) (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0041] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0042] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, a 5 gigahertz (GHz) unlicensed spectrum. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0043] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0044] 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 identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0045] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used in this document, it can broadly represent a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used in this document, it can broadly represent a frequency that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0046] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0047] Base station 180 may transmit beamformed signals in one or more transmit directions 182' to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0048] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, an MBMS gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service configuration and delivery. BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services in a public land mobile network (PLMN), and may be used to schedule MBMS delivery. MBMS gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area of ​​a broadcast specific service, and may be responsible for session management (start / stop) and for collecting eMBMS related billing information.

[0049] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides quality of service (QoS) flow and session management. All user IP packets are delivered through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IMS, a packet switching (PS) streaming service, and / or other IP services.

[0050] Base stations may include and / or be referred to as gNBs, Node Bs, eNBs, access points, base transceivers, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), transmit receive points (TRPs), or some other suitable terminology. Base stations 102 provide access points to EPC 160 or core network 190 for UEs 104. Examples of UEs 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0051] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a network device, a mobility element of a network, a RAN node, a core network node, a network element or network equipment such as a BS or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an eNB, an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.

[0052] The aggregated base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station 181 may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, the CU 183 may be implemented within a RAN node, and one or more DUs 185 may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. The DU may be implemented to communicate with one or more RUs 187. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0053] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0054] Although the present disclosure may focus on 5G NR, the concepts and aspects described herein may be applicable to other similar areas such as LTE, Advanced LTE (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), and / or other wireless / radio access technologies.

[0055] Reference again Figure 1A In some aspects, the UE 104 may include an odd-order modulation (OOM) signal component 198 configured to receive a configuration indicating network support for communications using odd-order modulation, and to transmit data in a signal using odd-order modulation. In some aspects, the base station 102 / 180 (or other network device having base station functionality) may include an OOM signal configuration component 199 configured to transmit a configuration indicating network support for communications using odd-order modulation, and to receive data in a signal using odd-order modulation.

[0056] Figure 1BA diagram illustrating an example decomposed base station 181 architecture is shown. The decomposed base station 181 architecture may include one or more CUs 183, which may communicate directly with the core network 190 via a backhaul link, or indirectly with the core network 190 through one or more decomposed base station units (such as a near real-time RIC 125 via an E2 link, or a non-real-time RIC 115 associated with a service management and orchestration (SMO) framework 105, or both). The CU 183 may communicate with one or more DUs 185 via corresponding midhaul links, such as an F1 interface. The DU 185 may communicate with one or more RUs 187 via corresponding fronthaul links. The RUs 187 may communicate with the UEs 104, respectively, via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be served simultaneously by multiple RUs 187.

[0057] Each of the units (i.e., CU 183, DU 185, RU 187, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0058] In some aspects, CU 183 may host higher-layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), or service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 183. CU 183 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 183 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 183 may be implemented to communicate with DU 185 for network control and signaling.

[0059] DU 185 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 187. In some aspects, DU 185 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling or modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 185 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 185 or with control functions hosted by CU 183.

[0060] The lower layer functionality may be implemented by one or more RUs 187. In some deployments, the RU 187 controlled by the DU 185 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 187 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, the real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 187 may be controlled by the corresponding DU 185. In some scenarios, this configuration may enable the implementation of the DU 185 and the CU 183 in a cloud-based RAN architecture (such as a vRAN architecture).

[0061] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 189) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 183, DU 185, RU 187, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 187 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0062] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 183, one or more DUs 185, or both, and the O-eNB with the near-RT RIC 125.

[0063] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0064] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of an UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), a subframe within the subcarrier set is dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 34 (most of which are UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0065] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10 millisecond (ms) frame may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbol on the DL may be a cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots in a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2 μ *15 kilohertz (kHz), where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15 kHz, and the subcarrier spacing for parameter set μ=4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific set of parameters.

[0066] A resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0067] like Figure 2AAs illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration). x , where 100x is the port number, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). RS may also include beam measurement RS (BRS), beam refinement RS (BRRS) and phase tracking RS (PT-RS).

[0068] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The PDCCH within a BWP may be referred to as a control resource set (CORESET). Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the physical layer identification and the physical layer cell identification group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the position of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0069] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0070] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0071] Figure 33 is a block diagram of a network device 310 (such as a base station) in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0072] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0073] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the network device 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the network device 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0074] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0075] Similar to the functionality described in conjunction with DL transmissions performed by the network device 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0076] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the network device 310 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0077] UL transmissions are handled at the network device 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0078] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0079] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform a combined Figure 1A Various aspects of the OOM signal component 198.

[0080] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform a combined Figure 1A Various aspects of the OOM signal configuration component 199.

[0081] In general, a network device (such as a base station) uses an MCS associated with an even modulation order to modulate data intended to be sent to a UE. For example, when modulating downlink data to be transmitted to a UE, the network device may apply QPSK (modulation order = 2) or square QAM, such as 16QAM (modulation order = 4), 64QAM (modulation order = 6), or 256QAM (modulation order = 8). Currently, network devices are limited to applying even modulation orders rather than odd modulation orders because the demodulation of signals including even modulation orders is relatively simple compared to signals including odd modulation orders (e.g., non-square QAM or APSK). However, a variety of methods have been developed for reducing the complexity in the demodulation of odd-order modulated signals. In addition, although due to these methods, the UE may have the ability to demodulate odd-order modulated signals to reduce complexity, this capability may not be used without some coordination with the network device to apply odd-order modulation. Since odd-order modulation may provide increased spectral efficiency granularity, improved PAPR, and improved phase noise mitigation compared to even-order modulation, it would be helpful if more MCSs could be configured to allow odd-order modulation to be applied to downlink or uplink signaling.

[0082] Typically, the demodulator of the UE (e.g., the RX processor 356 of the UE 350 or a component of the RX processor 356) includes a hard limiter component and a soft limiter component. The hard limiter component makes hard decisions about the bit values ​​of the modulation symbols or constellation points in the constellation diagram, while the soft limiter component makes soft decisions about the reliability of a certain bit value associated with the modulation symbols or constellation points in the constellation diagram. For even-order modulation (square QAM), these hard decisions or soft decisions can be performed in a relatively simple manner because the constellation diagram associated with the even-order modulation forms a square shape. For example, due to this square shape, the hard limiter can limit the constellation diagram in a single dimension (along the in-phase "I" signal axis or along the orthogonal "Q" signal axis), or determine the distance from the origin to the constellation point based only on the I value or Q value (but not both values) of the modulation symbol when making a hard decision about the associated bit value. Similarly, when making a soft decision regarding an associated bit value, the soft limiter may determine a log-likelihood ratio (LLR) associated with the bit value based only on the I value or the Q value of the modulation symbol (but not both values).

[0083] However, for odd-order modulations such as non-square QAM, these decisions are more complex to implement because the constellation diagram forms a non-square shape (e.g., a cross shape). For example, in a non-square QAM constellation diagram, although the hard limiter can similarly make decisions on the bit value based only on the I value or Q value of the constellation point that is closer to the origin in distance (e.g., the inner area of ​​the cross shape) as in square QAM, the hard limiter is generally required to make more complex decisions on the bit value based on both the I value and the Q value of the constellation point that is farther away from the origin in distance (e.g., the edge of the cross shape). Similarly, a soft limiter is generally required to determine the LLR value associated with the bit value based on both the I value and the Q value of the modulation symbol, which may require a very large lookup table with different mappings between I and Q for corresponding bit values.

[0084] FIG. 4A to FIG. 4C Examples 400, 420, 440 of non-square QAM constellations for 32QAM, 128QAM, and 512QAM are illustrated, respectively. As can be seen from these figures, such constellations may include cross-shaped constellation points or modulation symbols corresponding to possible bit values. Therefore, due to the lack of these constellation points at the corners of the constellation, hard decisions and soft decisions about a certain bit value in non-square QAM may be more complex than those in square QAM. For example, although FIG. 4A to FIG. 4C The bit values ​​in the inner area (central square area) of the constellation diagram can be determined based only on the I value or the Q value of its corresponding constellation point, but the bit values ​​in the outer area (outer rectangular area) of these constellation diagrams can be functions of both the I value and the Q value of its corresponding constellation point.

[0085] However, improvements have been made to facilitate demodulation of odd-order modulation signals. For example, to achieve simplified soft demapping of non-square QAM, geometric trends and folded overlap methods of non-square QAM constellations can be used to allow the nonlinear LLR equations based on the maximum logarithm MAP algorithm to be approximated as linear equations, thereby significantly reducing the computational complexity. This method, as well as other methods for reducing the demodulation complexity of odd-order modulation symbols, allows improved SPEF, PAPR reduction, and phase noise mitigation associated with odd-order modulation symbols to be achieved more efficiently.

[0086] As previously described, odd-order modulation can result in improved SPEF, PAPR, and phase noise mitigation. For example, square QAM typically includes a 6dB gap between adjacent modulation orders (e.g., 16QAM, 64QAM, 256QAM, etc.), while adding odd modulation orders may result in a smaller gap of 3dB between adjacent modulation orders (e.g., 16QAM, 32QAM, 64QAM, 128QAM, 256QAM, etc.), resulting in improved SPEF. In addition, for square QAM, the UE and base station (or other network equipment with base station functionality) typically include a power amplifier (PA) operating at a lower Tx power to avoid nonlinearity, while for odd-order modulation, the PA can operate at a higher Tx power (and therefore PA efficiency can be achieved) because the non-square QAM or APSK constellation is closer to a circle in shape than the square QAM constellation, resulting in improved PAPR. Furthermore, in square QAM, the constellation points at the corners of the constellation diagram have the largest radius and are therefore most susceptible to phase errors (e.g., for a given phase noise change or phase rotation, the angles or corresponding arcs of these symbols may be very large and result in high symbol error rates). However, for odd-order modulation, these corners are trimmed and the symbols are shaped to be more angularly apart (e.g., more circular in shape than a square QAM constellation), thereby resulting in symbols with smaller arcs and providing improved phase noise mitigation (more resilient to phase noise or the ability to eliminate phase noise).

[0087] The improved PAPR and phase noise mitigation associated with odd modulation orders can be most evident in single carrier or discrete Fourier transform (DFT) orthogonal frequency division multiplexing (OFDM) (DFT-OFDM) waveforms, which are typical candidate waveforms in sub-THz environments. Examples of these waveforms can include single carrier frequency division multiple access (SC-FDMA) waveforms, discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveforms, or Nyquist pulse-shaped single carrier waveforms. Such waveforms have simpler phase noise suppression than OFDM in the time domain because tracking pilot and phase noise and canceling noise in these waveforms is less complex than in OFDM. In OFDM (purely without DFT spreading), inter-carrier interference (ICI) may occur between adjacent carriers, making it difficult to completely cancel ICI or eliminate phase noise, while in single carrier or DFT-OFDM waveforms, phase noise can be almost completely eliminated. Furthermore, better PA efficiency may be achieved from the low PAPR associated with these waveforms, as UEs or base stations (or other network equipment) with lower cost PAs may exploit the improved PAPR from odd-order modulation to compensate for the nonlinearity of these PAs.

[0088] Thus, odd-order modulation can address the challenges of improving spectral efficiency, reducing PAPR, and mitigating phase noise at the same time in sub-THz environments (where phase noise is typically high, and where PA nonlinearity is typically poor or PA cost is high). For example, odd-order modulation can provide more resilience to phase noise, reduce PAPR and therefore provide better PA efficiency, and more efficiently handle bandwidth. Therefore, for a UE having the ability to demodulate odd-order modulated signals to coordinate with a network device (e.g., a base station), it would be helpful to apply this capability to subsequent signaling. Therefore, various aspects of the present disclosure allow a network device to configure an odd modulation order to be applied to a downlink or uplink transmission via signaling between the network device and the UE.

[0089] In one example, if the UE is currently communicating with a network device using even-order modulation in one MCS table, but the UE is capable of performing simplified soft demapping for non-square QAM as previously described in conjunction with LLR calculations (or is otherwise capable of demodulating odd-order modulated signals with minimized complexity), the UE may request the network device to switch from the MCS table to a different MCS table (an extended MCS table) that includes MCSs associated with odd-order modulation as well as even-order modulation. Thus, UEs capable of receiving odd-order modulated signals may benefit from the associated SPEF improvements with odd modulation orders. In another example, if the UE is also capable of correcting phase noise (typically in single-carrier or DFT-OFDM waveforms, but not limited to these waveforms), the UE may transmit this request to the network device to apply an extended MCS table, thereby similarly benefiting from improved phase noise resilience. In another example, if the UE is located at the edge of a cell but includes such capability to demodulate odd-order modulated signals, the UE may request the network device to switch to an extended MCS table to result in a lower PAPR. This lower PAPR may in turn allow the UE's transmit power to be increased by 0.8 dB, providing a significant improvement in signal quality at the cell edge.

[0090] Figure 5 An example 500 of an MCS table 502 including MCSs 504 with even modulation orders (e.g., QPSK, 16QAM, 64QAM, 256QAM) and various code rates (associated with up to N different MCS indices) and an extended MCS table 506 including additional MCSs 508 with odd modulation orders (e.g., 8QAM, 32QAM, 128QAM, 512QAM) and various code rates (associated with up to M different MCS indices) is illustrated. Each MCS 504 or row of the MCS table 502 for a given modulation order may indicate a particular code rate, with a lower amount indicating a stronger code rate (e.g., a code rate of 0.5 for 16QAM resulting in a SPEF of 2 bps / Hz) and a higher amount indicating a weaker code rate (e.g., a code rate of 0.9 for 16QAM resulting in a SPEF of 3.6 bps / Hz).

[0091] The extended MCS table 506 includes not only additional MCSs 508 with odd modulation orders, but also MCSs 510 with even modulation orders (e.g., QPSK, 16QAM, 64QAM, 256QAM) that correspond to the MCSs 504 in the MCS table 502. Thus, the size of the extended MCS table 506 may be effectively twice that of the MCS table 502. However, as described below with respect to Figure 8Further described, at certain code rates, odd modulation orders may have better SPEF or throughput than even modulation orders. Thus, the extended MCS table 506 can be designed to lack certain MCSs associated with even-order modulation (i.e., omit certain rows) that have code rates resulting in less SPEF or throughput compared to adjacent MCSs with odd modulation orders. For example, at certain code rates, the additional MCS 508 with 32QAM may result in better throughput than the MCS 504 with 64QAM, and thus the extended MCS table 506 can omit the 64QAM MCS with these specific code rates in the corresponding MCS 510. Figure 5 This is illustrated by the quantity N[modulation order] of the MCS table 502 and the quantity M[modulation order] of the extended MCS table 506, where for QPSK or modulation order 2, M2 < N2 (i.e., the number of corresponding MCSs 510 in the extended MCS table 506 for QPSK is less than the number of MCSs 504 in the MCS table 502 for QPSK), for 16QAM or modulation order 4, M4 < N4 (i.e., the number of corresponding MCSs 510 in the extended MCS table 506 for 16QAM is less than the number of MCSs 504 in the MCS table 502 for 16QAM), and so on.

[0092] Thus, the extended MCS table 506 can include the best MCSs from the MCS table 502 while omitting those MCSs 504 that do not add value compared to their adjacent counterparts with odd modulation orders. This selective approach for the extended MCS table 506 can also save communication overhead by minimizing the number of rows and thus the number of bits that a network device (e.g., a base station) can use to indicate the specific MCS index to be applied from the extended MCS table 506. Additionally, since the extended MCS table 506 can provide additional complexity to the UE when selecting which MCS to apply in a CSI report (due to the UE having additional odd modulation orders to consider for CQI), omitting certain MCSs can reduce the number of MCSs from which the UE can choose, thereby alleviating this complexity.

[0093] Figure 6 Example 600 illustrates a call flow between a UE 602 and a network device 604 (e.g., base station 102 / 180 or decomposed BS181) for odd modulation orders to be applied in downlink or uplink communication. Initially, the network device 604 can send information indicating configuration 606 to the UE 602 to indicate network support 608 for odd-order modulation (OOM). For example, the configuration 606 can be an RRC configuration 610 or a MAC-CE 612, and the OOM can be associated with a non-square QAM constellation 614 (e.g., as FIG. 4A to FIG. 4C) or non-square APSK constellation 616. UE 602 may receive the information indicating configuration 606, for example, after the UE enters a cell of network device 604, in which case the UE may determine whether the cell supports OOM (e.g., the network supports Figure 5 If the configuration 606 indicates that the network supports 608 such odd modulation order MCS, the network device 604 may switch between the MCS table 502 and the extended MCS table 506 to communicate with the UE 602. Otherwise, if the configuration 606 indicates that there is no network support 608 (e.g., the network support 608 does not exist), only even modulation orders such as in the MCS table 502 may be applied.

[0094] Network support 608 for OOM may be indicated via a flag, bit value, or information element (e.g., having a value of "1" indicating that network support is present and a value of "0" indicating that network support is not present, or vice versa). Network device 604 may support OOM (and thus may set network support 608 accordingly), for example, if network device 604 is capable of applying an MCS associated with an odd modulation order (e.g., non-square QAM or APSK) to its downlink transmissions. For example, if Figure 5 608 for OOM.

[0095] In one example, if network support 608 is present and the UE 602 is capable of performing simplified soft demapping for non-square QAM as previously described in conjunction with LLR calculations (or is otherwise capable of demodulating odd-order modulated signals with minimized complexity), the UE 602 may send a request 618 to the network device 604 to request a switch from the MCS table 502 to the extended MCS table 506. For example, the UE 602 may request a switch from a current MCS 620 from the MCS table 502 applied to communications between the UE 602 and the network device 604 to a new MCS 622 from the extended MCS table 506. The current MCS 620 may be, for example, an even modulation order and coding rate from the MCS table 502 applied to previous communications (such as configuration 606), and the new MCS 622 may be, for example, an odd modulation order and coding rate (or a corresponding even modulation and coding rate) from the extended MCS table 506. The UE 602 may provide a request 618 in the PUSCH 624 or in the PUCCH 626 (such as in a UCI or CSI report 628 ) to achieve an improvement in SPEF with the new MCS 622 .

[0096] In addition to providing the request 618 to the network device 604 to switch to the extended MCS table 506 for SPEF improvement, the UE 602 may also transmit the request 618 for reasons related to phase noise resilience or PAPR. For example, if the UE is operating under high SNR conditions (e.g., ≥ 28 dB), the UE may benefit from phase noise resilience, while if the UE is operating under low SNR conditions (e.g., ≤ -5 dB), the UE may benefit from PAPR reduction. In either case, the UE 602 may request the network device 604 to switch to the extended MCS table 506 and apply an odd modulation order to the new MCS 622. Thus, the UE 602 may determine whether to send the request 618 to the network device 604 based on the currently observed SNR (e.g., the SNR of the configuration 606 or other previous communications between the UE 602 and the network device 604).

[0097] For phase noise resilience, under high SNR conditions, thermal noise becomes less dominant, and phase noise becomes a significant factor affecting wireless communication. For example, typically as the UE increases its Tx power, its throughput also increases. As the SNR increases, the throughput will continue with this increase in Tx power until a certain threshold or phase noise level (e.g., 28dB in mmW) is reached, at which point the throughput may no longer rise even with increasing Tx power (because now phase noise may limit throughput). However, with phase noise correction, the UE may continue to increase its throughput beyond this limit. Therefore, at box 627, the UE 602 may check whether its observed SNR is at least equal to the phase noise SNR threshold (e.g., 28dB), at which point phase noise correction may be required to achieve maximum throughput. In response to this determination, the UE 602 may transmit a request 618 to switch its current MCS 620 (even modulation order) to a new MCS 622 (odd modulation order) from the extended MCS table 506 to better cope with phase noise at higher SNRs.

[0098] With respect to PAPR, if the UE is located at the cell edge, the UE may observe a very low or weak SNR (e.g., a negative SNR at QPSK with a strong code rate). Under such low SNR conditions, the UE may benefit from the reduced PAPR due to odd-order modulation, as this in turn may allow the UE to increase its Tx power to compensate for the low SNR. Thus, at box 629, the UE 602 may check whether its observed SNR is at most equal to a cell edge SNR threshold (e.g., -5dB), at which point an increase in Tx power may be helpful. In response to this determination, the UE 602 may transmit a request 618 to switch its current MCS 620 (even modulation order) to a new MCS 622 (odd modulation order) from the extended MCS table 506, thereby reducing its PAPR and increasing its Tx power by approximately 1 dB (e.g., as shown below for Fig. 9 described).

[0099] In another example where there is network support 608, instead of (or in addition to) the UE 602 transmitting a request 618 to the network device 604 to switch to the extended MCS table 506, if the UE 602 indicates that it is capable of supporting OOM, the network device 604 may determine to switch to the extended MCS table 506. For example, the network device 604 may send an OOM support inquiry message 631 to the UE 602 to inquire whether the UE 602 is capable of demodulating odd-order modulated signals. In response to the OOM support inquiry message 631, the UE 602 may send a confirmation 630 indicating whether the UE includes OOM support 632. For example, if the UE 602 is capable of performing simplified soft demapping for non-square QAM as previously described in conjunction with LLR calculations (or is otherwise capable of demodulating odd-order modulated signals with minimized complexity), the UE 602 may indicate in the confirmation 630 that it includes OOM support 632. Otherwise, the UE may indicate that it does not include OOM support 632. OOM support 632 may be indicated via a flag, a bit value, or an information element (e.g., having a value of "1" indicating that UE support is present and a value of "0" indicating that UE support is not present, or vice versa). In response to receiving the confirmation 630, if OOM support 632 is indicated, the network device 604 may determine to switch to the extended MCS table 506 and apply one of its MCSs 510 as the new MCS 622.

[0100] In another example where there is network support 608, the UE 602 may send a CSI report 634 indicating that the network device 604 is to apply OOM 636. In general, in response to receiving a CSI-RS (not shown), the UE may measure the CSI-RS to determine a CQI associated with a particular MCS and report the CQI to the network device 604 in the CSI report 634. If the MCS table 502 is currently being applied, the UE may select a CQI associated with an even modulation order in the MCS table 502. However, if the network device 604 indicates network support 608 for OOM (e.g., the extended MCS table 506 may be applied), the UE may instead select a CQI associated with an odd modulation order in the extended MCS table 506. The odd modulation order associated with the CQI may be indicated as OOM 636 in the CSI report 634. Therefore, there may be multiple predefined CQI tables associated with different MCSs (even modulation orders and odd modulation orders), similar to the MCS table 502 and the extended MCS table 506.

[0101] Alternatively or additionally, if the UE supports OOM (e.g., the UE includes OOM support 632) but is currently using an MCS from the MCS table 502, the UE may determine that it selects a new MCS with an odd modulation order from the extended MCS table 506 and includes a CQI associated with the new MCS in the CSI report 634. Thus, the CSI report 634 may effectively serve as a request (similar to the request 618) to the network device 604 to switch the current MCS 620 (even modulation order) to the new MCS 622 (odd modulation order indicated via the OOM 636). If the UE 602 determines that the odd modulation order MCS is better than the even modulation order MCS at the currently observed SNR, the UE 602 may transmit such a request in its CSI report 634. However, even if the UE includes OOM support 632, if the UE determines that at the currently observed SNR, the even-order modulation MCS in the MCS table 502 happens to be better than the odd-order modulation MCS in the extended MCS table 506, the UE can still select the CQI associated with the even-order modulation from the MCS table 502.

[0102] In response to receiving the request 618, the ACK 630 indicating OOM support 632, or the CSI report 634 including a CQI indicating OOM 636, the network device 604 may send a DCI 638 to the UE 602 scheduling a downlink or uplink transmission of data 640 using an odd-order modulation MCS from the extended MCS table 506. Subsequently, the UE 602 may receive or transmit a signal 642 including the data 640 using the new MCS 622 (odd-order modulation). The signal may be carried in an SC-FDMA waveform 644, a DFT-s-OFDM waveform 646, a Nyquist pulse-shaped single carrier waveform 648, or other waveforms that allow for simpler phase noise suppression and lower PAPR. As a result, the UE 602 may achieve improved SPEF, PAPR reduction, and phase noise resilience over its previous MCS (even-order modulation).

[0103] Figure 7An example 700 of a chart showing the SPEF improvement caused by an odd modulation order based on the relationship between SNR and block error rate (BLER) is illustrated. As can be seen in the illustrated chart and assuming a fixed code rate (e.g., 0.86 or 0.87), increasing the modulation order from an even modulation order to another even modulation order (e.g., 16QAM to 64QAM) requires an SNR increase of 6dB to handle the additional two bits provided by the increased modulation order. However, increasing the modulation order from an even modulation order to an odd modulation order (e.g., 16QAM to 32QAM) or vice versa (e.g., 32QAM to 64QAM) only requires an SNR increase of 3dB to handle the additional bits provided by the increased modulation order. Therefore, by configuring an odd modulation order for use in wireless communications, the SPEF granularity can be increased via a finer transition of the modulation order (e.g., even to odd and odd to even). Using such smaller SPEF particles can result in an improvement in throughput.

[0104] Figure 8 An example 800 of a graph showing the SPEF improvement from an odd modulation order based on the relationship between SNR and throughput (Tput) is illustrated. In this example, the curves shown refer to an even modulation order 256QAM (low curve 802), an odd modulation order 512QAM (middle curve 804), and an even modulation order 1024QAM (high curve 806), respectively, but other adjacent modulation orders may be used in other examples. As can be seen from the figure, the middle curve 804 shows a lower throughput at a higher SNR than the high curve 806, and a higher throughput at a lower SNR, while the middle curve 804 shows a higher throughput at a higher SNR than the low curve 802, and a lower throughput at a lower SNR. Therefore, an area 808 can be formed between the intersection of the low curve 802 and the middle curve 804 and the intersection of the middle curve 804 and the high curve 806. This region 808 represents the SNR range where odd modulation orders produce better SPEF than adjacent even modulation orders because in this region, the middle curve 804 includes the highest throughput at the lowest SNR between the three curves. Furthermore, this maximum throughput, minimum SNR region is not limited to the set of modulation orders 256QAM, 512QAM, and 1024QAM; rather, a similar region may exist for any odd modulation order between any two adjacent even modulation orders. For any of these regions (e.g., region 808), Figure 5 The extended MCS table 506 may omit even modulation orders with code rates that fit within these regions, because odd modulation orders will outperform adjacent even modulation orders for certain code rates in the associated SNR range.

[0105] As to why the middle curve 804 shows a lower throughput (per symbol bit) than the high curve 806 at a higher SNR, odd modulation orders are associated with one less bit than higher modulation orders (e.g., 512QAM vs. 1024QAM), resulting in odd modulation orders having a weaker code rate with less overhead than higher modulation orders. For example, if 1024QAM is associated with a 0.8 code rate, the number of decoded bits will be 8 (e.g., 10 bits * 0.8 code rate = 8 bits per symbol), and therefore in order to match this number, 512QAM will have to be associated with a 0.88 code rate (e.g., 9 bits * 0.88 code rate ≈ 8 bits per symbol). Therefore, at the same level of throughput, odd modulation orders will require a higher code rate than higher modulation orders, resulting in odd modulation orders requiring a higher SNR than higher modulation orders to maintain the same throughput. Therefore, a reduction in code rate (even as low as 1%) may result in significant losses at the decoder of the UE or network equipment (e.g., base station), and thus requires operation at a higher SNR, which is why the middle curve 804 is shown below the high curve 806 at a higher SNR. In addition, for similar reasons, at a higher SNR, the lower curve 802 shows a lower throughput than the middle curve 804.

[0106] As to why the middle curve 804 shows a higher throughput than the high curve 806 at a lower SNR, the receiver of the UE or network device (e.g., a base station) includes not only a decoder but also a demodulator. Although the decoder may benefit from a higher even-order modulation (e.g., 1024QAM) with a strong code rate (e.g., 0.5), at a low SNR, the demodulator may experience higher thermal noise, may perform less accurate hard or soft decisions (e.g., maximum likelihood approximation or LLR calculation), and may experience poor channel estimation. Therefore, at a lower SNR, the throughput of higher even modulation orders may be limited by the capabilities of the demodulator, regardless of the strength of the decoder, resulting in the middle curve 804 being shown above the high curve 806 at a lower SNR. In addition, for similar reasons, at a lower SNR, the higher curve 802 shows a lower throughput than the middle curve 804.

[0107] Fig. 9An example 900 of a graph showing PAPR improvements resulting from an odd modulation order configuration is illustrated. As illustrated in the figure, even modulation orders 902 are generally associated with a PAPR that is approximately 0.8 dB greater on average than odd modulation orders 904 that are respectively adjacent to these even modulation orders. This average value can be shown by the respective values ​​of PAPR for different constellations in table 906 associated with the PAPR graph. Therefore, a UE that uses odd modulation orders for its communications (e.g., at the cell edge) can achieve an average of 0.8 dB reduced PAPR, thereby allowing the UE to use this reduced PAPR to increase its Tx power and improve signal quality.

[0108] Fig.10 An example 1000 of a non-square QAM constellation diagram indicating phase noise resilience is illustrated. As can be seen from the figure, the individual constellation points are slightly blurred due to thermal noise (additive white Gaussian noise (AWGN)) and phase noise (PN). In a sub-THz environment where modulation symbols are carried on a single carrier or DFT-OFDM waveform, phase noise may be significant, and therefore the modulation symbols may experience phase rotation or arcing. Constellation points at a greater distance from the origin of the diagram may experience more phase rotation or longer arcs, especially the constellation points at the corners of the constellation diagram where the distance is the largest. For a square QAM constellation diagram, these corners may experience significant arcing and may therefore overlap with adjacent constellation points, resulting in high symbol error rates. However, for a non-square QAM constellation diagram, the constellation points 1002 at the corners lack adjacent constellation points that exist in a square QAM constellation (because the corners here have been trimmed to form a cross shape), and therefore the risk of such overlap is significantly reduced, resulting in a lower symbol error rate. Therefore, odd modulation orders can provide more resilience to phase noise than even modulation orders. Additionally, PAPR may refer to the ratio of the peak distance of constellation points to the average distance of constellation points, and since a non-square QAM constellation has a lower peak distance than a square QAM constellation (due to trimming of the diagonals), the PAPR may be reduced.

[0109] Fig.11 An example 1100 of a graph showing the performance improvement that can be achieved with odd modulation orders compared to even modulation orders in a single carrier waveform is illustrated. Fig.11 In the illustrated example, a gain of 0.5dB-0.85dB in SNR without phase noise and a gain of 0.5dB-1.1dB in SNR with phase noise can be achieved by increasing the corresponding order of non-square QAM over the adjacent order of square QAM to maintain the same corresponding throughput. Fig. 9With a PAPR reduction of 0.8 dB in the described SNR, applying odd modulation orders to communications in a single carrier waveform can result in an overall link budget benefit of 1.3 dB-1.9 dB over even modulation orders.

[0110] Fig.12 An example 1200 of a graph showing the performance improvement that can be achieved with odd modulation orders compared to even modulation orders in an OFDM waveform is illustrated. Fig.12 In the illustrated example, a gain of 0.3dB-1dB in SNR without phase noise can be achieved by the corresponding order of non-square QAM exceeding the adjacent order of square QAM to maintain the same corresponding throughput. Therefore, in the absence of phase noise, the OFDM waveform includes similar performance improvements as the single carrier waveform. However, in the case of phase noise, for the OFDM waveform, the receiver performs common phase error (CPE) correction after reaching a certain SNR level, which ultimately limits the throughput. For example, in Fig.12 In the illustrated example, gains may not be realized after an SNR of 28 dB with phase noise because throughput may be limited even at higher SNRs. Therefore, at high SNRs, the performance improvement of non-square QAM relative to square QAM for OFDM waveforms may no longer be realized. Therefore, if the observed SNR is less than the threshold associated with maximum throughput (e.g., an SNR of 28 dB), a UE that has the ability to demodulate the OFDM waveform using an odd modulation order to achieve improved SPEF but does not have the ability to correct the phase noise to increase throughput beyond this upper limit may request that OOM be applied. For example, the UE may transmit a request to the base station (or other network device having base station functionality) to switch from the MCS table 502 to the extended MCS table 506 (e.g., Figure 6 618 in ). If the observed SNR is greater than the threshold, the UE may avoid transmitting the request, since no SPEF improvement may be achieved at such a high SNR, since the UE cannot correct the phase noise above the limit. Conversely, if the UE is able to correct the phase noise so that the throughput may continue to be even above the threshold (e.g., above 28 dB), the UE may transmit the request upon determining that the observed SNR is greater than the threshold, as previously described (e.g., in Figure 6 627 of FIG. 11 ).

[0111] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 350, 602; device 1502). Optional aspects are illustrated by dashed lines. The method allows the UE to apply odd-order modulation to data transmission or reception based on network support configured for odd-order modulation.

[0112] At 1302, the UE receives a configuration indicating network support for communications using odd-order modulation. For example, 1302 can be performed by configuration component 1540. In one example, the configuration can be an RRC configuration or a MAC-CE. In one example, odd-order modulation can be associated with a non-square QAM constellation or a non-square APSK constellation. For example, reference Figure 6 , UE 602 may receive a message indicating network support 608 for OOM in communications between UE 602 and network device 604 (e.g., network support Figure 5 For example, the configuration 606 may be an RRC configuration 610 or a MAC-CE 612, and the OOM may be combined with a non-square QAM constellation 614 (e.g., FIG. 4A to FIG. 4C ) or non-square APSK constellation 616. Network support 608 for OOM can be indicated via a flag, bit value, or information element (e.g., having a value of "1" indicating that network support is present and a value of "0" indicating that network support is not present, or vice versa). Network device 604 can support OOM (and thus can set network support 608 accordingly), for example, if network device 604 is capable of applying an MCS associated with an odd modulation order (e.g., non-square QAM or APSK) to its downlink transmissions. For example, if Figure 5 If the extended MCS table 506 of the network device has been pre-defined or configured with odd modulation orders that the network device can utilize in its downlink transmissions, then this capability may exist, and therefore network support 608 for OOM may exist. For uplink transmissions, if the above MCS table has been pre-defined or configured, the network device 604 can similarly indicate that network support 608 exists so that the UE can similarly use its odd modulation order for its uplink transmissions.

[0113] At 1304, the UE may, in response to the configuration, send a request to change a current MCS applied to communications between the UE and the network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, the first MCS table including even order modulation and lacking odd order modulation, and the second MCS table including odd order modulation. For example, 1304 may be performed by request component 1542. In one example, the request may be sent in a PUSCH or a PUCCH. In one example, the request may be included in a CSI report. For example, reference Figure 6, the UE 602 may send a request 618 to change a current MCS 620 (e.g., one of the MCSs 504 in the MCS table 502) applied to communications between the UE 602 and the network device 604 to a new MCS 622 (e.g., one of the additional MCSs 508 in the extended MCS table 506) in response to the configuration 606. The MCS table 502 may include even modulation orders and coding rates, but not odd modulation orders and coding rates, such as Figure 5 . In contrast, the extended MCS table 506 may include both odd modulation orders and coding rates and even modulation orders and coding rates. The UE 602 may send a request 618 in a PUSCH 624 or in a PUCCH 626 (such as in a UCI or CSI report 628) to achieve an improvement in SPEF using the new MCS 622. In response to receiving the request 618, the network device 604 may send a DCI 638 to the UE 602 scheduling a downlink or uplink transmission of data 640 using an odd-order modulation MCS from the extended MCS table 506.

[0114] In one example, the UE may send the request at 1304 in response to the configured SNR received at 1302 being at least equal to the phase noise SNR threshold. In another example, the UE may send the request at 1304 in response to the configured SNR received at 1302 being at most equal to the cell edge SNR threshold. Figure 6 , the UE 602 may determine whether to send a request 618 to the network device 604 based on the currently observed SNR (e.g., the SNR of the configuration 606 or other previous communications between the UE 602 and the network device 604). For example, at block 627, the UE 602 may check whether its observed SNR is at least equal to a phase noise SNR threshold (e.g., 28 dB), at which point phase noise correction may be required to achieve maximum throughput. In response to this determination, the UE 602 may transmit a request 618 to switch its current MCS 620 (even modulation order) to a new MCS 622 (odd modulation order) from the extended MCS table 506 to better cope with phase noise at higher SNRs. Alternatively, at block 629, the UE 602 may check whether its observed SNR is at most equal to a cell edge SNR threshold (e.g., -5 dB), at which point a Tx power increase may be helpful. In response to this determination, UE 602 may transmit a request 618 to switch its current MCS 620 (even modulation order) to a new MCS 622 (odd modulation order) from extended MCS table 506, thereby reducing its PAPR and increasing its Tx power by approximately 1 dB (e.g., as described above for Fig. 9 described).

[0115] In one example, the second MCS table may also include a portion of the even-order modulations of the first MCS table. For example, referring to Figure 5 and Figure 8 , at certain code rates, odd modulation orders may have better SPEF or throughput than even modulation orders. Thus, the extended MCS table 506 can be designed to lack certain MCSs associated with even-order modulations (i.e., omit certain rows) that have code rates resulting in less SPEF or throughput compared to adjacent MCSs with odd modulation orders. For example, at certain code rates, an additional MCS 508 with 32QAM may result in better throughput than an MCS 504 with 64QAM, and thus the extended MCS table 506 can omit the 64QAM MCS with these specific code rates in the corresponding MCS 510. Figure 5 This is illustrated by the quantity N[modulation order] of the MCS table 502 and the quantity M[modulation order] of the extended MCS table 506, where for QPSK or modulation order 2, M2 < N2 (i.e., the number of corresponding MCSs 510 in the extended MCS table 506 for QPSK is less than the number of MCSs 504 in the MCS table 502 for QPSK), for 16QAM or modulation order 4, M4 < N4 (i.e., the number of corresponding MCSs 510 in the extended MCS table 506 for 16QAM is less than the number of MCSs 504 in the MCS table 502 for 16QAM), and so on.

[0116] At 1306, the UE may receive a message asking whether the device includes odd-order modulation support, and at 1308, the UE may send an acknowledgment indicating odd-order modulation support in response to the message. For example, 1306 may be performed by the message component 1544, while 1308 may be performed by the acknowledgment component 1546. In one example, the message may be received in the PDSCH or PDCCH. For example, referring to Figure 6, the UE 602 may receive an OOM support inquiry message 631 from the network device 604, asking whether the UE is capable of demodulating odd-order modulated signals. In response to the OOM support inquiry message 631, the UE 602 may send a confirmation 630 indicating whether the UE includes OOM support 632. For example, if the UE 602 is capable of performing simplified soft demapping for non-square QAM as previously described in conjunction with the LLR calculation (or is otherwise capable of demodulating odd-order modulated signals with minimized complexity), the UE 602 may indicate in the confirmation 630 that it includes OOM support 632. OOM support 632 may be indicated via a flag, a bit value, or an information element (e.g., having a value of "1" indicating that UE support is present and a value of "0" indicating that UE support is not present, or vice versa). In response to receiving the confirmation 630, if the OOM support 632 is indicated, the network device 604 may determine to switch to the extended MCS table 506 and apply one of its MCSs 510 as the new MCS 622.

[0117] In one example, the signal (at 1314) uses odd-order modulation based on odd-order modulation support. Figure 6 In response to receiving the ACK 630 indicating OOM support 632, the network device 604 may send a DCI 638 to the UE 602 scheduling a downlink or uplink transmission of data 640 using an odd-order modulation MCS from the extended MCS table 506. Subsequently, the UE 602 may receive or transmit a signal 642 including the data 640 using the new MCS 622 (odd-order modulation).

[0118] At 1310, the UE may send a CSI report indicating odd-order modulation. For example, 1310 may be performed by CSI reporting component 1548. For example, referring to Figure 6 , the UE 602 may send a CSI report 634 indicating the OOM 636 to be applied by the network device 604. For example, if the network device 604 indicates network support 608 for OOM (e.g., the extended MCS table 506 may be applied), the UE may instead select a CQI associated with an odd modulation order in the extended MCS table 506. This odd modulation order associated with the CQI may be indicated in the CSI report 634 as OOM 636. Thus, there may be multiple predefined CQI tables associated with different MCSs (even modulation orders and odd modulation orders), similar to the MCS table 502 and the extended MCS table 506.

[0119] At 1312, in response to the CSI report, the UE can receive DCI that schedules data in a signal transmitted using odd-order modulation. For example, 1312 can be performed by DCI component 1550. For example, referring to Figure 6In response to receiving a CSI report 634 including a CQI indicating OOM 636 (at 1310), the network device 604 may send a DCI 638 to the UE 602 scheduling a downlink or uplink transmission of data 640 in a signal 642 using an odd-order modulated MCS from the extended MCS table 506.

[0120] Finally, at 1314, the UE may transmit (or receive) data in a signal using odd-order modulation. For example, 1314 may be performed by signal component 1552. In one example, the data may be transmitted (or received) in a SC-FDMA waveform, a DFT-s-OFDM waveform, or a Nyquist pulse-shaped single carrier waveform. For example, referring to Figure 6 , the UE 602 may use the new MCS 622 (odd-order modulation) to send a signal 642 including data 640. For example, the Tx processor 368 of the UE 350 may use the following process to perform odd-order modulation: map the corresponding codewords including the odd bits (symbols) of the data 640 to the amplitudes (or frequencies or phase values) of the I and Q signals, perform digital-to-analog conversion of the I and Q signals, and generate a carrier waveform and multiply the carrier waveform with the I and Q signals. The signal may be carried in an SC-FDMA waveform 644, a DFT-s-OFDM waveform 646, a Nyquist pulse-shaped single carrier waveform 648, or other waveforms that allow simpler phase noise suppression and lower PAPR. Alternatively, the UE 602 may use the new MCS 622 (odd-order modulation) to receive a signal 642 including data 640. For example, the Rx processor 356 of the UE 350 can perform odd-order demodulation using the following process: frequency-shift the signal 642 including the mapped codewords having an odd number of bits (symbols) of the data 640 to equivalent baseband I and Q signals or intermediate frequency (IF signal), perform analog-to-digital conversion and detect the amplitude of the I and Q signals or the frequency or phase of the IF signal, and map the quantized amplitude, frequency or phase to the codeword. Therefore, the UE 602 can achieve improved SPEF, PAPR reduction, and phase noise resilience over its previous MCS (even-order modulation).

[0121] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a network entity or network device such as a base station (e.g., base station 102 / 180; decomposed BS 181; network device 310, 604; device 1602). Optional aspects are illustrated by dashed lines. The method allows a network entity (such as a base station) to apply odd-order modulation to data transmission or reception based on network support configured for odd-order modulation.

[0122] At 1402, a network entity sends a configuration indicating network support for communications using odd-order modulation. For example, 1402 can be performed by configuration component 1640. In one example, the configuration can be an RRC configuration or a MAC-CE. In one example, odd-order modulation can be associated with a non-square QAM constellation or a non-square APSK constellation. For example, reference Figure 6 , the network device 604 may send a message indicating network support 608 for OOM in communications between the UE 602 and the network device 604 (e.g., network support Figure 5 For example, the configuration 606 may be an RRC configuration 610 or a MAC-CE 612, and the OOM may be combined with a non-square QAM constellation 614 (e.g., FIG. 4A to FIG. 4C ) or non-square APSK constellation 616. Network support 608 for OOM can be indicated via a flag, bit value, or information element (e.g., having a value of "1" indicating that network support is present and a value of "0" indicating that network support is not present, or vice versa). Network device 604 can support OOM (and thus can set network support 608 accordingly), for example, if network device 604 is capable of applying an MCS associated with an odd modulation order (e.g., non-square QAM or APSK) to its downlink transmissions. For example, if Figure 5 If the extended MCS table 506 of the network device has been pre-defined or configured with odd modulation orders that the network device can utilize in its downlink transmissions, then this capability may exist, and therefore network support 608 for OOM may exist. For uplink transmissions, if the above MCS table has been pre-defined or configured, the network device 604 can similarly indicate that network support 608 exists so that the UE can similarly use its odd modulation order for its uplink transmissions.

[0123] At 1404, the network entity may, in response to the configuration, receive a request to change a current MCS applied to communications between the network entity and the UE from a first MCS in a first MCS table to a second MCS in a second MCS table, the first MCS table including even order modulation and lacking odd order modulation, and the second MCS table including odd order modulation. For example, 1404 may be performed by request component 1642. In one example, the request may be received in a PUSCH or a PUCCH. In one example, the request may be included in a CSI report. For example, reference Figure 6, the network device 604 may receive a request 618 to change a current MCS 620 (e.g., one of the MCSs 504 in the MCS table 502) applied to communications between the UE 602 and the network device 604 to a new MCS 622 (e.g., one of the additional MCSs 508 in the extended MCS table 506) in response to the configuration 606. The MCS table 502 may include even modulation orders and coding rates, but not odd modulation orders and coding rates, such as Figure 5 . In contrast, the extended MCS table 506 may include both odd modulation orders and coding rates and even modulation orders and coding rates. The network device 604 may receive a request 618 in a PUSCH 624 or in a PUCCH 626 (such as in a UCI or CSI report 628) to achieve an improvement in SPEF using the new MCS 622. In response to receiving the request 618, the network device 604 may send a DCI 638 to the UE 602 scheduling a downlink or uplink transmission of data 640 using an odd-order modulation MCS from the extended MCS table 506.

[0124] In one example, the network entity may receive the request at 1404 in response to the configured SNR received at 1402 being at least equal to the phase noise SNR threshold. In another example, the network entity may receive the request at 1404 in response to the configured SNR received at 1402 being at most equal to the cell edge SNR threshold. Figure 6 , the UE 602 may determine whether to send a request 618 to the network device 604 based on the currently observed SNR (e.g., the SNR of the configuration 606 or other previous communications between the UE 602 and the network device 604). For example, at block 627, the UE 602 may check whether its observed SNR is at least equal to a phase noise SNR threshold (e.g., 28 dB), at which point phase noise correction may be required to achieve maximum throughput. In response to this determination, the UE 602 may transmit and the network device 604 may obtain a request 618 to switch its current MCS 620 (even modulation order) to a new MCS 622 (odd modulation order) from the extended MCS table 506 to better cope with phase noise at higher SNRs. Alternatively, at block 629, the UE 602 may check whether its observed SNR is at most equal to a cell edge SNR threshold (e.g., -5 dB), at which point a Tx power increase may be helpful. In response to this determination, the UE 602 may transmit, and the network device 604 may obtain, a request 618 to switch its current MCS 620 (even modulation order) to a new MCS 622 (odd modulation order) from the extended MCS table 506, thereby reducing its PAPR and increasing its Tx power by approximately 1 dB (e.g., as described above for Fig. 9 as described).

[0125] In one example, the second MCS table may also include a portion of the even - order modulations of the first MCS table. For example, referring to Figure 5 and Figure 8 , at certain code rates, odd modulation orders may have better SPEF or throughput than even modulation orders. Thus, the extended MCS table 506 can be designed to lack certain MCSs associated with even - order modulations (i.e., omit certain rows) that have code rates resulting in less SPEF or throughput compared to adjacent MCSs with odd modulation orders. For example, at certain code rates, an additional MCS 508 with 32QAM may result in better throughput than an MCS 504 with 64QAM, and thus the extended MCS table 506 may omit the 64QAM MCS with these specific code rates in the corresponding MCS 510. Figure 5 This is illustrated by the quantity N[modulation order] of the MCS table 502 and the quantity M[modulation order] of the extended MCS table 506 in

[0126] At 1406, the network entity may send a message asking whether the UE includes odd - order modulation support, and at 1408, the network entity may receive an acknowledgment indicating odd - order modulation support from the UE in response to the message. For example, 1406 may be performed by the message component 1644, while 1408 may be performed by the acknowledgment component 1646. In one example, the message may be sent in the PDSCH or PDCCH. For example, referring to Figure 6, the network device 604 may send an OOM support inquiry message 631 to the UE 602, asking whether the UE is capable of demodulating odd-order modulated signals. In response to the OOM support inquiry message 631, the UE 602 may send and the network device 604 may receive a confirmation 630 indicating whether the UE includes OOM support 632. For example, if the UE 602 is capable of performing simplified soft demapping for non-square QAM as previously described in conjunction with the LLR calculation (or is otherwise capable of demodulating odd-order modulated signals with minimized complexity), the UE 602 may indicate in the confirmation 630 that it includes OOM support 632. OOM support 632 may be indicated via a flag, a bit value, or an information element (e.g., having a value of "1" indicating that UE support is present and a value of "0" indicating that UE support is not present, or vice versa). In response to receiving the confirmation 630, if the OOM support 632 is indicated, the network device 604 may determine to switch to the extended MCS table 506 and apply one of its MCSs 510 as the new MCS 622.

[0127] In one example, the signal (at 1414) uses odd-order modulation based on odd-order modulation support. Figure 6 In response to receiving the ACK 630 indicating OOM support 632, the network device 604 may send a DCI 638 to the UE 602 scheduling a downlink or uplink transmission of data 640 using an odd-order modulation MCS from the extended MCS table 506. Subsequently, the UE 602 may receive or transmit a signal 642 including the data 640 using the new MCS 622 (odd-order modulation).

[0128] At 1410, a network entity may receive a CSI report indicating odd-order modulation. For example, 1410 may be performed by CSI reporting component 1648. For example, referring to Figure 6 , the network device 604 may receive a CSI report 634 from the UE 602 indicating the OOM 636 that the network device 604 is to apply. For example, if the network device 604 indicates network support 608 for OOM (e.g., the extended MCS table 506 may be applied), the UE 602 may instead select a CQI associated with an odd modulation order in the extended MCS table 506. This odd modulation order associated with the CQI may be indicated in the CSI report 634 as OOM 636. Thus, there may be multiple predefined CQI tables associated with different MCSs (even modulation orders and odd modulation orders), similar to the MCS table 502 and the extended MCS table 506.

[0129] At 1412, in response to the CSI report, the network entity may send a DCI that schedules data in a signal to be sent using odd-order modulation. For example, 1412 may be performed by DCI component 1650. For example, referring to Figure 6 In response to receiving a CSI report 634 including a CQI indicating OOM 636 (at 1410), the network device 604 may send a DCI 638 to the UE 602 scheduling a downlink or uplink transmission of data 640 in a signal 642 using an odd-order modulated MCS from the extended MCS table 506.

[0130] Finally, at 1414, the network entity may receive (or transmit) data in a signal using odd-order modulation. For example, 1414 may be performed by signal component 1652. In one example, the data may be received (or transmitted) in a SC-FDMA waveform, a DFT-s-OFDM waveform, or a Nyquist pulse-shaped single carrier waveform. For example, referring to Figure 6 , the network device 604 may receive a signal 642 including data 640 using the new MCS 622 (odd-order modulation). For example, the Rx processor 370 of the network device 310 may perform odd-order demodulation using the following process: frequency-shift the signal 642 including the mapped codewords having an odd number of bits (symbols) of the data 640 to equivalent baseband I and Q signals or an intermediate frequency (IF signal), perform analog-to-digital conversion and detect the amplitude of the I and Q signals or the frequency or phase of the IF signal, and map the quantized amplitude, frequency, or phase to the codeword. The signal may be carried in an SC-FDMA waveform 644, a DFT-s-OFDM waveform 646, a Nyquist pulse-shaped single carrier waveform 648, or other waveforms that allow simpler phase noise suppression and lower PAPR. Alternatively, the network device 604 may send a signal 642 including data 640 using the new MCS 622 (odd-order modulation). For example, the Tx processor 316 of the network device 310 can perform odd-order modulation using the following process: mapping the corresponding codewords including the odd number of bits (symbols) of the data 640 to the amplitudes (or frequencies or phase values) of the I and Q signals, performing digital-to-analog conversion of the I and Q signals, and generating a carrier waveform and multiplying the carrier waveform with the I and Q signals. As a result, the network device 604 can achieve improved SPEF, PAPR reduction, and phase noise resilience over its previous MCS (even-order modulation).

[0131] Fig.1515 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1502. The apparatus 1502 is a UE and includes a cellular baseband processor 1504 (also referred to as a modem) coupled to a cellular RF transceiver 1522 and one or more subscriber identity modules (SIM) cards 1520, an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510, a Bluetooth module 1512, a wireless local area network (WLAN) module 1514, a global positioning system (GPS) module 1516, and a power source 1518. The cellular baseband processor 1504 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 1522. The cellular baseband processor 1504 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1504 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor 1504, causes the cellular baseband processor 1504 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1504 when executing the software. The cellular baseband processor 1504 also includes a receiving component 1530, a communication manager 1532, and a sending component 1534. The communication manager 1532 includes one or more illustrated components. The components within the communication manager 1532 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1504. The cellular baseband processor 1504 may be a component of the UE 350 and may include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1502 may be a modem chip and include only the baseband processor 1504, and in another configuration, the device 1502 may be the entire UE (e.g., see Figure 3 350), and includes the aforementioned additional modules of device 1502.

[0132] The communication manager 1532 includes a configuration component 1540 configured to receive a configuration indicating network support for communications using odd order modulation, eg, as described in connection with 1302 .

[0133] The communication manager 1532 also includes a request component 1542, which receives input in the form of a configuration from the configuration component 1540 and is configured to, in response to the configuration, send a request to change a current MCS applied to communications between the device and a network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes odd-order modulation, for example, as described in conjunction with 1304.

[0134] The communications manager 1532 also includes a message component 1544 that receives input in the form of a configuration from the configuration component 1540 and is configured to receive a message inquiring whether the device includes odd-order modulation support, for example, as described in conjunction with 1306.

[0135] The communication manager 1532 also includes a confirmation component 1546 that receives input in the form of a configuration from the configuration component 1540 and the message from the message component 1544 and is configured to send a confirmation indicating odd-order modulation support in response to the message, for example, as described in conjunction with 1308.

[0136] The communication manager 1532 also includes a CSI reporting component 1548 that receives input in the form of a configuration from the configuration component 1540 and is configured to send a CSI report indicating odd-order modulation, for example, as described in conjunction with 1310 .

[0137] The communication manager 1532 also includes a DCI component 1550 that receives input in the form of a configuration from the configuration component 1540 and a CSI report from the CSI reporting component 1548, and is configured to receive a DCI in response to the CSI report that schedules data in a signal to be transmitted using odd-order modulation, for example, as described in conjunction with 1312.

[0138] The communications manager 1532 also includes a signal component 1552 that receives input in the form of a configuration from the configuration component 1540 and is configured to transmit data in a signal using odd order modulation, for example, as described in conjunction with 1314 .

[0139] The apparatus may include executing Fig.13 Each of the boxes in the algorithm in the preceding flowchart is an additional component. Therefore, Fig.13 Each block in the aforementioned flow chart of can be performed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0140] In one configuration, the apparatus 1502 (and specifically the cellular baseband processor 1504) includes means for receiving a configuration indicating network support for communications using odd order modulation, and means for transmitting data in a signal using the odd order modulation.

[0141] In one configuration, odd-order modulation is associated with a non-square quadrature amplitude modulation (QAM) constellation or a non-square amplitude and phase shift keying (APSK) constellation.

[0142] In one configuration, data is transmitted in a single carrier frequency division multiple access (SC-FDMA) waveform, a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, or a Nyquist pulse-shaped single carrier waveform.

[0143] In one configuration, the configuration is a radio resource control (RRC) configuration or a medium access control (MAC) control element (MAC-CE).

[0144] In one configuration, the means for sending is further configured to, in response to the configuration, send a request to change a current modulation and coding scheme (MCS) applied for communications between the device and the network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, the first MCS table including even order modulation and lacking odd order modulation, and the second MCS table including odd order modulation.

[0145] In one configuration, the request is sent in a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0146] In one configuration, the means for transmitting is further configured to transmit the request in response to a signal-to-noise ratio (SNR) of the configuration being at least equal to a phase noise SNR threshold.

[0147] In one configuration, the means for transmitting is further configured to transmit the request in response to a signal-to-noise ratio (SNR) of the configuration being at most equal to a cell-edge SNR threshold.

[0148] In one configuration, the request is included in a channel state information (CSI) report.

[0149] In one configuration, the second MCS table also includes a portion of the even order modulation of the first MCS table.

[0150] In one configuration, the component for receiving is further configured to receive a message inquiring whether the device includes odd-order modulation support; and the component for sending is further configured to send a confirmation indicating odd-order modulation support in response to the message; wherein the signal uses odd-order modulation based on the odd-order modulation support.

[0151] In one configuration, the message is received in a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH).

[0152] In one configuration, the component for sending is further configured to send a channel state information (CSI) report indicating odd-order modulation; and the component for receiving is further configured to receive downlink control information (DCI) in response to the CSI report, which downlink control information (DCI) schedules data in the signal sent using odd-order modulation.

[0153] The aforementioned means may be one or more of the aforementioned components of the apparatus 1502 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1502 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.

[0154] Fig.16 1600 is a diagram illustrating an example of a hardware implementation for an apparatus 1602. The apparatus 1602 is a network entity or network device (such as a BS) and includes a baseband unit 1604. The baseband unit 1604 can communicate with the UE 104 via a cellular RF transceiver. The baseband unit 1604 may include a computer-readable medium / memory. The baseband unit 1604 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the baseband unit 1604, causes the baseband unit 1604 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1604 when executing the software. The baseband unit 1604 also includes a receiving component 1630, a communication manager 1632, and a sending component 1634. The communication manager 1632 includes one or more of the illustrated components. The components within the communication manager 1632 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1604. The baseband unit 1604 may be a component of the network device 310 and may include the memory 376 and / or at least one of the following: the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0155] The communication manager 1632 includes a configuration component 1640 configured to send a configuration indicating network support for communications using odd order modulation, eg, as described in connection with 1402 .

[0156] The communication manager 1632 also includes a request component 1642, which receives input in the form of a configuration from the configuration component 1640 and is configured to, in response to the configuration, receive a request to change a current MCS applied to communications between the device and the UE from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes odd-order modulation, for example, as described in conjunction with 1404.

[0157] The communications manager 1632 also includes a messaging component 1644 that receives input in the form of a configuration from the configuration component 1640 and is configured to send a message querying whether the UE includes odd-order modulation support, for example, as described in conjunction with 1406 .

[0158] The communications manager 1632 also includes a confirmation component 1646 that receives input in the form of a configuration from the configuration component 1640 and the message from the message component 1644 and is configured to receive a confirmation from the UE indicating odd-order modulation support in response to the message, for example, as described in conjunction with 1408.

[0159] The communication manager 1632 also includes a CSI reporting component 1648 that receives input in the form of a configuration from the configuration component 1640 and is configured to receive a CSI report indicating odd-order modulation, for example, as described in conjunction with 1410 .

[0160] The communication manager 1632 also includes a DCI component 1650 that receives input in the form of a configuration from the configuration component 1640 and a CSI report from the CSI reporting component 1648, and is configured to send a DCI in response to the CSI report that schedules data in a signal to be transmitted using odd-order modulation, for example, as described in conjunction with 1412.

[0161] The communications manager 1632 also includes a signal component 1652 that receives input in the form of a configuration from the configuration component 1640 and is configured to receive data in a signal using odd order modulation, for example, as described in conjunction with 1414 .

[0162] The apparatus may include executing Fig.14 Each of the boxes in the algorithm in the preceding flowchart is an additional component. Therefore, Fig.14 Each block in the aforementioned flow chart of can be performed by a component, and the apparatus may include one or more of those components. These components may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0163] In one configuration, the apparatus 1602 (and specifically the baseband unit 1604) includes means for transmitting a configuration indicating network support for communications using odd order modulation and means for receiving data in a signal using odd order modulation.

[0164] In one configuration, odd-order modulation is associated with a non-square quadrature amplitude modulation (QAM) constellation or a non-square amplitude and phase shift keying (APSK) constellation.

[0165] In one configuration, data is received as a single carrier frequency division multiple access (SC-FDMA) waveform, a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, or a Nyquist pulse-shaped single carrier waveform.

[0166] In one configuration, the configuration is a radio resource control (RRC) configuration or a medium access control (MAC) control element (MAC-CE).

[0167] In one configuration, the component for receiving is further configured to, in response to the configuration, receive a request to change a current modulation and coding scheme (MCS) applied for communication between the device and the UE from a first MCS in a first MCS table to a second MCS in a second MCS table, the first MCS table including even-order modulation and lacking odd-order modulation, and the second MCS table including odd-order modulation.

[0168] In one configuration, the request is received in a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0169] In one configuration, the means for receiving is further configured to receive the request in response to a signal-to-noise ratio (SNR) of the configuration being at least equal to a phase noise SNR threshold.

[0170] In one configuration, the means for receiving is further configured to receive the request in response to a signal-to-noise ratio (SNR) of the configuration being at most equal to a cell-edge SNR threshold.

[0171] In one configuration, the request is included in a channel state information (CSI) report.

[0172] In one configuration, the second MCS table also includes a portion of the even order modulation of the first MCS table.

[0173] In one configuration, the component for sending is further configured to send a message querying the UE whether it includes odd-order modulation support; and the component for receiving is further configured to receive a confirmation indicating odd-order modulation support from the UE in response to the message; wherein the signal uses odd-order modulation based on the odd-order modulation support.

[0174] In one configuration, the message is sent in a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH).

[0175] In one configuration, the component for receiving is further configured to receive a channel state information (CSI) report indicating odd-order modulation; and the component for sending is further configured to send downlink control information (DCI) in response to the CSI report, which schedules data in the signal sent using odd-order modulation.

[0176] The aforementioned means may be one or more of the aforementioned components of the apparatus 1602 configured to perform the functions recited by the aforementioned means. As described above, the apparatus 1602 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Therefore, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0177] Thus, aspects of the present disclosure allow a network entity (e.g., a base station or other network device having base station functionality) to configure an odd modulation order to be applied to downlink or uplink transmissions via signaling between the network entity and the UE so that improved SPEF, PAPR reduction, and phase noise mitigation associated with the odd modulation order can be achieved. If the UE is currently using even-order modulation in one MCS table to communicate with the network entity, but the UE is capable of demodulating odd-order modulated signals with minimized complexity, the UE can request the network entity to switch from the MCS table to an extended MCS table that includes MCSs associated with odd-order modulation as well as even-order modulation, thereby benefiting from the associated SPEF improvement with the odd modulation order. In another example, if the UE is also capable of correcting phase noise (typically in a single carrier or DFT-OFDM waveform), the UE can transmit this request to the network entity to apply the extended MCS table, thereby similarly benefiting from improved phase noise resilience. In another example, if the UE is located at the cell edge but includes such capability to demodulate odd-order modulation signals, the UE may request the network entity to switch to an extended MCS table to result in a lower PAPR, which in turn may allow the UE's transmit power to be increased by 0.8 dB, thereby providing a significant improvement in signal quality at the cell edge. Additionally, the extended MCS table may include the best MCSs from the MCS table while omitting those MCSs that do not add value relative to adjacent odd-modulation order counterparts, thereby saving communication overhead for MCS configuration and reducing CSI reporting complexity.

[0178] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not meant to be limited to the specific order or hierarchy provided.

[0179] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language claims, wherein the elements mentioned in the singular are not intended to represent "one and only one", unless specifically so stated, but "one or more". Terms such as "if", "when ......" and "while ......" should be interpreted as "under the conditions of ......", rather than meaning an immediate time relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," "device," etc. cannot replace the word "component." Therefore, no claim element will be construed as part-plus-function unless the element is explicitly recited using the phrase "component for..."

[0180] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein, but are not limited thereto.

[0181] Aspect 1 is a device for wireless communication, the device comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the device to: receive a configuration indicating network support for communications using odd-order modulation; and send data in a signal using the odd-order modulation.

[0182] Aspect 2 is an apparatus according to aspect 1, wherein the odd-order modulation is associated with a non-square quadrature amplitude modulation (QAM) constellation or a non-square amplitude and phase shift keying (APSK) constellation.

[0183] Aspect 3 is an apparatus according to aspect 1 or 2, wherein data is transmitted in a single carrier frequency division multiple access (SC-FDMA) waveform, a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, or a Nyquist pulse-shaped single carrier waveform.

[0184] Aspect 4 is an apparatus according to any one of aspects 1 to 3, wherein the configuration is a radio resource control (RRC) configuration or a medium access control (MAC) control element (MAC-CE).

[0185] Aspect 5 is an apparatus according to any one of Aspects 1 to 4, wherein the instructions, when executed by the processor, further cause the apparatus to: in response to the configuration, send a request to change a current modulation and coding scheme (MCS) applied to communication between the apparatus and a network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes the odd-order modulation.

[0186] Aspect 6 is the apparatus according to aspect 5, wherein the request is sent in a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0187] Aspect 7 is an apparatus according to aspect 5 or 6, wherein the instructions, when executed by the processor, further cause the apparatus to send the request in response to the configured signal-to-noise ratio (SNR) being at least equal to a phase noise SNR threshold.

[0188] Aspect 8 is an apparatus according to aspect 5 or 6, wherein the instructions, when executed by the processor, further cause the apparatus to send the request in response to the configured signal-to-noise ratio (SNR) being at most equal to a cell-edge SNR threshold.

[0189] Aspect 9 is an apparatus according to any one of aspects 5 to 8, wherein the request is included in a channel state information (CSI) report.

[0190] Aspect 10 is an apparatus according to any one of aspects 1 to 9, wherein the second MCS table also includes a portion of the even-order modulation of the first MCS table.

[0191] Aspect 11 is an apparatus according to any one of Aspects 1 to 10, wherein the instructions, when executed by the processor, further cause the apparatus to: receive a message inquiring whether the apparatus includes odd-order modulation support; and in response to the message, send a confirmation indicating the odd-order modulation support; wherein the signal uses the odd-order modulation based on the odd-order modulation support.

[0192] Aspect 12 is the apparatus according to aspect 11, wherein the message is received in a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH).

[0193] Aspect 13 is an apparatus according to any one of Aspects 1 to 12, wherein the instruction, when executed by the processor, further causes the apparatus to: send a channel state information (CSI) report indicating the odd-order modulation; and in response to the CSI report, receive downlink control information (DCI), the downlink control information (DCI) scheduling the data in the signal sent using the odd-order modulation.

[0194] Aspect 14 is a device for wireless communication, the device comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the device to: send a configuration indicating network support for communications using odd-order modulation; and receive data in a signal using the odd-order modulation.

[0195] Aspect 15 is an apparatus according to aspect 14, wherein the odd-order modulation is associated with a non-square quadrature amplitude modulation (QAM) constellation or a non-square amplitude and phase shift keying (APSK) constellation.

[0196] Aspect 16 is an apparatus according to aspect 14 or 15, wherein the data is received in a single carrier frequency division multiple access (SC-FDMA) waveform, a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, or a Nyquist pulse-shaped single carrier waveform.

[0197] Aspect 17 is an apparatus according to any one of aspects 14 to 16, wherein the configuration is a radio resource control (RRC) configuration or a medium access control (MAC) control element (MAC-CE).

[0198] Aspect 18 is an apparatus according to any one of Aspects 14 to 17, wherein the instructions, when executed by the processor, further cause the apparatus to: in response to the configuration, receive a request to change a current modulation and coding scheme (MCS) applied to communication between the apparatus and a user equipment (UE) from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes the odd-order modulation.

[0199] Aspect 19 is the apparatus according to aspect 18, wherein the request is received in a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

[0200] Aspect 20 is an apparatus according to aspect 18 or 19, wherein the instructions, when executed by the processor, further cause the apparatus to receive the request in response to the configured signal-to-noise ratio (SNR) being at least equal to a phase noise SNR threshold.

[0201] Aspect 21 is an apparatus according to aspect 18 or 19, wherein the instructions, when executed by the processor, further cause the apparatus to receive the request in response to the configured signal-to-noise ratio (SNR) being at most equal to a cell-edge SNR threshold.

[0202] Aspect 22 is an apparatus according to any one of aspects 18 to 21, wherein the request is included in a channel state information (CSI) report.

[0203] Aspect 23 is an apparatus according to any one of aspects 14 to 22, wherein the second MCS table also includes a portion of the even-order modulation of the first MCS table.

[0204] Aspect 24 is an apparatus according to any one of Aspects 14 to 23, wherein the instructions, when executed by the processor, further cause the apparatus to: send a message inquiring whether a user equipment (UE) includes odd-order modulation support; and in response to the message, receive a confirmation from the UE indicating the odd-order modulation support; wherein the signal uses the odd-order modulation based on the odd-order modulation support.

[0205] Aspect 25 is the apparatus according to aspect 24, wherein the message is sent in a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH).

[0206] Aspect 26 is an apparatus according to any one of Aspects 14 to 25, wherein the instructions, when executed by the processor, further cause the apparatus to: receive a channel state information (CSI) report indicating the odd-order modulation; and in response to the CSI report, send downlink control information (DCI), wherein the downlink control information (DCI) schedules the data in the signal to be sent using the odd-order modulation.

[0207] Aspect 27 is a method of wireless communication at a user equipment (UE), the method comprising: receiving a configuration indicating network support for communications using odd order modulation; and transmitting data in a signal using the odd order modulation.

[0208] Aspect 28 is a method according to Aspect 27, the method further comprising: in response to the configuration, sending a request to change a current modulation and coding scheme (MCS) applied to communication between the UE and the network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes the odd-order modulation.

[0209] Aspect 29 is a method of wireless communications at a network entity, the method comprising: sending a configuration indicating network support for communications using odd order modulation; and receiving data in a signal using the odd order modulation.

[0210] Aspect 30 is a method according to aspect 29, the method further comprising: in response to the configuration, receiving a request to change a current modulation and coding scheme (MCS) applied to communication between the network entity and a user equipment (UE) from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes the odd-order modulation.

Claims

1. A device for wireless communication, the device comprising: processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the apparatus to: receiving a configuration indicating network support for communications using odd order modulation; and Data in a signal is transmitted using the odd-order modulation.

2. The apparatus of claim 1, wherein the odd-order modulation is associated with a non-square quadrature amplitude modulation (QAM) constellation or a non-square amplitude and phase shift keying (APSK) constellation.

3. The apparatus of claim 1, wherein the data is transmitted in a single carrier frequency division multiple access (SC-FDMA) waveform, a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, or a Nyquist pulse-shaped single carrier waveform. 4 . The apparatus of claim 1 , wherein the configuration is a radio resource control (RRC) configuration or a medium access control (MAC) control element (MAC-CE).

5. The apparatus of claim 1 , wherein the instructions, when executed by the processor, further cause the apparatus to: In response to the configuration, a request is sent to change a current modulation and coding scheme (MCS) applied to communications between the device and a network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes the odd-order modulation.

6. The apparatus of claim 5, wherein the request is sent in a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

7. The apparatus of claim 5, wherein the instructions, when executed by the processor, further cause the apparatus to send the request in response to the configured signal-to-noise ratio (SNR) being at least equal to a phase noise SNR threshold.

8. The apparatus of claim 5, wherein the instructions, when executed by the processor, further cause the apparatus to send the request in response to the configured signal-to-noise ratio (SNR) being at most equal to a cell-edge SNR threshold.

9. The apparatus of claim 5, wherein the request is included in a channel state information (CSI) report.

10. The apparatus of claim 5, wherein the second MCS table further includes a portion of the even-order modulation of the first MCS table.

11. The apparatus of claim 1 , wherein the instructions, when executed by the processor, further cause the apparatus to: receiving a message inquiring whether the device includes odd-order modulation support; and In response to the message, sending an acknowledgement indicating support of the odd-order modulation; wherein the signal uses the odd-order modulation based on the odd-order modulation support.

12. The apparatus of claim 11, wherein the message is received in a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH).

13. The apparatus of claim 1, wherein the instructions, when executed by the processor, further cause the apparatus to: sending a channel state information (CSI) report indicating the odd order modulation; and In response to the CSI report, downlink control information (DCI) is received, the downlink control information (DCI) scheduling transmission of the data in the signal using the odd-order modulation.

14. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and operable when executed by the processor to cause the apparatus to: sending a configuration indicating network support for communications using odd order modulation; and Data in a signal is received using the odd-order modulation.

15. The apparatus of claim 14, wherein the odd-order modulation is associated with a non-square quadrature amplitude modulation (QAM) constellation or a non-square amplitude and phase shift keying (APSK) constellation.

16. The apparatus of claim 14, wherein the data is received in a single carrier frequency division multiple access (SC-FDMA) waveform, a discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM) waveform, or a Nyquist pulse-shaped single carrier waveform.

17. The apparatus of claim 14, wherein the configuration is a radio resource control (RRC) configuration or a medium access control (MAC) control element (MAC-CE).

18. The apparatus of claim 14, wherein the instructions, when executed by the processor, further cause the apparatus to: In response to the configuration, a request is received to change a current modulation and coding scheme (MCS) applied to communications between the device and a user equipment (UE) from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes the odd-order modulation.

19. The apparatus of claim 18, wherein the request is received in a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

20. The apparatus of claim 18, wherein the instructions, when executed by the processor, further cause the apparatus to receive the request in response to the configured signal-to-noise ratio (SNR) being at least equal to a phase noise SNR threshold.

21. The apparatus of claim 18, wherein the instructions, when executed by the processor, further cause the apparatus to receive the request in response to the configured signal-to-noise ratio (SNR) being at most equal to a cell-edge SNR threshold.

22. The apparatus of claim 18, wherein the request is included in a channel state information (CSI) report.

23. The apparatus of claim 18, wherein the second MCS table further includes a portion of the even-order modulation of the first MCS table.

24. The apparatus of claim 14, wherein the instructions, when executed by the processor, further cause the apparatus to: Sending a message asking a user equipment (UE) whether it includes odd-order modulation support; and receiving, in response to the message, an acknowledgement from the UE indicating support of the odd-order modulation; wherein the signal uses the odd-order modulation based on the odd-order modulation support.

25. The apparatus of claim 24, wherein the message is sent in a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH).

26. The apparatus of claim 14, wherein the instructions, when executed by the processor, further cause the apparatus to: receiving a channel state information (CSI) report indicating the odd order modulation; and In response to the CSI report, downlink control information (DCI) is transmitted, the downlink control information (DCI) scheduling transmission of the data in the signal using the odd order modulation.

27. A method of wireless communication at a user equipment (UE), comprising: receiving a configuration indicating network support for communications using odd order modulation; as well as Data in a signal is transmitted using the odd-order modulation.

28. The method according to claim 27, further comprising: In response to the configuration, a request is sent to change a current modulation and coding scheme (MCS) applied to communications between the UE and a network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes the odd-order modulation.

29. A method for wireless communication at a network entity, the method comprising: sending a configuration indicating network support for communications using odd order modulation; as well as Data in a signal is received using the odd-order modulation.

30. The method according to claim 29, further comprising: In response to the configuration, a request is received to change a current modulation and coding scheme (MCS) applied to communications between the network entity and a user equipment (UE) from a first MCS in a first MCS table to a second MCS in a second MCS table, wherein the first MCS table includes even order modulation and lacks odd order modulation, and the second MCS table includes the odd order modulation.

Images