WO2024236446A1

WO2024236446A1 - Methods for multi‐waveforms pusch for dws indication

Info

Publication number: WO2024236446A1
Application number: PCT/IB2024/054581
Authority: WO
Inventors: Majed SAAD; Nhat-Quang NHAN; Amir Mehdi AHMADIAN TEHRANI; Karim KASAN; Marco MASO
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2023-05-15
Filing date: 2024-05-10
Publication date: 2024-11-21
Anticipated expiration: 2025-11-15
Also published as: CN121100509A

Abstract

A method including determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

Description

METHODS FOR MULTI-WAVEFORMS PUSCH FOR DWS INDICATION

RELATED APPLICATION

[0001] This application claims priority to US provisional Application No. 63/466458 filed May 15, 2023, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] The example and non-limiting embodiments relate generally to uplink transmission and, more particularly, to waveform selection.

BRIEF DESCRIPTION OF PRIOR DEVELOPMENTS

[0003] Two types of PUSCH repetitions are currently defined in the NR specifications: PUSCH repetitions Type A, and PUSCH repetitions Type B. Different types of waveforms are also known such as using orthogonal frequency division multiplexing including CP-OFDM and DFT-s-OFDM for example.

SUMMARY OF THE INVENTION

[0004] The following summary is merely intended to be an example. The summary is not intended to limit the scope of the claims.

[0005] In accordance with one aspect, an example method comprises: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

[0006] In accordance with an example embodiment, an apparatus is provided comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

[0007] In accordance with an example embodiment, an apparatus is provided comprising: means for determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and means for transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

[0008] In accordance with an example embodiment, an apparatus is provided comprising: a non-transitory program storage device readable by an apparatus, tangibly embodying a program of instructions executable with the apparatus for performing operations, the operations comprising: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

[0009] In accordance with an example method is provided comprising: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.

[0010] In accordance with an example embodiment, an apparatus is provided comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes. [0011] In accordance with an example embodiment, an apparatus is provided comprising: means for determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and means for transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.

[0012] In accordance with an example embodiment, an apparatus is provided comprising a non-transitory program storage device readable by an apparatus, tangibly embodying a program of instructions executable with the apparatus for performing operations, the operations comprising: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.

[0013] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are provided in subject matter of the dependent claims.

BRIEF DESCRIPTION OF DRAWINGS

[0014] The foregoing aspects and other features are explained in the following description, taken in connection with the accompanying drawings, wherein:

[0015] FIG. 1 is a block diagram of one possible and non-limiting example system in which the example embodiments may be practiced;

[0016] FIG. 2 is a diagram illustrating PUSCH repetition Type A (PUSCH mapping type B);

[0017] FIG. 3 is a diagram illustrating PUSCH repetition Type B (PUSCH mapping type B);

[0018] FIG. 4 is a diagram illustrating an actual PUSCH Type B repetitions when invalidSymbolP cittern is applied to the nominal repetitions;

[0019] FIG. 5 is a diagram illustrating examples of proposed PUSCH repetitions with two (2) waveforms or transmission modes; [0020] FIG. 6 is a diagram illustrating examples of proposed PUSCH repetitions with more than two (2) waveforms or transmission modes;

[0021] FIG. 7 is a diagram illustrating a hybrid PUSCH transmission with at least one symbol based on another waveform;

[0022] FIG. 8 is a diagram illustrating a hybrid PUSCH transmission with symbol(s) based on at least two waveforms and a modified DMRS position closer to that of the other WF(s);

[0023] FIG. 9 is a diagram illustrating an example method.

[0024] FIG. 10 is a diagram illustrating an example method;

[0025] FIG. 11 is a diagram illustrating an example method.

DETAILED DESCRIPTION

[0026] The following abbreviations that may be found in the specification and/or the drawing figures are defined as follows:

3GPP third generation partnership project

5G fifth generation

5GC 5G core network

AMF access and mobility management function

CE control element

CP-OFDM cyclic prefix orthogonal frequency division multiplexing

CU central unit

DCI downlink control information

DCI Format 0 1 UU grant configurable by RRC

DFT-s-OFDM Discrete Fourier transform spread orthogonal frequency division multiplexing

DMRS demodulation reference signal

DU distributed unit

DWS dynamic waveform switching eNB (or eNodeB) evolved Node B (e.g., an UTE base station)

EN-DC E-UTRA-NR dual connectivity en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DC

E-UTRA evolved universal terrestrial radio access, i.e., the LTE radio access technology

FDRA frequency-domain resource allocation

FDSS frequency domain spectrum shaping gNB (or gNodeB) base station for 5G/NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC

IBO/OBO input power backoff / output power backoff

I/F interface

LTE 1 long term evolution

MAC medium access control

MCS modulation and coding scheme

MME mobility management entity

MPR maximum power reduction mTRP multiple transmission and reception point ng or NG new generation ng-eNB or NG-eNB new generation eNB

NR new radio

N/W or NW network

OFDM orthogonal frequency division multiplexing

PDCCH physical downlink control channel

PDCP packet data convergence protocol

PDU protocol data unit

PHR power headroom report

PHY physical layer

PUSCH physical uplink shared channel

QPSK quadrature phase shift keying

RAN radio access network

RB, PRB resource block, physical resource block

Rel release Rel-17 release 17

Rel-18 release 18

RLC radio link control

RRH remote radio head

RRC radio resource control

RSRP reference signal received power

RU radio unit

Rx receiver

SDAP service data adaptation protocol

SGW serving gateway

SINR signal-to-noise ratio

SMF session management function

S/P serial-to-parallel

SR scheduling request

TB transform block

TBS transform block size

TDRA time-domain resource allocation

TPC transmit power control

TS technical specification

Tx transmitter

UE user equipment (e.g., a wireless, typically mobile device)

UL uplink

UPF user plane function

WF waveform

WI work item w/wo SE with/without spectrum extension

[0027] Turning to FIG. 1, this figure shows a block diagram of one possible and non-limiting example in which the examples may be practiced. A user equipment (UE) 110, radio access network (RAN) node 170, and network element(s) 190 are illustrated. Network equipment or a network entity might be understood and referred to as at least part of a transmission reception point or a cell or a gNB for example. In the example of FIG. 1, the user equipment (UE) 110 is in wireless communication with a wireless network 100. A UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a module 140, comprising one of or both parts 140-1 and/or 140-2, which may be implemented in a number of ways. The module 140 may be implemented in hardware as module 140-1, such as being implemented as part of the one or more processors 120. The module 140-1 maybe implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 140 may be implemented as module 140-2, which is implemented as computer program code 123 and is executed by the one or more processors 120. For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with RAN node 170 via a wireless link 111.

[0028] The RAN node 170 in this example is a base station that provides access by wireless devices such as the UE 110 to the wireless network 100. The RAN node 170 may be, for example, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or a ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (such as, for example, the network element(s) 190). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown. Note that the DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the Fl interface connected with the gNB-DU. The Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-CU supports one or multiple cells. One cell is supported by only one gNB- DU. The gNB-DU terminates the Fl interface 198 connected with the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of a RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for UTE (long term evolution), or any other suitable base station or node.

[0029] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N/W I/F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160 includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory/memories and processor(s), and/or other hardware, but these are not shown.

[0030] The RAN node 170 includes a module 150, comprising one of or both parts 150-1 and/or 150-2, which may be implemented in a number of ways. The module 150 may be implemented in hardware as module 150-1, such as being implemented as part of the one or more processors 152. The module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 150 may be implemented as module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152. For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.

[0031] The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more gNBs 170 may communicate using, e.g., link 176. The link 176 may be wired or wireless or both and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.

[0032] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH/DU, and the one or more buses 157 could be implemented in part as, for example, fiber optic cable or other suitable network connection to connect the other elements (e.g., a central unit (CU), gNB-CU) of the RAN node 170 to the RRH/DU 195. Reference 198 also indicates those suitable network link(s).

