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

Abstract

A method is provided that allows a network entity, such as a base station, to configure aspects of the odd-order modulation order to be applied to downlink or uplink transmissions via signaling between the network entity and the UE. Initially, the network entity sends a configuration to the UE indicating network support for communication using odd-order modulation. Subsequently, the UE transmits data in the signal using the odd-order modulation, and the network entity receives the data. Therefore, based on the network support configured for such odd-order modulation, improved SPEF, PAPR reduction, and phase noise mitigation associated with odd-order modulation can be achieved by applying odd-order modulation to data transmission or reception.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Patent Application Serial No. 17 / 931,019, filed September 9, 2022, entitled “IMPROVED POWER AND SPECTRALEFFICIENCY BASED ON ADDING ODD ORDER MODULATIONS”, which has been assigned to the assignee of this invention and is incorporated herein by reference in its entirety. Background Technology Technical Field

[0004] This disclosure relates in general to communication systems, and more specifically to wireless communication systems between user equipment (UE) and network entities or devices such as base stations.

[0005] introduction

[0006] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. 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.

[0007] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0008] The following is a simplified overview of one or more aspects to provide a basic understanding of these aspects. This invention is not a comprehensive overview of all anticipated aspects, nor is it intended to identify key or essential 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 the more detailed descriptions that follow.

[0009] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a UE (User Equipment). The UE receives a configuration indicating network support for communication using odd-order modulation, and the UE transmits data in a signal using odd-order modulation.

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

[0011] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate some exemplary features of one or more aspects in detail. However, these features indicate only 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. Attached Figure Description

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

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

[0014] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0015] Figure 2B This is a diagram illustrating examples of DL channels within a subframe according to various aspects of this disclosure.

[0016] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0017] Figure 2D This is a diagram illustrating examples of UL channels within a subframe according to various aspects of this disclosure.

[0018] Figure 3 This is a diagram illustrating examples of network devices such as base stations and user equipment (UEs) in an access network.

[0019] Figures 4A to 4C An example of a non-square quadrature amplitude modulation (QAM) constellation diagram is shown.

[0020] Figure 5 Examples of modulation and decoding scheme (MCS) tables, including MCSs with even modulation orders and various code rates, and extended MCS tables, including MCSs with odd modulation orders and various code rates, are shown.

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

[0022] Figure 7 An example is shown, illustrating the improvement in spectral efficiency (SPEF) resulting from odd modulation order based on the relationship between signal-to-noise ratio (SNR) and block error rate (BLER).

[0023] Figure 8 An example is shown in the graph illustrating the SPEF improvement from odd modulation order based on the relationship between SNR and throughput.

[0024] Figure 9 An example graph illustrating the improvement in peak to average power ratio (PAPR) of odd modulation order configurations compared to even modulation order configurations is shown.

[0025] Figure 10 An example of a non-square QAM constellation diagram indicating phase noise elasticity is shown.

[0026] Figure 11 An example is shown in the graph illustrating the performance improvement achieved by odd modulation order compared to even modulation order in a single-carrier waveform.

[0027] Figure 12 An example is shown in the graph illustrating the performance improvement achieved by odd modulation order compared to even modulation order in an orthogonal frequency division multiplexing (OFDM) waveform.

[0028] Figure 13 This is a flowchart of a method for wireless communication at the UE.

[0029] Figure 14 This is a flowchart of a method for conducting wireless communication at network entities such as base stations.

[0030] Figure 15 This is a diagram illustrating an example of the hardware implementation of the example device.

[0031] Figure 16 This is a diagram illustrating another example of the hardware implementation of another example device. Detailed Implementation

[0032] The specific embodiments described below with reference to the accompanying drawings are intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the specific embodiments include detailed descriptions. However, it will be apparent to those skilled in the art that these concepts can be practiced without these detailed descriptions. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0033] Generally, network devices (such as base stations) use modulation and decoding schemes (MCS) associated with even-numbered modulation orders to modulate data intended for transmission to the UE. For example, when modulating downlink data to be transmitted to the UE, network devices 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 using even-numbered modulation orders rather than odd-numbered modulation orders (e.g., modulation orders 3, 5, 7, 9, etc., such as non-square QAM or amplitude and phase shift keying (APSK)) because demodulating signals including even-numbered modulation orders is relatively simpler compared to signals including odd-numbered modulation orders. However, methods have been developed to reduce the complexity of demodulating odd-numbered modulation signals. For example, to achieve simplified soft demapping of non-square QAMs, the geometric trend and folding overlap of non-square QAM constellations can be used to allow the nonlinear log-likelihood ratio (LLR) equation based on the maximum log-maximum a posteriori (MAP) algorithm to be approximated as a linear equation, thereby significantly reducing computational complexity.

[0034] However, while these methods allow UEs to demodulate odd-order modulated signals to reduce complexity, this capability may not be utilized without some form of coordination with network equipment (e.g., base stations) to apply odd-order modulation. Since odd-order modulation offers increased spectral efficiency granularity, improved peak-to-average power ratio (PAPR), and improved phase noise reduction compared to even-order modulation, it would be beneficial to configure more MCSs to allow odd-order modulation to be applied to downlink or uplink signaling.

[0035] Therefore, aspects of this disclosure allow network devices to configure odd-order modulation orders to be applied to downlink or uplink transmissions via signaling between the network device and the UE. For example, the network device can send configuration information to the UE indicating support for odd-order modulation. The network device and the UE can then communicate using odd-order modulation. In this way, odd-order modulation between the UE and the network device can be facilitated, allowing for 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 an MCS table, but the UE is capable of demodulating odd-order modulated signals, the UE can request the network device to switch from that MCS table to a different MCS table (extended MCS table) that includes MCS associated with both odd-order and even-order modulation. Thus, a UE capable of receiving odd-order modulated signals can benefit from the associated SPEF improvement with odd-order modulation. In another example, if the UE is also capable of correcting phase noise, the UE can send this request to the network device 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 the capability to demodulate odd-order modulated signals, the UE can request the network equipment to switch to an extended MCS table, resulting in a lower PAPR. This lower PAPR, in turn, allows the UE to increase its transmit power by 0.8 dB, thus providing a significant improvement in signal quality at the cell edge.

[0036] Various apparatuses and methods will now be used to present several aspects of a telecommunications system. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can 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 system as a whole.

[0037] As an example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" that 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuitry, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0038] Therefore, in one or more example embodiments, the described functionality can be implemented using hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of storing computer-executable code in the form of computer-accessible instructions or data structures.

[0039] Figure 1A This is an illustration of 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, 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 macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0040] 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 EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, 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, location, and delivery of warning messages. Base stations 102 can communicate directly or indirectly with each other via a third backhaul link 134 (e.g., an X2 interface) (e.g., via EPC 160 or core network 190). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0041] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to restricted groups referred to as closed subscriber groups (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. This communication link may use one or more carriers. For each carrier allocated in carrier aggregation for transmission in each direction, totaling up to Yx MHz (x component carriers), base station 102 / UE104 may use a spectrum with a bandwidth of up to Y 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. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0042] 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 the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0043] 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, unlicensed spectrum at 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

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

[0045] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often referred to as the (interchangeably) "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the extremely high frequency (EHF) band (30GHz–300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0046] Considering the above aspects, unless otherwise specified, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, it should be understood that when the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0047] 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, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0048] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. 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 optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0049] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, MBMS Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 provides functions for MBMS user service configuration and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmission, authorizing and initiating MBMS bearer services within a Public Land Mobile Network (PLMN), and scheduling MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base station 102 within a Multicast-Broadcast Single Frequency Network (MBSFN) area belonging to a broadcast-specific service, and is responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0050] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are delivered via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IMS, packet switching (PS) streaming services, and / or other IP services.

