Patent ID: 12244410

DETAILED DESCRIPTION

Some wireless communications systems may implement different waveforms for communications at one or more wireless devices (e.g., user equipments (UEs) and network entities), such as a direct Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform or a cyclic prefix (CP)-OFDM waveform. In some cases, for CP-OFDM, a last portion of a data transmission in an OFDM transmission frame may be appended at the beginning of a different OFDM transmission frame and a length of a cyclic prefix may be greater than a channel delay spread. In some other cases, for DFT-s-OFDM, a sequence of bits transmitted for each user may be mapped to a complex constellation of symbols, where each user may be assigned a different Fourier coefficient. A wireless device may support multiple waveforms for one or more downlink or uplink transmissions. However, the wireless device may be unaware of which waveform to use for scheduled data.

As described herein, a UE and network entity may use modulation and coding scheme (MCS) tables with mixed waveform entries to determine when to switch between waveforms. For example, the UE may receive control signaling configuring the MCS table, where a subset of rows in the MCS table (e.g., 16 of 32 rows or 8 of 32 rows) may indicate a DFT-s-OFDM waveform and the rest of the rows may indicate a CP-OFDM waveform (or some other waveform as described herein). The UE may receive dynamic control signaling that selects one or more waveforms to use for scheduled data. For example, the UE may transmit or receive the scheduled data using the DFT-s-OFDM waveform, the CP-OFDM waveform, or both according to the dynamic control signaling.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further described in the context of process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to configuring a mixed-waveform MCS table.

FIG.1illustrates an example of a wireless communications system100that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The wireless communications system100may include one or more network entities105, one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

The network entities105may be dispersed throughout a geographic area to form the wireless communications system100and may include devices in different forms or having different capabilities. In various examples, a network entity105may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities105and UEs115may wirelessly communicate via one or more communication links125(e.g., a radio frequency (RF) access link). For example, a network entity105may support a coverage area110(e.g., a geographic coverage area) over which the UEs115and the network entity105may establish one or more communication links125. The coverage area110may be an example of a geographic area over which a network entity105and a UE115may support the communication of signals according to one or more radio access technologies (RATs).

The UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. The UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115or network entities105, as shown inFIG.1.