[0033] It is noted that description herein indicates that “cells” perform functions, but it should be clear that equipment which forms the cell will perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For example, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one- third of a 360 degree area so that the single base station’s coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.

[0034] The wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and/or a data communications network (e.g., the Internet). Such core network functionality for 5G may include access and mobility management fimction(s) (AMF(S)) and/or user plane functions (UPF(s)) and/or session management fimction(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity )/SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network element(s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to a network element 190. The link 131 may be implemented as, e.g., an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N/W I/F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.

[0035] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.

[0036] The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.

[0037] In general, the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permiting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

[0038] Features as described herein may be used in regard to dynamic waveform switching, such as between CP-OFDM and DFT-S-OFDM for example, for uplink transmissions on physical uplink shared channel (PUSCH). Features may be used to select, by the gNB, whether CP-OFDM or DFT-S-OFDM is a beter waveform based on one PUSCH transmission with CP-OFDM and another PUSCH transmission with DFT-S-OFDM. Conventionally, the two transmissions might be granted by separate downlink control information (DCI i.e. control channels). However, conventionally, the transmissions shall be close to each other in time and use similar or same frequency resources to let the gNB make an accurate decision about the appropriate waveform. Thus, with features as described herein, to assist the gNB with selecting a beter waveform, there may be a grant of PUSCH transmission(s) with a single uplink grant (DCI), where the PUSCH transmission(s) uses two different waveforms such as CP-OFDM and DFT-S-OFDM for example. Based on the PUSCH transmission(s) using the two waveforms, the gNB may select a beter one of the waveforms, and the gNB may grant subsequent PUSCH transmissions to use the selected waveform. Because the PUSCH transmission(s) for using different waveforms are granted by a same DCI, the subsequent transmissions may be consecutive or close in time, and the transmissions may use (or substantially use) a same resource block allocation in frequency. This may positively impact the gNB ability/comparison to optimally subsequently select one of the waveforms for future PUSCH transmissions. Thus, dynamic waveform switching may be provided.

[0039] From RP-213579, the objectives of Rel-18 work item for UU coverage enhancements are generally as follows:

• Specify following PRACH coverage enhancements (RANI, RAN2) o Multiple PRACH transmissions with same beams for 4-step RACH procedure o Study, and if justified, specify PRACH transmissions with different beams for 4-step RACH procedure o Note 1 : The enhancements of PRACH are targeting for FR2, and can also apply to FR1 when applicable. o Note 2: The enhancements of PRACH are targeting short PRACH formats, and can also apply to other formats when applicable.

• Study and, if necessary, specify following power domain enhancements o Enhancements to realize increasing UE power high limit for CA and DC based on Rel-17 RAN4 work on “Increasing UE power high limit for CA and DC”, in compliance with relevant regulations (RAN4, RANI) o Enhancements to reduce MPR/PAR, including frequency domain spectrum shaping with and without spectrum extension for DFT-S-OFDM and tone reservation (RAN4, RANI)

• Specify enhancements to support dynamic switching between DFT-S-OFDM and CP- OFDM (RANI)

[0040] For an objective of assisting the scheduler specifying dynamic switching between DFT-s-OFDM and CP-OFDM, RANI made an agreement in RAN1#112bis-e meeting as follows:

Agreement

For potential enhancements to assist the scheduler in determining waveform switching, RANI to select 1 from the following options:

Option 1: Reporting of power headroom information for a reference PUSCH using target waveform different from waveform of actual PUSCH. o Details FFS. o Note: reporting PH information for both waveforms is not precluded. o Note: additional trigger for PH for reference PUSCH is not precluded.

Option 2: New trigger of power headroom report based on waveform switching event. o Details FFS.

Option 3: Both Option 1 and Option 2. o Details FFS.

Option 4: No enhancement.

[0041] As general background understanding of PUSCH repetitions, two types of PUSCH repetitions are currently defined in the NR specifications: • PUSCH repetitions Type A, and

• PUSCH repetitions Type B.

PUSCH repetitions Type A are characterized by a same allocation in each of the slots in which the PUSCH is repeated, and in the case of paired spectrum the slots for repetitions are determined as consecutive slots:

For PUSCH repetition Type A, in case K>1,

- If the PUSCH is scheduled by DCI format 0 1 or 0 2

- if AvailableSlotCounting is enabled, the same symbol allocation is applied across the N ■ K slots determined for the PUSCH transmission and the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the N ■ K slots determined for the PUSCH transmission, applying the same symbol allocation in each slot.

- Otherwise, the same symbol allocation is applied across the N ■ K consecutive slots and the PUSCH is limited to a single transmission layer. The UE shall repeat the TB across the N ■ K consecutive slots applying the same symbol allocation in each slot.

This is also pictorially shown in FIG. 2, an example of PUSCH repetition Type A as illustrated with 206 (PUSCH mapping type B), where the PUSCH allocation 202 does not span the entire slot 204. The PUSCH mapping type A may also be used. FIG. 2 illustrates PUSCH mapping type B with PUSCH repetition type A merely to illustrate the difference between PUSCH repetition types.

[0042] PUSCH repetitions Type B are characterized by back-to-back PUSCH repetitions, each repetition of the same nominal length in terms of OFDM symbols:

For PUSCH repetition Type B, except for PUSCH transmitting CSI report(s) with no transport block, the number of nominal repetitions is given by numberOfRepetitions. For the n-th nominal repetition, n = 0, . . . , numberOfRepetitions - 1, S+n-L

- The slot where the nominal repetition starts is given by K_s + , and the starting symbol relative to the start of the slot is given by modfS+w -L, Nf^_b ) .

- The slot where the nominal repetition ends is given by and the