[0051] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides access to EPC 160 or core network 190 for UE 104. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term.

[0052] Communication systems (such as 5G NR systems) can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network devices, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment such as BS or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), eNB, NR BS, 5G NB, Access Point (AP), TRP, or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0053] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decomposed base stations 181 can be configured to utilize a protocol stack that is physically or logically distributed across 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, CUs 183 can be implemented within a RAN node, and one or more DUs 185 can be co-located with a CU, or alternatively, can be geographically or virtually distributed across one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs 187. Each of the CUs, DUs, and RUs can 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).

[0054] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations advocated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. Individual units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

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

[0056] Refer again Figure 1A In some aspects, UE 104 may include an odd-order modulation (OOM) signaling 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, base station 102 / 180 (or other network equipment with base station functionality) may include an OOM signaling 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.

[0057] 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 via 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). CUs 183 may communicate with one or more DUs 185 via corresponding midhaul links such as F1 interfaces. DUs 185 may communicate with one or more RUs 187 via corresponding fronthaul links. RUs 187 may communicate with UEs 104 via one or more radio frequency (RF) access links. In some implementations, UE 104 may be served simultaneously by multiple RUs 187.

[0058] Each of the units (i.e., CU 183, DU 185, RU 187, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more other units over 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 transmit signals, or both, to one or more other units over a wireless transmission medium.

[0059] In some respects, the CU 183 can host higher-level control functions. These control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), or Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 183. The CU 183 can 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 implementations, the CU 183 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). The CU 183 can be implemented to communicate with the DU 185 for network control and signaling, as needed.

[0060] DU 185 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 187s. In some aspects, DU 185 may at least partially host one or more of the Radio Link Control (RLC) layer, 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) according to functional splits (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 configured to communicate signaling with other layers (and modules) hosted by DU 185 or with control functions hosted by CU 183.

[0061] Lower-layer functionality can be implemented by one or more RU 187s. In some deployments, an RU187 controlled by a 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, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 187 can be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 187 can be controlled by the corresponding DU 185. In some scenarios, this configuration enables the implementation of DU 185 and CU 183 in cloud-based RAN architectures (such as vRAN architectures).

[0062] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 189) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the 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 implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 187s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0063] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface (e.g., via an E2 interface) through data collection and action, connecting one or more CU 183s, one or more DU 185s, or both, and O-eNBs to the near-RT RIC 125.

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

[0065] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 illustrates an example of the second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL), or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). In the process of... Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 34 (mostly UL). Although subframes 3 and 4 are shown as having slot formats 34 and 28 respectively, any particular subframe can 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 mixture of DL, UL, and flexible symbols. The UE is configured using the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0066] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10-millisecond (ms) frame can be divided into 10 equal-sized subframes (1ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may contain 7, 4, or 2 symbols. Each time slot may contain 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may contain 14 symbols, and for time slot configuration 1, each time slot may contain 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ0 to 4 allow for 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols per slot and 2 per subframe. μ Each time slot. Subcarrier spacing and symbol length / duration are functions of a parameter set. Subcarrier spacing can be equal to 2. μ *15 kHz, where μ is the parameter set from 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set μ = 0, and 240 kHz for parameter set μ = 4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples are 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 the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters.

[0067] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0068] like Figure 2AAs illustrated, some REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulated 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 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).

[0069] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising 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 in the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location 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 known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0070] like Figure 2CAs illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or second symbol of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

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

[0072] Figure 3This is a block diagram showing the communication between network device 310 (such as a base station) and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting 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 upper-layer packet data unit (PDU) transfer, error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (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 transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0073] 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) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal cluster 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 decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from channel estimator 374 are used to determine the decoding and modulation scheme, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel state feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier with the corresponding spatial stream for transmission.

[0074] At UE 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and 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 UE 350. If multiple spatial streams are destined for UE 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by network device 310. These soft decisions can be based on a channel estimate calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by network device 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0076] Similar to the functionality described in conjunction with DL transmission performed by network device 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transmission of upper-layer PDUs, error correction via 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 to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0077] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted by the channel estimator 358 from the network device 310 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0078] The UL transmission at network device 310 is handled in a manner similar to that described for the receiver function integrated at UE 350. Each receiver 318RX receives the signal via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0079] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the UE 350. 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 operation.

[0080] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1A The various aspects of the OOM signal component 198.

[0081] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform coupling. Figure 1A The various aspects of the OOM signal configuration component 199.

[0082] Generally, network devices (such as base stations) use an MCS associated with an even modulation order to modulate data intended for transmission to the UE. For example, when modulating downlink data to be transmitted to the 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 demodulating signals with even modulation orders is relatively simpler compared to signals with odd modulation orders (e.g., non-square QAM or APSK). However, various methods have been developed to reduce the complexity in demodulating odd-order modulated signals. Furthermore, while these methods allow the UE to demodulate odd-order modulated signals to reduce complexity, this capability may not be used without some form of coordination with the network device to apply odd-order modulation. Since odd-order modulation can provide increased spectral efficiency granularity, improved PAPR, and improved phase noise reduction compared to even-order modulation, it would be helpful to be able to configure more MCS to allow odd-order modulation to be applied to downlink or uplink signaling.

[0083] Typically, a UE's demodulator (e.g., the RX processor 356 of UE 350 or components 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 modulation symbols or constellation points in the constellation diagram, while the soft limiter component makes soft decisions about the reliability of a bit value associated with a modulation symbol or constellation point in the constellation diagram. For even-order modulation (square QAM), these hard or soft decisions can be performed in a relatively simple way because the constellation diagram associated with 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 quadrature "Q" signal axis), or determine the distance from the origin to the constellation point based solely on the I or Q value of the modulation symbol (but not both values) when making a hard decision about the associated bit value. Similarly, when making soft decisions about associated bit values, the soft limiter can determine the log-likelihood ratio (LLR) associated with a bit value based solely on the I or Q value of the modulation symbol (rather than both of these values).

[0084] However, for odd-order modulations such as non-square QAM, these decisions are more complex to implement because the constellation diagrams form non-square shapes (e.g., cross-shaped). For example, in a non-square QAM constellation diagram, while a hard limiter can similarly make decisions about bit values ​​based solely on the I or Q values ​​of constellation points that are geographically closer to the origin (e.g., the inner region of the cross-shaped shape) as in square QAM, a hard limiter typically requires making more complex decisions based on both the I and Q values ​​of constellation points that are geographically farther from the origin (e.g., the edges of the cross-shaped shape). Similarly, a soft limiter typically needs to determine the LLR value associated with the bit value based on both the I and Q values ​​of the modulation symbol, which may require very large lookup tables with different mappings between the I and Q values ​​for the corresponding bit values.

[0085] Figures 4A to 4C Examples 400, 420, and 440 illustrate non-square QAM constellation diagrams for 32QAM, 128QAM, and 512QAM, respectively. As can be seen from these diagrams, such constellation diagrams can include cross-shaped constellation points or modulation symbols corresponding to possible bit values. Therefore, because these constellation points are missing from the corners of the constellation diagram, hard and soft decisions regarding a bit value in non-square QAM can be more complex than those in square QAM. For example, although... Figures 4A to 4C The position values ​​in the inner region (central square region) of a constellation can be determined solely based on the I or Q values ​​of its corresponding constellation point, but the position values ​​in the outer region (outer rectangular region) of these constellation diagrams can be a function of both the I and Q values ​​of their corresponding constellation points.

