WO2021012845A1

WO2021012845A1 - Method and apparatus of physical uplink shared channel transmission

Info

Publication number: WO2021012845A1
Application number: PCT/CN2020/096564
Authority: WO
Inventors: Li Guo
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-07-19
Filing date: 2020-06-17
Publication date: 2021-01-28
Anticipated expiration: 2022-01-19
Also published as: CN113366772A; CN113366772B

Abstract

Methods and apparatuses of physical uplink shared channel (PUSCH) transmission are provided. A method of a PUSCH transmission of a user equipment (UE) includes being configured a list of transmit (Tx) beam candidate identities (IDs) by a base station (BS) and being indicated one of the Tx beam candidate IDs for each PUSCH transmission by the BS. Each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID. For one PUSCH transmission, the UE can derive a spatial domain transmission filter according to the RS ID, CORESET ID or PUCCH resource ID that is associated with a Tx beam candidate ID that is indicated for the PUSCH transmission.

Description

METHOD AND APPARATUS OF PHYSICAL UPLINK SHARED CHANNEL TRANSMISSION

BACKGROUND OF DISCLOSURE

1. Field of Disclosure

The present disclosure relates to the field of communication systems, and more particularly, to methods and apparatuses of physical uplink shared channel (PUSCH) transmission.

2. Description of Related Art

In current designs, a main shortcoming is transmit (Tx) beam information for a physical uplink shared channel (PUSCH) is indicated implicitly and indirectly through bridging of a sounding reference signal (SRS) resource dedicatedly configured for PUSCH transmission. There is no direct connection between a PUSCH transmission and a reference signal (RS) indicating a Tx beam of a UE side, which causes large latency and signaling overhead for PUSCH Tx beam switching. In order to switch Tx beam for a PUSCH, a next generation node B (gNB) would have to re-configure SRS resources configured for PUSCH transmission through higher layer signaling. That causes large overhead of control signaling and also causes large latency for Tx beam switching operation.

For a fallback PUSCH, according to current designs, s system is not allowed to transmit fallback PUSCH in any bandwidth part (BWP) where no physical uplink control channel (PUCCH) is configured. In most of deployment, a secondary cell (SCell) does not have configured PUCCH, which implies that no fallback PUSCH can be used on the SCell. However, motivation for fallback PUSCH is coverage enhancement. Thus, such performance enhancement cannot benefit SCells.

Therefore, there is a need for methods and apparatuses of physical uplink shared channel (PUSCH) transmission.

SUMMARY

An object of the present disclosure is to propose methods and apparatuses of physical uplink shared channel (PUSCH) transmission capable of providing at least one of advantages including directly configuring and updating a transmit (Tx) beam for a physical uplink shared channel (PUSCH) transmission, reducing signaling overhead and latency for PUSCH beam updating and switching, flexibly using any type of reference signal and/or physical channel as a Tx beam reference for PUSCH transmission, and enabling a next generation node B (gNB) to schedule fallback PUSCH in any secondary cell (SCell) so that performance gain of coverage enhancement can benefit SCells.

In a first aspect of the present disclosure, a method of a physical uplink shared channel (PUSCH) transmission of a user equipment (UE) includes being configured a list of transmit (Tx) beam candidate identities (IDs) by a base station (BS) and being indicated one of the Tx beam candidate IDs for each PUSCH transmission by the BS.

In a second aspect of the present disclosure, a user equipment (UE) of a physical uplink shared channel (PUSCH) transmission includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to be configured with a list of transmit (Tx) beam candidate identities (IDs) by a base station (BS) and be indicated with one of the Tx beam candidate IDs for each PUSCH transmission by the BS.

In a third aspect of the present disclosure, a method of a physical uplink shared channel (PUSCH) transmission of a base station (BS) includes configuring, to a user equipment (UE) , a list of transmit (Tx) beam candidate identities (IDs) and indicating, to the UE, one of the Tx beam candidate IDs for each PUSCH transmission.

In a fourth aspect of the present disclosure, a base station (BS) of a physical uplink shared channel (PUSCH) transmission includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to configure, to a user equipment (UE) , a list of transmit (Tx) beam candidate identities (IDs) and indicate, to the UE, one of the Tx beam candidate IDs for each PUSCH transmission.

In a fifth aspect of the present disclosure, a method of a physical uplink shared channel (PUSCH) transmission of a user equipment (UE) includes being configured uplink Tx candidate configurations by a BS and performing a PUSCH transmission according to the uplink Tx candidate configurations.

In a sixth aspect of the present disclosure, a user equipment (UE) of a physical uplink shared channel (PUSCH) transmission includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to be configured with uplink Tx candidate configurations by a BS and perform a PUSCH transmission according to the uplink Tx candidate configurations.

In a seventh aspect of the present disclosure, a method of a physical uplink shared channel (PUSCH) transmission of a base station (BS) includes configuring, to a user equipment (UE) , uplink Tx candidate configurations and indicating, to the UE, one of the uplink Tx candidate configurations for each PUSCH transmission.

In an eighth aspect of the present disclosure, a base station (BS) of a physical uplink shared channel (PUSCH) transmission includes a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to configure, to a user equipment (UE) , uplink Tx candidate configurations and indicate, to the UE, one of the uplink Tx candidate configurations for each PUSCH transmission.

In a ninth aspect of the present disclosure, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.

In a tenth aspect of the present disclosure, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.

In an eleventh aspect of the present disclosure, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method.

In a twelfth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to execute the above method.

In a thirteenth aspect of the present disclosure, a computer program causes a computer to execute the above method.

BRIEF DESCRIPTION OF DRAWINGS

In order to more clearly illustrate the embodiments of the present disclosure or related art, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.

FIG. 1 illustrates a transmitter block diagram for a downlink (DL) or uplink (UL) transmission.

FIG. 2 illustrates a receiver block diagram for receiving a DL or UL transmission.

FIG. 3 is a block diagram of a user equipment (UE) and a base station of a physical uplink shared channel (PUSCH) transmission according to an embodiment of the present disclosure.

FIG. 4 is a flowchart illustrating a method of a physical uplink shared channel (PUSCH) transmission of a UE according to an embodiment of the present disclosure.

FIG. 5 is a flowchart illustrating a method of a physical uplink shared channel (PUSCH) transmission of a base station (BS) according to an embodiment of the present disclosure.

FIG. 6 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.