As described herein, a node of the wireless communications system100, which may be referred to as a network node, or a wireless node, may be a network entity105(e.g., any network entity described herein), a UE115(e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE115. As another example, a node may be a network entity105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE115, the second node may be a network entity105, and the third node may be a UE115. In another aspect of this example, the first node may be a UE115, the second node may be a network entity105, and the third node may be a network entity105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE115, network entity105, apparatus, device, computing system, or the like may include disclosure of the UE115, network entity105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE115is configured to receive information from a network entity105also discloses that a first node is configured to receive information from a second node.

In some examples, network entities105may communicate with the core network130, or with one another, or both. For example, network entities105may communicate with the core network130via one or more backhaul communication links120(e.g., in accordance with an S1, N2, N3, or other interface protocol). In some examples, network entities105may communicate with one another over a backhaul communication link120(e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities105) or indirectly (e.g., via a core network130). In some examples, network entities105may communicate with one another via a midhaul communication link162(e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link168(e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication links120, midhaul communication links162, or fronthaul communication links168may be or include one or more wired links (e.g., an electrical link, an optical fiber link), one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE115may communicate with the core network130through a communication link155.

One or more of the network entities105described herein may include or may be referred to as a base station140(e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network entity105(e.g., a base station140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity105(e.g., a single RAN node, such as a base station140).

In some examples, a network entity105may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity105may include one or more of a central unit (CU)160, a distributed unit (DU)165, a radio unit (RU)170, a RAN Intelligent Controller (RIC)175(e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO)180system, or any combination thereof. An RU170may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities105in a disaggregated RAN architecture may be co-located, or one or more components of the network entities105may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities105of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

The split of functionality between a CU160, a DU165, and an RU175is flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU160, a DU165, or an RU175. For example, a functional split of a protocol stack may be employed between a CU160and a DU165such that the CU160may support one or more layers of the protocol stack and the DU165may support one or more different layers of the protocol stack. In some examples, the CU160may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaption protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU160may be connected to one or more DUs165or RUs170, and the one or more DUs165or RUs170may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU165and an RU170such that the DU165may support one or more layers of the protocol stack and the RU170may support one or more different layers of the protocol stack. The DU165may support one or multiple different cells (e.g., via one or more RUs170). In some cases, a functional split between a CU160and a DU165, or between a DU165and an RU170may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU160, a DU165, or an RU170, while other functions of the protocol layer are performed by a different one of the CU160, the DU165, or the RU170). A CU160may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU160may be connected to one or more DUs165via a midhaul communication link162(e.g., F1, F1-c, F1-u), and a DU165may be connected to one or more RUs170via a fronthaul communication link168(e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link162or a fronthaul communication link168may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities105that are in communication over such communication links.

In wireless communications systems (e.g., wireless communications system100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network130). In some cases, in an IAB network, one or more network entities105(e.g., IAB nodes104) may be partially controlled by each other. One or more IAB nodes104may be referred to as a donor entity or an IAB donor. One or more DUs165or one or more RUs170may be partially controlled by one or more CUs160associated with a donor network entity105(e.g., a donor base station140). The one or more donor network entities105(e.g., IAB donors) may be in communication with one or more additional network entities105(e.g., IAB nodes104) via supported access and backhaul links (e.g., backhaul communication links120). IAB nodes104may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs165of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs115, or may share the same antennas (e.g., of an RU170) of an IAB node104used for access via the DU165of the IAB node104(e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB nodes104may include DUs165that support communication links with additional entities (e.g., IAB nodes104, UEs115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes104or components of IAB nodes104) may be configured to operate according to the techniques described herein.

For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB nodes104, and one or more UEs115. The IAB donor may facilitate connection between the core network130and the AN (e.g., via a wired or wireless connection to the core network130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network130. The IAB donor may include a CU160and at least one DU165(e.g., and RU170), in which case the CU160may communicate with the core network130over an interface (e.g., a backhaul link). IAB donor and IAB nodes104may communicate over an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol). Additionally, or alternatively, the CU160may communicate with the core network over an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs160(e.g., a CU160associated with an alternative IAB donor) over an Xn-C interface, which may be an example of a portion of a backhaul link.

An IAB node104may refer to a RAN node that provides IAB functionality (e.g., access for UEs115, wireless self-backhauling capabilities). A DU165may act as a distributed scheduling node towards child nodes associated with the IAB node104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes104). Additionally, or alternatively, an IAB node104may also be referred to as a parent node or a child node to other IAB nodes104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes104may provide a Uu interface for a child IAB node104to receive signaling from a parent IAB node104, and the DU interface (e.g., DUs165) may provide a Uu interface for a parent IAB node104to signal to a child IAB node104or UE115.

For example, IAB node104may be referred to as a parent node that supports communications for a child IAB node, and referred to as a child IAB node associated with an IAB donor. The IAB donor may include a CU160with a wired or wireless connection (e.g., a backhaul communication link120) to the core network130and may act as parent node to IAB nodes104. For example, the DU165of IAB donor may relay transmissions to UEs115through IAB nodes104, and may directly signal transmissions to a UE115. The CU160of IAB donor may signal communication link establishment via an F1 interface to IAB nodes104, and the IAB nodes104may schedule transmissions (e.g., transmissions to the UEs115relayed from the IAB donor) through the DUs165. That is, data may be relayed to and from IAB nodes104via signaling over an NR Uu interface to MT of the IAB node104. Communications with IAB node104may be scheduled by a DU165of IAB donor and communications with IAB node104may be scheduled by DU165of IAB node104.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support configuring a mixed-waveform MCS table as described herein. For example, some operations described as being performed by a UE115or a network entity105(e.g., a base station140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes104, DUs165, CUs160, RUs170, RIC175, SMO180).

A UE115may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE115may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE115may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

The UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as the network entities105and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown inFIG.1.

The UEs115and the network entities105may wirelessly communicate with one another via one or more communication links125(e.g., an access link) over one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links125. For example, a carrier used for a communication link125may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity105and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity105, may refer to any portion of a network entity105(e.g., a base station140, a CU160, a DU165, a RU170) of a RAN communicating with another device (e.g., directly or via one or more other network entities105).

In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be positioned according to a channel raster for discovery by the UEs115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs115via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology).

The communication links125shown in the wireless communications system100may include downlink transmissions (e.g., forward link transmissions) from a network entity105to a UE115, uplink transmissions (e.g., return link transmissions) from a UE115to a network entity105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system100(e.g., the network entities105, the UEs115, or both) may have hardware configurations that support communications over a particular carrier bandwidth or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system100may include network entities105or UEs115that support concurrent communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE115may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) such that the more resource elements that a device receives and the higher the order of the modulation scheme, the higher the data rate may be for the device. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE115.

One or more numerologies for a carrier may be supported, where a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE115may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE115may be restricted to one or more active BWPs.

The time intervals for the network entities105or the UEs115may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1/(Δfmax·Nf) seconds, where Δfmaxmay represent the maximum supported subcarrier spacing (SCS), and Nfmay represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on SCS. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the SCS or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system100and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs115. For example, one or more of the UEs115may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs115and UE-specific search space sets for sending control information to a specific UE115.

A network entity105may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity105(e.g., over a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some examples, a cell may also refer to a coverage area110or a portion of a coverage area110(e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs115with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity105(e.g., a lower-powered base station140), as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs115with service subscriptions with the network provider or may provide restricted access to the UEs115having an association with the small cell (e.g., the UEs115in a closed subscriber group (CSG), the UEs115associated with users in a home or office). A network entity105may support one or multiple cells and may also support communications over the one or more cells using one or multiple component carriers.

In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

In some examples, a network entity105(e.g., a base station140, an RU170) may be movable and therefore provide communication coverage for a moving coverage area110. In some examples, different coverage areas110associated with different technologies may overlap, but the different coverage areas110may be supported by the same network entity105. In some other examples, the overlapping coverage areas110associated with different technologies may be supported by different network entities105. The wireless communications system100may include, for example, a heterogeneous network in which different types of the network entities105provide coverage for various coverage areas110using the same or different radio access technologies.

The wireless communications system100may support synchronous or asynchronous operation. For synchronous operation, network entities105(e.g., base stations140) may have similar frame timings, and transmissions from different network entities105may be approximately aligned in time. For asynchronous operation, network entities105may have different frame timings, and transmissions from different network entities105may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

Some UEs115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity105(e.g., a base station140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program. Some UEs115may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

Some UEs115may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs115include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs115may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC). The UEs115may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE115may be able to communicate directly with other UEs115over a device-to-device (D2D) communication link135(e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs115of a group that are performing D2D communications may be within the coverage area110of a network entity105(e.g., a base station140, an RU170), which may support aspects of such D2D communications being configured by or scheduled by the network entity105. In some examples, one or more UEs115in such a group may be outside the coverage area110of a network entity105or may be otherwise unable to or not configured to receive transmissions from a network entity105. In some examples, groups of the UEs115communicating via D2D communications may support a one-to-many (1:M) system in which each UE115transmits to each of the other UEs115in the group. In some examples, a network entity105may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs115without the involvement of a network entity105.

In some systems, a D2D communication link135may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities105, base stations140, RUs170) using vehicle-to-network (V2N) communications, or with both.

The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs115served by the network entities105(e.g., base stations140) associated with the core network130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services150for one or more network operators. The IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

The wireless communications system100may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs115located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system100may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band, or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system100may support millimeter wave (mmW) communications between the UEs115and the network entities105(e.g., base stations140, RUs170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate use of antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

The wireless communications system100may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system100may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating in unlicensed RF spectrum bands, devices such as the network entities105and the UEs115may employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A network entity105(e.g., a base station140, an RU170) or a UE115may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity105or a UE115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity105may be located in diverse geographic locations. A network entity105may have an antenna array with a set of rows and columns of antenna ports that the network entity105may use to support beamforming of communications with a UE115. Likewise, a UE115may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

The network entities105or the UEs115may use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity105, a UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

A network entity105or a UE115may use beam sweeping techniques as part of beamforming operations. For example, a network entity105(e.g., a base station140, an RU170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity105multiple times along different directions. For example, the network entity105may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity105, or by a receiving device, such as a UE115) a beam direction for later transmission or reception by the network entity105.

Some signals, such as data signals associated with a particular receiving device, may be transmitted by transmitting device (e.g., a transmitting network entity105, a transmitting UE115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity105or a receiving UE115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE115may receive one or more of the signals transmitted by the network entity105along different directions and may report to the network entity105an indication of the signal that the UE115received with a highest signal quality or an otherwise acceptable signal quality.

In some examples, transmissions by a device (e.g., by a network entity105or a UE115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity105to a UE115). The UE115may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity105may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or unprecoded. The UE115may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity105(e.g., a base station140, an RU170), a UE115may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

A receiving device (e.g., a UE115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

The wireless communications system100may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate over logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE115and a network entity105or a core network130supporting radio bearers for user plane data. At the PHY layer, transport channels may be mapped to physical channels.

The UEs115and the network entities105may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link (e.g., a communication link125, a D2D communication link135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

In some examples, one or more wireless devices, such as a network entity105and a UE115, may communicate according to a waveform, which may be a shape of a signal's graph as a function of time. The wireless communications system100may support usage of one or more OFDM waveforms, such as a DFT-s-OFDM waveform, a CP-OFDM waveform, or any other type of waveform. In some cases, the network entity105may periodically configure the UE115to use the different waveforms. However, the UE115may not be able to switch waveform usage dynamically, which may cause inefficient resource allocation.

In some examples, a network entity105may dynamically configure a UE115to use an MCS table with mixed waveform entries (e.g., DFT-s-OFDM waveform entries and CP-OFDM waveform entries). For example, the network entity105may transmit control signaling indicating to the UE115to select an MCS table from a set of configured MCS tables (e.g., RRC signaling). The UE115may determine a capability to support a mixed waveform MCS table for transmitting scheduled data, receiving scheduled data, or both. Thus, the mixed-waveform MCS table may be applicable depending on a UE capability, which the UE115may indicate to the network entity105in a capability message. In some examples, the network entity105may transmit additional control singling (e.g., dynamic control signaling) that indicates for the UE115to use the waveforms from the mixed-waveform MCS table for scheduled data. The UE115may select a mixed-waveform MCS table based on the MCS table indication and the waveform indication. In some cases, the mixed-waveform MCS table may be applicable for uplink scheduling, downlink scheduling, or both.

FIG.2illustrates an example of a wireless communications system200that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. In some examples, a wireless communications system200may implement aspects of wireless communications system100and may include a UE115-aand a network entity105-awith a coverage area110-a, which may be examples of a UE115and a network entity105with a coverage area110as described with reference toFIG.1. In some examples, the network entity105-amay communicate control information, data, or both with the UE115-ausing a downlink communication link205. Similarly, the UE115-amay communicate control information, data or both with the network entity105-ausing an uplink communication link, such as the uplink communication link210.

In some examples, one or more wireless devices, such as a network entity105-aand a UE115-a, may communicate according to a waveform, which may be a shape of a signal's graph as a function of time. The wireless communications system200may support usage of one or more OFDM waveforms, such as a DFT-s-OFDM waveform, a CP-OFDM waveform, or any other type of waveform. For example, the UE115-aand the network entity105-amay implement a CP-OFDM waveform in which a last part of an OFDM transmission frame may be appended at the beginning of the OFDM transmission frame, and a length of a cyclic prefix may be chosen to be greater than a channel delay spread. Additionally, or alternatively, the UE115-aand the network entity105-amay implement a DFT-s-OFDM waveform in which a sequence of transmitted bits may be mapped to a constellation of symbols. Different wireless devices may use different Fourier coefficients for transmissions according to the DFT-s-OFDM waveform.

In some cases, the network entity105-amay indicate to the UE115-ato use the DFT-s-OFDM or CP-OFDM waveforms by enabling or disabling transform precoding, where transform precoding may be a form of DFT used to spread uplink data to reduce a peak-to-average power ratio (PAPR). For example, the network entity105-amay transmit an indication to enable transform precoding, such that the UE115-amay use the DFT-s-OFDM waveform. In some other examples, the network entity105-amay transmit an indication disabling transform precoding, and the UE115-amay use the CP-OFDM waveform. The network entity105-amay transmit the indication in a random access channel procedure (RACH) procedure. The RACH procedure may be a four-step RACH procedure with four different message exchanges, and the network entity105-amay include the transform precoding indication in a third message of the RACH procedure.

Additionally, or alternatively, the network entity105-amay include the transform precoding indication in an uplink shared channel message (e.g., a physical uplink shared channel (PUSCH) message) when the UE115-ais in a connected mode. The connected mode may be an RRC connected mode in which the UE115-amay transmit and receive data and control signaling. Thus, the network entity105-amay periodically enable or disable one or more waveforms by using an indication in a RACH procedure, a PUSCH transmission, or both. However, the UE115-amay not be able to switch waveform usage dynamically, which may cause inefficient resource allocation.

In some examples, a network entity105-amay configure a UE115-awith a set of MCS tables with mixed waveform entries (e.g., via RRC signaling, a medium access control-control element (MAC-CE), or the like). Subsequently, the network entity105-amay indicate for the UE115-ato select a mixed-waveform MCS table and one or more waveforms to use for scheduled data. The network entity105-amay transmit the indication in RRC signaling, a MAC-CE, a DCI message, or the like. Each MCS table may have one or more entries for different waveforms, such as one or more CP-OFDM entries and one or more DFT-s-OFDM entries. For example, a subset of the rows of the MCS table may have coding rates and modulations used with the CP-OFDM waveform and another subset may have coding rates and modulations used with the DFT-s-OFDM waveform (e.g., 16 of 32 rows or 8 of 32 rows may be for DFT-s-OFDM, and the rest may be CP-OFDM). That is, the first k entries of the MCS table may be used with DFT-s-OFDM and the rest may be used with CP-OFDM, where k may be a configured or otherwise defined integer value.

In some cases, usage of the mixed waveform MCS table may override semi-statically or periodically configured transform precoding, such as whether the transform precoding is enabled or disabled. A bit (e.g., a most significant bit (MSB)) in an MCS may indicate whether the transform precoding is enabled or disabled. The network entity105-amay enable transform precoding, which may indicate to the UE115-ato use the DFT-s-OFDM waveform, if the UE115-ahas a reduced coverage. The DFT-s-OFDM waveform may provide lower values for an MCS. In some cases, the network entity105-amay configure the mixed-waveform MCS tables for a frequency range, a subcarrier spacing (SCS), or both. For example, the network entity105-amay determine the UE115-ais operating within the frequency range or the SCS and may transmit control signaling230indicating for the UE115-ato use a mixed-waveform MCS table.

The network entity105-amay transmit an MCS table indication215to the UE115-ain control signaling220(e.g., via the downlink communication link205). The MCS table indication215may indicate to the UE115-ato select an MCS table from a set of MCS tables configured by the network entity105-a. The control signaling220carrying the MCS table indication215may be semi-persistent or dynamic control signaling, such as a MAC-CE, a downlink control information (DCI) message, or the like. For example, the MCS table indication215may be a parameter in a DCI message that may be any number of bits.

The UE115-amay determine a capability to support a mixed waveform MCS table for transmitting scheduled data, receiving scheduled data, or both. For example, the UE115-amay have one or more components (e.g., antennas, power capability, or any other component) that support dynamic waveform switching or the UE115-amay be configured with the capability to support dynamic waveform switching. Thus, the mixed-waveform MCS table may be applicable depending on a UE capability, which the UE115-amay indicate to the network entity105-ain a capability message225. The UE115-amay transmit the capability message225to the network entity105-awith other capability information in a capability report or independent of the other capability information. The UE115-amay have a set of UE features, which may be a set of functionalities (e.g., signaling functionalities) the UE115-amay be capable of. In some examples, the network entity105-amay receive the capability message225per UE, per frequency range, per frequency band, per UE feature in a feature set, or the like. In some cases, the network entity105-amay transmit the MCS table indication215based on receiving the capability message225from the UE115-a, where the capability message indicates that the UE115-asupports mixed-waveform MCS tables.

In some examples, the network entity105-amay transmit control singling220that indicates for the UE115-ato use the waveforms from the mixed-waveform MCS table for scheduled data. For example, the network entity105-amay transmit a waveform indication230in same control signaling220as the MCS table indication215or in different control signaling220. The network entity105-amay transmit the waveform indication230in a DCI message, such that the UE115-amay dynamically select a mixed-waveform MCS table. At235, the UE115-amay select a mixed-waveform MCS table based on the MCS table indication215and the waveform indication230. For example, the UE115-amay select a mixed-waveform MCS table from a set, or list, that may be configured by RRC signaling.

In some cases, the mixed-waveform MCS table may be applicable for uplink scheduling, such that the UE115-amay transmit scheduled data240-ato the network entity105-ausing the selected mixed-waveform MCS table and the waveform indication230. In some other cases, the mixed-waveform MCS table may be applicable for uplink and downlink scheduling, such that the UE115-amay transmit scheduled data240-ato the network entity105-aand receive scheduled data240-bfrom the network entity105-ausing the selected mixed-waveform MCS table and the waveform indication230. In some examples, the network entity105-amay transmit the waveform indication230in a fallback DCI, which may be a DCI with a set of parameters and conditions defining a DCI format, such as DCI Format 1_0.

In some cases, the UE115-amay receive the control signaling220based on a minimum duration between the control signaling220and the scheduled data240-aor the scheduled data240-b, which may be referred to as K0 for a downlink transmission and K2 for an uplink transmission. For example, K0 may be a number of slots between a DCI message carrying the waveform indication230and a scheduled downlink shared channel transmission (e.g., physical downlink shared channel (PDSCH) transmission), such as scheduled data240-b. Similarly, K2 may be a number of slots between a DCI message carrying the waveform indication230and a scheduled uplink shared channel transmission (e.g., physical uplink shared channel (PUSCH) transmission), such as scheduled data240-a. The minimum duration may be defined as a number of slots, where each slot may be a dynamic scheduling unit.

In some examples, the network entity105-amay configure the minimum duration for uplink and downlink transmissions. The minimum duration for a mixed-waveform MCS table may be greater than a minimum duration for a single waveform MCS table due to the time allocated to switching between waveforms. The network entity105-amay configure the minimum duration per frequency band, per BWP, or both. The UE115-amay apply the configured minimums if an MCS bitfield indicates waveform switching. For example, an MCS bitfield in a DCI message may include one or more bits that indicate for the UE115-ato perform waveform switching. In some examples, the network entity105-amay configure the minimum durations for uplink and downlink mixed-waveform transmissions based on the capability message225from the UE115-a. For example, the network entity105-amay configure the minimum durations according capability indicated per UE, per frequency range, per frequency band, per UE feature, or any combination thereof.

FIG.3illustrates an example of a process flow300that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. In some examples, a process flow300may implement aspects of wireless communications system100and wireless communications system200. The process flow300may illustrate an example of a network entity105-bdynamically configuring a UE115-bto use an MCS table with mixed waveform entries. Network entity105-band UE115-bmay be examples of a network entity105and UE115as described with reference toFIGS.1and2. Alternative examples of the following may be implemented, where some processes are performed in a different order than described or are not performed. In some cases, processes may include additional features not mentioned below, or further processes may be added.

At305, a network entity105-bmay receive a capability message from a UE115-b, such as in a capability report or independent of a capability report. The capability message may indicate to the network entity105-ba capability of the UE115-bto support an MCS table for a set of frequencies (e.g., a frequency band, a frequency range, a BWP, or the like), a UE feature, or both.

At310, the network entity105-bmay transmit MCS table signaling to the UE115-b. The network entity105-bmay transmit the signaling in control signaling, such as RRC signaling, a MAC-CE, DCI message, or any other control signaling. The MCS table signaling may indicate for the UE115-bto select a mixed-waveform MCS table with entries for multiple waveforms (e.g., a DFT-s-OFDM waveform, a CP-OFDM waveform, or any other waveform). In some cases, a first row of entries may include modulation rates, coding rates, or both for a first waveform, and a second row of entries may include modulation rates, coding rates, or both for a second waveform. For example, 16 of 32 rows of a 32 row mixed-waveform MCS table may be for a DFT-s-OFDM waveform, while the other 16 of the 32 rows may be for a CP-OFDM waveform.

In some cases, the control signaling may include a bit indicating for the UE115-bto enable transform precoding for the waveforms in the mixed-waveform MCS table. For example, the control signaling may indicate for the UE115-bto enable transform precoding for DFT-s-OFDM waveform transmissions and disable transform precoding for CP-OFDM waveform transmissions.

In some cases, at315, the UE115-bmay determine the first row of entries based on a threshold number of entries for the first waveform. For example, the network entity105-bmay configure a threshold number of DFT-s-OFDM waveform entries, CP-OFDM waveform entries, or a threshold number of entries for any other waveform. The UE115-bmay determine the mixed-waveform MCS table with a number of entries for the first waveform that satisfies the threshold (e.g., above the threshold or below the threshold depending on the configuration from the network entity105-b).

At320, the UE115-bmay receive additional control signaling indicating for the UE115-bto use the first waveform, the second waveform, or both for scheduled data. For example, the UE115-bmay receive additional dynamic control signaling, such as a DCI message, indicating the waveforms for the scheduled data. In some other examples, the network entity105-bmay transmit the waveform signaling in same control signaling as the MCS table signaling (e.g., a same DCI message).

In some examples, the additional control signaling may indicate one or more rows of the MCS table to use for the scheduled data, which may indicate one or more waveforms. The network entity105-bmay transmit the additional control signaling in accordance with a minimum duration between the additional control signaling (e.g., a DCI message) and the scheduled data, which may be K0 for a downlink transmission and K2 for an uplink transmission. The minimum durations may be different depending on a set of frequencies, a UE feature, or both. In some cases, the additional control signaling may include an indication of the minimum duration per frequency band, per BWP, or both. In some other cases, the UE115-bmay determine and apply the minimum duration if a bitfield of the MCS table indicates for the UE115-bto perform waveform switching between the waveforms. The UE115-band the network entity105-bmay determine the minimum duration based on a capability of the UE115-bper frequency band, per UE feature, or both to use the waveforms. In some examples, the UE115-bmay receive the additional control signaling based on a frequency range of the scheduled data, a SCS of the scheduled data, or both being within a threshold value.

At325, the UE115-bmay select a mixed-waveform MCS table to use based on the MCS table signaling at310, the waveform signaling at320, or both.

At330, the UE115-band the network entity105-bmay exchange scheduled data. For example, the mixed-waveform MCS table may be applicable for uplink transmissions, downlink transmissions, or both. Thus, the UE115-bmay transmit the scheduled data to the network entity105-bin accordance with the selected mixed-waveform MCS table and waveforms in the waveform signaling at320. Additionally, or alternatively, the UE115-bmay receive the scheduled data from the network entity105-bin accordance with the selected mixed-waveform MCS table and waveforms in the waveform signaling at320.

FIG.4shows a block diagram400of a device405that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The device405may be an example of aspects of a UE115as described herein. The device405may include a receiver410, a transmitter415, and a communications manager420. The device405may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver410may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to configuring a mixed-waveform MCS table). Information may be passed on to other components of the device405. The receiver410may utilize a single antenna or a set of multiple antennas.

The transmitter415may provide a means for transmitting signals generated by other components of the device405. For example, the transmitter415may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to configuring a mixed-waveform MCS table). In some examples, the transmitter415may be co-located with a receiver410in a transceiver module. The transmitter415may utilize a single antenna or a set of multiple antennas.

The communications manager420, the receiver410, the transmitter415, or various combinations thereof or various components thereof may be examples of means for performing various aspects of configuring a mixed-waveform MCS table as described herein. For example, the communications manager420, the receiver410, the transmitter415, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager420, the receiver410, the transmitter415, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager420, the receiver410, the transmitter415, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager420, the receiver410, the transmitter415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

In some examples, the communications manager420may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver410, the transmitter415, or both. For example, the communications manager420may receive information from the receiver410, send information to the transmitter415, or be integrated in combination with the receiver410, the transmitter415, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager420may support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager420may be configured as or otherwise support a means for receiving first control signaling indicating for the UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The communications manager420may be configured as or otherwise support a means for receiving second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

By including or configuring the communications manager420in accordance with examples as described herein, the device405(e.g., a processor controlling or otherwise coupled with the receiver410, the transmitter415, the communications manager420, or a combination thereof) may support techniques for a network entity105to dynamically configuring a UE115to use an MCS table with mixed waveform entries, which may provide for reduced processing, reduced power consumption, more efficient utilization of communication resources, and the like.

FIG.5shows a block diagram500of a device505that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The device505may be an example of aspects of a device405or a UE115as described herein. The device505may include a receiver510, a transmitter515, and a communications manager520. The device505may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver510may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to configuring a mixed-waveform MCS table). Information may be passed on to other components of the device505. The receiver510may utilize a single antenna or a set of multiple antennas.

The transmitter515may provide a means for transmitting signals generated by other components of the device505. For example, the transmitter515may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to configuring a mixed-waveform MCS table). In some examples, the transmitter515may be co-located with a receiver510in a transceiver module. The transmitter515may utilize a single antenna or a set of multiple antennas.

The device505, or various components thereof, may be an example of means for performing various aspects of configuring a mixed-waveform MCS table as described herein. For example, the communications manager520may include an MCS table component525a waveform component530, or any combination thereof. The communications manager520may be an example of aspects of a communications manager420as described herein. In some examples, the communications manager520, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver510, the transmitter515, or both. For example, the communications manager520may receive information from the receiver510, send information to the transmitter515, or be integrated in combination with the receiver510, the transmitter515, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager520may support wireless communication at a UE in accordance with examples as disclosed herein. The MCS table component525may be configured as or otherwise support a means for receiving first control signaling indicating for the UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The waveform component530may be configured as or otherwise support a means for receiving second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

FIG.6shows a block diagram600of a communications manager620that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The communications manager620may be an example of aspects of a communications manager420, a communications manager520, or both, as described herein. The communications manager620, or various components thereof, may be an example of means for performing various aspects of configuring a mixed-waveform MCS table as described herein. For example, the communications manager620may include an MCS table component625, a waveform component630, a capability component635, a duration component640, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The communications manager620may support wireless communication at a UE in accordance with examples as disclosed herein. The MCS table component625may be configured as or otherwise support a means for receiving first control signaling indicating for the UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The waveform component630may be configured as or otherwise support a means for receiving second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

In some examples, a first row of entries of the set of multiple entries includes a first set of multiple modulation rates, coding rates, or both for the first waveform, and a second row of entries of the set of multiple entries includes a second set of multiple modulation rates, coding rates, or both for the second waveform.

In some examples, the waveform component630may be configured as or otherwise support a means for determining the first row of entries based on a threshold number of entries of the set of multiple entries that correspond to the first waveform. In some examples, the second control signaling indicates one or more rows from the first row of entries, the second row of entries, or both to use for the scheduled data.

In some examples, the capability component635may be configured as or otherwise support a means for transmitting a capability message indicating that the UE supports the MCS table for a set of frequencies, a UE feature, or both.

In some examples, the waveform component630may be configured as or otherwise support a means for transmitting the scheduled data in accordance with the second control signaling. In some examples, the waveform component630may be configured as or otherwise support a means for receiving the scheduled data in accordance with the second control signaling. In some examples, the first control signaling includes a bit indicating for the UE to enable transform precoding for the first waveform and the second waveform.

In some examples, receiving the second control signaling is in accordance with a minimum duration between the second control signaling and the scheduled data based on a set of frequencies, a UE feature, or both.

In some examples, to support receiving the first control signaling, the duration component640may be configured as or otherwise support a means for receiving an indication of the minimum duration per frequency band, per BWP, or both. In some examples, the duration component640may be configured as or otherwise support a means for determining the minimum duration based on a bitfield of the MCS table indicating for the UE to perform waveform switching between the first waveform and the second waveform. In some examples, the duration component640may be configured as or otherwise support a means for determining the minimum duration based on a capability of the UE per frequency band, per UE feature, or both to use the first waveform and the second waveform.

In some examples, receiving the second control signaling is based on a frequency range of the scheduled data, a SCS of the scheduled data, or both. In some examples, the first control signaling is RRC signaling. In some examples, the second control signaling is DCI signaling.

FIG.7shows a diagram of a system700including a device705that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The device705may be an example of or include the components of a device405, a device505, or a UE115as described herein. The device705may communicate (e.g., wirelessly) with one or more network entities105, one or more UEs115, or any combination thereof. The device705may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager720, an input/output (I/O) controller710, a transceiver715, an antenna725, a memory730, code735, and a processor740. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus745).

The I/O controller710may manage input and output signals for the device705. The I/O controller710may also manage peripherals not integrated into the device705. In some cases, the I/O controller710may represent a physical connection or port to an external peripheral. In some cases, the I/O controller710may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I/O controller710may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller710may be implemented as part of a processor, such as the processor740. In some cases, a user may interact with the device705via the I/O controller710or via hardware components controlled by the I/O controller710.

In some cases, the device705may include a single antenna725. However, in some other cases, the device705may have more than one antenna725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver715may communicate bi-directionally, via the one or more antennas725, wired, or wireless links as described herein. For example, the transceiver715may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver715may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas725for transmission, and to demodulate packets received from the one or more antennas725. The transceiver715, or the transceiver715and one or more antennas725, may be an example of a transmitter415, a transmitter515, a receiver410, a receiver510, or any combination thereof or component thereof, as described herein.

The memory730may include random access memory (RAM) and read-only memory (ROM). The memory730may store computer-readable, computer-executable code735including instructions that, when executed by the processor740, cause the device705to perform various functions described herein. The code735may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code735may not be directly executable by the processor740but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory730may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor740may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor740may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor740. The processor740may be configured to execute computer-readable instructions stored in a memory (e.g., the memory730) to cause the device705to perform various functions (e.g., functions or tasks supporting configuring a mixed-waveform MCS table). For example, the device705or a component of the device705may include a processor740and memory730coupled with or to the processor740, the processor740and memory730configured to perform various functions described herein.

The communications manager720may support wireless communication at a UE in accordance with examples as disclosed herein. For example, the communications manager720may be configured as or otherwise support a means for receiving first control signaling indicating for the UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The communications manager720may be configured as or otherwise support a means for receiving second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

By including or configuring the communications manager720in accordance with examples as described herein, the device705may support techniques for a network entity105to dynamically configuring a UE115to use an MCS table with mixed waveform entries, which may provide for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, and the like.

In some examples, the communications manager720may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver715, the one or more antennas725, or any combination thereof. Although the communications manager720is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager720may be supported by or performed by the processor740, the memory730, the code735, or any combination thereof. For example, the code735may include instructions executable by the processor740to cause the device705to perform various aspects of configuring a mixed-waveform MCS table as described herein, or the processor740and the memory730may be otherwise configured to perform or support such operations.

FIG.8shows a block diagram800of a device805that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The device805may be an example of aspects of a network entity105as described herein. The device805may include a receiver810, a transmitter815, and a communications manager820. The device805may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver810may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device805. In some examples, the receiver810may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver810may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

The transmitter815may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device805. For example, the transmitter815may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter815may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter815may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter815and the receiver810may be co-located in a transceiver, which may include or be coupled with a modem.

The communications manager820, the receiver810, the transmitter815, or various combinations thereof or various components thereof may be examples of means for performing various aspects of configuring a mixed-waveform MCS table as described herein. For example, the communications manager820, the receiver810, the transmitter815, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager820, the receiver810, the transmitter815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager820, the receiver810, the transmitter815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager820, the receiver810, the transmitter815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

In some examples, the communications manager820may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver810, the transmitter815, or both. For example, the communications manager820may receive information from the receiver810, send information to the transmitter815, or be integrated in combination with the receiver810, the transmitter815, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager820may support wireless communication at a network entity in accordance with examples as disclosed herein. For example, the communications manager820may be configured as or otherwise support a means for transmitting first control signaling indicating for a UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The communications manager820may be configured as or otherwise support a means for transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

By including or configuring the communications manager820in accordance with examples as described herein, the device805(e.g., a processor controlling or otherwise coupled with the receiver810, the transmitter815, the communications manager820, or a combination thereof) may support techniques for a network entity105to dynamically configuring a UE115to use an MCS table with mixed waveform entries, which may provide for reduced processing, reduced power consumption, more efficient utilization of communication resources, and the like.

FIG.9shows a block diagram900of a device905that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The device905may be an example of aspects of a device805or a network entity105as described herein. The device905may include a receiver910, a transmitter915, and a communications manager920. The device905may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver910may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device905. In some examples, the receiver910may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver910may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

The transmitter915may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device905. For example, the transmitter915may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter915may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter915may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter915and the receiver910may be co-located in a transceiver, which may include or be coupled with a modem.

The device905, or various components thereof, may be an example of means for performing various aspects of configuring a mixed-waveform MCS table as described herein. For example, the communications manager920may include an MCS table manager925a waveform manager930, or any combination thereof. The communications manager920may be an example of aspects of a communications manager820as described herein. In some examples, the communications manager920, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver910, the transmitter915, or both. For example, the communications manager920may receive information from the receiver910, send information to the transmitter915, or be integrated in combination with the receiver910, the transmitter915, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager920may support wireless communication at a network entity in accordance with examples as disclosed herein. The MCS table manager925may be configured as or otherwise support a means for transmitting first control signaling indicating for a UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The waveform manager930may be configured as or otherwise support a means for transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

FIG.10shows a block diagram1000of a communications manager1020that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The communications manager1020may be an example of aspects of a communications manager820, a communications manager920, or both, as described herein. The communications manager1020, or various components thereof, may be an example of means for performing various aspects of configuring a mixed-waveform MCS table as described herein. For example, the communications manager1020may include an MCS table manager1025, a waveform manager1030, a capability manager1035, a duration manager1040, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) which may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity105, between devices, components, or virtualized components associated with a network entity105), or any combination thereof.

The communications manager1020may support wireless communication at a network entity in accordance with examples as disclosed herein. The MCS table manager1025may be configured as or otherwise support a means for transmitting first control signaling indicating for a UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The waveform manager1030may be configured as or otherwise support a means for transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

In some examples, a first row of entries of the set of multiple entries includes a first set of multiple modulation rates, coding rates, or both for the first waveform, and a second row of entries of the set of multiple entries includes a second set of multiple modulation rates, coding rates, or both for the second waveform.

In some examples, the waveform manager1030may be configured as or otherwise support a means for determining the first row of entries based on a threshold number of entries of the set of multiple entries that correspond to the first waveform.

In some examples, the second control signaling indicates one or more rows from the first row of entries, the second row of entries, or both to use for the scheduled data.

In some examples, the capability manager1035may be configured as or otherwise support a means for receiving a capability message indicating that the UE supports the MCS table for a set of frequencies, a UE feature, or both.

In some examples, the waveform manager1030may be configured as or otherwise support a means for receiving the scheduled data in accordance with the second control signaling.

In some examples, the waveform manager1030may be configured as or otherwise support a means for transmitting the scheduled data in accordance with the second control signaling.

In some examples, the first control signaling includes a bit indicating for the UE to enable transform precoding for the first waveform and the second waveform.

In some examples, transmitting the second control signaling is in accordance with a minimum duration between the second control signaling and the scheduled data based on a set of frequencies, a UE feature, or both.

In some examples, to support transmitting the first control signaling, the duration manager1040may be configured as or otherwise support a means for transmitting an indication of the minimum duration per frequency band, per BWP, or both.

In some examples, a bitfield of the MCS table indicates for the UE to perform waveform switching between the first waveform and the second waveform.

In some examples, the duration manager1040may be configured as or otherwise support a means for determining the minimum duration based on a capability of the UE per frequency band, per UE feature, or both to use the first waveform and the second waveform.

In some examples, transmitting the second control signaling is based on a frequency range of the scheduled data, a SCS of the scheduled data, or both. In some examples, the first control signaling is RRC signaling. In some examples, the second control signaling is DCI signaling.

FIG.11shows a diagram of a system1100including a device1105that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The device1105may be an example of or include the components of a device805, a device905, or a network entity105as described herein. The device1105may communicate with one or more network entities105, one or more UEs115, or any combination thereof, which may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device1105may include components that support outputting and obtaining communications, such as a communications manager1120, a transceiver1110, an antenna1115, a memory1125, code1130, and a processor1135. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1140).

The transceiver1110may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver1110may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver1110may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device1105may include one or more antennas1115, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver1110may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas1115, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas1115, from a wired receiver), and to demodulate signals. The transceiver1110, or the transceiver1110and one or more antennas1115or wired interfaces, where applicable, may be an example of a transmitter815, a transmitter915, a receiver810, a receiver910, or any combination thereof or component thereof, as described herein. In some examples, the transceiver may be operable to support communications via one or more communications links (e.g., a communication link125, a backhaul communication link120, a midhaul communication link162, a fronthaul communication link168).