ending symbol relative to the start of the slot is given by mod ( S' + ( M + 1) • L - 1, N^s^_b ) .

Here is the slot where the PUSCH transmission starts, and

is the number of symbols per slot as defined in Clause 4.3.2 of [4, TS 38.211].

This is pictorially shown in below FIG. 3, an example of PUSCH repetition Type B as illustrated with 302, for a PUSCH allocation length L = 7 OFDM symbols. Thus, in this example, each PUSCH repetition (e.g., “302”) has alength of 7 OFDM symbols. 304 illustrates a complete slot of 14 OFDM symbols not used for PUSCH repetition.

[0043] However, before the actual PUSCH Type B transmission, a UE would consider the downlink symbols as invalid symbols for the PUSCH repetitions as well as symbols indicated as invalid by the higher layer parameter invalidSymbolP cittern (invalid meaning that UE cannot transmit in such symbols) as specified in TS 38.214:

The UE may be configured with the higher layer parameter invalidSymbolPattem, which provides a symbol level bitmap spanning one or two slots (higher layer parameter symbols given by invalidSymbolPattem). A bit value equal to 1 in the symbol level bitmap symbols indicates that the corresponding symbol is an invalid symbol for PUSCH repetition Type B transmission. The UE may be additionally configured with a time-domain pattern (higher layer parameter periodicityAndPattem given by invalidSymbolPattem), where each bit of periodicityAndPattem corresponds to a unit equal to a duration of the symbol level bitmap symbols, and a bit value equal to 1 indicates that the symbol level bitmap symbols is present in the unit. The periodicityAndPattem can be { 1, 2, 4, 5, 8, 10, 20 or 40} units long, but maximum of 40 msec. The first symbol of periodicityAndPattem every 40 msec/P periods is a first symbol in frame nf mod 4 = 0, where P is the duration of periodicityAndPattem-rl6 in units of msec. When periodicityAndPattem is not configured, for a symbol level bitmap spanning two slots, the bits of the first and second slots correspond respectively to even and odd slots of a radio frame, and for a symbol level bitmap spanning one slot, the bits of the slot correspond to every slot of a radio frame.

[0044] To further clarify, let us analyze a relevant example scenario in FIG. 4, an actual PUSCH Type B repetitions when invalidSymbolP cittern is applied to the nominal repetitions, where the groups of 1’s and 0’s in the invalidSymbolPcittern are pictorially represented by the low rectangles 402 and by the high rectangles 404, respectively, and the dashed boxes represent each of the 8 scheduled PUSCH repetitions. After applying the pattern to the PUSCH allocation, a UE would not transmit part of the 4th repetition 406, as shown from the actual repetitions pattern. This invalid symbol pattern was originally introduced to avoid UEs transmitting PUSCH in flexible symbols of the frame where gNB may be configuring different UL or DL transmissions.

[0045] It can be observed from the above agreement from RAN1#112bis-e that, if there is no enhancement to power headroom report from UE to assist the NW scheduler in determining waveform switching (i.e., if Option 4 is adopted), then other means are needed for the NW to proactively identify the waveform to be used. Indeed, discussions in RANl#112bis-e on this aspect can be summarized as follows (from comments in regard to Rl-2304222):

“Just as a thought exercise, can’t the gNB give the UE two back-to-back grants, one with CP-OFDM and another with DFT-s-OFDM and infer what works better? gNB should be able to infer the quality of PUSCH (uplink SNR) from the DMRS it receives. It can even be a deliberate retx request if we don’t want to tinker with the UE data buffers.

Wouldn’t this be a rather simple way to figure out which waveform works best without even having to wait for PHR? Note that typical PHR periodicity in commercial deployments in 200 ms. Will the gNB really want to wait this long to determine what to do next? Wouldn’t the approach outlined above be more timely?”

“say you are currently using CP-OFDM, you’ll only consider a waveform switch if TPC commands seem to have no impact on the received SNR. This is implicitly indicative of CP-OFDM being at max power. Once this state is confirmed, all you’ll have to do is send the second grant with a TPC command of say 4 dB. This will force the UE to max out its power for DFT-S-OFDM. You’ll then know what the difference in Pcmax is. It seems workable . Remember that all of this is executed when the UE Tx power is already hovering close to its power class limit. So not much headroom left.”

[0046] Examples of NW proactively identifying waveform for DWS in Rl-2304222 includes:

[0047] Although several concerns on Option 4 exist, there may not be a RAN 1 agreement on Option(s) 1 -3. Therefore, Option 4 (no enhancement on assisting information from UE to NW) may be a fallback agreement. In this context, with use of Option 4, means for the NW to proactively identify the waveform to be used are needed. The above example operation of Option 4 based on two back-to-back PUSCH grants using different waveforms for each PUSCH grant would mainly be used by the NW to proactively get an educated guess on DWS appropriateness before the DWS decision, where this guess or estimate may be based on real- received signals at the NW with different waveforms (WFs).

[0048] PCmax relates to the maximum transmit power of the UE. The RSRP of the complete PUSCH or DM-RS or estimated SINR based on DM-RS RS (and/or other reference signals) can be used where the former can provide some insights about deltaPcmax between WFs only (i.e., the difference between the PCmax of CP-OFDM and the PCmax of DFT-s-OFDM) while the latter also includes the impact of RF impairments that could change with WF (PA nonlinearity, EVM, etc. may change with IBO/OBO after DWS). In all cases, to satisfy the requirements for obtaining meaningful measurement and educated guess of deltaPcmax or DWS appropriateness, based on two scheduled PUSCHs, the following constraints must be taken into account for scheduled PUSCHs with different WFs:

1. Same/similar channel conditions/path loss o All PUSCH using different WFs or transmission modes may be transmitted within the channel coherence time o Same frequency (PRB) position to avoid different frequency selectivity o If DMRS are used only for SINR, both scheduled PUSCHs should be also on the same/similar positions (avoid frequency selectivity impact on DM-RS mainly).

2. UE maximum power transmission: Both PUSCH’s power are increased to reach at least UE maximum power Pcmax for example by consecutive TPC until a steady state is reached, or by over resource allocation leading to higher transmit power for both WFs,

3. Similar configuration : o Same PRB allocation, modulation, etc. that may impact PUSCH power equation

4. Same power constraints: o There is no change in power sharing behavior (if any), or in power reduction not related to WF (e.g., P-MPR), or power class fallback, etc.

[0049] Hence, the NW would need at least to choose and maintain a configuration compatible with all WFs as much as possible for realizing a meaningful comparison, and to configure two PUSCH using different WFs as back-to-back (preferably)(consecutively) or very close in time. We use the expression “as much as possible” because at least aspects such as:

• DMRS type configuration

Number of allocated PRBs (constrained to valid DFT sizes for DFT-s-OFDM and unconstrainted for CP-OFDM) could still be different between CP-OFDM and DFT-S-OFDM. This may be especially true if CP-OFDM configuration is not constrained to the available options for DFT-s-OFDM.

[0050] A targeted problem with features as described herein may be summarized as follows: In case there is no other TB ready in the UE buffer for transmission (the delay could break condition 1 or 4 which may be transparent to NW and, thus, making the estimation misleading for DWS decision), how to guarantee that both PUSCH using different WFs are scheduled/transmitted with the shortest time-gap without violating current specifications? (see specs excerpt from TS 38.214 shown below).

[0051] Indeed, in case these two PUSCH are carrying the same TB, the distance between two PUSCH grants provided by two DCIs format O x should be far to avoid violating a current specification (Section 6.1 of TS 38.214), which states that a DCI that schedules a PUSCH associated with a HARQ process should not come before another PUSCH of the same HARQ process. In other words, the NW needs to wait until the end of a PUSCH to schedule another PUSCH if the two PUSCHs are associated with the same HARQ process. From 38.214:

“The UE is not expected to be scheduled to transmit another PUSCH by a DCI format 0_0 with CRC scrambled by TC-RNTI, for a given HARQ process with the DCI received before the end of the expected transmission of the last PUSCH for that HARQ process if the latter is scheduled by a DCI format 0_0 with CRC scrambled by TC-RNTI or by an UL grant in RA Response. The UE is not expected to be scheduled to transmit another PUSCH by DCI format 0_0, 0_1 or 0_2 scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI for a given HARQ process with the DCI received before the end of the expected transmission of the last PUSCH for that HARQ process if the latter is scheduled by a DCI with CRC scrambled by C-RNTI, CS-RNTI or MCS-C-RNTI.”

Note that the issue is still relevant even if the UE buffer is full or having more than one TB, because it is challenging for a scheduler to satisfy the condition 3 when different TBs (with different HARQ processes) are scheduled with different sizes.

[0052] With features as described herein, in order to avoid specification violation or a long delay between both PUSCH transmissions that may break some condition (e.g, 1, 4) and enable two different PUSCH transmissions with different WFs (e.g., DFT-s-OFDM and CP-OFDM), a single DCI may be used for scheduling at least one PUSCH transmission occasion using at least two WFs (same DCI scheduling and configuring more than one WF or all WFs or transmission modes) and methods for determination/indication of other WF(S) configurations where:

• A single DCI schedules and configures at least one PUSCH transmission(s) using different WFs,

• This single DCI provides at least the configuration for first WF (e.g., current WF) and may indicate at least one configuration parameter for the second WF(s): o The indicated configuration for the second WF could be the same as first WF or inferred from its value (e.g., RB allocation rounded up/down or to the nearest valid RB allocation for DFT-s-OFDM, nearest valid MCS to ensure same TBS, etc.)

• New RRC or MAC-CE parameters may be used to set a default configuration for the second WF(s) at least for the parameters that cannot be indicated/inferred from the DCI parameter(s) of the first WF.

• This method may include an implicit or explicit power increase command/indication between WF (e.g, 4 dB) where the value could be pre- configured/defined power increase (especially when the second WF is DFT-s- OFDM), e.g., RRC configured.

R1 -2300481, in the mTRP, context indicates that:

“When DWS is indicated by DCI, the DCI may be used to indicate multiple PUSCH transmissions to different TRPs or on different cells. In this case, it should be discussed whether same waveform is required to be supported for PUSCH transmissions for different TRPs or cells, or whether different waveforms can be signaled for different PUSCH transmissions independently. In our view, it’s not necessary to restrict same waveform for multiple PUSCH transmissions for different TRPs or cells”

One difference here is that we have one TRP. In addition, Rl-2300481 considers one waveform (WF) for all PUSCH transmissions to the same node mainly one TRP and the WF could be different among multiple PUSCH for different TRPs/NW nodes. In our proposal, PUSCH transmission would contain at least two WFs regardless of if it is to the same NW node or not. In addition, mTRP can be configured with single DCI or multi-DCI where multi-DCI can be straightforward to configure different WFs for mTRP. In case of single DCI for mTRP, others didn’t disclose any information related to the configuration indication for multiple PUSCH using the other WF. With features as described herein, a power offset may be indicated to make sure that the Pcmax with the other WF is reached so that gNB can evaluate and learn which WF is better. Different WFs with PUSCH repetitions and hybrid PUSCH transmission as illustrated in FIGS. 5-8 may be used.

[0053] In a first example, the PUSCH transmissions could re-use PUSCH repetition framework in Rel-17 where a same TB is repeated while indicating to use different WFs in contrast to existing PUSCH repetitions where all transmissions are using a same WF:

• FIG. 5 shows an example of proposed PUSCH repetitions with two (2) WFs or transmission modes. As shown with 502 and 504 in FIG. 5, each WF may be used at least in one repetition. This is applicable with both PUSCH repetition types (Type A shown at the top of Fig. 5 and Type B shown at the bottom of Fig. 5). Note that PUSCH with two (2) repetitions based on different WFs could be enough for DWS purpose between CP-OFDM and DFT-s-OFDM.

• The idea can be also extended to more than two (2) WFs (or more than two (2) transmission modes) to consider more WF alternatives or variants (e.g., DFT-s- OFDM with FDSS-SE) and then decide the most suitable WF/mode for DWS. In one type of example embodiment four (4) DFT-s-OFDM with FDSS-SE transmission modes may be identified as follows (See FIG. 6, an example of proposed PUSCH repetitions with more than two WFs or transmission modes; 502, 504, 606, 608): i. FDSS DFT-s-OFDM without spectrum extension, ii. FDSS DFT-s-OFDM with spectrum extension, iii. FDSS DFT-s-OFDM with spectrum extension and with tone reservation, iv. FDSS DFT-s-OFDM without spectrum extension and with tone reservation. • The above illustrates some examples of different transmission modes with DFT-s- OFDM (e.g., DFT-s-OFDM with/without FDSS and with/without Spectral Extension or with/without Tone reservation). PUSCH using different transmission modes may be considered as a more generic term than merely using same or different WFs. In one type of example embodiment, a new entry could be added in TDRA table to consider this repetition configuration mode with different WFs, as example repetition mode “Ibis” corresponds to 1 repetition per WF, etc.

• In one type of example embodiment, more than one repetition could be used for each WF. With this, the estimation accuracy for SNIR or RSRP difference between WFs could be enhanced to avoid precision error and its misleading impact on DWS decision (e.g., 2 repetitions for each. WF),

• According to one example implementation the waveform switch might only occur in case of non-back-to-back UL slots (such as, for example, if the device hardware capability doesn’t allow an immediate switch and power variation with WF). In other words, a UE might not expect to receive a DCI which schedules the PUSCH transmission repetition according to a configuration mode with different WFs, when a WF switch involves back-to-back UL slots (this would be an error case and the UE would ignore the DCI ) if the UE device capability is a limiting factor. Otherwise back-to-back UL slots with different WFs would not be an error case.

[0054] In a second example, which may be alternatively or additionally relative to the first example noted above, a method may be provided which indicate a hybrid PUSCH, where a same PUSCH transmission carry at least one symbol from each WF (in this example CP- OFDM and DFT-s-OFDM) :

• at least one symbol is allocated for transmission using second WF (e.g., DMRS): as example shown in FIG. 7; an example of proposed hybrid PUSCH transmission with at least one symbol based on other waveform (more than two WFs or transmission mode is also possible), or • FIG. 8, an example of proposed hybrid PUSCH transmission with symbol(s) based on at least two waveforms and a modified DMRS position closer to that of the other WF(s).

• the symbol(s) for second WF could be front-loaded or appended as a suffix (i.e., to avoid breaking single carrier properties especially if first WF is DFT-s-OFDM)

• this option may increase TDRA to account for the symbol(s) with other WF or consider same TDRA similar to the case without these symbol(s). In the latter case, this method could:

• maintain a same TBS by using rate matching, or

• update its TBS calculation by considering the symbols for second WF as overhead in a current TBS equation.

[0055] In regard to FIG. 7, it suggests that the second waveform is used only in symbols with DM-RS. However, this is not always the case. Features as described herein may be used in a case when, in one slot, there is at least one PUSCH symbol without DM-RS with CP-OFDM and at least one PUSCH symbol without DM-RS with DFT-S-OFDM. Features as described herein may be used for both cases where we have at least one symbol with each possible WF and this symbol can be PUSCH data, DMRS or other (e.g., UCI multiplexing). RSRP difference between WFs may be the implementation if this symbol is data (not a known signal at the Rx).

[0056] For both examples noted above:

• Some configuration constraints could be added in the specs to guarantee the maximum configuration compatibility between PUSCH with different WFs using single-DCI scheduling. For example, we may add: o UE doesn’t expect to receive a single DCI scheduling PUSCH with different WFs with configuration comprising or indicating any one of the following:

1. RB allocation size not 2^Aa*3^Ab^A5^Ac, where a, b and c are positive integers, 2. modulation (e.g., pi/2BPSK) or code rate not supported available for all WFs,

3. Configuration for more than one layer transmission,

4. a specific DMRS or FDRA type ,etc.

[0057] The SINR or RSRP estimation based on the resources using different WF may need to consider (preferably) the same number of symbols for a similar accuracy and thus a fair comparison of WFs and their power/quality impact. Hence, these estimations could be using partially or fully the received PUSCH resources from different WFs.

[0058] Referring also to Fig. 9, features of an example embodiment are illustrated including new steps 1-5.

Step 1 at 902: NW determines the most compatible configuration among different WFs respecting the aforementioned constraints.

Step 2 at 904: NW provides PUSCH grant and schedules at least one PUSCH transmission occasion using at least 2 WFs via single DCI format 0_X based on the determined configuration.

Step 3 at 906: NW indicates to UE the PUSCH configuration for the 1^st WF and the other WF(s) using same DCI and possibly some RRC parameters (e.g., transmit power modification between WFs) or pre-defined default configuration. The NW may use TDRA table to indicate the repetition configuration with different WFs.

Step 4 at 908:UE determines the configuration for all WFs based on at least on one configuration parameter of the 1^st WF and possibly higher layer (e.g., RRC, MAC- CE) pre-configured parameters or pre-defined value s/configurations. UE determines the transmit power for each WF. In addition, UE may

■ determine same or another TBS value according to this single-DCI.

■ adjust its rate matching

Step 5 at 910: UE transmits to gNB at least one PUSCH with at least two WFs in the shortest possible duration (e.g., back-to-back) based on single-DCI configuration. Step 6 at 912: NW receives the transmitted PUSCH, as indicated with 914 measures the power (or RSRP) of some or all resources for each WF, or use some or all DMRS to estimate SNIR. NW determines power or SINR difference between different WFs or transmission modes. NW determines 916 the most suitable WF or transmission mode for DWS based on the measured or estimated difference between WFs.

Step 7 at 918: NW transmits a re -configuration via DCI and indicates to UE a DWS for the next scheduled PUSCH. Thus, dynamic waveform switching based on DCI.

Step 8 at 920: UE transmits the next scheduled PUSCH according to the configured WF or transmission mode.

[0059] Fig. 9 shows different control signals 904, 906, 908 to provide the configuration for different WFs or transmission modes. The signals 904, 906, 908 would be at least one single DCI (LI signal) and an RRC signal, but another uplink control or configuration signal based on MAC-CE is not precluded.

[0060] In one example embodiment, a same TBS or different TBS may be used for a waveform due to including a symbol(s) of another WF to a slot. The “same” means the same TBS as in the case when the symbol of another waveform is not included. In case the same TDRA/FDRA is used after adding the at least one symbol of another WF(s) then either: o TBS may be reduced by considering the overhead of the symbols using other WFs, or o a rate matching may be performed to maintain a same TBS like the case without symbol of another WF.

[0061] In another example embodiment, the DCI may indicate that the same TBS is used for both of the waveforms, or that different TBSs are used for the waveforms.

[0062] Features as described herein may be used to allow gNB evaluation of DWS effectiveness based on received signal subjected to similar conditions. The method allows scheduling of PUSCH with different WFs to be back-to-back (consecutive) or at least the closest possible. An error case is also disclosed to account for one possible UE implementation and its constraints on RF loop reconfiguration for back-to-back uplink slots. Features as described herein may be used to avoid additional UE overhead to monitor and read more than one PDCCH configuring to allow PUSCH transmission of a same TB using different WFs. Features as described herein may be used to avoid scheduling overhead and latency by not having to send two or more DCI to schedule different PUSCH with different WFs. Features as described herein may be used to maintain backward compatibility and avoid specification violation.

[0063] Features as described herein may be used in connection with 3GPP Rel-18 specifications such as, for example, impacting one or more of the following: o TS 38.213, o TS 38.331, o TS 38.321

[0064] With features as described herein, a single DCI may be provided which can grant PUSCH transmission(s) using at least two different waveforms to the same cell/gNB/transmission point. Two or more different waveforms can be used in different PUSCH transmissions/repetitions as shown by the example in FIG. 5, or in a same PUSCH transmission as shown by the example in FIG. 7. Features might also include a power increase for one of the waveforms (e.g. for DFT-S-OFDM) to make sure that the waveform is (or both waveforms are) transmitted with a maximum UE power for comparing two things that are very much alike (an apples-to-apples comparison) rather than two things that are contrasting or different.

[0065] The UE may receive a single DCI, where the DCI grants at least one PUSCH transmission using a plurality of waveforms, where the plurality of waveforms includes at least CP-OFDM and DFT-S-OFDM, where at least one CP-OFDM symbol of the transmission(s) and at least one DFT-S-OFDM symbol of the transmission(s) do not overlap in time and where the single DCI indicates configuration parameters for at least a first waveform of the plurality of waveforms. The UE may determine at least one configuration parameter for a second waveform of the plurality of waveforms, where the configuration parameter is based on the configuration parameters or comprised in the configuration parameters. The UE may transmit the at least one PUSCH transmission using the plurality of waveforms. The UE then receive a second DCI granting a second PUSCH transmission using a waveform of the plurality of waveforms. The UE may then transmit the second PUSCH transmission using the selected waveform. [0066] The gNB transmits a single DCI, where the DCI grants at least one PUSCH transmission using a plurality of waveforms, where the plurality of waveforms includes at least CP-OFDM and DFT-S-OFDM, where at least one CP-OFDM symbol of the transmission(s) and at least one DFT-S-OFDM symbol of the transmission(s) do not overlap in time, where the single DCI indicates configuration parameters for a first waveform of the plurality of waveforms. With features as described herein, there may both be: grants by a same DCI so that they are closer in time, and sharing most configuration parameters for a fair comparison. The gNB receives the at least one PUSCH transmission using the plurality of waveforms. Based on the at least one PUSCH transmission, the gNB may select a waveform of the plurality of waveforms. The gNB may then transmits a second DCI granting a second PUSCH transmission using the selected waveform. The gNB may then receive the second PUSCH transmission using the waveform transmitted from the UE.

[0067] Referring also to Fig. 10, in accordance with one example, a method is provided comprising: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes as indicated with block 1002; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes as indicated with block 1004.

[0068] The method may further comprise receiving the signal from the network equipment, where the signal comprises downlink control information (DCI). The downlink control information (DCI) may comprise a single uplink grant configured for granting use of the at least two different waveforms or transmission modes. The transmitting of the at least one physical uplink shared channel may comprise use of repetition Type A with using the at least two different waveforms or transmission modes. The transmitting of the at least one physical uplink shared channel may comprise use of repetition Type B with using the at least two different waveforms or transmission modes. The transmitting of the at least one physical uplink shared channel may comprise use of the at least one physical uplink shared channel with at least one symbol based upon a first one of the at least two different waveforms or transmission modes, and at least one other symbol based upon a different second one of the at least two different waveforms or transmission modes. The other symbol, based upon the different second one of the at least two different waveforms or transmission modes, may be at least one of: prepended to the at least one symbol, or appended to the at least one symbol. The at least two different waveforms or transmission modes may comprise more than two waveforms or transmission modes. The method may further comprise determining, respectively, a respective transmit power for using the at least two different waveforms or transmission modes. The signal may provide a power increase indication between waveforms or transmission modes for at least one of the at least two waveforms or transmission modes. A value of the power increase indication may be a pre -configured or pre-defined power increase. A value of the power increase indication may be set to a maximum achievable transmit output power using a current waveform or transmission mode on a symbol or a transmission occasion. The determining of the configurations for using at least two different waveforms or transmission modes may comprise, in addition to the a signal from a network equipment, using at least one of: at least one RRC parameter, at least one medium access control (MAC) control element (CE), or a predefined default configuration. The method may further comprise: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot. The downlink control information (DCI) may comprise an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication. The method may further comprise adjusting a rate matching based, at least partially, upon the signal. The signal may provide at least a configuration for a first one of the at least two different waveforms or transmission modes, and indicates at least one configuration parameter for a second one of the at least two different waveforms or transmission modes. The indicated at least one configuration parameter for the second waveform or transmission mode may be one of: a same as the first waveform or transmission modes, or not the same as the first waveform or transmission modes, or not an additional field/information element in the signal. The signal may provide at least a configuration for a first one of the at least two different waveforms or transmission modes, and the method further comprises inferring at least one configuration parameter for a second one of the at least two different waveforms or transmission modes based upon the at least a configuration for the first waveform or transmission mode.

[0069] In accordance with one example, an apparatus is provided comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed with the at least one processor, cause the apparatus to perfomrdetermining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

[0070] The instructions, when executed with the at least one processor, may cause the apparatus to perform receiving the signal from the network equipment, where the signal comprises downlink control information (DCI). The downlink control information (DCI) may comprise a single uplink grant configured for granting use of the at least two different waveforms or transmission modes. The transmitting of the at least one physical uplink shared channel may comprise use of repetition Type A with using the at least two different waveforms or transmission modes. The transmitting of the at least one physical uplink shared channel may comprise use of repetition Type B with using the at least two different waveforms or transmission modes. The transmitting of the at least one physical uplink shared channel may comprise use of the at least one physical uplink shared channel with at least one symbol based upon a first one of the at least two different waveforms or transmission modes, and at least one other symbol based upon a different second one of the at least two different waveforms or transmission modes. The other symbol, based upon the different second one of the at least two different waveforms or transmission modes, may be at least one of: prepended to the at least one symbol, or appended to the at least one symbol. The at least two different waveforms or transmission modes may comprise more than two waveforms or transmission modes. The instructions, when executed with the at least one processor, may cause the apparatus to perform determining, respectively, a respective transmit power for using the at least two different waveforms or transmission modes. The signal may provide a power increase indication between waveforms or transmission modes for at least one of the at least two waveforms or transmission modes. A value of the power increase indication may be a pre-configured or predefined power increase. A value of the power increase indication may be set to a maximum achievable transmit output power using a current waveform or transmission mode on a symbol or a transmission occasion. The determining of the configurations for using at least two different waveforms or transmission modes may comprise, in addition to the a signal from a network equipment, using at least one of: at least one RRC parameter, at least one medium access control (MAC) control element (CE), or a pre-defined default configuration. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot. The downlink control information (DCI) may comprise an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication. The instructions, when executed with the at least one processor, may cause the apparatus to perform adjusting a rate matching based, at least partially, upon the signal. The signal may provide at least a configuration for a first one of the at least two different waveforms or transmission modes, and indicates at least one configuration parameter for a second one of the at least two different waveforms or transmission modes. The indicated at least one configuration parameter for the second waveform or transmission mode may be one of: a same as the first waveform or transmission modes, or not the same as the first waveform or transmission modes, or not an additional field/information element in the signal. The signal may provide at least a configuration for a first one of the at least two different waveforms or transmission modes, and the instructions may cause inferring at least one configuration parameter for a second one of the at least two different waveforms or transmission modes based upon the at least a configuration for the first waveform or transmission mode.

[0071] In accordance with one example, apparatus is provided comprising: means for determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and means for transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

[0072] In accordance with one example, non-transitory program storage device readable by an apparatus is provided, tangibly embodying a program of instructions executable with the apparatus for performing operations, the operations comprising: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

[0073] Referring also to Fig. 11, in accordance with one example, a method is provided comprising: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes as indicated with block 1102; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes as indicated with block 1104.

[0074] The physical uplink shared channel configurations for the at least two respective different waveforms or transmission modes may be configured to provide symbols which do not overlap in time. The information may comprise a single downlink control information (DCI) indicating configuration parameters for a first one of the at least two different waveforms or transmission modes. The information may comprise the single downlink control information (DCI) indicating at least one configuration parameter for a second one of the at least two different waveforms or transmission modes. The information may comprise the single downlink control information (DCI) indicating for second waveform or transmission mode configuration information one of: a same as the first waveform or transmission mode, or not the same as the first waveform or transmission mode, or not an additional field/information element in the signal. The second waveform or transmission mode configuration information might not be included with the single downlink control information (DCI). The method may further comprise transmitting a RRC or MAC-CE parameter to at least partially set a default configuration for the second waveform or transmission mode. The RRC or MAC-CE parameter may be configured to be used for a parameter which is not indicated and cannot be inferred from the single downlink control information (DCI) parameter(s) regarding the first waveform or transmission mode. The RRC or MAC-CE parameter may comprise information for: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot. The downlink control information (DCI) may comprise an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication. A value of the implicit or explicit power increase command or indication between waveforms or transmission modes may be a pre- configured or a pre-defined power increase. The method may further comprise receiving at least one physical uplink shared channel, where the at least one physical uplink shared channel comprises use of the at least two different waveforms or transmission modes. The method may further comprise, based at least partially upon the receiving of the at least one physical uplink shared channel, selecting one of the at least two different waveforms or transmission modes. The method may further comprise, based at least partially upon the selected waveform or transmission mode, transmitting a second signal, for using the selected waveform or transmission modes, granting a second physical uplink shared channel transmission.

[0075] In accordance with one example, an apparatus is provided comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.

[0076] The physical uplink shared channel configurations for the at least two respective different waveforms or transmission modes may be configured to provide symbols which do not overlap in time. The information may comprise a single downlink control information (DCI) indicating configuration parameters for a first one of the at least two different waveforms or transmission modes. The information may comprise the single downlink control information (DCI) indicating at least one configuration parameter for a second one of the at least two different waveforms or transmission modes. The information may comprise the single downlink control information (DCI) indicating for second waveform or transmission mode configuration information one of: a same as the first waveform or transmission mode, or not the same as the first waveform or transmission mode, or not an additional field/information element in the signal. The second waveform or transmission mode configuration information might not be included with the single downlink control information (DCI). The instructions, when executed with the at least one processor, might cause the apparatus to perform transmitting a RRC or MAC-CE parameter to at least partially set a default configuration for the second waveform or transmission mode. The RRC or MAC-CE parameter may be configured to be used for a parameter which is not indicated and cannot be inferred from the single downlink control information (DCI) parameter(s) regarding the first waveform or transmission mode. The RRC or MAC-CE parameter may comprise information for: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot. The downlink control information (DCI) may comprise an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication. A value of the implicit or explicit power increase command or indication between waveforms or transmission modes may be a preconfigured or a pre-defined power increase. The instructions, when executed with the at least one processor, may cause the apparatus to perform receiving at least one physical uplink shared channel, where the at least one physical uplink shared channel comprises use of the at least two different waveforms or transmission modes. The instructions, when executed with the at least one processor, may cause the apparatus to perform, based at least partially upon the receiving of the at least one physical uplink shared channel, selecting one of the at least two different waveforms or transmission modes. The apparatus may further cause, based at least partially upon the selected waveform or transmission mode, transmitting a second signal, for using the selected waveform or transmission modes, granting a second physical uplink shared channel transmission.

[0077] In accordance with one example, an apparatus is provided comprising: means for determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and means for transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.

[0078] In accordance with one example, a non-transitory program storage device readable by an apparatus is provided, tangibly embodying a program of instructions executable with the apparatus for performing operations, the operations comprising: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes. [0079] In accordance with one example, a method is provided comprising: receiving, from a network device, a signal scheduling a physical uplink shared channel with at least two different waveforms or transmission modes; and transmitting, to the network device, the physical uplink shared channel using at least two different waveforms or transmission modes.

[0080] The signal may comprise configurations of the physical uplink shared channel for the at least two different waveforms or transmission modes, respectively. The method may further comprise transmitting one or more transport blocks in the physical uplink shared channel using the at least two different waveforms or transmission modes and corresponding the corresponding configurations of the physical uplink shared channel. The method may further comprise transmitting a transport block of the one or more transport blocks in the physical uplink shared channel using the at least two different waveforms or transmission modes. The method may further comprise: transmitting the transport block of the one or more transport blocks in the physical uplink shared channel using a first waveform or transmission mode of the at least two different waveforms or transmission modes; and re-transmitting the transport block in the physical uplink shared channel using a second waveform or transmission mode of the at least two different waveforms or transmission modes. The method may further comprise: determining, based on the signal, a first transport power value for the first waveform or transmission mode and a second transport power value for the second waveform or transmission mode; applying the first transport power value in transmitting the transport block in the physical uplink shared channel using the first waveform or transmission mode; and applying the second transport power value in re-transmitting the transport block in the physical uplink shared channel using the second waveform or transmission mode. The method may further comprise: transmitting different transport blocks of the one or more transport blocks in the physical uplink shared channel using the at least two different waveforms or transmission modes. The method may further comprise: transmitting a first transport block of the one or more transport blocks in the physical uplink shared channel using a first waveform or transmission mode of the at least two different waveforms or transmission modes; and transmitting a second transport block of the one or more transport blocks in the physical uplink shared channel using a second waveform or transmission mode of the at least two different waveforms or transmission modes. The method may further comprise: determining, based on the signal, a first transport power value for the first waveform or transmission mode and a second transport power value for the second waveform or transmission mode; applying the first transport power value in transmitting the first transport block in the physical uplink shared channel using the first waveform or transmission mode; and applying the second transport power value in transmitting the transport block in the physical uplink shared channel using the second waveform or transmission mode. The signal may comprise downlink control information (DCI).

[0081] The following is a description of the way in which the present embodiments may be proposed for future 3GPP standards. Whilst various features may be described as being essential or necessary, this may only be the case for the 3GPP standards, for example due to other requirements imposed by the standards. These statements should not, therefore, be construed as limiting the present embodiments in any way.

Dynamic switching between DFT-s-OFDM and CP-OFDM

In RAN #94e a new work item description was approved on further NR coverage enhancements. Three main objectives characterize the work item:

This contribution focuses on the last objective of the work item, i.e., dynamic switching between DFT-S-OFDM and CP-OFDM.

Enhancements to assist the scheduler in determining waveform switching

In RAN1#111 meeting, following was agreed on the potential enhancements to assist the scheduler in determining waveform switching:

Above agreement led to a followed-up agreement in RAN 1# 112bis-e:

In RAN1#111, RAN1#112 and RAN1#112bis-e, the necessity of reporting assistance information from UE to gNB was identified and discussed. The motivation for reporting assistance information is that only the UE knows its power head room for power boosting when switching to a target waveform. The specification defines only requirements for UE minimum transmit power for certain MCS (TS 38.101-1). In contrast, when adapting the UE Tx power and/or considering waveform switching, gNB knows only the maximum power reduction (MPR) requirement defined by RAN4 specs, as well as PHR of the current waveform reported by the UE. Therefore, it is beneficial for gNB to be exposed to the information known by the UE. From the discussions in RAN1#111, such assistance information can be reported in two ways, namely in form of PHR of the target waveform before DWS or PHR of current WF triggered after DWS or letting UE recommend a waveform via L1/L2 signaling. In either way, the assistance information is essential for gNB to select good waveform in different coverage scenarios, which completes the DWS feature. Without the assistance information, gNB may blindly switch back and forth between the two waveforms, which may not provide clear benefit while it may unnecessarily increase signaling overhead. Therefore, enhancements to assist the scheduler in determining waveform switching should be specified.

Observation 1. The assistance information is essential for gNB to select a suitable waveform in different coverage scenarios, which completes the DWS feature. Without the assistance information, gNB may blindly switch back and forth between the two waveforms, which may not provide clear benefit while it may unnecessarily increase signaling overhead.

With Option 4, the PHR (of the new waveform) is not updated after waveform is switched, but it is only updated in the next report according to legacy configured periodic report, which may happen much later than needed, i.e., when PHR information of the previous waveform is already outdated. Since Option 4 proposes no enhancement to current PHR framework, another approach for gNB to get information about power head room for waveform selection is needed. Such approach was discussed in RANl#112bis-e, wherein gNB may schedule two back-to- back PUSCH grants using different waveforms in which each PUSCH grant would mainly be used by NW to proactively get an educated guess on DWS appropriateness before DWS decision. The RSRP of the complete PUSCH or DM-RS or estimated SINR of DM-RS can be used, where the former can provide some insights about deltaPcmax between waveforms only (i.e., the difference between the PCmax of CP-OFDM and the PCmax of DFT-s-OFDM) while the latter also includes the impact of RF impairments that could change with WF (PA nonlinearity, EVM, etc. may change with IBO/OBO after DWS). However, the corresponding requirements on how the meaningful measurements and educated guess of of deltaPcmax or DWS appropriateness based on PUSCH using different WFs has to be further discussed while considering the following constraints:

1. Same/similar channel conditions/path loss o Both PUSCH are transmitted within the channel coherence time o Same frequency (PRB) allocation and position are used to avoid different frequency selectivity o If DMRS are used only for SINR, both scheduled PUSCHs especially DMRS should be also on the same/similar positions (avoid frequency selectivity impact on DM-RS).

2. UE maximum power transmission: Both PUSCHs power are increased to reach at least UE maximum power Pcmax for example by consecutive TPC until a steady state is reached, or by over resource allocation leading to higher transmit power for both WFs,

4. Same power constraints: o There is no change in power sharing behavior (if any), or in power reduction constraints not related to WF switch (e.g., P-MPR), or power class fallback, etc.

Hence, the NW would need at least to choose a configuration compatible with all WFs as much as possible for realizing a meaningful and fair comparison among the different WFs (condition 3), to configure/schedule PUSCH using different WFs very close in time (e.g., two repetitions with different waveforms for testing purpose) to satisfy mainly condition 1 and 4, and to guarantee that UE is always transmitting at its maximum achievable transmit output power for a given scheduled WF (condition 2).

[0082] The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0083] As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and