Fifth-generation (5G) wireless systems are generally a multi-beam based system in a frequency range 2 (FR2) ranging from 24.25 GHz to 52.6 GHz, where multiplex transmit (Tx) and receive (Rx) analog beams are employed by a base station (BS) and/or a user equipment (UE) to combat a large path loss in a high frequency band. In a high frequency band system, for example, mmWave systems, the BS and the UE are deployed with large number of antennas, so that a large gain beamforming can be used to defeat the large path loss and signal blockage. Due to the hardware limitation and cost, the BS and the UE might only be equipped with a limited number of transmission and reception units (TXRUs) . Therefore, hybrid beamforming mechanisms can be utilized in both BS and UE. To get the best link quality between the BS and the UE, the BS and the UE need to align analog beam directions for a particular downlink or uplink transmission. For a downlink transmission, the BS and the UE need to find the best pair of a BS Tx beam and a UE Rx beam while for an uplink transmission, the BS and the UE need to find the best pair of the UE Tx beam and the BS Rx beam.

For a communication between one UE and a BS, the BS and the UE need to determine which Tx and Rx beam are going to be used. When one UE moves, the beams used by the BS and the UE for communication might change. In 3GPP 5G specification, the following functions are defined to support such multi-beam-based operation: beam measurement and reporting, beam indication, and beam switch.

At an operation associated with beam measurement and reporting, in this function, the UE can measure one or multiple Tx beams of the BS and then the UE can select the best Tx beam and report his selection to the BS. By measuring the Tx beams of the BS, the UE can also measure one or more different Rx beams and then select the best Rx beam for one particular Tx beam of the BS. In this function, the gNB can also measure one or multiple Tx beams of the UE and then select the best Tx beam of the UE for an uplink transmission. To support measuring Tx beams of the BS, the BS can transmit multiple reference signal (RS) resources and then configures the UE to measure the RS resources. Then, the UE can report an index of one or more selected RS resources that are selected based on some measure metric, for example, a layer 1 reference signal received power (L1-RSRP) . To support measuring Tx beams of the UE used for an uplink transmission, the BS can configure the UE to transmit one or more uplink RS resources, for example, sounding reference signal (SRS) resources, and then the BS can measure the RS resources. The BS can figure out which Tx beam of the UE is the best for the uplink transmission based on measuring, for example, L1-RSRP of the RS resources.

At an operation associated with beam indication, for a downlink transmission, the BS can indicate the UE of which Tx beam of the BS is used to transmit, so that the UE can use proper Rx beam to receive the downlink transmission. For a physical downlink control channel (PDCCH) transmission, the BS can indicate an identify (ID) of one Tx beam of the BS to the UE. For a physical sidelink discovery channel (PSDCH) transmission, the BS can use downlink control information (DCI) in a PDCCH to indicate the ID of one Tx beam that is used to transmit a corresponding PDSCH. For an uplink transmission from the UE, the BS can also indicate the UE of which Tx beam of the UE to be used. For example, for a physical uplink control channel (PUCCH) transmission, the UE uses a Tx beam that is indicated by the BS through a configuration of spatial relation information. For an SRS transmission, the UE uses the Tx beam that is indicated by the BS through the configuration of spatial relation information. For a physical uplink shared channel (PUSCH) transmission, the UE uses a Tx beam that indicated by an information element contained in a scheduling DCI.

At an operation associated with beam switch, this function is used by the BS to switch a Tx beam used for a downlink or uplink transmission. This function is useful when the Tx beam used for transmission currently is out of date due to for example a movement of the UE. When the BS finds a Tx beam currently used for a downlink transmission is not good or the BS finds another Tx beam that is better than the current Tx beam, the BS can send signaling to the UE to inform a change of Tx beam. Similarly, the BS can switch an uplink Tx beam of the UE used to transmit some uplink transmission.

In a communication system, such as a new radio (NR) system, DL signals can include control signaling conveying DCI through a PDCCH, data signals conveying information packet through a PDSCH and some types of reference signals. The DCI can indicate information of how the PDSCH is transmitted, including for example resource allocation and transmission parameters for the PDSCH. The BS can transmit one or more types of reference signals for different purposes, including a demodulation reference symbol (DM-RS) that is transmitted along with the PDSCH and can be used by the UE to demodulate the PDSCH, a channel state information reference signal (CSI-RS) that can be used by the UE to measure BS’s Tx beam or CSI of a downlink channel between the BS and the UE, a phase tracking reference signal (PT-RS) that is also transmitted along with a PDSCH and can be used by the UE to estimate a phase noise caused by imperfection in a radio frequency (RF) part in a transmitter and a receiver and then compensate it when decoding the PDSCH. In NR, DL resource allocation for PDCCH, PDSCH, and reference signals is performed in a unit of orthogonal frequency division multiplexing (OFDM) symbols and a group of physical resource blocks (PRBs) . Each PRB contains a few resource elements (REs) , for example 12 REs, in a frequency domain. A transmission bandwidth (BW) of one downlink transmission consists of frequency resource unit called as resource blocks (RBs) and each RB consists of a few subcarriers or REs, for example, 12 subcarriers or 12 REs.

UL signals transmitted by the UE to the BS can include data signals conveying data packet through a PUSCH, uplink control signals conveying UL control information (UCI) which can be transmitted in the PUSCH or a PUCCH, and UL reference signals. The UCI can carry a schedule request (SR) used by the UE to request an uplink transmission resource, a hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for a PDSCH transmission or a channel state information (CSI) report. The UE can transmit one or more types of uplink reference signals for different purposes, including DM-RS that is transmitted along with a PUSCH transmission and can be used by the BS to demodulate the PUSCH, PT-RS that is also transmitted along with a PUSCH and can be used by the BS to estimate the phase noise caused by imperfection in RF parts and the BS then can compensate it when decoding PUSCH, and SRS signals that are used by the BS to measure one or more UE Tx beams or CSI of the uplink channel between the UE and the BS. Similarly, UL resource allocation for PUSCH, PUCCH, and UL reference signal is also performed in a unit of symbols and a group of PRBs.

A transmission interval for DL or UL channels/signals is referred to as a slot and each slot contains a few, for example 14, symbols in time domain. In a NR system, the duration of one slot can be 1, 0.5, 0.25 or 0.123 millisecond, for the subcarrier spacing 15KHz, 30KHz, 60KHz, and 120 KHz, respectively. NR systems support flexible numerologies and an embodiment can choose proper OFDM subcarrier spacing based on the deployment scenario and service requirement. In the NR system, DL and UL transmission can use different numerologies.