The memory1125may include RAM and ROM. The memory1125may store computer-readable, computer-executable code1130including instructions that, when executed by the processor1135, cause the device1105to perform various functions described herein. The code1130may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1130may not be directly executable by the processor1135but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1125may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1135may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the processor1135may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1135. The processor1135may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1125) to cause the device1105to perform various functions (e.g., functions or tasks supporting configuring a mixed-waveform MCS table). For example, the device1105or a component of the device1105may include a processor1135and memory1125coupled with the processor1135, the processor1135and memory1125configured to perform various functions described herein. The processor1135may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code1130) to perform the functions of the device1105.

In some examples, a bus1140may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus1140may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device1105, or between different components of the device1105that may be co-located or located in different locations (e.g., where the device1105may refer to a system in which one or more of the communications manager1120, the transceiver1110, the memory1125, the code1130, and the processor1135may be located in one of the different components or divided between different components).

In some examples, the communications manager1120may manage aspects of communications with a core network130(e.g., via one or more wired or wireless backhaul links). For example, the communications manager1120may manage the transfer of data communications for client devices, such as one or more UEs115. In some examples, the communications manager1120may manage communications with other network entities105, and may include a controller or scheduler for controlling communications with UEs115in cooperation with other network entities105. In some examples, the communications manager1120may support an X2 interface within an LTE/LTE-A wireless communications network technology to provide communication between network entities105.