(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(iii) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[0084] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0085] It should be understood that the foregoing description is only illustrative. Various alternatives and modifications can be devised by those skilled in the art. For example, features recited in the various dependent claims could be combined with each other in any suitable combination(s). In addition, features from different embodiments described above could be selectively combined into a new embodiment. Accordingly, the description is intended to embrace all such alternatives, modifications and variances which fall within the scope of the appended claims.

Claims

What is claimed is:

1. A method comprising: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

2. The method as claimed in claim 1, further comprising: receiving the signal from the network equipment, where the signal comprises downlink control information (DCI).

3. The method as claimed in claim 2, where the downlink control information (DCI) comprises a single uplink grant configured for granting use of the at least two different waveforms or transmission modes.

4. The method as claimed in any one of claims 1-3, where the transmitting of the at least one physical uplink shared channel comprises use of repetition Type A with using the at least two different waveforms or transmission modes.

5. The method as claimed in any one of claims 1-3, where the transmitting of the at least one physical uplink shared channel comprises use of repetition Type B with using the at least two different waveforms or transmission modes.

6. The method as claimed in any one of claims 1-3, where the transmitting of the at least one physical uplink shared channel comprises use of the at least one physical uplink shared channel with at least one symbol based upon a first one of the at least two different waveforms or transmission modes, and at least one other symbol based upon a different second one of the at least two different waveforms or transmission modes.