FIG. 1 illustrates a transmitter block diagram for a DL or UL transmission. An embodiment of the transmitter block illustrated in FIG. 1 is for illustration only. Other embodiments could be used without departing from the scope of the present disclosure. Information bits 001 can be first encoded by an encoder 002 such as a low density parity check (LDPC) encoder or polar encoder, and then modulated by a modulator 003. The modulation can be, for example, binary phase-shift keying (BPSK) , quadrature amplitude modulation (QAM) 4, QAM 16, QAM 64, or QAM 256. Then a serial to parallel (S/P) converter 004 can generate parallel multiple modulation symbols that are subsequently inputted to a RE mapper and precoder 005. The RE mapper and precoder 005 can map the modulation symbols to selected REs and then apply some precoder on the modulation symbols on the BW resource assigned to a DL or UL transmission. Then in 006, the modulation symbols are applied with an inverse fast fourier transform (IFFT) and an output thereof is then serialized by a parallel to serial (P/S) converter 007. Then the signals are sent to a Tx unit 008 including for example a digital-to-analog (D/A) convertor, a radio frequency convertor, a filter, a power amplified, and Tx antenna elements, and transmitted out.

FIG. 2 illustrates a receiver block diagram for receiving a DL or UL transmission. An embodiment of the receiver block illustrated in FIG. 2 is for illustration only. Other embodiments could be used without departing from the scope of the present disclosure. Received signals 011 are first passed through a Rx unit 012 including for example Rx antenna elements, a low noise power amplifier, radio frequency converters, and filters. And an output thereof is passed through a P/S013 and then applied an FFT 014. After converting into a frequency domain, useful signals are extracted by a RE demapping 015 according to a resource allocation for the DL or UL transmission. Subsequently, a demod 016 demodulates data symbols with a channel estimation that is calculated based on DM-RS and then a decoder 017 such as LDPC decoder or polar decoder, decodes the demodulated data to output information bits 018.

In current designs, for PUSCH transmission, a next generation node B (gNB) can first configure a set of SRS resources that is dedicated for that PUSCH transmission to a user equipment (UE) . A usage of that set of SRS resources can be set to be ‘codebook’ or ‘non-codebook’ . To schedule a PUSCH transmission, the gNB can send one DCI format to the UE and in the DCI format, a bit-field SRI is used to indicate one or more SRS resources from that SRS resource set dedicated for PUSCH transmission. For the UE to determine the Tx beam (transmit beam) for that PUSCH, the UE can derive it based on the Tx beam information configured to the SRS resource dedicated for PUSCH transmission. If the gNB needs to change the Tx beam for PUSCH transmission, the gNB would have to use higher layer signaling to change the Tx beam configuration of those SRS resources dedicated for PUSCH transmission.

In some embodiments of the present disclosure, the Tx beam configured to the SRS resources dedicated for PUSCH transmission can be an SRS resource, a CSI-RS resource, or a SS/PBCH block. In a fallback PUSCH mode, the gNB can use DCI format 0_0 to schedule PUSCH transmission. Since there is no SRI field in DCI format 0_0 for small payload size, the Tx beam for fallback PUSCH follows a predefined rule. As in some embodiments of the present disclosure, the PUSCH scheduled by DCI format 0_0 can use the same Tx beam as the active PUCCH with lowest resource ID in the same UL BWP (bandwidth part) .

In new radio (NR) 3GPP specification release 15, a beam indication is conducted per PUCCH resource. For a given uplink bandwidth part (BWP) in a serving Cell, a UE can be configured with 4 PUCCH resource set and in each PUCCH resource set, the UE is configured with one or more PUCCH resources. For a transmission on each PUCCH resource, the UE is configured with a parameter PUCCH-spatialRelationInfo, which can contain one or more reference signal resource ID (s) . Each of those reference signal resource is used to provide information on which transmit beam the UE can use for the transmission on that PUCCH resource. For example, if the reference signal resource is a sounding reference signal (SRS) resource, the UE can use the same Tx beam used to transmit that SRS resource on the transmission on that PUCCH resource. If the reference signal resource is a channel state information reference signal (CSI-RS) resource or synchronization signal/physical broadcast channel (SS/PBCH) block, the UE can use the uplink Tx beam corresponding to the receive beam used to receive the CSI-RS resource transmission or SS/PBCH block transmission on the transmission on that PUCCH resource. A gNB can configure only one PUCCH-spatialRelationInfo to a PUCCH resource and when the gNB wants to switch the Tx beam of that PUCCH resource, the gNB can re-configure a radio resource control (RRC) parameter. The gNB can also configure multiple PUCCH-spatialRelationInfo to a PUCCH resource in RRC and then use medium access control control element (MAC CE) signaling to activate one of those configured PUCCH-spatialRelationInfo as the current Tx beam for that PUCCH resource. If the gNB wants to switch the Tx beam of one PUCCH resource, the gNB can use one MAC CE message to indicate another PUCCH-spatialRelationInfo for that PUCCH resource. The gNB can use MAC CE message to indicate the PUCCH-spatialRelationInfo for each individual PUCCH resource. The advantage of that method is flexibility and the gNB is allowed to applied different Tx beams on different PUCCH resources.

For PUSCH scheduled by DCI format 0_0 on a cell, the UE can be requested to transmit that PUSCH according to the spatial relation corresponding to the dedicated PUCCH resources with the lowest ID within the UL BWP of the cell. In other word, if the UE is scheduled with a PUSCH transmission by a DCI format 0_0 in one UL BWP, the UE can use the Tx beam configured to the PUCCH with lowest PUCCH resource ID in the same UL BWP to transmit that PUSCH.

In 3GPP release 16, the Tx beam indication/updating for PUCCH resource will be changed to per PUCCH group. In one UL BWP, all the PUCCH resource can be divided into one or two groups. Use case for one group is single TRP transmission and use case for two group is multi-TRP transmission. Every TRP can schedule a PUSCH transmission for a user equipment (UE) and the UE can apply different Tx beam accordingly.

FIG. 3 illustrates that, in some embodiments, a user equipment (UE) 10 and a base station 20 of a physical uplink shared channel (PUSCH) transmission according to an embodiment of the present disclosure are provided. The UE 10 may include a processor 11, a memory 12, and a transceiver 13. The base station 20 such as a next generation node B (gNB) may include a processor 21, a memory 22 and a transceiver 23. The

processor

11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio interface protocol may be implemented in the

processor

11 or 21. The

memory

12 or 22 is operatively coupled with the