The communications manager1120may support wireless communication at a network entity in accordance with examples as disclosed herein. For example, the communications manager1120may be configured as or otherwise support a means for transmitting first control signaling indicating for a UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The communications manager1120may be configured as or otherwise support a means for transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

By including or configuring the communications manager1120in accordance with examples as described herein, the device1105may support techniques for a network entity105to dynamically configuring a UE115to use an MCS table with mixed waveform entries, which may provide for improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability, and the like.

In some examples, the communications manager1120may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver1110, the one or more antennas1115(e.g., where applicable), or any combination thereof. Although the communications manager1120is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1120may be supported by or performed by the processor1135, the memory1125, the code1130, the transceiver1110, or any combination thereof. For example, the code1130may include instructions executable by the processor1135to cause the device1105to perform various aspects of configuring a mixed-waveform MCS table as described herein, or the processor1135and the memory1125may be otherwise configured to perform or support such operations.

FIG.12shows a flowchart illustrating a method1200that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The operations of the method1200may be implemented by a UE or its components as described herein. For example, the operations of the method1200may be performed by a UE115as described with reference toFIGS.1through7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1205, the method may include receiving first control signaling indicating for the UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The operations of1205may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1205may be performed by an MCS table component625as described with reference toFIG.6.

At1210, the method may include receiving second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data. The operations of1210may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1210may be performed by a waveform component630as described with reference toFIG.6.