7. The method as claimed in claim 6, where the other symbol, based upon the different second one of the at least two different waveforms or transmission modes, is at least one of: prepended to the at least one symbol, or appended to the at least one symbol.

8. The method as claimed in any one of claims 1-7, where the at least two different waveforms or transmission modes comprises more than two waveforms or transmission modes.

9. The method as claimed in any one of claims 1-8, further comprising determining, respectively, a respective transmit power for using the at least two different waveforms or transmission modes.

10. The method as claimed in any one of claims 1-9, where the signal provides a power increase indication between waveforms or transmission modes for at least one of the at least two waveforms or transmission modes.

11. The method as claimed in claim 10, where a value of the power increase indication is a preconfigured or pre-defined power increase.

12. The method as claimed in claim 10, where a value of the power increase indication is set to a maximum achievable transmit output power using a current waveform or transmission mode on a symbol or a transmission occasion.

13. The method as claimed in any one of claims 1-12, where the determining of the configurations for using at least two different waveforms or transmission modes comprises, in addition to the a signal from a network equipment, using at least one of: at least one RRC parameter, at least one medium access control (MAC) control element (CE), or a pre -defined default configuration.

14. The method as claimed in any one of claims 1-12, further comprising: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot.

15. The method as claimed in any one of claims 1-8, where the downlink control information (DCI) comprises an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication.