processor

11 or 21 and stores a variety of information to operate the

processor

11 or 21. The

transceiver

13 or 23 is operatively coupled with the

processor

11 or 21, and the

transceiver

13 or 23 transmits and/or receives a radio signal.

The

processor

11 or 21 may include an application-specific integrated circuit (ASIC) , other chipsets, logic circuit and/or data processing devices. The

memory

12 or 22 may include a read-only memory (ROM) , a random access memory (RAM) , a flash memory, a memory card, a storage medium and/or other storage devices. The

transceiver

13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the

memory

12 or 22 and executed by the

processor

11 or 21. The

memory

12 or 22 can be implemented within the

processor

11 or 21 or external to the

processor

11 or 21, in which those can be communicatively coupled to the

processor

11 or 21 via various means are known in the art.

In some embodiments, the processor 11 is configured to be configured with a list of transmit (Tx) beam candidate identities (IDs) by the base station (BS) 20 and be indicated with one of the Tx beam candidate IDs for each PUSCH transmission by the BS 20.

In some embodiments, the processor 11 is configured to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the processor 11 is configured to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the indication of one of the Tx beam candidate IDs for each PUSCH transmission by the BS 20 is through one of a higher layer signaling and a physical layer signaling. In some embodiments, the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .

In some embodiments, each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID. For one PUSCH transmission, the UE 10 can derive a spatial domain transmission filter according to the RS ID, CORESET ID or PUCCH resource ID that is associated with a Tx beam candidate ID that is indicated for the PUSCH transmission. In some embodiments, the RS ID includes a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission includes deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission includes deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.

In some embodiments, the processor 11 is configured to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the processor 11 is configured to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH. In some embodiments, the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule. In some embodiments, the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs. In some embodiments, the fallback PUSCH is scheduled by a DCI format 0_0.

In some embodiments, the processor 21 is configured to configure, to the user equipment (UE) 10, a list of transmit (Tx) beam candidate identities (IDs) and indicate, to the UE 10, one of the Tx beam candidate IDs for each PUSCH transmission.

In some embodiments, the processor 21 is configured to request the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the processor 21 is configured to request the UE to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the indication of one of the Tx beam candidate IDs for each PUSCH transmission to the UE is through one of a higher layer signaling and a physical layer signaling. In some embodiments, the higher layer signaling includes a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .

In some embodiments, the processor 21 is configured to request the UE 10 to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the processor 21 is configured to request the UE 10 to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH. In some embodiments, the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule. In some embodiments, the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs. In some embodiments, the fallback PUSCH is scheduled by a DCI format 0_0.

FIG. 4 illustrates a method 400 of a physical uplink shared channel (PUSCH) transmission of a UE according to an embodiment of the present disclosure. The method 400 includes: a block 410, being configured a list of transmit (Tx) beam candidate identities (IDs) by a base station (BS) , and a block 420, being indicated one of the Tx beam candidate IDs for each PUSCH transmission by the BS.

In some embodiments, the method further includes deriving spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the method further includes calculating uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the indication of one of the Tx beam candidate IDs for each PUSCH transmission by the BS is through one of a higher layer signaling and a physical layer signaling. In some embodiments, the higher layer signaling includes a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .

In some embodiments, each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID. For one PUSCH transmission, the UE can derive a spatial domain transmission filter according to the RS ID, CORESET ID or PUCCH resource ID that is associated with a Tx beam candidate ID that is indicated for the PUSCH transmission. In some embodiments, the RS ID includes a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission includes deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission includes deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.

In some embodiments, the method further includes using the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the method further includes applying an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH. In some embodiments, the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule. In some embodiments, the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs. In some embodiments, the fallback PUSCH is scheduled by a DCI format 0_0.

FIG. 5 illustrates a method 500 of a physical uplink shared channel (PUSCH) transmission of a BS according to an embodiment of the present disclosure. The method 500 includes: a block 510, configuring, to a user equipment (UE) , a list of transmit (Tx) beam candidate identities (IDs) , and a block 520, indicating, to the UE, one of the Tx beam candidate IDs for each PUSCH transmission.

In some embodiments, the method further includes requesting the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the method further includes requesting the UE to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs. In some embodiments, the indication of one of the Tx beam candidate IDs for each PUSCH transmission to the UE is through one of a higher layer signaling and a physical layer signaling. In some embodiments, the higher layer signaling includes a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .

In some embodiments, each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID. For one PUSCH transmission, the UE can derive a spatial domain transmission filter according to the RS ID, CORESET ID or PUCCH resource ID that is associated with a Tx beam candidate ID that is indicated for the PUSCH transmission. In some embodiments, the RS ID includes a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission includes deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.

In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission includes deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs. In some embodiments, the method further includes requesting the UE to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.

In some embodiments, the method further includes requesting the UE to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH. In some embodiments, the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule. In some embodiments, the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs. In some embodiments, the fallback PUSCH is scheduled by a DCI format 0_0.

In some embodiments, methods of transmission of PUSCH are proposed. In some embodiment of the present disclosure, a ‘beam’ can correspond to an RS resource, which can be a channel state information reference signal (CSI-RS) resource, an SRS resource, a SS/PBCH block or any other type of RS.

In one embodiment, a UE can be configured with a list of Tx beam candidates for uplink PUSCH transmission. Each Tx beam candidate can be configured through one or more RS resources, for example CSI-RS resource, SRS resource, or SS/PBCH block. Each Tx beam candidate can also be configured through an ID of another downlink or uplink channel, for example an ID of control resource set (CORESET) or an ID of PUCCH resource. For one PUSCH transmission, a gNB can indicate one of those configured Tx beam candidates to the UE and the UE can derive the transmit beam for that PUSCH according to the ID (s) of RS resources or ID of CORESET or ID of PUCCH resource corresponding to the indicated Tx beam candidate for the PUSCH transmission. For the PUSCH transmission, the UE can also be requested to derive the transmit precoder and/or antenna port information according to the indicated Tx beam candidates. The gNB can indicate one Tx beam candidate for PUSCH transmission through a higher layer signaling, for example a medium access control control element (MAC CE) message or through a physical layer signaling, for example a DCI.