[0086] However, improvements have been made to facilitate the demodulation of odd-order modulated signals. For example, to achieve simplified soft demapping of non-square QAMs, the geometric trend and folding overlap methods of the non-square QAM constellation can be used to allow the nonlinear LLR equation based on the maximum logarithmic MAP algorithm to be approximated as a linear equation, thereby significantly reducing computational complexity. This method, along with other methods for reducing the demodulation complexity of odd-order modulated symbols, allows for more efficient achievement of improved SPEF, PAPR reduction, and phase noise mitigation associated with odd-order modulated symbols.

[0087] As previously mentioned, odd-order modulation can lead to improved SPEF, PAPR, and phase noise reduction. For example, square QAM typically includes a 6 dB gap between adjacent modulation orders (e.g., 16QAM, 64QAM, 256QAM, etc.), while adding odd-order modulation orders can result in a smaller 3 dB gap between adjacent modulation orders (e.g., 16QAM, 32QAM, 64QAM, 128QAM, 256QAM, etc.), thus leading to improved SPEF. Furthermore, for square QAM, the UE and base station (or other network equipment with base station functionality) typically include power amplifiers (PAs) operating at lower Tx power to avoid nonlinearity, while for odd-order modulation, the PA can operate at higher Tx power (and therefore achieve PA efficiency) because non-square QAM or APSK constellations are closer to circular in shape than square QAM constellations, resulting in improved PAPR. Furthermore, in square QAM, the constellation points at the corners of the constellation diagram have the largest radii and are therefore most prone to phase errors (e.g., for a given phase noise variation or phase rotation, the angles or corresponding arcs of these symbols can be very large, leading to a high symbol error rate). However, for odd-order modulation, these corners are trimmed and the symbols are shaped to be more angularly away (e.g., more circular in shape than square QAM constellations), resulting in symbols with smaller arcs and providing improved phase noise mitigation (more resilient to phase noise or the ability to eliminate phase noise).

[0088] The improved PAPR and phase noise reduction associated with odd modulation orders are 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 Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveforms, or Nyquist pulse-shaped single-carrier waveforms. Compared to OFDM in the time domain, these waveforms exhibit simpler phase noise suppression because tracking pilot and phase noise and eliminating noise in these waveforms is less complex than in OFDM. In OFDM (purely without DFT extension), inter-carrier interference (ICI) can occur between adjacent carriers, making it difficult to completely eliminate ICI or phase noise, while in single-carrier or DFT-OFDM waveforms, phase noise can be almost completely eliminated. Furthermore, better PA efficiency can be achieved from the low PAPR associated with these waveforms, because UEs or base stations (or other network devices) with lower-cost PAs can utilize the improved PAPR from odd-order modulation to compensate for the nonlinearity of these PAs.

[0089] Therefore, odd-order modulation can address the challenges of improving spectral efficiency, reducing PAPR, and mitigating phase noise in sub-THz environments (where phase noise is typically high, and PA nonlinearity is typically poor or PA cost is high). For example, odd-order modulation can provide greater resilience to phase noise, reduce PAPR and thus provide better PA efficiency, and handle bandwidth more effectively. Therefore, it would be helpful for UEs with the ability to demodulate odd-order modulated signals to coordinate with network devices (e.g., base stations) in subsequent signaling. Thus, aspects of this disclosure allow network devices to configure the odd-order modulation order to be used for downlink or uplink transmission via signaling between the network device and the UE.

[0090] In one example, if the UE is currently communicating with the network device using an even-order modulation from an MCS table, but the UE is capable of performing the simplified soft demapping for non-square QAM as previously described in conjunction with LLR calculations (or otherwise capable of demodulating odd-order modulated signals with minimal complexity), the UE can request the network device to switch from that MCS table to a different MCS table (an extended MCS table) that includes MCSs associated with both odd-order and even-order modulation. Therefore, a UE capable of receiving odd-order modulated signals can benefit from the associated SPEF improvement with odd-order 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), the UE can send this request to the network device to apply the extended MCS table, thus similarly benefiting from improved phase noise resilience. In yet another example, if the UE is located at the cell edge but includes the capability to demodulate odd-order modulated signals, the UE can request the network device to switch to an extended MCS table, resulting in a lower PAPR. This lower PAPR also allows the UE's transmit power to increase by 0.8 dB, thus providing a significant improvement in signal quality at the cell edge.

[0091] Figure 5 Example 500 illustrates an MCS table 502 comprising an MCS 504 having 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 comprising an additional MCS 508 having odd modulation orders (e.g., 8QAM, 32QAM, 128QAM, 512QAM) and various code rates (associated with up to M different MCS indices). Each row of an MCS 504 or MCS table 502 for a given modulation order can indicate a specific code rate, where lower values ​​indicate stronger code rates (e.g., a code rate of 0.5 for 16QAM results in an SPEF of 2 bps / Hz), while higher values ​​indicate weaker code rates (e.g., a code rate of 0.9 for 16QAM results in an SPEF of 3.6 bps / Hz).

[0092] Extended MCS table 506 includes not only an additional MCS 508 with odd modulation orders, but also an MCS 510 corresponding to MCS 504 in MCS table 502 with even modulation orders (e.g., QPSK, 16QAM, 64QAM, 256QAM). Therefore, the size of extended MCS table 506 can effectively be twice that of MCS table 502. However, as discussed below... 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.

[0093] 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.

[0094] Figure 6 Example 600 illustrates a call flow between a UE 602 and a network device 604 (e.g., base station 102 / 180 or split BS 181) 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 Figures 4A to 4C(As illustrated in the diagram) or associated with a non-square APSK constellation 616. UE 602 can receive this information indicating configuration 606, for example, after the UE enters the cell of network device 604, in which case the UE can determine, according to configuration 606, whether the cell supports OOM (e.g., network supports...). Figure 5 (The MCS in the extended MCS table 506). If configuration 606 indicates that the network supports odd-number modulation order MCS such as 608, then network device 604 can switch between MCS table 502 and extended MCS table 506 to communicate with UE 602. Otherwise, if configuration 606 indicates that no network supports 608 (e.g., network support for 608 does not exist), then only even-number modulation orders such as those in MCS table 502 can be applied.

[0095] Network support for OOM 608 can be indicated via flags, bit values, or information elements (e.g., having a value "1" indicating the presence of network support and a value "0" indicating the absence of network support, or vice versa). Network device 604 can support OOM (and therefore network support 608 can be configured accordingly), for example, if network device 604 is able to apply the MCS associated with odd modulation order (e.g., non-square QAM or APSK) to its downlink transmission. For example, if Figure 5 If the extended MCS table 506 is predefined or configured with the odd modulation order that the network device can utilize in its downlink transmissions, then this capability may exist, and therefore network support 608 for OOM may exist. Conversely, if the extended MCS table 502 is not yet defined or configured and only supports MCS table 506, then this capability may not exist, and therefore network support 608 for OOM may be lacking. For uplink transmissions, if the aforementioned MCS table is predefined or configured, the network device 604 can similarly indicate that network support 608 exists, allowing the UE to similarly use its odd modulation order for its uplink transmissions. Therefore, network support 608 can be a static indication broadcast from the network device 604 to the UE 602.

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

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

[0098] Regarding phase noise resilience, under high SNR conditions, thermal noise becomes less dominant, while phase noise becomes a significant factor affecting wireless communication. For example, typically, as a UE increases its Tx power, its throughput also increases. As SNR increases, throughput continues with this increase in Tx power until a certain threshold or phase noise level (e.g., 28 dB in mmW) is reached, at which point throughput may no longer increase even with further increases in Tx power (because phase noise may now limit throughput). However, with phase noise correction, the UE can continue to increase its throughput beyond this limit. Therefore, at block 627, UE 602 can check whether its observed SNR is at least equal to the 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, UE 602 can transmit 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 better handling phase noise at higher SNRs.

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