16. The method as claimed in any one of claims 1-15, further comprising: adjusting a rate matching based, at least partially, upon the signal.

17. The method as claimed in any one of claims 1-16, where the signal provides at least a configuration for a first one of the at least two different waveforms or transmission modes, and indicates at least one configuration parameter for a second one of the at least two different waveforms or transmission modes.

18. The method as claimed in claim 17, where the indicated at least one configuration parameter for the second waveform or transmission mode is one of: a same as the first waveform or transmission modes, or not the same as the first waveform or transmission modes, or not an additional field/information element in the signal.

19. The method as claimed in any one of claims 1-18, where the signal provides at least a configuration for a first one of the at least two different waveforms or transmission modes, and the method further comprises inferring at least one configuration parameter for a second one of the at least two different waveforms or transmission modes based upon the at least a configuration for the first waveform or transmission mode.

20. An apparatus comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

21. The apparatus as claimed in claim 20, where the instructions, when executed with the at least one processor, cause the apparatus to perform receiving the signal from the network equipment, where the signal comprises downlink control information (DCI).

22. The apparatus as claimed in claim 21, where the downlink control information (DCI) comprises a single uplink grant configured for granting use of the at least two different waveforms or transmission modes.

23. The apparatus as claimed in any one of claims 20-22, where the transmitting of the at least one physical uplink shared channel comprises use of repetition Type A with using the at least two different waveforms or transmission modes.