In one method, the UE can be configured with a list M uplink Tx candidate configurations through a higher layer parameter. Examples of uplink Tx candidate configuration can be called: spatialrelation_info, UL_TCI_state (where TCI can be transmission configuration indicator) , UTCI_state (uplink transmission configuration indicator) , UL TCI_state, and Tx beam candidate ID. The UE is configured with those M uplink Tx candidate configurations to transmit PUSCH according to a detected PDCCH with DCI intended for that UE or to transmit PUSCH that is semi-statically configured to operate upon the reception of higher layer parameter configuring the transmission of PUSCH. Each uplink Tx candidate configuration contains parameter for configuring spatial relation information between one or multiple RS resources or other channels and the antenna ports of the PUSCH and also the antenna ports of DM-RS of that PUSCH. One uplink Tx candidate configuration can contain one or more of the following configuration parameters: an identification of an CSI-RS resource, an identification of an SS/PBCH block, an identification of an SRS resource; an identification of a CORESET, an identification of a PUCCH resource, an ID of serving cell, an ID of serving DL BWP for a CSI-RS resource, SS/PBCH block or a CORESET, and an ID of UL BWP for an SRS resource or a PUCCH resource.

Here are some examples for configuring an uplink Tx candidate configuration. In one example, an uplink Tx candidate configuration contains: an Uplink Tx candidate configuration ID, one or more CSI-RS resource IDs and/or SS/PBCH block index (es) , and an ID of serving cell and an ID of DL BWP for the CSI-RS resources or SS/PBCH configured in the same Tx candidate configuration. In one example, an uplink Tx candidate configuration contains: an uplink Tx candidate configuration ID, one ID of CORESET, and an ID of serving cell and ID of DL BWP for the ID of CORESET in the same uplink Tx candidate configuration. In one example, an uplink Tx candidate configuration contains: an uplink Tx candidate configuration ID, one ID of PUCCH resource, and an ID of serving cell and an ID of UL BWP for the ID of PUCCH resource in the same uplink Tx candidate configuration. In one example, an uplink Tx candidate configuration contains: an uplink Tx candidate configuration ID, one or more IDs of SRS resources, and an ID of serving cell and tan ID of UL BWP for the ID (s) of SRS resource in the same uplink Tx candidate configuration.

In some embodiments, a bit-field in a DCI that schedules a PUSCH transmission can be used to indicate one of those configured uplink Tx candidate configurations. For example, a bit-field A0 in a DCI scheduling a PUSCH transmission can be used to indicate one of those configured uplink Tx candidate configurations. If the number of uplink Tx candidate configurations configured in higher layer signaling is above some value, the gNB can send an activation command (for example a MAC CE message) to activate and map up to N ₁ Uplink Tx candidate configurations to the codepoints of the bit-field A0 in the DCI scheduling PUSCH transmission.

In one method of an embodiment, a UE can receive a first DCI that schedules a PUSCH transmission and the code-point of bit-field A0 in the first DCI indicates one Uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains one CORESET ID, the UE can be requested to apply spatial domain transmit filter on the PUSCH transmission, which corresponds to the reference signal resource that is configured as quasi co-location (QCL) type D (spatial Rx parameter) for the CORESET identified by the CORSET ID configured in the Uplink Tx candidate configuration indicated by the code-point of bit field A0 in the first DCI. This method can provide a simplified multi-beam operation, in which the uplink PUSCH transmission follows the downlink control channel on the beam selection.

In one method of an embodiment, a UE can receive a first DCI that schedules a PUSCH transmission and the code-point of bit-field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains one PUCCH resource ID, the UE can be requested to apply spatial domain transmit filter on the PUSCH transmission, which corresponds to the reference signal resource that is configured as spatial relation information for the PUCCH transmission identified by the PUCCH resource ID configured in the uplink Tx candidate configuration indicated by the code-point of bit field A0 in the first DCI. This method of an embodiment can provide a simplified multi-beam operation, in which the uplink PUSCH transmission follows the uplink control channel on the beam selection.

In one method of an embodiment, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains Id of one CSI-RS resource or one SS/PBCH block, the UE can be requested to apply spatial domain transmit filter on the PUSCH transmission, which corresponds to spatial domain receive filter used to receive the CSI-RS resource or SS/PBCH identified by the RS ID configured in the uplink Tx candidate configuration indicated by the code-point of bit field A0 in the first DCI. For example, in the first DCI, the UE can also be indicated with information of rank (i.e., number of layers in the PUSCH transmission) for PUSCH transmission. In this case, the UE can calculate the transmission precoder (s) according to the rank and uplink Tx candidate configuration indicated by the first DCI. For example, in the first DCI, the UE can also be indicated with information of transmission precoder (s) for the scheduled PUSCH transmission.

In one method of an embodiment, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains Ids of more than one CSI-RS resources or SS/PBCH blocks, the UE can be requested to apply spatial domain transmit filters on the PUSCH transmission, which corresponds to spatial domain receive filters used to receive the CSI-RS resources or SS/PBCH blocks identified by the RS Ids configured in the uplink Tx candidate configuration indicated by the code-point of bit field A0 in the first DCI. In this case of an embodiment, the UE can be requested to assume the number of layers for the scheduled PUSCH transmission is equal to the number of RS Ids configured in the indicated uplink Tx candidate configuration. The UE can apply spatial domain transmit filter on one antenna port of PUSCH, which corresponds to the spatial domain receiver filter used to receive one of the CSI-RS resources or SS/PBCH blocks configured in the indicated uplink Tx candidate configuration.

In one method of an embodiment, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains ID of one SRS resource, the UE can be requested to apply spatial domain transmit filter on the PUSCH transmission, which corresponds to spatial domain transmit filter used to transmit the SRS resource identified by the RS ID configured in the Uplink Tx candidate configuration indicated by the code-point of bit field A0 in the first DCI.

In one method of an embodiment, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicates one Uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains Ids of more than one SRS resources, the UE can be requested to apply spatial domain transmit filters on the PUSCH transmission, which corresponds to spatial domain transmit filters used to transmit the SRS resources identified by the RS IDs configured in the Uplink Tx candidate configuration indicated by the code-point of bit field A0 in the first DCI. In this case of an embodiment, the UE can be requested to assume the number of layers for the scheduled PUSCH transmission is equal to the number of RS Ids configured in the indicated uplink Tx candidate configuration. The UE can apply spatial domain transmit filter on one antenna port of PUSCH, which corresponds to the spatial domain transmit filter used to transmit one of the SRS resources configured in the indicated uplink Tx candidate configuration.