[0100] In another example where network support 608 exists, as an alternative (or supplement) to UE 602 sending a request 618 to network device 604 to switch to extended MCS table 506, network device 604 may determine to switch to extended MCS table 506 if UE 602 indicates that it can support OOM. For example, network device 604 may send an OOM support query message 631 to UE 602 to inquire whether UE 602 can demodulate odd-order modulated signals. In response to OOM support query message 631, UE 602 may send an acknowledgment 630 indicating whether the UE includes OOM support 632. For example, if UE 602 can perform the simplified soft demapping for non-square QAM as previously described in conjunction with LLR calculations (or otherwise can demodulate odd-order modulated signals with minimized complexity), UE 602 may indicate in acknowledgment 630 that it includes OOM support 632. Otherwise, the UE may indicate that it does not include OOM support 632. OOM support 632 can be indicated via flags, bit values, or information elements (e.g., having a value "1" indicating the presence of UE support and a value "0" indicating the absence of UE support, or vice versa). In response to receiving confirmation 630, if OOM support 632 is indicated, network device 604 can determine to switch to extended MCS table 506 and apply one of its MCS 510 as the new MCS 622.

[0101] In another example where network support 608 exists, UE 602 may send a CSI report 634 instructing network device 604 to apply OOM 636. Generally, in response to receiving a CSI-RS (not shown), the UE may measure the CSI-RS to determine the CQI associated with a specific MCS and report that CQI to network device 604 in the CSI report 634. If MCS table 502 is currently being applied, the UE may select a CQI associated with an even-numbered modulation order in MCS table 502. However, if network device 604 indicates network support 608 for OOM (e.g., an extended MCS table 506 may be applied), the UE may alternatively select a CQI associated with an odd-numbered modulation order in the extended MCS table 506. This odd-numbered 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 MCS (even modulation order and odd modulation order), similar to MCS table 502 and extended MCS table 506.

[0102] Alternatively or additionally, if the UE supports OOM (e.g., the UE includes OOM support 632) but is currently using an MCS from MCS table 502, the UE can determine itself to select a new MCS with an odd modulation order from extended MCS table 506 and include the CQI associated with that new MCS in CSI report 634. Thus, CSI report 634 can effectively function as a request to network device 604 (similar to request 618) to switch the current MCS 620 (even modulation order) to the new MCS 622 (odd modulation order indicated via OOM 636). If UE 602 determines that the odd modulation order MCS is superior to the even modulation order MCS at the currently observed SNR, UE 602 can 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 MCS table 502 is exactly better than the odd-order modulation MCS in extended MCS table 506, the UE can still select the CQI associated with the even-order modulation from MCS table 502.

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

[0104] Figure 7Example 700 illustrates a graph showing the SPEF improvement resulting from odd modulation order based on the relationship between SNR and block error rate (BLER). As can be seen in the illustrated graph and assuming a fixed code rate (e.g., 0.86 or 0.87), increasing the modulation order from one even modulation order to another (e.g., 16QAM to 64QAM) requires a 6dB increase in SNR 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) requires only a 3dB increase in SNR to handle the additional bits provided by the increased modulation order. Therefore, by configuring odd modulation orders for use in wireless communication, the SPEF granularity can be increased via finer transitions in the modulation order (e.g., even-to-odd and odd-to-even). Using such finer SPEF granularity can lead to improved throughput.

[0105] Figure 8 Example 800 illustrates a graph showing the SPEF improvement from odd modulation orders based on the relationship between SNR and throughput (Tput). In this example, the curves shown refer to even modulation order 256QAM (low curve 802), odd modulation order 512QAM (middle curve 804), and even modulation order 1024QAM (high curve 806), but other adjacent modulation orders can be used in other examples. As can be seen from the graph, the middle curve 804 shows a lower throughput at higher SNR than the high curve 806, and a higher throughput at lower SNR, while the middle curve 804 shows a higher throughput at higher SNR than the low curve 802, and a lower throughput at lower SNR. Therefore, a region 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. Region 808 represents the SNR range where odd modulation orders produce better SPEF than adjacent even modulation orders, because in this region, the intermediate curve 804 includes the highest throughput at the lowest SNR between the three curves. Furthermore, this region of maximum throughput and minimum SNR is not limited to the set of modulation orders 256QAM, 512QAM, and 1024QAM; conversely, a similar region can 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 can omit even modulation orders with code rates suitable for these regions, because odd modulation orders will be superior to adjacent even modulation orders for certain code rates in the associated SNR range.

[0106] Regarding why the intermediate curve 804 shows a lower throughput (bits per symbol) at a higher SNR than the high curve 806, the odd modulation order is associated with one less bit than the higher modulation order (e.g., 512QAM vs. 1024QAM), resulting in a weaker code rate with less overhead for the odd modulation order. 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, to match that number, 512QAM would 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, the odd modulation order will require a higher code rate than the higher modulation order, resulting in the odd modulation order requiring a higher SNR to maintain the same throughput. Therefore, a reduction in the bit rate (even as low as 1%) can lead to significant losses at the decoder of the UE or network equipment (e.g., base station), and thus necessitates operation at a higher SNR. This is why the intermediate curve 804 is shown below the high curve 806 at higher SNR. Furthermore, for similar reasons, the lower curve 802 shows lower throughput than the intermediate curve 804 at higher SNR.

[0107] Regarding why the intermediate curve 804 exhibits higher throughput at lower SNR than the high curve 806, the receiver of the UE or network device (e.g., a base station) includes not only a decoder but also a demodulator. While the decoder can benefit from higher even-order modulation (e.g., 1024QAM) with a strong code rate (e.g., 0.5), at lower SNR, the demodulator may experience higher thermal noise, may perform less accurate hard or soft decisions (e.g., maximum likelihood approximation or LLR calculations), and may experience poorer channel estimation. Therefore, at lower SNR, the throughput of higher even-order modulation may be limited by the demodulator's capabilities, regardless of the decoder's strength, resulting in the intermediate curve 804 appearing above the high curve 806 at lower SNR. Furthermore, for similar reasons, the high curve 802 exhibits lower throughput than the intermediate curve 804 at lower SNR.

[0108] Figure 9Example 900 illustrates a graph showing the PAPR improvement resulting from an odd modulation order configuration. As illustrated, even modulation orders 902 are typically associated with an average PAPR of approximately 0.8 dB higher than the odd modulation orders 904 that are adjacent to these even modulation orders. This average can be shown by the individual values ​​of PAPR for different constellations in Table 906 associated with the PAPR graph. Therefore, a UE using odd modulation orders for its communications (e.g., at the cell edge) can achieve an average PAPR reduction of 0.8 dB, allowing the UE to use this reduced PAPR to increase its Tx power and improve signal quality.

[0109] Figure 10 Example 1000 illustrates a non-square QAM constellation diagram indicating phase noise resilience. As can be seen from the diagram, the individual constellation points are slightly blurred due to thermal noise (additive white Gaussian noise (AWGN)) and phase noise (PN). In sub-THz environments carrying modulation symbols on single-carrier or DFT-OFDM waveforms, phase noise can be significant, and therefore modulation symbols may experience phase rotation or arcing. Constellation points farther from the origin of the diagram may experience more phase rotation or longer arcs, especially those at the corners of the constellation diagram with the greatest distance. For square QAM constellations, these corners can experience significant arcing and therefore may overlap with adjacent constellation points, leading to a high symbol error rate. However, for a non-square QAM constellation diagram, the corner constellation points 1002 lack the adjacent constellation points present in a square QAM constellation (because the corners here have been trimmed to form a cross shape), and therefore the risk of this overlap is significantly reduced, resulting in a lower symbol error rate. Therefore, odd modulation orders provide more resilience to phase noise than even modulation orders. Additionally, PAPR can refer to the ratio of the peak distance of a constellation point to the average distance of the constellation point, and PAPR may be lower because non-square QAM constellations have a lower peak distance than square QAM constellations (due to diagonal trimming).