24. The apparatus as claimed in any one of claims 20-22, where the transmitting of the at least one physical uplink shared channel comprises use of repetition Type B with using the at least two different waveforms or transmission modes.

25. The apparatus as claimed in any one of claims 20-22, where the transmitting of the at least one physical uplink shared channel comprises use of the at least one physical uplink shared channel with at least one symbol based upon a first one of the at least two different waveforms or transmission modes, and at least one other symbol based upon a different second one of the at least two different waveforms or transmission modes.

26. The apparatus as claimed in claim 25, where the other symbol, based upon the different second one of the at least two different waveforms or transmission modes, is at least one of: prepended to the at least one symbol, or appended to the at least one symbol.

27. The apparatus as claimed in any one of claims 20-26, where the at least two different waveforms or transmission modes comprises more than two waveforms or transmission modes.

28. The apparatus as claimed in any one of claims 20-27, where the instructions, when executed with the at least one processor, cause the apparatus to perform determining, respectively, a respective transmit power for using the at least two different waveforms or transmission modes.

29. The apparatus as claimed in any one of claims 20-28, where the signal provides a power increase indication between waveforms or transmission modes for at least one of the at least two waveforms or transmission modes.

30. The apparatus as claimed in claim 29, where a value of the power increase indication is a pre-configured or pre-defined power increase.