In some embodiments of the present disclosure, power control on PUSCH are provided. In one method of an embodiment, to calculate the transmit power for a PUSCH transmission, the UE can be requested to derive a reference signal according to the Uplink Tx candidate configuration that is indicated for that PUSCH transmission and then use that reference signal to calculate the path loss used in calculation of transmit power for that PUSCH transmission.

In one example, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains ID of one CSI-RS resource or one SS/PBCH block, the UE can be requested to use the CSI-RS resource or SS/PBCH block contained in the indicated uplink Tx candidate configuration as the reference signal to calculate path loss for the calculation of transmit power for that PUSCH transmission.

In one example, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicates one Uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains Id of CORESET, the UE can be requested to use the RS ID configured as QCL configuration for the CORESET contained in the indicated uplink Tx candidate configuration as the reference signal to calculate path loss for the calculation of transmit power for that PUSCH transmission.

In one example, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated Uplink Tx candidate configuration contains PUCCH resource Id, the UE can be requested to use the RS ID configured as spatial relation information for the PUCCH resource contained in the indicated uplink Tx candidate configuration as the reference signal to calculate path loss for the calculation of transmit power for that PUSCH transmission.

In one example, a UE can receive a first DCI that schedules a PUSCH transmission and the codepoint of bit-field A0 in the first DCI indicated one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains a SRS resource Id, the UE can be requested to use a RS ID that is configured as the path loss reference signal for the indicated SRS resource to calculate path loss for the calculation of transmit power for that PUSCH transmission.

In some embodiments of the present disclosure, fallback PUSCH are provided. For a fallback PUSCH (for example, a PUSCH scheduled by DCI format 0_0) , the UE can be requested to apply one particular uplink Tx candidate configuration on the PUSCH transmission as predefined or pre-specified rule. In one example, the UE can be requested to apply the Uplink Tx candidate configuration with lowest index on the transmission of a fallback PUSCH.

In one example, the UE receives one activation command (for example a MAC CE) that is used to map N ₁ uplink Tx candidate configurations to the codepoints of the DCI bit-field A0 and those N ₁ uplink Tx candidate configurations are selected among those M uplink Tx candidate configurations configured through higher layer parameters. For a transmission on a fallback PUSCH, the UE can be requested to apply one particular uplink Tx candidate configuration among those N ₁ uplink Tx candidate configurations indicated by the activation command as predefined, for example, the first or the last of those N ₁ uplink Tx candidate configurations. This method of an embodiment can remove the dependency of fallback PUSCH on PUCCH for the transmit beam information. Thus, the fallback PUSCH can be implemented in any serving cell and the benefit of coverage enhancement from fallback PUSCH can be applied to any serving cell.

In some embodiments of the present disclosure, another method for uplink (UL) transmission configuration indication (TCI) are provided. In one embodiment, the UE can be configured with a list M uplink Tx candidate configurations through a higher layer parameter. An uplink Tx candidate configuration can contain one or more RS ID (s) or CORESET ID or PUCCH resource ID to provide the following information for a transmission of a PUSCH. A first PUSCH transmission information: an information of spatial domain transmit filter that can be applied on the antenna ports of PUSCH and the DM-RS associated with the PUSCH transmission. A second PUSCH transmission information: the information of reference signal resource that provides reference for uplink precoder (s) that the gNB indicate for a PUSCH transmission.

In one example, an Uplink Tx candidate configuration contains: an uplink Tx candidate configuration ID, an ID of an SRS resource that is used to provide both the first PUSCH transmission information and the second PUSCH transmission. In one example, an uplink Tx candidate configuration contains: an uplink Tx candidate configuration ID, an ID of CSI-RS resource or SS/PBCH block or SRS resource that is used to provide the first PUSCH transmission information and an ID of an SRS resource that is used to provide the second PUSCH transmission information.

In one example, an uplink Tx candidate configuration contains: an uplink Tx candidate configuration ID, and an ID of CORESET or PUCCH resource that is used to provide the first PUSCH transmission information and an Id of an SRS resource that is used to provide the second PUSCH transmission information.

In some embodiments of the present disclosure, in a first DCI scheduling PUSCH transmission, a bit-field A0 can be used to indicate one configured uplink Tx candidate configuration and a bit-field A1 can be used to indicate transmission precoder (s) for the scheduled PUSCH. For the PUSCH transmission, the UE can apply spatial domain transmit filter (s) on the PUSCH and associated DM-RS, which corresponds to the RS ID (s) or CORESET ID or PUCCH resource ID configured for the first PUSCH transmission information which is contained in the uplink Tx candidate configuration indicated by the codepoint of bit-field A0 in the first DCI. The UE can apply the precoder (s) on the PUSCH, which is indicated by the codepoint of bit-field A1 and corresponds to the RS resource configured for the second PUSCH transmission information which is contained in the uplink Tx candidate configuration indicated by the codepoint of bit-field A0 in the first DCI.

According to some embodiments of the present disclosure, the methods of PUSCH transmission are proposed. The gNB configures a list of Tx beam candidate IDs to a UE and each Tx beam candidate ID is associated with one or more reference signal (RS) IDs or a CORESET (control resource set) ID or a PUCCH resource ID. For each PUSCH transmission, the gNB indicates (for example in a DCI) one Tx beam candidates ID to the UE. The UE derives the spatial domain transmit filter information for the scheduled PUSCH and also calculates the uplink transmit power parameters accordingly for that PUSCH transmission. In current NR specification, the Tx beam information for a PUSCH transmission is signaled implicitly through one SRS resource configured in an SRS set that is configured dedicatedly for PUSCH transmission. The current method imposes great limitation on system implementation and operation. For example, according to the current method, the gNB would have to configure those dedicated SRS resources for PUSCH, which is not necessary in some case and in order to change a Tx beam for PUSCH, the gNB would have to trigger the transmission of both SRS resources dedicated for PUSCH transmission and SRS resources that are configured for uplink beam management.

Furthermore, in some embodiments, new method of Tx beam indication for fallback PUSCH (i.e., PUSCH scheduled by DCI format 0_0) is presented in this disclosure too. The fallback PUSCH can apply a Tx beam that corresponds to the lowest Tx beam candidate IDs that are configured for PUSCH transmission. In current design, the Tx beam of fallback PUSCH is associated with PUCCH channel and the fallback PUSCH transmission can follow the Tx beam used by some particular PUCCH. The consequence of that method is the gNB is not able to schedule fallback PUSCH in SCells where no PUCCH is configured and thus the coverage enhancement gain of fallback PUSCH cannot benefit SCells.