FIG.13shows a flowchart illustrating a method1300that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The operations of the method1300may be implemented by a UE or its components as described herein. For example, the operations of the method1300may be performed by a UE115as described with reference toFIGS.1through7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1305, the method may include transmitting a capability message indicating that a UE supports an MCS table for a set of frequencies, a UE feature, or both. The operations of1305may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1305may be performed by a capability component635as described with reference toFIG.6.

At1310, the method may include receiving first control signaling indicating for the UE to select the MCS table with a set of multiple entries associated with a first waveform and a second waveform. The operations of1310may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1310may be performed by an MCS table component625as described with reference toFIG.6.

At1315, the method may include receiving second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data. The operations of1315may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1315may be performed by a waveform component630as described with reference toFIG.6.

FIG.14shows a flowchart illustrating a method1400that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The operations of the method1400may be implemented by a network entity or its components as described herein. For example, the operations of the method1400may be performed by a network entity as described with reference toFIGS.1through3and8through11. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At1405, the method may include transmitting first control signaling indicating for a UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by an MCS table manager1025as described with reference toFIG.10.

At1410, the method may include transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by a waveform manager1030as described with reference toFIG.10.

FIG.15shows a flowchart illustrating a method1500that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The operations of the method1500may be implemented by a network entity or its components as described herein. For example, the operations of the method1500may be performed by a network entity as described with reference toFIGS.1through3and8through11. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At1505, the method may include transmitting first control signaling indicating for a UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The operations of1505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1505may be performed by an MCS table manager1025as described with reference toFIG.10.