31. The apparatus as claimed in claim 29, where a value of the power increase indication is set to a maximum achievable transmit output power using a current waveform or transmission mode on a symbol or a transmission occasion.

32. The apparatus as claimed in any one of claims 20-31, where the determining of the configurations for using at least two different waveforms or transmission modes comprises, in addition to the a signal from a network equipment, using at least one of: at least one RRC parameter, at least one medium access control (MAC) control element (CE), or a pre -defined default configuration.

33. The apparatus as claimed in any one of claims 20-31, where the instructions, when executed with the at least one processor, cause the apparatus to perform: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot.

34. The apparatus as claimed in any one of claims 20-27, where the downlink control information (DCI) comprises an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication.

35. The apparatus as claimed in any one of claims 20-34, where the instructions, when executed with the at least one processor, cause the apparatus to perform adjusting a rate matching based, at least partially, upon the signal.

36. The apparatus as claimed in any one of claims 20-35, where the signal provides at least a configuration for a first one of the at least two different waveforms or transmission modes, and indicates at least one configuration parameter for a second one of the at least two different waveforms or transmission modes.

37. The apparatus as claimed in claim 36, where the indicated at least one configuration parameter for the second waveform or transmission mode is one of: a same as the first waveform or transmission modes, or not the same as the first waveform or transmission modes, or not an additional field/information element in the signal.

38. The apparatus as claimed in any one of claims 20-37, where the signal provides at least a configuration for a first one of the at least two different waveforms or transmission modes, and the method further comprises inferring at least one configuration parameter for a second one of the at least two different waveforms or transmission modes based upon the at least a configuration for the first waveform or transmission mode.

39. An apparatus comprising: means for determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and means for transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

40. A non-transitory program storage device readable by an apparatus, tangibly embodying a program of instructions executable with the apparatus for performing operations, the operations comprising: determining, based at least partially upon a signal from a network equipment, configurations for using at least two different waveforms or transmission modes; and transmitting to the network equipment, based upon the determined configurations for using the at least two different waveforms or transmission modes, at least one physical uplink shared channel comprising use of the at least two different waveforms or transmission modes.

41. A method comprising: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.

42. The method as claimed in claim 41, where the physical uplink shared channel configurations for the at least two respective different waveforms or transmission modes are configured to provide symbols which do not overlap in time.

43. The method as claimed in any one of claims 41-42, where the information comprises a single downlink control information (DCI) indicating configuration parameters for a first one of the at least two different waveforms or transmission modes.

44. The method as claimed in claim 43, where the information comprises the single downlink control information (DCI) indicating at least one configuration parameter for a second one of the at least two different waveforms or transmission modes.

45. The method as claimed in claim 43, where the information comprises the single downlink control information (DCI) indicating for second waveform or transmission mode configuration information one of: a same as the first waveform or transmission mode, or not the same as the first waveform or transmission mode, or not an additional field/information element in the signal.

46. The method as claimed in claim 43, where second waveform or transmission mode configuration information is not included with the single downlink control information (DCI).

47. The method as claimed in any one of claims 43-46, further comprising transmitting a RRC or MAC-CE parameter to at least partially set a default configuration for the second waveform or transmission mode.

48. The method as claimed in claim 47, where the RRC or MAC-CE parameter is configured to be used for a parameter which is not indicated and cannot be inferred from the single downlink control information (DCI) parameter(s) regarding the first waveform or transmission mode.

49. The method as claimed in claim 46, where the RRC or MAC-CE parameter comprises information for: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot.

50. The method as claimed in claim 46, where the downlink control information (DCI) comprises an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication.

51. The method as claimed in claim 48, where a value of the implicit or explicit power increase command or indication between waveforms or transmission modes is a pre-configured or a predefined power increase.

52. The method as claimed in any one of claims 41-51, further comprising: receiving at least one physical uplink shared channel, where the at least one physical uplink shared channel comprises use of the at least two different waveforms or transmission modes.

53. The method as claimed in claim 52, further comprising, based at least partially upon the receiving of the at least one physical uplink shared channel, selecting one of the at least two different waveforms or transmission modes.

54. The method as claimed in claim 53, further comprising, based at least partially upon the selected waveform or transmission mode, transmitting a second signal, for using the selected waveform or transmission modes, granting a second physical uplink shared channel transmission.

55. An apparatus comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.

56. The apparatus as claimed in claim 55, where the physical uplink shared channel configurations for the at least two respective different waveforms or transmission modes are configured to provide symbols which do not overlap in time.

57. The apparatus as claimed in any one of claims 55-56, where the information comprises a single downlink control information (DCI) indicating configuration parameters for a first one of the at least two different waveforms or transmission modes.

58. The apparatus as claimed in claim 57, where the information comprises the single downlink control information (DCI) indicating at least one configuration parameter for a second one of the at least two different waveforms or transmission modes.

59. The apparatus as claimed in claim 57, where the information comprises the single downlink control information (DCI) indicating for second waveform or transmission mode configuration information one of: a same as the first waveform or transmission mode, or not the same as the first waveform or transmission mode, or not an additional field/information element in the signal.

60. The apparatus as claimed in claim 57, where second waveform or transmission mode configuration information is not included with the single downlink control information (DCI).

61. The apparatus as claimed in any one of claims 57-60, where the instructions, when executed with the at least one processor, cause the apparatus to perform transmitting a RRC or MAC- CE parameter to at least partially set a default configuration for the second waveform or transmission mode.

62. The apparatus as claimed in claim 61, where the RRC or MAC-CE parameter is configured to be used for a parameter which is not indicated and cannot be inferred from the single downlink control information (DCI) parameter(s) regarding the first waveform or transmission mode.

63. The apparatus as claimed in claim 60, where the RRC or MAC-CE parameter comprises information for: determining a same TBS or another TBS for a waveform or transmission mode based upon inclusion of a symbol(s) of another waveform to a slot.

64. The apparatus as claimed in claim 60, where the downlink control information (DCI) comprises an indication indicating a same TBS is used for both of the waveforms or transmission modes, or that different TBSs are used for the waveforms or transmission modes, where the method further comprises determining a same TBS or another TBS for a waveform or transmission mode based upon the indication.

65. The apparatus as claimed in claim 62, where a value of the implicit or explicit power increase command or indication between waveforms or transmission modes is a pre-configured or a pre -defined power increase.

66. The apparatus as claimed in any one of claims 55-65, where the instructions, when executed with the at least one processor, cause the apparatus to perform receiving at least one physical uplink shared channel, where the at least one physical uplink shared channel comprises use of the at least two different waveforms or transmission modes.

67. The apparatus as claimed in claim 66, where the instructions, when executed with the at least one processor, cause the apparatus to perform, based at least partially upon the receiving of the at least one physical uplink shared channel, selecting one of the at least two different waveforms or transmission modes.

68. The apparatus as claimed in claim 67, where the instructions, when executed with the at least one processor, cause the apparatus to perform, based at least partially upon the selected waveform or transmission mode, transmitting a second signal, for using the selected waveform or transmission modes, granting a second physical uplink shared channel transmission.

69. An apparatus comprising: means for determining physical uplink shared channel configurations for using at least two respective different waveforms or transmission modes; and means for transmitting information, with a single downlink control information, regarding the determined physical uplink shared channel configurations, configured for granting use of the at least two different waveforms or transmission modes.