In some embodiments of the present disclosure, methods and apparatuses of physical uplink shared channel (PUSCH) transmission capable of providing at least one of advantages including directly configuring and updating a transmit (Tx) beam for a physical uplink shared channel (PUSCH) transmission, reducing signaling overhead and latency for PUSCH beam updating and switching, flexibly using any type of reference signal and/or physical channel as a Tx beam reference for PUSCH transmission, and enabling a next generation node B (gNB) to schedule fallback PUSCH in any secondary cell (SCell) so that performance gain of coverage enhancement can benefit SCells are provided.

According to some embodiments of the present disclosure, the system can directly configure and update the Tx beam for a PUSCH transmission. The signaling overhead and latency for PUSCH beam updating and switching is reduced. Furthermore, by using Tx candidate configuration proposed in this invention, the system can flexibly use any type of reference signal and/or physical channel as the Tx beam reference for a PUSCH transmission. For example, in a simple deployment, the system can use downlink channel as the reference for PUSCH so that a ‘single-beam’s ystem can be implemented. In some embodiments of the present disclosure, regarding the fallback PUSCH, the method in some embodiments of the present disclosure enables the gNB to schedule fallback PUSCH in any SCell so that the performance gain of coverage enhancement can benefit the SCells. In the deployment scenario where SCell is in FR2, coverage distance in SCell can be the limited factor to system performance. Sone embodiments of the present disclosure are a combination of techniques/processes that can be adopted in 3GPP specification to create an end product. Some embodiments of the present disclosure are used by 5G-NR chipset vendors, V2X communication system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles) , smartphone makers, communication devices for public safety use, AR/VR device maker for example gaming, conference/seminar, education purposes. Some embodiments of the present disclosure propose technical mechanisms.

FIG. 6 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. FIG. 6 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, an application circuitry 730, a memory/storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled with each other at least as illustrated.

The application circuitry 730 may include a circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combinations of general-purpose processors and dedicated processors, such as graphics processors and application processors. The processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.

The baseband circuitry 720 may include a circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) . Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

The RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry. As used herein, “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC) , an electronic circuit, a processor (shared, dedicated, or group) , and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC) .

The memory/storage 740 may be used to load and store data and/or instructions, for example, for system. The memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM) ) , and/or non-volatile memory, such as flash memory. In various embodiments, the I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.

In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite. In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system may have more or less components, and/or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.

It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.

The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.

If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM) , a random access memory (RAM) , a floppy disk, or other kinds of media capable of storing program codes.

While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

A method of a physical uplink shared channel (PUSCH) transmission of a user equipment (UE) , comprising:

being configured a list of transmit (Tx) beam candidate identities (IDs) by a base station (BS) ; and

being indicated one of the Tx beam candidate IDs for each PUSCH transmission by the BS.
The method of claim 1, further comprising deriving spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of claim 2, further comprising calculating uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 1 to 3, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission by the BS is through one of a higher layer signaling and a physical layer signaling.
The method of claim 4, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The method of any one of claims 2 to 5, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 6, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The method of claim 6 or 7, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 6 or 7, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 3 to 9, further comprising using the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 1 to 10, further comprising applying an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The method of claim 11, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The method of claim 11 or 12, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The method of any one of claim 11 to 13, wherein the fallback PUSCH is scheduled by a DCI format 0_0.
A user equipment (UE) of a physical uplink shared channel (PUSCH) transmission, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

be configured with a list of transmit (Tx) beam candidate identities (IDs) by a base station (BS) ; and

be indicated with one of the Tx beam candidate IDs for each PUSCH transmission by the BS.
The UE of claim 15, wherein the processor is configured to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The UE of claim 16, wherein the processor is configured to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The UE of any one of claims 15 to 17, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission by the BS is through one of a higher layer signaling and a physical layer signaling.
The UE of claim 18, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The UE of any one of claims 16 to 19, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The UE of claim 20, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The UE of claim 20 or 21, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The UE of claim 20 or 21, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The UE of any one of claims 17 to 23, wherein the processor is configured to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The UE of any one of claims 15 to 24, wherein the processor is configured to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The UE of claim 25, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The UE of claim 25 or 26, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The UE of any one of claim 25 to 27, wherein the fallback PUSCH is scheduled by a DCI format 0_0.
A method of a physical uplink shared channel (PUSCH) transmission of a base station (BS) , comprising:

configuring, to a user equipment (UE) , a list of transmit (Tx) beam candidate identities (IDs) ; and

indicating, to the UE, one of the Tx beam candidate IDs for each PUSCH transmission.
The method of claim 29, further comprising requesting the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of claim 30, further comprising requesting the UE to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 29 to 31, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission to the UE is through one of a higher layer signaling and a physical layer signaling.
The method of claim 32, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The method of any one of claims 30 to 33, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 34, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The method of claim 34 or 35, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 34 or 35, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 31 to 37, further comprising requesting the UE to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 29 to 38, further comprising requesting the UE to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The method of claim 39, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The method of claim 39 or 40, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The method of any one of claim 39 to 41, wherein the fallback PUSCH is scheduled by a DCI format 0_0.
A base station (BS) of a physical uplink shared channel (PUSCH) transmission, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

configure, to a user equipment (UE) , a list of transmit (Tx) beam candidate identities (IDs) ; and

indicate, to the UE, one of the Tx beam candidate IDs for each PUSCH transmission.
The BS of claim 43, wherein the processor is configured to request the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The BS of claim 44, wherein the processor is configured to request the UE to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The BS of any one of claims 43 to 45, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission to the UE is through one of a higher layer signaling and a physical layer signaling.
The BS of claim 46, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The BS of any one of claims 44 to 47, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The BS of claim 48, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The BS of claim 48 or 49, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The BS of claim 48 or 49, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The BS of any one of claims 45 to 51, wherein the processor is configured to request the UE to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The BS of any one of claims 43 to 52, wherein the processor is configured to request the UE to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The BS of claim 53, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The BS of claim 53 or 54, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The BS of any one of claim 53 to 55, wherein the fallback PUSCH is scheduled by a DCI format 0_0.
A method of a physical uplink shared channel (PUSCH) transmission of a user equipment (UE) , comprising:

being configured uplink Tx candidate configurations by a BS; and

performing a PUSCH transmission according to the uplink Tx candidate configurations.
The method of claim 57, wherein the uplink Tx candidate configurations comprise at least one of the following:

spatial relation information;

uplink transmission configuration indicators; or