[0110] Figure 11 Example 1100 illustrates a graph showing the performance improvement achievable with an odd modulation order compared to an even modulation order in a single-carrier waveform. For example, in Figure 11 In the illustrated example, gains of 0.5dB–0.85dB in the SNR without phase noise and 0.5dB–1.1dB in the SNR with phase noise can be achieved by using a non-square QAM with a corresponding order exceeding the adjacent order of the square QAM to maintain the same throughput. If we add at the top for Figure 9The 0.8 dB PAPR reduction in the described SNR means that applying odd modulation order to communication in a single-carrier waveform can result in a total link budget benefit of 1.3 dB–1.9 dB greater than that of even modulation order.

[0111] Figure 12 Example 1200 illustrates a graph showing the performance improvement achievable with odd modulation orders compared to even modulation orders in OFDM waveforms. Figure 12 In the illustrated example, a gain of 0.3dB–1dB in the SNR without phase noise can be achieved by exceeding the adjacent orders of a non-square QAM to maintain the same throughput. Therefore, in the absence of phase noise, OFDM waveforms include performance improvements similar to single-carrier waveforms. However, in the case of phase noise, for OFDM waveforms, the receiver performs common phase error (CPE) correction after reaching a certain SNR level, which ultimately limits throughput. For example, in… Figure 12 In the illustrated example, the gain may not be realized after an SNR of 28 dB with phase noise because throughput is limited even at higher SNRs. Therefore, at high SNRs, the performance improvement of non-square QAM over square QAM for OFDM waveforms may no longer be achievable. Thus, if the observed SNR is less than the threshold associated with maximum throughput (e.g., an SNR of 28 dB), a UE with the ability to demodulate the OFDM waveform using an odd modulation order to achieve improved SPEF but without the ability to correct phase noise to increase throughput beyond that limit can request the application of OOM. For example, the UE may transmit a request to the base station (or other network equipment with base station functionality) to switch from MCS table 502 to extended MCS table 506 (e.g., Figure 6 (Request 618 in the text). If the observed SNR is greater than the threshold, the UE can avoid transmitting the request because, since the UE cannot correct phase noise exceeding the limit, SPEF improvement may no longer be achievable at such a high SNR. Conversely, if the UE is able to correct the phase noise such that the throughput can continue to exceed the threshold (e.g., above 28 dB), the UE can transmit the request when it determines that the observed SNR is greater than the threshold, as previously described (e.g., in the text). Figure 6 (at frame 627).

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

[0113] At 1302, the UE receives a configuration indicating network support for communication using odd-order modulation. For example, 1302 may be performed by configuration component 1540. In one example, this configuration may be RRC configuration or MAC-CE. In one example, odd-order modulation may be associated with a non-square QAM constellation or a non-square APSK constellation. For example, refer to... Figure 6 UE 602 can receive network support 608 (e.g., network support) indicating an OOM (Out of Memory) in the communication between UE 602 and network device 604. Figure 5 The extended MCS table 506 contains the MCS configuration 606. For example, configuration 606 can be RRC configuration 610 or MAC-CE 612, and OOM can be with a non-square QAM constellation 614 (e.g., as...). Figures 4A to 4C (As illustrated in the diagram) or a non-square APSK constellation 616 is associated. Network support for OOM 608 can be indicated via flags, bit values, or information elements (e.g., having a value "1" indicating the presence of network support and a value "0" indicating the absence of network support, or vice versa). Network device 604 can support OOM (and therefore network support 608 can be configured accordingly), for example, if network device 604 is able to apply the 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 has been predefined or configured with the odd modulation order 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 aforementioned MCS table has been predefined or configured, the network device 604 may similarly indicate that network support 608 exists, so that the UE can similarly use its odd modulation order for its uplink transmissions.

[0114] At 1304, the UE may, in response to this configuration, send a request to change the current MCS used for 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 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 PUCCH. In one example, the request may be included in a CSI report. For example, refer to... Figure 6UE 602 may, in response to configuration 606, send a request 618 to change the current MCS 620 (e.g., one of MCS 504 in MCS table 502) used for communication between UE 602 and network device 604 to a new MCS 622 (e.g., one of additional MCS 508 in extended MCS table 506). MCS table 502 may include even-numbered modulation orders and decoding rates, but not odd-numbered modulation orders and decoding rates, such as... Figure 5 As illustrated in the example. In contrast, the extended MCS table 506 may include both odd modulation order and decoding rate, as well as even modulation order and decoding rate. UE 602 may send request 618 in PUSCH 624 or in PUCCH 626 (such as in UCI or CSI report 628) to utilize the new MCS 622 to achieve SPEF improvements. In response to receiving request 618, network device 604 may send DCI 638 to UE 602 to schedule downlink or uplink transmission of data 640 using the odd-order modulation MCS from the extended MCS table 506.

[0115] 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. For example, refer to... Figure 6 UE 602 can determine whether to send request 618 to network device 604 based on the currently observed SNR (e.g., the SNR of configuration 606 or other previous communications between UE 602 and network device 604). For example, at block 627, UE 602 can check whether its observed SNR is at least equal to the phase noise SNR threshold (e.g., 28 dB), where phase noise correction may be needed to achieve maximum throughput. In response to this determination, UE 602 can transmit 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 better handling phase noise at higher SNRs. Alternatively, at block 629, UE 602 can check whether its observed SNR is at most equal to the cell edge SNR threshold (e.g., -5 dB), where Tx power increases may be helpful. In response to this determination, UE 602 can transmit 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 nearly 1 dB (e.g., as above for...). Figure 9 (As described).

[0116] 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 the MCS 504 with 64QAM, and thus the extended MCS table 506 can omit the 64QAM MCSs 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

[0117] 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, and 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 6UE 602 can receive an OOM support query message 631 from network device 604, querying whether the UE is capable of demodulating odd-order modulated signals. In response to the OOM support query message 631, UE 602 can send an acknowledgment 630 indicating whether the UE includes OOM support 632. For example, if UE 602 is capable of performing the simplified soft demapping for non-square QAM as previously described in conjunction with LLR calculations (or otherwise capable of demodulating odd-order modulated signals with minimized complexity), UE 602 can indicate in acknowledgment 630 that it includes OOM support 632. OOM support 632 can be indicated via flags, bit values, or information elements (e.g., having a value "1" indicating the presence of UE support and a value "0" indicating the absence of UE support, or vice versa). In response to receiving acknowledgment 630, if the presence of OOM support 632 is indicated, network device 604 can determine to switch to extended MCS table 506 and apply one of its MCS 510 as the new MCS 622.

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

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

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

[0121] Finally, at 1314, the UE can transmit (or receive) data in the signal using odd-order modulation. For example, 1314 can be performed by signal component 1552. In one example, the data can be transmitted (or received) in an SC-FDMA waveform, a DFT-s-OFDM waveform, or a Nyquist pulse-shaped single-carrier waveform. For example, refer to... Figure 6 UE 602 can use the new MCS 622 (odd-order modulation) to transmit signal 642 including data 640. For example, the Tx processor 368 of UE 350 can perform odd-order modulation by mapping the corresponding codewords of the odd-numbered bits (symbols) of data 640 to the amplitude (or frequency or phase value) of the I and Q signals, performing digital-to-analog conversion of the I and Q signals, generating a carrier waveform, and multiplying the carrier waveform with the I and Q signals. This signal can be carried as an SC-FDMA waveform 644, a DFT-s-OFDM waveform 646, a Nyquist pulsed single-carrier waveform 648, or other waveforms that allow for simpler phase noise suppression and lower PAPR. Alternatively, UE 602 can use the new MCS 622 (odd-order modulation) to receive signal 642 including data 640. For example, the Rx processor 356 of UE 350 can perform odd-order demodulation using the following process: frequency-shifting a signal 642, which includes a mapped codeword with an odd number of bits (symbols) of data 640, to equivalent baseband I and Q signals or intermediate frequency (IF) signals; performing analog-to-digital conversion and detecting the amplitude of the I and Q signals or the frequency or phase of the IF signal; and mapping the quantized amplitude, frequency, or phase to the codeword. Therefore, UE 602 can achieve improved SPEF, PAPR reduction, and phase noise resilience compared to its previous MCS (even-order modulation).

[0122] Figure 14 This is a flowchart 1400 of a wireless communication method. The method can 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; apparatus 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.

[0123] At 1402, the network entity sends a configuration indicating network support for communication using odd-order modulation. For example, 1402 may be performed by configuration component 1640. In one example, this configuration may be RRC configuration or MAC-CE. In one example, odd-order modulation may be associated with a non-square QAM constellation or a non-square APSK constellation. For example, refer to... Figure 6 Network device 604 can send an indication of network support 608 (e.g., network support) for OOM in the communication between UE 602 and network device 604. Figure 5 The extended MCS table 506 contains the MCS configuration 606. For example, configuration 606 can be RRC configuration 610 or MAC-CE 612, and OOM can be with a non-square QAM constellation 614 (e.g., as...). Figures 4A to 4C (As illustrated in the diagram) or a non-square APSK constellation 616 is associated. Network support for OOM 608 can be indicated via flags, bit values, or information elements (e.g., having a value "1" indicating the presence of network support and a value "0" indicating the absence of network support, or vice versa). Network device 604 can support OOM (and therefore network support 608 can be configured accordingly), for example, if network device 604 is able to apply the 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 has been predefined or configured with the odd modulation order 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 aforementioned MCS table has been predefined or configured, the network device 604 may similarly indicate that network support 608 exists, so that the UE can similarly use its odd modulation order for its uplink transmissions.

[0124] At 1404, the network entity can respond to this configuration by receiving a request to change the current MCS used for communication 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, 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, 1404 can be performed by request component 1642. In one example, the request can be received in a PUSCH or PUCCH. In one example, the request can be included in a CSI report. For example, refer to... Figure 6Network device 604 may, in response to configuration 606, receive a request 618 to change the current MCS 620 (e.g., one of MCS 504 in MCS table 502) used for communication between UE 602 and network device 604 to a new MCS 622 (e.g., one of additional MCS 508 in extended MCS table 506). MCS table 502 may include even-numbered modulation orders and decoding rates, but not odd-numbered modulation orders and decoding rates, such as... Figure 5 As illustrated in the example. In contrast, the extended MCS table 506 may include both odd modulation order and decoding rate, as well as even modulation order and decoding rate. Network device 604 may receive request 618 in PUSCH 624 or in PUCCH 626 (such as in UCI or CSI report 628) to utilize the new MCS 622 to achieve SPEF improvements. In response to receiving request 618, network device 604 may send DCI 638 to UE 602 to schedule downlink or uplink transmission of data 640 using the odd-order modulation MCS from extended MCS table 506.

[0125] In one example, a network entity may receive the request at 1404 in response to a configured SNR received at 1402 that is at least equal to the phase noise SNR threshold. In another example, a network entity may receive the request at 1404 in response to a configured SNR received at 1402 that is at most equal to the cell edge SNR threshold. For example, refer to... Figure 6 UE 602 can determine whether to send request 618 to network device 604 based on the currently observed SNR (e.g., the SNR of configuration 606 or other previous communications between UE 602 and network device 604). For example, at block 627, UE 602 can check whether its observed SNR is at least equal to the phase noise SNR threshold (e.g., 28 dB), where phase noise correction may be needed to achieve maximum throughput. In response to this determination, UE 602 can transmit, and network device 604 can receive, 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 better handling phase noise at higher SNRs. Alternatively, at block 629, UE 602 can check whether its observed SNR is at most equal to the cell edge SNR threshold (e.g., -5 dB), where Tx power increases may be helpful. In response to this determination, UE602 can transmit and network device 604 can receive 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 nearly 1 dB (e.g., as above for...). Figure 9 as described

[0126] 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 Figure 5 and Figure 8 , at certain code rates, the odd modulation orders may have better SPEF or throughput than the 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 MCSs 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 [[REF]], 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.

[0127] 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 acknowledgement 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 acknowledgement component 1646. In one example, the message may be sent in the PDSCH or PDCCH. For example, referring Figure 6Network device 604 may send an OOM support query message 631 to UE 602, querying whether the UE is capable of demodulating odd-order modulated signals. In response to the OOM support query message 631, UE 602 may send, and network device 604 may receive, an acknowledgment 630 indicating whether the UE includes OOM support 632. For example, if UE 602 is capable of performing the simplified soft demapping for non-square QAM as previously described in conjunction with LLR calculations (or otherwise capable of demodulating odd-order modulated signals with minimized complexity), then UE 602 may indicate in acknowledgment 630 that it includes OOM support 632. OOM support 632 may be indicated via flags, bit values, or information elements (e.g., having a value "1" indicating the presence of UE support and a value "0" indicating the absence of UE support, or vice versa). In response to receiving acknowledgment 630, if the presence of OOM support 632 is indicated, network device 604 may determine to switch to extended MCS table 506 and apply one of its MCS 510 as the new MCS 622.

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

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

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

[0131] Finally, at 1414, the network entity can receive (or transmit) data in the signal using odd-order modulation. For example, 1414 can be performed by signal component 1652. In one example, data can be received (or transmitted) in an SC-FDMA waveform, a DFT-s-OFDM waveform, or a Nyquist pulse-shaped single-carrier waveform. For example, refer to... Figure 6 Network device 604 can use the new MCS 622 (odd-order modulation) to receive signal 642 including data 640. For example, the Rx processor 370 of network device 310 can perform odd-order demodulation by: frequency-shifting signal 642, which includes a mapped codeword containing an odd number of bits (symbols) of data 640, to equivalent baseband I and Q signals or intermediate frequency (IF signal); performing analog-to-digital conversion and detecting the amplitude of the I and Q signals or the frequency or phase of the IF signal; and mapping the quantized amplitude, frequency, or phase to codewords. This signal can be carried as an SC-FDMA waveform 644, a DFT-s-OFDM waveform 646, a Nyquist pulsed single-carrier waveform 648, or other waveforms that allow for simpler phase noise suppression and lower PAPR. Alternatively, network device 604 can use the new MCS 622 (odd-order modulation) to transmit signal 642 including data 640. For example, the Tx processor 316 of network device 310 can perform odd-order modulation using the following process: mapping the corresponding codewords, including the odd-numbered bits (symbols) of 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; generating a carrier waveform; and multiplying the carrier waveform by the I and Q signals. Therefore, network device 604 can achieve improved SPEF, PAPR reduction, and phase noise resilience compared to its previous MCS (even-order modulation).

[0132] Figure 15Figure 1500 illustrates an example of a hardware implementation for device 1502. Device 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 Module (SIM) cards 1520, an application processor 1506 coupled to a Secure Digital Card (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 BS 102 / 180 via the cellular RF transceiver 1522. The cellular baseband processor 1504 may include computer-readable media / memory. This computer-readable media / memory may be non-transitory. The cellular baseband processor 1504 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1504, the software causes the cellular baseband processor 1504 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1504 during software execution. The cellular baseband processor 1504 also includes a receiving component 1530, a communication manager 1532, and a transmitting component 1534. The communication manager 1532 includes one or more exemplary components. 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 module of device 1502.

[0133] The communication manager 1532 includes a configuration component 1540 configured to receive configurations indicating network support for communication using odd-order modulation, for example, as described in conjunction with 1302.

[0134] The communication manager 1532 also includes a request component 1542 that receives configuration-form input from the configuration component 1540 and is configured to, in response to the configuration, send a request to change the current MCS applied to communication 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, for example, as described in conjunction with 1304.

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

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

[0137] The communication manager 1532 also includes a CSI reporting component 1548, which receives configuration-form input 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.

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

[0139] The communication 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 the signal using odd-order modulation, for example, as described in conjunction with 1314.

[0140] The apparatus may include execution Figure 13 The additional components of each box in the algorithm's box in the aforementioned flowchart. Therefore, Figure 13 Each block in the aforementioned flowchart can be executed by a component, and the apparatus can include one or more of those components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0141] In one configuration, device 1502 (and specifically cellular baseband processor 1504) includes: means for receiving a configuration indicating network support for communication using odd-order modulation; and means for transmitting data in a signal using the odd-order modulation.

[0142] 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.

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

[0144] In one configuration, the configuration is either a Radio Resource Control (RRC) configuration or a Media Access Control (MAC) control element (MAC-CE).

[0145] In one configuration, the component for transmitting is further configured to, in response to the configuration, send a request to change the current modulation and decoding scheme (MCS) used for communication 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, wherein the first MCS table includes even-order modulation and lacks odd-order modulation, and the second MCS table includes odd-order modulation.

[0146] In one configuration, the request is sent on the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH).

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

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

[0149] In one configuration, the request is included in the Channel State Information (CSI) report.

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

[0151] In one configuration, the receiving component is further configured to receive a message inquiring whether the device includes odd-order modulation support; and the transmitting component is further configured to, in response to the message, transmit an acknowledgment indicating odd-order modulation support; wherein the signal uses odd-order modulation based on odd-order modulation support.

[0152] In one configuration, the message is received on the Physical Downlink Shared Channel (PDSCH) or the Physical Downlink Control Channel (PDCCH).

[0153] In one configuration, the transmitting component is further configured to transmit a Channel State Information (CSI) report indicating odd-order modulation; and the receiving component is further configured to receive downlink control information (DCI) in response to the CSI report, the downlink control information (DCI) scheduling data in the transmitted signal using odd-order modulation.

[0154] The aforementioned components may be one or more of the aforementioned components of the device 1502 configured to perform the functions described thereas. As described above, the device 1502 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the aforementioned components may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described thereas.

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

[0156] The communication manager 1632 includes a configuration component 1640 configured to send configurations indicating network support for communication using odd-order modulation, for example, as described in conjunction with 1402.

[0157] The communication manager 1632 also includes a request component 1642 that receives configuration-form input from the configuration component 1640 and is configured to, in response to the configuration, receive a request to change the current MCS applied to 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, for example, as described in conjunction with 1404.

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

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

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

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

[0162] The communication 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.

[0163] The apparatus may include execution Figure 14 The additional components of each box in the algorithm's box in the aforementioned flowchart. Therefore, Figure 14 Each block in the aforementioned flowchart can be executed by a component, and the apparatus can include one or more of those components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0164] In one configuration, device 1602 (and specifically baseband unit 1604) includes: means for transmitting a configuration indicating network support for communication using odd-order modulation; and means for receiving data in a signal using odd-order modulation.

[0165] 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.

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

[0167] In one configuration, the configuration is either a Radio Resource Control (RRC) configuration or a Media Access Control (MAC) control element (MAC-CE).

[0168] In one configuration, the receiving component is further configured to, in response to the configuration, receive a request to change the current modulation and decoding scheme (MCS) used 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.

[0169] In one configuration, the request is received on the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH).

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

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