At1510, the method may include transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data. The operations of1510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1510may be performed by a waveform manager1030as described with reference toFIG.10.

At1515, the method may include receiving the scheduled data in accordance with the second control signaling. The operations of1515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1515may be performed by a waveform manager1030as described with reference toFIG.10.

FIG.16shows a flowchart illustrating a method1600that supports configuring a mixed-waveform MCS table in accordance with one or more aspects of the present disclosure. The operations of the method1600may be implemented by a network entity or its components as described herein. For example, the operations of the method1600may be performed by a network entity as described with reference toFIGS.1through3and8through11. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

At1605, the method may include transmitting first control signaling indicating for a UE to select an MCS table with a set of multiple entries associated with a first waveform and a second waveform. The operations of1605may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1605may be performed by an MCS table manager1025as described with reference toFIG.10.

At1610, the method may include transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data. The operations of1610may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1610may be performed by a waveform manager1030as described with reference toFIG.10.

At1615, the method may include transmitting the scheduled data in accordance with the second control signaling. The operations of1615may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1615may be performed by a waveform manager1030as described with reference toFIG.10.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communication at a UE, comprising: receiving first control signaling indicating for the UE to select a modulation and coding scheme table with a plurality of entries associated with a first waveform and a second waveform; and receiving second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