Tx beam candidate IDs.
The method of claim 57 or 58, further comprising being indicated one of the Tx beam candidate IDs for each PUSCH transmission by the BS.
The method of claim any one of claims 57 to 59, wherein the PUSCH transmission is according to a PDCCH with DCI or is semi-statically configured.
The method of claim any one of claims 57 to 60, further comprising deriving spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of claim any one of claims 57 to 61, further comprising deriving spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of claim 62, further comprising calculating uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 57 to 63, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission by the BS is through one of a higher layer signaling and a physical layer signaling.
The method of claim 64, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The method of any one of claims 58 to 65, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 66, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The method of claim 66 or 67, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 66 or 67, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 63 to 69, further comprising using the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 57 to 70, further comprising applying an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The method of claim 71, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The method of claim 71 or 72, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The method of any one of claim 71 to 73, wherein the fallback PUSCH is scheduled by a DCI format 0_0.
A user equipment (UE) of a physical uplink shared channel (PUSCH) transmission, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

be configured with uplink Tx candidate configurations by a BS; and

perform a PUSCH transmission according to the uplink Tx candidate configurations.
The UE of claim 75, wherein the uplink Tx candidate configurations comprise at least one of the following:

spatial relation information;

uplink transmission configuration indicators; or

Tx beam candidate IDs.
The UE of claim 75 or 76, wherein the processor is configured to be indicated one of the Tx beam candidate IDs for each PUSCH transmission by the BS.
The UE of claim any one of claims 75 to 77, wherein the PUSCH transmission is according to a PDCCH with DCI or is semi-statically configured.
The UE of claim any one of claims 75 to 78, wherein the processor is configured to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The UE of claim any one of claims 75 to 79, wherein the processor is configured to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The UE of claim 80, wherein the processor is configured to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The UE of any one of claims 75 to 81, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission by the BS is through one of a higher layer signaling and a physical layer signaling.
The UE of claim 82, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The UE of any one of claims 76 to 83, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The UE of claim 84, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The UE of claim 84 or 85, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The UE of claim 84 or 85, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The UE of any one of claims 81 to 87, wherein the processor is configured to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The UE of any one of claims 75 to 88, wherein the processor is configured to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The UE of claim 89, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The UE of claim 89 or 90, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The UE of any one of claim 89 to 91, wherein the fallback PUSCH is scheduled by a DCI format 0_0. 93. A method of a physical uplink shared channel (PUSCH) transmission of a base station (BS) , comprising:

configuring, to a user equipment (UE) , uplink Tx candidate configurations; and

indicating, to the UE, one of the uplink Tx candidate configurations for each PUSCH transmission.
The method of claim 93, wherein the uplink Tx candidate configurations comprise at least one of the following:

spatial relation information;

uplink transmission configuration indicators; or

Tx beam candidate IDs.
The method of claim 93 or 94, further comprising indicating, to the UE, one of the Tx beam candidate IDs for each PUSCH transmission.
The method of claim any one of claims 93 to 95, wherein the PUSCH transmission is according to a PDCCH with DCI or is semi-statically configured.
The method of any one of claim 93 to 95, further comprising requesting the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of claim 97, further comprising requesting the UE to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 93 to 98, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission to the UE is through one of a higher layer signaling and a physical layer signaling.
The method of claim 99, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The method of any one of claims 97 to 100, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 101, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The method of claim 101 or 102, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The method of claim 101 or 102, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 98 to 104, further comprising requesting the UE to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The method of any one of claims 94 to 105, further comprising requesting the UE to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The method of claim 106, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The method of claim 106 or 107, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The method of any one of claim 106 to 108, wherein the fallback PUSCH is scheduled by a DCI format 0_0.
A base station (BS) of a physical uplink shared channel (PUSCH) transmission, comprising:

a memory;

a transceiver; and

a processor coupled to the memory and the transceiver,

wherein the processor is configured to:

configure, to a user equipment (UE) , uplink Tx candidate configurations; and

indicate, to the UE, one of the uplink Tx candidate configurations for each PUSCH transmission.
The BS of claim 110, wherein the uplink Tx candidate configurations comprise at least one of the following:

spatial relation information;

uplink transmission configuration indicators; or

Tx beam candidate IDs.
The BS of claim of claim 110 or 111, wherein the PUSCH transmission is according to a PDCCH with DCI or is semi-statically configured.
The BS of any one of claims 100 to 112, wherein the processor is configured to request the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The BS of claim 113, wherein the processor is configured to request the UE to calculate uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The BS of any one of claims 100 to 114, wherein the indication of one of the Tx beam candidate IDs for each PUSCH transmission to the UE is through one of a higher layer signaling and a physical layer signaling.
The BS of claim 115, wherein the higher layer signaling comprises a medium access control control element (MAC CE) message, and the physical layer signaling comprises a downlink control information (DCI) .
The BS of any one of claims 111 to 116, wherein each of the Tx beam candidate IDs is associated with a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The BS of claim 117, wherein the RS ID comprises a channel state information reference signal (CSI-RS) resource, a sounding reference signal (SRS) resource, or a synchronization signal/physical broadcast channel (SS/PBCH) block.
The BS of claim 117 or 118, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission according to a reference signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink control channel (PUCCH) resource ID.
The BS of claim 117 or 118, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information according to the indicated one of the Tx beam candidate IDs.
The BS of any one of claims 114 to 120, wherein the processor is configured to request the UE to use the spatial domain transmit filter information to calculate path loss in calculation of uplink Tx power parameters for each PUSCH transmission corresponding to the indicated one of the Tx beam candidate IDs.
The BS of any one of claims 110 to 121, wherein the processor is configured to request the UE to apply an uplink Tx candidate configuration on each PUSCH transmission for a fallback PUSCH.
The BS of claim 122, wherein the uplink Tx candidate configuration is in a predefined rule or a pre-specified rule.
The BS of claim 122 or 123, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.
The BS of any one of claim 122 to 124, wherein the fallback PUSCH is scheduled by a DCI format 0_0.
A non-transitory machine-readable storage medium having stored thereon instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 14, 29 to 42, 57 to 74, and 93 to 109.
A chip, comprising:

a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the method of any one of claims 1 to 14, 29 to 42, 57 to 74, and 93 to 109.
A computer readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the method of any one of claims 1 to 14, 29 to 42, 57 to 74, and 93 to 109.
A computer program product, comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 14, 29 to 42, 57 to 74, and 93 to 109.
A computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 14, 29 to 42, 57 to 74, and 93 to 109.