[0172] In one configuration, the request is included in the Channel State Information (CSI) report.

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

[0174] In one configuration, the transmitting component is further configured to transmit a message inquiring whether the UE includes odd-order modulation support; and the receiving component is further configured to receive, in response to the message, an acknowledgment from the UE indicating odd-order modulation support; wherein the signal uses odd-order modulation based on odd-order modulation support.

[0175] In one configuration, the message is sent on the Physical Downlink Shared Channel (PDSCH) or the Physical Downlink Control Channel (PDCCH).

[0176] In one configuration, the receiving component is further configured to receive a Channel State Information (CSI) report indicating odd-order modulation; and the transmitting component is further configured to transmit downlink control information (DCI) in response to the CSI report, the downlink control information (DCI) scheduling data in the transmitted signal using odd-order modulation.

[0177] The aforementioned components may be one or more of the aforementioned components of the device 1602 configured to perform the functions described thereas. As described above, the device 1602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the aforementioned components may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions described thereas.

[0178] Therefore, aspects of this disclosure allow network entities (e.g., base stations or other network devices with base station functionality) to configure odd modulation orders to be applied to downlink or uplink transmissions via signaling between the network entity and the UE, enabling improved SPEF, PAPR reduction, and phase noise mitigation associated with odd modulation orders. If the UE is currently communicating with the network entity using even-order modulation from an MCS table, but the UE is able to demodulate odd-order modulated signals with minimal complexity, the UE can request the network entity to switch from that MCS table to an extended MCS table that includes MCSs associated with both odd and even-order modulations, thereby benefiting from the associated SPEF improvement with odd modulation orders. In another example, if the UE is also able to correct phase noise (typically in single-carrier or DFT-OFDM waveforms), the UE can transmit this request to the network entity to apply an extended MCS table, similarly benefiting from improved phase noise resilience. In another example, if the UE is located at the cell edge but includes the capability to demodulate odd-order modulated signals, the UE can request the network entity to switch to an extended MCS table, resulting in a lower PAPR. This, in turn, allows the UE's transmit power to increase by 0.8 dB, providing a significant improvement in signal quality at the cell edge. Furthermore, the extended MCS table can include the best MCS from the existing MCS table while omitting those MCSs that do not have added values ​​relative to their adjacent odd-order modulation entries, thus saving communication overhead in MCS configuration and reducing CSI reporting complexity.