Aspect 2: The method of aspect 1, wherein a first row of entries of the plurality of entries comprises a first plurality of modulation rates, coding rates, or both for the first waveform, and a second row of entries of the plurality of entries comprises a second plurality of modulation rates, coding rates, or both for the second waveform.

Aspect 3: The method of aspect 2, further comprising: determining the first row of entries based at least in part on a threshold number of entries of the plurality of entries that correspond to the first waveform.

Aspect 4: The method of any of aspects 2 through 3, wherein the second control signaling indicates one or more rows from the first row of entries, the second row of entries, or both to use for the scheduled data.

Aspect 5: The method of any of aspects 1 through 4, further comprising: transmitting a capability message indicating that the UE supports the modulation and coding scheme table for a set of frequencies, a UE feature, or both.

Aspect 6: The method of any of aspects 1 through 5, further comprising: transmitting the scheduled data in accordance with the second control signaling.

Aspect 7: The method of any of aspects 1 through 5, further comprising: receiving the scheduled data in accordance with the second control signaling.

Aspect 8: The method of any of aspects 1 through 7, wherein the first control signaling comprises a bit indicating for the UE to enable transform precoding for the first waveform and the second waveform.

Aspect 9: The method of any of aspects 1 through 8, wherein receiving the second control signaling is in accordance with a minimum duration between the second control signaling and the scheduled data based at least in part on a set of frequencies, a UE feature, or both.