[0179] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims give the elements of each box in a sample order, but this does not imply limitation to the given specific order or hierarchy.

[0180] 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 may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein elements referred to in the singular are not intended to mean “one and only one,” but rather “one or more” unless specifically stated otherwise. Terms such as “if,” “when,” and “while” should be interpreted as “under the condition of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply suggest that if the condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” means 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, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known to those skilled in the art or will be known later are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” cannot replace the term “component.” Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase “component for…”.

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

[0182] Aspect 1 is an apparatus for wireless communication, the apparatus 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 apparatus to: receive a configuration indicating network support for communication using odd-order modulation; and transmit data in a signal using the odd-order modulation.

[0183] Aspect 2 is the 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.

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

[0185] 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 Media Access Control (MAC) control element (MAC-CE).

[0186] 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 the current modulation and decoding scheme (MCS) for 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, the first MCS table including even-order modulation and lacking odd-order modulation, and the second MCS table including the odd-order modulation.

[0187] Aspect 6 is the apparatus according to aspect 5, wherein the request is sent in the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH).

[0188] Aspect 7 is the 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 a signal-to-noise ratio (SNR) at least equal to a phase noise SNR threshold.

[0189] Aspect 8 is the 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 a signal-to-noise ratio (SNR) configured to be at most equal to a cell edge SNR threshold.

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

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

[0192] 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 an acknowledgment indicating the odd-order modulation support; wherein the signal uses the odd-order modulation based on the odd-order modulation support.

[0193] Aspect 12 is the apparatus according to aspect 11, wherein the message is received in the Physical Downlink Shared Channel (PDSCH) or the Physical Downlink Control Channel (PDCCH).

[0194] Aspect 13 is an apparatus according to any one of aspects 1 to 12, wherein the instructions, when executed by the processor, further cause 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) that schedules the transmission of the data in the signal using the odd-order modulation.

[0195] Aspect 14 is an apparatus for wireless communication, the apparatus 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 apparatus to: transmit a configuration indicating network support for communication using odd-order modulation; and receive data in a signal using the odd-order modulation.

[0196] Aspect 15 is the 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.

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

[0198] 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 Media Access Control (MAC) control element (MAC-CE).

[0199] 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 the current modulation and decoding scheme (MCS) for communication between the apparatus and the user equipment (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 the odd-order modulation.

[0200] Aspect 19 is the apparatus according to aspect 18, wherein the request is received in the Physical Uplink Shared Channel (PUSCH) or the Physical Uplink Control Channel (PUCCH).

[0201] 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 a signal-to-noise ratio (SNR) configured to be at least equal to a phase noise SNR threshold.

[0202] 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 a signal-to-noise ratio (SNR) configured to be at most equal to a cell edge SNR threshold.

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

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

[0205] 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 the user equipment (UE) includes odd-order modulation support; and in response to the message, receive from the UE an acknowledgment indicating the odd-order modulation support; wherein the signal uses the odd-order modulation based on the odd-order modulation support.

[0206] Aspect 25 is the apparatus according to aspect 24, wherein the message is transmitted in the Physical Downlink Shared Channel (PDSCH) or the Physical Downlink Control Channel (PDCCH).

[0207] 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, transmit downlink control information (DCI) that schedules the transmission of the data in the signal using the odd-order modulation.

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

[0209] Aspect 28 is the method according to aspect 27, the method further comprising: in response to the configuration, sending a request to change the current modulation and decoding 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, the first MCS table including even-order modulation and lacking odd-order modulation, and the second MCS table including the odd-order modulation.

[0210] Aspect 29 is a method for wireless communication at a network entity, the method comprising: transmitting a configuration indicating network support for communication using odd-order modulation; and receiving data in a signal using the odd-order modulation.

[0211] Aspect 30 is the method according to aspect 29, the method further comprising: in response to the configuration, receiving a request to change the current modulation and decoding scheme (MCS) for communication between the network entity and the user equipment (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 the odd-order modulation.

Claims

1. An apparatus for wireless communication, the apparatus comprising: a processor; a memory coupled with the processor; and instructions stored in the memory and operable, when executed by the processor, to cause the apparatus to: receive a configuration indicating network support for communications using odd order modulations; in response to the configuration, transmit, to a network entity, a request to change a current modulation and coding scheme, MCS, applied to communications between the apparatus and the network entity from a first MCS in a first MCS table to a second MCS in a second MCS table, the apparatus being a user equipment, UE, the first and second MCS tables each including a plurality of MCSs associated with MCS indexes, each of the plurality of MCSs including a modulation order and a code rate, the first MCS table including even order modulations and lacking odd order modulations, and the second MCS table including the odd order modulations; and transmit data in a signal using the second MCS, the second MCS including one of the odd order modulations.

2. The apparatus of claim 1, wherein the one of the odd order modulations 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 request is transmitted in a physical uplink shared channel, PUSCH, or a physical uplink control channel, PUCCH.

6. The apparatus of claim 1, wherein the instructions, when executed by the processor, further cause the apparatus 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.

7. The apparatus of claim 1, wherein the instructions, when executed by the processor, further cause the apparatus 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.

8. The apparatus of claim 1, wherein the request is included in a channel state information, CSI, report.

9. The apparatus of claim 1, wherein the second MCS table further includes a portion of the even order modulations of the first MCS table.

10. The apparatus of claim 1, wherein the instructions, when executed by the processor, further cause the apparatus to: receive a message interrogating whether the apparatus includes odd order modulation support; and in response to the message, transmit a confirmation indicating the odd order modulation support; wherein the signal uses the one of the odd order modulations based on the odd order modulation support.

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

12. The apparatus of claim 1, wherein the instructions, when executed by the processor, further cause the apparatus to: transmit a channel state information (CSI) report indicating the one of the odd-order modulations; and receive, in response to the CSI report, downlink control information (DCI) scheduling transmission of the data in the signal using the one of the odd-order modulations.

13. An apparatus for wireless communication, the apparatus comprising: a processor; a memory coupled with the processor; and instructions stored in the memory and operable, when executed by the processor, to cause the apparatus: to transmit a configuration indicating network support for communications using odd-order modulations; to receive, in response to the configuration, a request from a user equipment (UE) to change a current modulation and coding scheme (MCS) applied for communications between the apparatus and the UE from a first MCS in a first MCS table to a second MCS in a second MCS table, the apparatus being a network entity, the first and second MCS tables each including a plurality of MCSs associated with MCS indexes, each of the plurality of MCSs including a modulation order and a code rate, the first MCS table including even-order modulations and lacking odd-order modulations, and the second MCS table including the odd-order modulations; and to receive data in a signal using the second MCS, the second MCS including one of the odd-order modulations.

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

15. The apparatus of claim 13, 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.

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

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

18. The apparatus of claim 13, wherein the instructions, when executed by the processor, further cause the apparatus 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.

19. The apparatus of claim 13, wherein the instructions, when executed by the processor, further cause the apparatus 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.

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

21. The apparatus of claim 13, wherein the second MCS table further includes a portion of the even order modulations of the first MCS table.

22. The apparatus of claim 13, wherein the instructions, when executed by the processor, further cause the apparatus to: transmit a message that interrogates whether the UE includes odd order modulation support; and receive, from the UE in response to the message, an acknowledgement that indicates the odd order modulation support; wherein the signal uses the one of the odd order modulations based on the odd order modulation support.

23. The apparatus of claim 22, wherein the message is transmitted in a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH).

24. The apparatus of claim 13, wherein the instructions, when executed by the processor, further cause the apparatus to: receive a channel state information (CSI) report that indicates the one of the odd order modulations; and transmit, in response to the CSI report, downlink control information (DCI) that schedules transmission of the data in the signal using the one of the odd order modulations.

25. A method of wireless communication at a user equipment (UE), comprising: receiving a configuration that indicates network support for communications using odd order modulations; transmitting, to a network entity in response to the configuration, a request for changing a current modulation and coding scheme (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 and second MCS tables each including a plurality of MCSs associated with MCS indexes, each of the plurality of MCSs including a modulation order and a code rate, the first MCS table including even order modulations and lacking odd order modulations, and the second MCS table including the odd order modulations; and transmitting data in a signal using the second MCS, the second MCS including one of the odd order modulations.

26. The method of claim 25, wherein the second MCS table further includes a portion of the even order modulations of the first MCS table.

27. A method of wireless communication at a network entity, the method comprising: transmitting a configuration that indicates network support for communications using odd order modulations; In response to the configuration, receiving, from a user equipment (UE), a request to change a current modulation and coding scheme (MCS) applied for 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 and second MCS tables each including a plurality of MCSs associated with MCS indexes, each of the plurality of MCSs including a modulation order and a code rate, the first MCS table including even order modulations and lacking odd order modulations, and the second MCS table including the odd order modulations; and receiving data in signals using the second MCS, the second MCS including one of the odd order modulations.

28. The method of claim 27, wherein the second MCS table further includes a portion of the even order modulations of the first MCS table.

29. A computer-readable medium having program code stored thereon, wherein the program code is executable by one or more processors of a user equipment (UE) to cause the processors to perform the method of any of claims 25-26.

30. A computer-readable medium having program code stored thereon, wherein the program code is executable by one or more processors of a network entity to cause the processors to perform the method of any of claims 27-28.

Images