Aspect 10: The method of aspect 9, wherein receiving the first control signaling comprises: receiving an indication of the minimum duration per frequency band, per bandwidth part, or both.

Aspect 11: The method of any of aspects 9 through 10, further comprising: determining the minimum duration based at least in part on a bitfield of the modulation and coding scheme table indicating for the UE to perform waveform switching between the first waveform and the second waveform.

Aspect 12: The method of any of aspects 9 through 11, further comprising: determining the minimum duration based at least in part on a capability of the UE per frequency band, per UE feature, or both to use the first waveform and the second waveform.

Aspect 13: The method of any of aspects 1 through 12, wherein receiving the second control signaling is based at least in part on a frequency range of the scheduled data, a subcarrier spacing of the scheduled data, or both.

Aspect 14: The method of any of aspects 1 through 13, wherein the first control signaling is radio resource control signaling.

Aspect 15: The method of any of aspects 1 through 14, wherein the second control signaling is downlink control information signaling.

Aspect 16: A method for wireless communication at a network entity, comprising: transmitting first control signaling indicating for a UE to select a modulation and coding scheme table with a plurality of entries associated with a first waveform and a second waveform; and transmitting second control signaling indicating for the UE to use the first waveform, the second waveform, or both for scheduled data.

Aspect 17: The method of aspect 16, wherein a first row of entries of the plurality of entries comprises a first plurality of modulation rates, coding rates, or both for the first waveform, and a second row of entries of the plurality of entries comprises a second plurality of modulation rates, coding rates, or both for the second waveform.

Aspect 18: The method of aspect 17, further comprising: determining the first row of entries based at least in part on a threshold number of entries of the plurality of entries that correspond to the first waveform.

Aspect 19: The method of any of aspects 17 through 18, wherein the second control signaling indicates one or more rows from the first row of entries, the second row of entries, or both to use for the scheduled data.

Aspect 20: The method of any of aspects 16 through 19, further comprising: receiving a capability message indicating that the UE supports the modulation and coding scheme table for a set of frequencies, a UE feature, or both.

Aspect 21: The method of any of aspects 16 through 20, further comprising: receiving the scheduled data in accordance with the second control signaling.

Aspect 22: The method of any of aspects 16 through 20, further comprising: transmitting the scheduled data in accordance with the second control signaling.

Aspect 23: The method of any of aspects 16 through 22, wherein the first control signaling comprises a bit indicating for the UE to enable transform precoding for the first waveform and the second waveform.

Aspect 24: The method of any of aspects 16 through 23, wherein transmitting the second control signaling is in accordance with a minimum duration between the second control signaling and the scheduled data based at least in part on a set of frequencies, a UE feature, or both.

Aspect 25: The method of aspect 24, wherein transmitting the first control signaling comprises: transmitting an indication of the minimum duration per frequency band, per bandwidth part, or both.

Aspect 26: The method of any of aspects 24 through 25, wherein a bitfield of the modulation and coding scheme table indicates for the UE to perform waveform switching between the first waveform and the second waveform.

Aspect 27: The method of any of aspects 24 through 26, further comprising: determining the minimum duration based at least in part on a capability of the UE per frequency band, per UE feature, or both to use the first waveform and the second waveform.

Aspect 28: The method of any of aspects 16 through 27, wherein transmitting the second control signaling is based at least in part on a frequency range of the scheduled data, a subcarrier spacing of the scheduled data, or both.

Aspect 29: An apparatus for wireless communication at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 15.

Aspect 30: An apparatus for wireless communication at a UE, comprising at least one means for performing a method of any of aspects 1 through 15.

Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 15.

Aspect 32: An apparatus for wireless communication at a network entity, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 16 through 28.

Aspect 33: An apparatus for wireless communication at a network entity, comprising at least one means for performing a method of any of aspects 16 through 28.

Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform a method of any of aspects 16 through 28.

It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

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

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data in a memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.