CN113366772B

CN113366772B - Physical uplink shared channel transmission method and device

Info

Publication number: CN113366772B
Application number: CN202080010951.0A
Authority: CN
Inventors: 郭力
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: 2022-12-20
Anticipated expiration: 2040-06-17
Also published as: CN113366772A; WO2021012845A1

Abstract

A Physical Uplink Shared Channel (PUSCH) transmission method and apparatus are provided. A PUSCH transmission method of a User Equipment (UE) includes: configuring, by a Base Station (BS), a list of transmit (Tx) beam candidate Identities (IDs); and indicating, by the BS, one of the Tx beam candidate IDs for each PUSCH transmission. Each Tx beam candidate ID 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 may derive a spatial domain transmit filter from the RS ID, CORESET ID, or PUCCH resource ID associated with the Tx beam candidate ID indicated for that PUSCH transmission.

Description

Physical uplink shared channel transmission method and device

Technical Field

The present disclosure relates to the field of communication systems, and more particularly, to a Physical Uplink Shared Channel (PUSCH) transmission method and apparatus.

Background

In the current design, the main drawback is that the transmit (Tx) beam information for the Physical Uplink Shared Channel (PUSCH) is implicitly and indirectly indicated by the bridging of Sounding Reference Signal (SRS) resources configured specifically for PUSCH transmission. There is no direct link between the PUSCH transmission and the Reference Signal (RS) indicating the Tx beam at the UE side, which results in large delay and signaling overhead for PUSCH Tx beam switching. In order to switch Tx beams for PUSCH, a next generation base station (gNB) will have to reconfigure through higher layer signaling to SRS resources configured for PUSCH transmission. This results in large control signaling overhead for Tx beam switching operations, and also results in large delays. For fallback PUSCH, according to the current design, the system is not allowed to transmit the fallback PUSCH in any bandwidth part (BWP) of the Physical Uplink Control Channel (PUCCH) not configured. In most deployments, the second cell (SCell) is not configured with PUCCH, which means that fallback PUSCH cannot be used on the SCell. However, the motivation for fallback PUSCH is coverage enhancement. Thus, this performance enhancement cannot benefit the SCell.

Therefore, a Physical Uplink Shared Channel (PUSCH) transmission method and apparatus are needed.

Disclosure of Invention

An object of the present disclosure is to provide a Physical Uplink Shared Channel (PUSCH) transmission method and apparatus, which can provide at least one of the following advantages, including: directly configuring and updating a transmit (Tx) beam for Physical Uplink Shared Channel (PUSCH) transmission; reducing signaling overhead and delay of PUSCH beam update and handover; flexibly using any type of reference signal and/or physical channel as a Tx beam reference for PUSCH transmission; and enabling a next generation base station (gNB) to schedule a fallback PUSCH in any second cell (SCell) such that coverage enhanced performance gains may benefit the SCell.

In a first aspect of the present disclosure, a method of Physical Uplink Shared Channel (PUSCH) transmission for a User Equipment (UE) includes configuring, by a Base Station (BS), a list of transmit (Tx) beam candidate Identities (IDs); and indicating, by the BS, one of the Tx beam candidate IDs for each PUSCH transmission.

In a second aspect of the disclosure, a User Equipment (UE) for Physical Uplink Shared Channel (PUSCH) transmission includes a memory, a transceiver, and a processor coupled with the memory and the transceiver. The processor is configured to configure, by a Base Station (BS), a list of transmit (Tx) beam candidate identification IDs, and to indicate, by the BS, one of the Tx beam candidate IDs for each PUSCH transmission.

In a third aspect of the present disclosure, a method of Physical Uplink Shared Channel (PUSCH) transmission by a Base Station (BS) includes configuring a list of transmit (Tx) beam candidate Identities (IDs) to a User Equipment (UE), and indicating one of the Tx beam candidate IDs to the UE for each PUSCH transmission.

In a fourth aspect of the disclosure, a Base Station (BS) for Physical Uplink Shared Channel (PUSCH) transmissions includes a memory, a transceiver, and a processor coupled with the memory and the transceiver. The processor is configured to configure a User Equipment (UE) with a list of transmit (Tx) beam candidate Identifications (IDs), and to 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 Physical Uplink Shared Channel (PUSCH) transmission for a User Equipment (UE) includes configuring, by a Base Station (BS), an uplink Tx candidate configuration, and performing PUSCH transmission according to the uplink Tx candidate configuration.

In a sixth aspect of the disclosure, a User Equipment (UE) for Physical Uplink Shared Channel (PUSCH) transmission includes a memory, a transceiver, and a processor coupled with the memory and the transceiver. The processor is configured to configure an uplink Tx candidate configuration by a Base Station (BS), and perform PUSCH transmission according to the uplink Tx candidate configuration.

In a seventh aspect of the present disclosure, a method of Physical Uplink Shared Channel (PUSCH) transmission by a Base Station (BS) includes configuring an uplink Tx candidate configuration to a User Equipment (UE), and indicating one of the uplink Tx candidate configurations to the UE for each PUSCH transmission.

In an eighth aspect of the present disclosure, a Base Station (BS) for Physical Uplink Shared Channel (PUSCH) transmission includes a memory, a transceiver, and a processor coupled with the memory and the transceiver. The processor is configured to configure an uplink Tx candidate configuration to a User Equipment (UE); and indicating one of the uplink Tx candidate configurations to the UE for each PUSCH transmission.

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

In a tenth aspect of the disclosure, a chip includes a processor configured to call and execute a computer program stored in a memory to cause an apparatus for mounting a chip to perform the above method.

In an eleventh aspect of the present disclosure, a computer-readable storage medium has stored therein a computer program for causing a computer to execute the above-described method.

In a twelfth aspect of the disclosure, a computer program product comprises a computer program, and the computer program causes a computer to perform the above-described method.

In a thirteenth aspect of the disclosure, a computer program causes a computer to perform the above-described method.

Drawings

In order to more clearly explain embodiments of the present disclosure or related art, the following drawings, which will be described in the embodiments, are briefly introduced. It should be apparent that the drawings are only some embodiments of the disclosure and that other drawings may be derived by those of ordinary skill in the art without undue experimentation.

Fig. 1 shows a block diagram of a transmitter for Downlink (DL) or Uplink (UL) transmission.

Fig. 2 shows a block diagram of a receiver for receiving DL or UL transmissions.

Fig. 3 is a block diagram of a User Equipment (UE) and a base station for Physical Uplink Shared Channel (PUSCH) transmission in accordance with an embodiment of the present disclosure.

Fig. 4 is a flowchart illustrating a Physical Uplink Shared Channel (PUSCH) transmission method of a UE according to an embodiment of the present disclosure.

Fig. 5 is a flowchart illustrating a Physical Uplink Shared Channel (PUSCH) transmission method of a Base Station (BS) according to an embodiment of the present disclosure.

Fig. 6 is a block diagram of a wireless communication system in accordance with an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in detail with reference to the following accompanying drawings in terms of technical problems, structural features, objects, and effects achieved. In particular, the terminology in the embodiments of the present disclosure is for the purpose of describing particular embodiments only, and is not intended to be limiting of the present disclosure.

Fifth generation (5G) wireless systems are typically a multi-beam based system in the frequency range 2 (frequency range 2, fr2) ranging from 24.25GHz to 52.6GHz, where multiple transmit (Tx) and receive (Rx) analog beams are employed by the Base Station (BS) and/or User Equipment (UE) to combat large path losses in the high band. In high band systems, such as millimeter wave (mmWave) systems, BSs and UEs are deployed with a large number of antennas so that large gain beamforming can be used to overcome large path loss and signal blocking. Due to hardware limitations and cost, the BS and the UE may be equipped with only a limited number of transmission and reception units (TXRUs). Therefore, a hybrid beamforming mechanism may be used in both the BS and the UE. In order to obtain the best link quality between the BS and the UE, the BS and the UE need to align the analog beam direction for a particular downlink or uplink transmission. For downlink transmission, the BS and the UE need to find the best pair of the BS Tx beam and the UE Rx beam, and for uplink transmission, the BS and the UE need to find the best pair of the UE Tx beam and the BS Rx beam.

For communication between one UE and the BS, the BS and the UE need to determine which Tx and Rx beams are to be used. When one UE moves, a beam used by the BS and the UE to communicate may change. In the 3gpp 5G specification, the following functions are defined to support this multi-beam based operation: beam measurement and reporting, beam indication and beam switching.

In an operation associated with beam measurement and reporting, in this function, the UE may measure one or more Tx beams of the BS, and then the UE may select the best Tx beam and report its selection to the BS. By measuring the Tx beams of the BS, the UE may 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 may also measure one or more Tx beams of the UE and then select the best Tx beam of the UE for uplink transmission. To support measuring the Tx beams of the BS, the BS may transmit a plurality of Reference Signal (RS) resources and then configure the UE to measure the RS resources. The UE may then report an index of one or more selected RS resources, which are selected based on some measurement criteria, such as physical layer 1reference signal received power (l 1-RSRP). To support measuring the Tx beams of the UE for uplink transmission, the BS may configure the UE to transmit one or more uplink RS resources, e.g., sounding Reference Signal (SRS) resources, and then the BS may measure the RS resources. The BS may find out which Tx beam of the UE is best for uplink transmission based on measuring, for example, L1-RSRP of the RS resource.

In operation associated with beam indication, for downlink transmission, the BS may indicate to the UE which Tx beam of the BS is used for transmission so that the UE may receive downlink transmission using the appropriate Rx beam. For Physical Downlink Control Channel (PDCCH) transmission, the BS may indicate to the UE an Identification (ID) of one Tx beam of the BS. For physical downlink discovery channel (PSDCH) transmission, the BS may use Downlink Control Information (DCI) in the PDCCH to indicate an ID of one Tx beam used to transmit a corresponding PDSCH. For uplink transmission from the UE, the BS may also indicate to the UE which Tx beam of the UE to use. For example, for Physical Uplink Control Channel (PUCCH) transmission, the UE uses a Tx beam indicated by the BS through spatial relationship information configuration. For SRS transmission, the UE uses the Tx beam indicated by the BS through spatial relationship information configuration. For Physical Uplink Shared Channel (PUSCH) transmission, the UE uses the Tx beam indicated by the information element contained in the scheduling DCI.

This function is used by the BS to switch Tx beams for downlink or uplink transmission in operations associated with beam switching. This functionality is useful when the Tx beam currently used for transmission is out of date due to, for example, movement of the UE. When the BS finds that the Tx beam currently used for downlink transmission is not good, or the BS finds another Tx beam better than the current Tx beam, the BS may transmit signaling to the UE to inform of changing the Tx beam. Similarly, the BS may switch the uplink Tx beams of the UE for transmitting some uplink transmissions.

In a communication system, such as a New Radio (NR) system, the DL signal may include control signaling that transmits DCI through a PDCCH, a data signal that transmits an information packet through a PDSCH, and some types of reference signals. The DCI may indicate information on how to transmit the PDSCH, including, for example, resource allocation and transmission parameters of the PDSCH. The BS may transmit one or more types of reference signals for different purposes, including: a demodulation reference signal (DM-RS) which is transmitted together with the PDSCH and may be used by the UE to demodulate the PDSCH; a channel state information reference signal (CSI-RS) that may be used by the UE to measure a CSI of a Tx beam of the BS or a downlink channel between the BS and the UE; a phase tracking reference signal (PT-RS), which is also transmitted with the PDSCH, may be used by the UE to estimate phase noise caused by imperfections in the Radio Frequency (RF) parts in the transmitter and receiver, and then compensate for the PDSCH when decoding it. In NR, DL resource allocation for a PDCCH, a PDSCH, and a reference signal is performed in units of Orthogonal Frequency Division Multiplexing (OFDM) symbols and Physical Resource Block (PRB) groups. Each PRB contains several Resource Elements (REs), for example 12 REs, in the frequency domain. A transmission Bandwidth (BW) for one downlink transmission is composed of frequency resource units called Resource Blocks (RBs), and each RB is composed of several subcarriers or REs, for example, 12 subcarriers or 12 REs.

The UL signal transmitted by the UE to the BS may include: transmitting a data signal of the data packet through a PUSCH; an uplink control signal for transmitting Uplink Control Information (UCI), which may be transmitted in a PUSCH or a PUCCH; and a UL reference signal. The UCI may carry Scheduling Request (SR) for requesting uplink transmission resources by the UE, hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for PDSCH transmission, or a Channel State Information (CSI) report. The UE may transmit one or more types of uplink reference signals for different purposes, including: a DM-RS transmitted with the PUSCH transmission and usable by the BS to demodulate the PUSCH; a PT-RS, which is also transmitted with the PUSCH, may be used by the BS to estimate phase noise caused by imperfections in the RF section, and then the BS may compensate for the PUSCH when decoding it; and an SRS signal used by the BS to measure CSI of one or more UE Tx beams or an uplink channel between the UE and the BS. Similarly, UL resource allocation for PUSCH, PUCCH, and UL reference signals is also made in units of symbols and PRB groups.

The transmission interval of a DL or UL channel/signal is called a slot, and each slot contains several symbols, for example, 14 symbols, in the time domain. In the NR system, the duration of one slot may be 1, 0.5, 0.25, or 0.123 msec for subcarrier intervals of 15KHz, 30KHz, 60KHz, and 120KHz, respectively. NR systems support flexible parameter sets and embodiments may select an appropriate OFDM subcarrier spacing based on deployment scenarios and service requirements. In NR systems, DL and UL transmissions may use different sets of parameters.

Fig. 1 shows a block diagram of a transmitter for DL or UL transmission. The embodiment of the transmitter block shown in fig. 1 is for illustration only. Other embodiments may be used without departing from the scope of this disclosure. Information bits 001 may be first encoded by an encoder 002, such as a Low Density Parity Check (LDPC) encoder or a polar (polar) encoder, and then modulated by a modulator 003. The modulation may be, for example, binary phase-shift keying (BPSK), quadrature Amplitude Modulation (QAM) 4, QAM16, QAM64, or QAM256. Then, a serial to parallel (S/P) converter 004 may generate a plurality of modulation symbols in parallel, which are then input to an RE mapper and precoder 005. The RE mapper and precoder 005 may map modulation symbols to selected REs and then apply some precoder to modulation symbols on BW resources allocated to DL or UL transmission. Then, in 006, an Inverse Fast Fourier Transform (IFFT) is applied to the modulation symbols, and then a parallel to serial (P/S) converter 007 serializes the output thereof. Then, the signal is transmitted to a Tx unit 008, which includes, for example, a digital-to-analog (D/a) converter, a radio frequency converter, a filter, a power amplifier, and a Tx antenna element, and is transmitted.

Fig. 2 shows a block diagram of a receiver for receiving DL or UL transmissions. The embodiment of the receiver block shown in fig. 2 is for illustration only. Other embodiments may be used without departing from the scope of this disclosure. The received signal 011 first passes through an Rx unit 012, which comprises e.g. an Rx antenna element, a low noise power amplifier, a radio frequency converter and a filter. Its output passes P/S013 and then FFT014 is applied. After conversion to the frequency domain, the useful signal is extracted by the RE demapping 015 according to the resource allocation of the DL or UL transmission. Subsequently, the demodulator 016 demodulates the data symbols with the channel estimation calculated based on the DM-RS, and then the decoder 017, such as an LDPC decoder or a polar decoder, decodes the demodulated data into output information bits 018.

In the current design, for PUSCH transmission, a next generation base station (gNB) may first configure a User Equipment (UE) with a set of SRS resources dedicated for the PUSCH transmission. The usage of the set of SRS resources may be set to "codebook" or "non-codebook". To schedule PUSCH transmissions, the gNB may send a DCI format to the UE, and in the DCI format, a bit field SRI is used to indicate one or more SRS resources from the set of SRS resources dedicated to PUSCH transmissions. For the UE to determine the Tx beam (transmit beam) of this PUSCH, the UE may 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 will 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 resource dedicated to PUSCH transmission may be an SRS resource, a CSI-RS resource, or an SS/PBCH block. In fallback PUSCH mode, the gNB may schedule PUSCH transmissions using DCI format 0_0. Since there is no SRI field in DCI format 0 _0for small payload sizes, the Tx beam of the fallback PUSCH follows a predefined rule. As in some embodiments of the present disclosure, PUSCH scheduled by DCI format 0_0 may use the same Tx beam as the active PUCCH with the lowest resource ID in the same UL BWP (bandwidth part).

In New Radio (NR) 3GPP specification release 15, beam indication is done per PUCCH resource. For a given uplink bandwidth part (BWP) in a serving cell, a UE may be configured with 4 PUCCH resource sets, and in each PUCCH resource set, the UE is configured with one or more PUCCH resources. For transmission on each PUCCH resource, the UE is configured with a parameter PUCCH-spatial relationinfo, which may contain one or more reference signal resource IDs. Each of these reference signal resources is used to provide information about which transmit beam the UE may use for transmission on that PUCCH resource. For example, if the reference signal resource is a Sounding Reference Signal (SRS) resource, the UE may use the same Tx beam used to transmit the SRS resource in the transmission of the PUCCH resource. If the reference signal resource is a channel state information reference signal (CSI-RS) resource or a synchronization signal/physical broadcast channel (SS/PBCH) block, the UE may use an uplink Tx beam corresponding to a receive beam used to receive CSI-RS resource transmissions or SS/PBCH block transmissions in the transmission of the PUCCH resource. The gNB may configure only one PUCCH-spatial relationinfo for the PUCCH resource, and may reconfigure Radio Resource Control (RRC) parameters when the gNB wants to switch the Tx beam of the PUCCH resource. The gNB may also configure multiple PUCCH-spatialrelalationinfo for the PUCCH resource in RRC, and then use medium access control element (MAC CE) signaling to activate one of these configured PUCCH-spatialrelalationinfo as the current Tx beam of the PUCCH resource. If the gNB wants to switch Tx beams of one PUCCH resource, the gNB may indicate another PUCCH-spatial relationship info of the PUCCH resource using one MAC CE message. The gmb may indicate PUCCH-spatial relationinfo of each individual PUCCH resource using the MAC CE message. The advantage of this approach is flexibility and allows the gNB to apply different Tx beams on different PUCCH resources.

For PUSCH scheduled with DCI format 0_0 on a cell, the UE may be requested to transmit the PUSCH according to the spatial relationship corresponding to the dedicated PUCCH resource with the lowest ID within the UL BWP of the cell. In other words, if the UE is scheduled PUSCH transmission through DCI format 0_0 in one UL BWP, the UE may transmit the PUSCH using a Tx beam configured to the PUCCH having the lowest PUCCH resource ID in the same UL BWP.

In 3GPP release 16, the Tx beam indication/update of PUCCH resources will be changed per PUCCH group. In one UL BWP, all PUCCH resources may be divided into one group or two groups. One group use case is single TRP transmission and two groups use case is multiple TRP transmission. Each TRP may schedule a PUSCH transmission for a User Equipment (UE), and the UE may apply a different Tx beam accordingly.

Fig. 3 shows, in some embodiments, a User Equipment (UE) 10 and a base station 20 providing Physical Uplink Shared Channel (PUSCH) transmission according to embodiments of the present disclosure. The UE 10 may include a processor 11, a memory 12, and a transceiver 13. A base station 20, such as a next generation base station (gNB), may include a processor 21, a memory 22, and a transceiver 23. The

processor

11 or 21 may be configured to implement the proposed functions, processes and/or methods described in this specification. The layers of the 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 various 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 radio signals.

The

processor

11 or 21 may comprise an application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device.

Memory

12 or 22 may include read-only memory (ROM), random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. The

transceiver

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

memory

12 or 22 and executed by the

processor

11 or 21. The

memory

12 or 22 may be implemented within the

processor

11 or 21 or external to the

processor

11 or 21, in which case they may be communicatively coupled to the

processor

11 or 21 via various means as is known in the art.

In some embodiments, the processor 11 is configured to configure a list of transmit (Tx) beam candidate Identifications (IDs) by the Base Station (BS) 20 and to indicate 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 one of the indicated Tx beam candidate IDs. In some embodiments, the processor 11 is configured to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs. In some embodiments, one of the Tx beam candidate IDs is indicated by the BS 20 for each PUSCH transmission by one of higher layer signaling and physical layer signaling. In some embodiments, the higher layer signaling comprises a medium access control element (MAC CE) message and the physical layer signaling comprises Downlink Control Information (DCI).

In some embodiments, each Tx beam candidate ID 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 may derive the spatial domain transmit filter from the RS ID, CORESET ID, or PUCCH resource ID associated with the Tx beam candidate ID 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 spatial domain transmit filter information for each PUSCH transmission includes deriving a Tx beam for each PUSCH transmission from a Reference Signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink shared channel (PUCCH) resource ID. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

In some embodiments, the processor 11 is configured to calculate the path loss using the spatial domain transmit filter information when calculating the uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs. In some embodiments, the processor 11 is configured to apply the uplink Tx candidate configuration for each PUSCH transmission of the fallback PUSCH. In some embodiments, the uplink Tx candidate configuration conforms to a predefined rule or a predefined rule. In some embodiments, the uplink Tx candidate configuration corresponds to the lowest Tx beam candidate ID among the Tx beam candidate IDs. In some embodiments, fallback PUSCH is scheduled with DCI format 0_0.

In some embodiments, the processor 21 is configured to configure a list of transmit (Tx) beam candidate Identities (IDs) to the User Equipment (UE) 10 and to indicate one of the Tx beam candidate IDs to the UE 10 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 one of the indicated Tx beam candidate IDs. In some embodiments, the processor 21 is configured to request the UE to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs. In some embodiments, one of the Tx beam candidate IDs is indicated to the UE for each PUSCH transmission by one of higher layer signaling and physical layer signaling. In some embodiments, the higher layer signaling comprises medium access control element (MAC CE) messages and the physical layer signaling comprises Downlink Control Information (DCI).

In some embodiments, each Tx beam candidate ID 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 may derive the spatial domain transmit filter from the RS ID, CORESET ID, or PUCCH resource ID associated with the Tx beam candidate ID 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 spatial domain transmit filter information for each PUSCH transmission includes deriving a Tx beam for each PUSCH transmission from a Reference Signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink shared channel (PUCCH) resource ID. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

In some embodiments, the processor 21 is configured to request the UE 10 to use the spatial domain transmit filter information to calculate the pathloss when calculating the uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs. In some embodiments, the processor 21 is configured to request the UE 10 to apply the uplink Tx candidate configuration for each PUSCH transmission of the fallback PUSCH. In some embodiments, the uplink Tx candidate configuration complies with a predefined rule or a predefined rule. In some embodiments, the uplink Tx candidate configuration corresponds to the lowest Tx beam candidate ID among the Tx beam candidate IDs. In some embodiments, fallback PUSCH is scheduled with DCI format 0_0.

Fig. 4 illustrates a Physical Uplink Shared Channel (PUSCH) transmission method 400 for a UE according to an embodiment of the present disclosure. The method 400 includes: configuring, by a Base Station (BS), a list of transmit (Tx) beam candidate Identifications (IDs), block 410; and block 420, indicating, by the BS, one of the Tx beam candidate IDs for each PUSCH transmission.

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

In some embodiments, each Tx beam candidate ID 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 may derive a spatial domain transmit filter from the RS ID, CORESET ID, or PUCCH resource ID associated with the Tx beam candidate ID 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 spatial domain transmit filter information for each PUSCH transmission includes deriving a Tx beam for each PUSCH transmission from a Reference Signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink shared channel (PUCCH) resource ID. In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of a Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

In some embodiments, the method further comprises, in calculating the uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs, calculating the path loss using the spatial domain transmit filter information. In some embodiments, the method further comprises applying the uplink Tx candidate configuration for each PUSCH transmission of the fallback PUSCH. In some embodiments, the uplink Tx candidate configuration conforms to a predefined rule or a predefined rule. In some embodiments, the uplink Tx candidate configuration corresponds to the lowest Tx beam candidate ID among the Tx beam candidate IDs. In some embodiments, fallback PUSCH is scheduled with DCI format 0_0.

Fig. 5 illustrates a Physical Uplink Shared Channel (PUSCH) transmission method 500 of a BS according to an embodiment of the present disclosure. The method 500 includes: configuring a list of transmit (Tx) beam candidate Identifications (IDs) to a User Equipment (UE), block 510; and block 520, indicating one of the Tx beam candidate IDs to the UE for each PUSCH transmission.

In some embodiments, the method further comprises requesting the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs. In some embodiments, the method further comprises requesting the UE to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs. In some embodiments, one of the Tx beam candidate IDs is indicated to the UE for each PUSCH transmission by one of higher layer signaling and physical layer signaling. In some embodiments, the higher layer signaling comprises medium access control element (MAC CE) messages and the physical layer signaling comprises Downlink Control Information (DCI).

In some embodiments, each Tx beam candidate ID 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 may derive a spatial domain transmit filter from the RS ID, CORESET ID, or PUCCH resource ID associated with the Tx beam candidate ID 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 spatial domain transmit filter information for each PUSCH transmission includes deriving a Tx beam for each PUSCH transmission from a Reference Signal (RS) ID, a control resource set (CORESET) ID, or a physical uplink shared channel (PUCCH) resource ID.

In some embodiments, deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs. In some embodiments, the method further comprises requesting the UE to calculate the pathloss using the spatial domain transmit filter information when calculating the uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

In some embodiments, the method further comprises requesting the UE to apply an uplink Tx candidate configuration for each PUSCH transmission of the fallback PUSCH. In some embodiments, the uplink Tx candidate configuration conforms to a predefined rule or a predefined rule. In some embodiments, the uplink Tx candidate configuration corresponds to the lowest Tx beam candidate ID among the Tx beam candidate IDs. In some embodiments, fallback PUSCH is scheduled with DCI format 0_0.

In some embodiments, a PUSCH transmission method is proposed. In some embodiments of the present disclosure, a "beam" may correspond to an RS resource, which may be a channel state information reference signal (CSI-RS) resource, an SRS resource, an SS/PBCH block, or any other type of RS.

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

In one approach, the UE may be configured with a list of M uplink Tx candidate configurations via higher layer parameters. An example of the uplink Tx candidate configuration may be referred to as: spatial _ info, UL _ TCI _ state (where TCI may be a transmission configuration indication), UTCI _ state, UL TCI _ state, and Tx beam candidate ID. The UE is configured with these M uplink Tx candidate configurations to transmit PUSCH according to a detected PDCCH with DCI intended for the UE, or to transmit PUSCH semi-statically configured to operate upon reception of higher layer parameters configuring transmission of PUSCH. Each uplink Tx candidate configuration contains parameters for configuring spatial relationship information between one or more RS resources or other channels and the antenna ports of the PUSCH and also the antenna ports of the DM-RS of the PUSCH. One uplink Tx candidate configuration may contain one or more of the following configuration parameters: CSI-RS resource identification, SS/PBCH block identification and SRS resource identification; a CORESET identifier, a PUCCH resource identifier, a serving cell ID, an ID of a serving DL BWP of a CSI-RS resource, an SS/PBCH block or an ID of a CORESET and an UL BWP of an SRS resource or a PUCCH resource.

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

In some embodiments, a bit field in DCI scheduling PUSCH transmissions may be used to indicate one of those configured uplink Tx candidate configurations. For example, bit field A0 in DCI scheduling PUSCH transmissions may be used to indicate one of those configured uplink Tx candidate configurations. The gNB may send an activation command if the number of uplink Tx candidate configurations configured in the higher layer signaling is above a certain value(e.g., MAC CE messages) to activate and will be at most N ₁ The uplink Tx candidate configurations are mapped to code points of bit field A0 in DCI scheduling PUSCH transmission.

In one method of an embodiment, a UE may receive a first DCI scheduling a PUSCH transmission, and a 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 may be requested to apply a spatial domain transmit filter on the PUSCH transmission corresponding to a reference signal resource of quasi co-location (QCL) type D (spatial Rx parameter) configured as CORESET identified by the CORESET ID configured in the uplink Tx candidate configuration indicated by the codepoint of bit field A0 in the first DCI. This approach may provide simplified multi-beam operation, where uplink PUSCH transmissions follow the downlink control channel on beam selection.

In one method of an embodiment, a UE may receive a first DCI scheduling a PUSCH transmission, and a 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 may be requested to apply a spatial domain transmit filter on the PUSCH transmission corresponding to the reference signal resource configured as the spatial relationship 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. The method of this embodiment may provide simplified multi-beam operation, where uplink PUSCH transmissions follow the uplink control channel on beam selection.

In one method of an embodiment, a UE may receive a first DCI scheduling a PUSCH transmission, and a code point of bit field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains an ID of one CSI-RS resource or one SS/PBCH block, the UE may be requested to apply a spatial domain transmit filter on the PUSCH transmission, which corresponds to a spatial domain receive filter for receiving 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, rank information of PUSCH transmission (i.e., the number of layers in PUSCH transmission) may also be indicated to the UE. In this case, the UE may 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, information of the transmission precoder(s) used for the scheduled PUSCH transmission may also be indicated to the UE.

In one method of an embodiment, a UE may receive first DCI scheduling a PUSCH transmission, and a code point of bit field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains more than one CSI-RS resource or ID of the SS/PBCH block, the UE may be requested to apply a spatial domain transmit filter on the PUSCH transmission, which corresponds to the spatial domain receive filter used to receive the CSI-RS resource or SS/PBCH block 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 this case of the embodiment, the UE may be requested to assume that the number of layers for scheduled PUSCH transmission is equal to the number of RS IDs configured in the indicated uplink Tx candidate configuration. The UE may apply a spatial domain transmit filter on one antenna port of the PUSCH, which corresponds to a spatial domain receiver filter for receiving 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 may receive first DCI scheduling a PUSCH transmission, and a code point of bit field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains an ID of one SRS resource, the UE may be requested to apply a spatial domain transmit filter on the PUSCH transmission, which corresponds to the 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 codepoint of bit field A0 in the first DCI.

In one method of an embodiment, a UE may receive first DCI scheduling a PUSCH transmission, and a code point of bit field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration contains more than one SRS resource ID, the UE may be requested to apply a spatial domain transmit filter on the PUSCH transmission, which corresponds to the 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 codepoint of bit field A0 in the first DCI. In this case of the embodiment, the UE may be requested to assume that the number of layers for scheduled PUSCH transmission is equal to the number of RS IDs configured in the indicated uplink Tx candidate configuration. The UE may apply a spatial domain transmit filter on one antenna port of the PUSCH corresponding 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 for PUSCH is provided. In one method of the embodiment, to calculate the transmit power for a PUSCH transmission, the UE may be requested to derive a reference signal from the uplink Tx candidate configuration indicated for the PUSCH transmission, and then use the reference signal to calculate the pathloss used in calculating the transmit power for the PUSCH transmission.

In one example, the UE may receive a first DCI scheduling 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 an ID of one CSI-RS resource or one SS/PBCH block, the UE may be requested to calculate the path loss using the CSI-RS resource or the SS/PBCH block contained in the indicated uplink Tx candidate configuration as a reference signal to calculate the transmit power of the PUSCH transmission.

In one example, the UE may receive a first DCI scheduling a PUSCH transmission, and a code point of bit field A0 in the first DCI indicates one uplink Tx candidate configuration. If the indicated uplink Tx candidate configuration includes an ID of CORESET, the UE may be requested to calculate a path loss using the RS ID of the QCL configuration of CORESET included in the configured indicated uplink Tx candidate configuration as a reference signal to calculate a transmit power of the PUSCH transmission.

In one example, the UE may receive a first DCI scheduling 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 a PUCCH resource ID, the UE may be requested to calculate a path loss using an RS ID configured as spatial relationship information of the PUCCH resource contained in the indicated uplink Tx candidate configuration as a reference signal to calculate a transmission power of the PUSCH transmission.

In one example, the UE may receive a first DCI scheduling 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 an SRS resource ID, the UE may be requested to calculate the pathloss using the RS ID of the pathloss reference signal configured to the indicated SRS resource to calculate the transmit power of the PUSCH transmission.

In some embodiments of the present disclosure, fallback PUSCH is provided. For fallback PUSCH (e.g., PUSCH scheduled with DCI format 0 _0), the UE may be requested to apply one specific uplink Tx candidate configuration on the PUSCH transmission as a predefined rule or a predefined rule. In one example, the UE may be requested to apply the uplink Tx candidate configuration with the lowest index on the transmission of the fallback PUSCH.

In one example, the UE receives an activation command (e.g., MAC CE) for N ₁ The uplink Tx candidate configuration is mapped to the code point of DCI bit field A0, and N is ₁ The plurality of uplink Tx candidate configurations are selected from the M uplink Tx candidate configurations configured by the higher layer parameter. For transmission on fallback PUSCH, the UE may be requested to apply the N indicated by the activate command ₁ One specific one of the uplink Tx candidate configurations as predefined, e.g. that N ₁ The first or last of the uplink Tx candidate configurations. The method of an embodiment may eliminate the dependency of fallback PUSCH on PUCCH for transmitting beam information. Thus, fallback PUSCH may be implemented in any serving cell, and the benefits from coverage enhancement of fallback PUSCH may be applied to any serving cell.

In some embodiments of the present disclosure, another method for Uplink (UL) Transmission Configuration Indication (TCI) is provided. In one embodiment, the list of M uplink Tx candidate configurations may be configured for the UE by higher layer parameters. The uplink Tx candidate configuration may contain one or more RS IDs or CORESET IDs or PUCCH resource IDs to provide the following information for transmission of PUSCH. First PUSCH transmission information: the filter information may be transmitted in a spatial domain applied to antenna ports of a PUSCH and DM-RSs associated with a PUSCH transmission. Second PUSCH transmission information: reference signal resource information that provides reference for the uplink precoder(s) indicated by the uplink PUSCH transmission is provided for the gNB.

In one example, the uplink Tx candidate configuration includes: an uplink Tx candidate configuration ID, an ID of an SRS resource for providing the first PUSCH transmission information and the second PUSCH transmission. In one example, the uplink Tx candidate configuration includes: an uplink Tx candidate configuration ID, an ID of a CSI-RS resource or SS/PBCH block or SRS resource for providing first PUSCH transmission information, and an ID of an SRS resource for providing second PUSCH transmission information.

In one example, the uplink Tx candidate configuration includes: an uplink Tx candidate configuration ID, an ID of a CORESET or PUCCH resource for providing the first PUSCH transmission information, and an ID of an SRS resource for providing the second PUSCH transmission information.

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

According to some embodiments of the present disclosure, a PUSCH transmission method is proposed. The gNB configures the UE with a list of Tx beam candidate IDs, and each Tx beam candidate ID is associated with one or more Reference Signal (RS) IDs or CORESET (control resource set) IDs or PUCCH resource IDs. For each PUSCH transmission, the gNB indicates (e.g., in DCI) one Tx beam candidate ID to the UE. The UE derives spatial domain transmit filter information for the scheduled PUSCH and also calculates the uplink transmit power parameter for this PUSCH transmission accordingly. In the current NR specification, tx beam information for PUSCH transmission is implicitly signaled by one SRS resource configured in an SRS set specifically configured for PUSCH transmission. Current methods impose significant limitations on system implementation and operation. For example, according to current methods, the gNB would have to configure those dedicated SRS resources for PUSCH, which is unnecessary in some cases, and in order to change the Tx beam of PUSCH, the gNB would have to trigger the transmission of SRS resources dedicated to PUSCH transmission and SRS resources configured for uplink beam management.

Furthermore, in some embodiments, a new method for fallback Tx beam indication of PUSCH (i.e. PUSCH scheduled with DCI format 0_0) is also proposed in the present disclosure. The fallback PUSCH may apply a Tx beam corresponding to the lowest Tx beam candidate ID configured for PUSCH transmission. In the current design, the Tx beam of the fallback PUSCH is associated with the PUCCH channel, and the fallback PUSCH transmission may follow the Tx beam used by a particular PUCCH. The consequence of this approach is that the gbb cannot schedule the fallback PUSCH in the SCell without PUCCH configured and thus the coverage enhancement gain of the fallback PUSCH cannot benefit the SCell.

In some embodiments of the present disclosure, physical Uplink Shared Channel (PUSCH) transmission methods and apparatus can provide at least one of the following advantages, including: directly configuring and updating a transmit (Tx) beam for Physical Uplink Shared Channel (PUSCH) transmission; reducing signaling overhead and delay of PUSCH beam update and handover; flexibly using any type of reference signal and/or physical channel as a Tx beam reference for PUSCH transmission; and enabling a next generation base station (gNB) to schedule a fallback PUSCH in any second cell (SCell) such that the SCell may benefit from the performance gain that provides coverage enhancement.

According to some embodiments of the present disclosure, the system may directly configure and update the Tx beam for PUSCH transmission. Signaling overhead and delay for PUSCH beam updates and handovers are reduced. Furthermore, by using the Tx candidate configuration proposed by the present invention, the system can flexibly use any type of reference signal and/or physical channel as the Tx beam reference for PUSCH transmission. For example, in a simple deployment, the system may use the downlink channel as a reference for PUSCH, so that a "single beam" system may be implemented. In some embodiments of the present disclosure, with respect to fallback PUSCH, methods in some embodiments of the present disclosure enable the gNB to schedule the fallback PUSCH in any SCell such that coverage enhanced performance gains may benefit the SCell. In a deployment scenario where the SCell is in FR2, the coverage distance in SCell may be a limiting factor for system performance. Some embodiments of the present disclosure are a combination of techniques/processes that may be employed in 3GPP specifications to create a final product. Some embodiments of the disclosure are used as follows: 5G-NR chipset vendors, V2X communication system developers, car manufacturers including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc., drones (unmanned aerial vehicles), smart phone manufacturers, communication devices for public safety, AR/VR device manufacturers (e.g. for gaming, conference/seminar, educational purposes). Some embodiments of the present disclosure propose a technical mechanism.

Fig. 6 is a block diagram of an example system 700 for wireless communication in accordance with an embodiment of the present disclosure. The embodiments described herein may be implemented in a system using any suitably configured hardware and/or software. Fig. 6 shows a system 700 that includes Radio Frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory/storage 740, display 750, camera 760, sensors 770, and input/output (I/O) interface 780, coupled to one another at least as shown.

Application circuitry 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general purpose processors and special purpose processors, such as a graphics processor and an application processor. The processor 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 to be implemented that run on the system.

The baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry may handle various radio control functions that enable communication with one or more radio networks through the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency translation, and the like. In some embodiments, the baseband circuitry may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other Wireless Metropolitan Area Networks (WMAN), wireless Local Area Networks (WLAN), wireless Personal Area Networks (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, baseband circuitry 720 may include circuitry for operating with signals that are not strictly considered to be at baseband frequencies. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency that is between the baseband frequency and the radio frequency.

The RF circuitry 710 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. In various embodiments, radio frequency circuitry 710 may include circuitry for operating with signals that are not strictly considered to be at radio frequencies. For example, in some embodiments, the RF circuitry may include circuitry for operating with signals having an intermediate frequency between baseband and radio frequencies.

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, baseband circuitry, and/or application circuitry. As used herein, "circuitry" may refer to, be part of, or include the following: an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory that executes one or more software or firmware programs (shared, dedicated, or group), 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, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, application circuitry, and/or memory/storage devices may be implemented together in a system on a chip (SOC).

Memory/storage 740 may be used to load and store data and/or instructions, for example, for a system. The memory/storage of 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, I/O interface 780 may include one or more user interfaces designed to enable a user to interact with the system, and/or peripheral component interfaces designed to enable peripheral components to interact with the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. The 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 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 gyroscope 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, such as Global Positioning System (GPS) satellites. In various embodiments, display device 750 may include displays, such as liquid crystal displays and touch screen displays. In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a notebook computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, and the like. In various embodiments, the system may have more or fewer components, and/or a different architecture. Where appropriate, the 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.

One of ordinary skill in the art would understand that each of the units, algorithms, and steps described and disclosed in the embodiments of the present disclosure are implemented using electronic hardware or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the application and design requirements of the solution. Skilled artisans may implement the functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. A person skilled in the art will understand that since the working processes of the above-described systems, devices and units are substantially the same, he/she may refer to the working processes of the systems, devices and units in the above-described embodiments. For ease of description and simplicity, these operations will not be described in detail.

It should be understood that the systems, devices, and methods disclosed in the embodiments of the present disclosure may be implemented in other ways. The above embodiments are merely exemplary. The partitioning of cells is based solely on logical functions, while other partitions exist in the implementation. Multiple units or components may be combined or integrated into another system. It is also possible to omit or skip certain features. In another aspect, the interconnections, direct couplings, or communicative couplings shown or discussed are operated indirectly or communicatively through some port, device, or element, whether electrically, mechanically, or otherwise.

The elements of the separating member as an explanatory means may or may not be physically separated. The unit for displaying may or may not be a physical unit, i.e. located at one place or distributed over a plurality of network units. Depending on the purpose of the embodiment, some or all of the units are used. Furthermore, each of the functional units in each embodiment may be integrated in one processing unit, physically separated, or integrated in one processing unit having two or more units.

If the software functional unit is implemented, used, or sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical solutions proposed by the present disclosure can be implemented in the form of a software product, either fundamentally or partially. Alternatively, a part of the technical solution that is advantageous to the conventional technology may be implemented in the form of a software product. A software product in a computer is stored in a storage medium and includes a plurality of instructions for a computing device, such as a personal computer, server, or network device, to perform all or some of the steps disclosed by embodiments of the present disclosure. The storage medium includes a USB disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a floppy disk, or other kind of medium capable of storing program code.

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

Claims

1. A method for transmitting a Physical Uplink Shared Channel (PUSCH) of User Equipment (UE) comprises the following steps:

configuring, by a base station BS, a list of transmit Tx beam candidate identification IDs;

indicating, by the BS, one of the Tx beam candidate IDs for each PUSCH transmission; and

applying an uplink Tx candidate configuration for each PUSCH transmission of a fallback PUSCH, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.

2. The method of claim 1, further comprising deriving spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

3. The method of claim 2, further comprising calculating an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

4. The method according to any of claims 1-3, wherein one of the Tx beam candidate IDs is indicated by the BS for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

5. The method according to claim 4, wherein the higher layer signaling comprises a media Access control element, MAC CE, message and the physical layer signaling comprises Downlink control information, DCI.

6. The method of claim 2 or 3, 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.

7. The method of claim 6, in which 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.

8. The method of claim 6, 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.

9. The method of claim 6, 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 from one of the indicated Tx beam candidate IDs.

10. The method of claim 3, further comprising, in calculating an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs, calculating a pathloss using the spatial domain transmit filter information.

11. The method of any one of claims 1-3, wherein the fallback PUSCH is scheduled by DCI format 0_0.

12. A User Equipment (UE) for Physical Uplink Shared Channel (PUSCH) transmission, comprising:

a memory;

a transceiver; and

a processor coupled with the memory and the transceiver;

wherein the processor is configured to:

configuring, by a base station BS, a list of transmit Tx beam candidate identities ID;

13. The UE of claim 12, wherein the processor is configured to derive spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

14. The UE of claim 13 wherein the processor is configured to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

15. The UE of any of claims 12 to 14, wherein one of the Tx beam candidate IDs is indicated by the BS for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

16. The UE according to claim 15, characterized in that the higher layer signaling comprises a medium access control element, MAC CE, message and the physical layer signaling comprises downlink control information, DCI.

17. The UE of claim 13 or 14, 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.

18. The UE of claim 17, 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.

19. The UE of claim 17, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission based on a reference signal, RS ID, a control resource set, CORESET, ID, or a physical uplink control channel, PUCCH, resource ID.

20. The UE of claim 17, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

21. The UE of claim 14, wherein the processor is configured to use the spatial domain transmit filter information to calculate a pathloss when calculating an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

22. The UE of any of claims 12-14, wherein the fallback PUSCH is scheduled with DCI format 0_0.

23. A method for transmitting a Physical Uplink Shared Channel (PUSCH) of a Base Station (BS) comprises the following steps:

configuring a list of transmit Tx beam candidate Identities (IDs) to a User Equipment (UE);

indicating one of the Tx beam candidate IDs to the UE for each PUSCH transmission; and

requesting the UE to apply an uplink Tx candidate configuration for each PUSCH transmission of a fallback PUSCH, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID of the Tx beam candidate IDs.

24. The method of claim 23 further comprising requesting the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

25. The method of claim 24 further comprising requesting the UE to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

26. The method according to any of claims 23-25, wherein one of the Tx beam candidate IDs is indicated to the UE for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

27. The method of claim 26, wherein the higher layer signaling comprises a medium access control element (MAC CE) message and wherein the physical layer signaling comprises Downlink Control Information (DCI).

28. The method according to claim 24 or 25, 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.

29. The method of claim 28, 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.

30. The method of claim 28, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission based on a reference signal, RS ID, a control resource set, CORESET, ID, or a physical uplink control channel, PUCCH, resource ID.

31. The method of claim 28, wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

32. The method of claim 25, further comprising requesting the UE to use the spatial domain transmit filter information to calculate a pathloss when calculating an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

33. The method of any of claims 23-25, wherein the fallback PUSCH is scheduled with DCI format 0_0.

34. A Base Station (BS) for Physical Uplink Shared Channel (PUSCH) transmission comprises:

a memory;

a transceiver; and

a processor coupled with the memory and the transceiver;

wherein the processor is configured to:

configuring a list of Tx beam candidate identification IDs to a user equipment UE;

35. The BS of claim 34, wherein the processor is configured to request the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

36. The BS of claim 35, wherein the processor is configured to request the UE to calculate uplink Tx power parameters for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

37. The BS of any one of claims 34-36, wherein one of the Tx beam candidate IDs is indicated to the UE for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

38. The BS of claim 37, wherein the higher layer signaling comprises a medium access control element, MAC CE, message and wherein the physical layer signaling comprises downlink control information, DCI.

39. The BS of claim 35 or 36, 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.

40. The BS of claim 39, 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.

41. The BS of claim 39, wherein deriving the spatial-domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission based on a reference signal (RS ID), a control resource set (CORESET ID), or a Physical Uplink Control Channel (PUCCH) resource ID.

42. The BS of claim 39, 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 from one of the indicated Tx beam candidate IDs.

43. The BS of claim 36, wherein the processor is configured to request the UE to use the spatial domain transmit filter information to calculate pathloss when calculating uplink Tx power parameters for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

44. The BS of any one of claims 34-36, wherein the fallback PUSCH is scheduled with DCI format 0 _0.

45. A method for transmitting a Physical Uplink Shared Channel (PUSCH) of User Equipment (UE) comprises the following steps:

configuring, by a base station BS, an uplink Tx candidate configuration;

performing PUSCH transmission according to the uplink Tx candidate configuration; and

46. The method of claim 45, wherein the uplink Tx candidate configuration comprises at least one of:

spatial relationship information;

an uplink transmission configuration indication; or

The Tx beam candidate identification ID.

47. The method of claim 45 or 46, further comprising indicating, by the BS, one of the Tx beam candidate IDs for each PUSCH transmission.

48. The method according to claim 45 or 46, wherein the PUSCH transmission is according to a Physical Downlink Control Channel (PDCCH) with Downlink Control Information (DCI) or is semi-statically configured.

49. The method of claim 45 or 46, further comprising deriving spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

50. The method of claim 49 further comprising calculating an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

51. The method according to claim 45 or 46, wherein one of the Tx beam candidate IDs is indicated by the BS for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

52. The method of claim 51, wherein the higher layer signaling comprises a media Access control element (MAC CE) message and wherein the physical layer signaling comprises Downlink Control Information (DCI).

53. The method of claim 46, 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.

54. The method of claim 53, 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.

55. The method of claim 53 or 54, wherein deriving 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.

56. The method of claim 53 or 54, wherein deriving spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

57. The method of claim 50 further comprising using the spatial domain transmit filter information to calculate pathloss when calculating uplink Tx power parameters for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

58. The method of claim 45 or 46, wherein the fallback PUSCH is scheduled by DCI format 0_0.

59. A User Equipment (UE) for Physical Uplink Shared Channel (PUSCH) transmission, comprising:

a memory;

a transceiver; and

a processor coupled with the memory and the transceiver;

wherein the processor is configured to:

configuring, by a base station BS, an uplink transmission Tx candidate configuration;

carrying out PUSCH transmission according to the uplink Tx candidate configuration; and

applying an uplink Tx candidate configuration for each PUSCH transmission of a fallback PUSCH, wherein the uplink Tx candidate configuration corresponds to a lowest Tx beam candidate ID among Tx beam candidate IDs.

60. The UE of claim 59, wherein the uplink Tx candidate configuration comprises at least one of:

spatial relationship information;

an uplink transmission configuration indication; or

The Tx beam candidate identification ID.

61. The UE of claim 59 or 60, wherein the processor is configured to indicate one of the Tx beam candidate IDs by the BS for each PUSCH transmission.

62. The UE according to claim 59 or 60, wherein the PUSCH transmission is according to a physical downlink control channel, PDCCH, with downlink control information, DCI, or is semi-statically configured.

63. The UE of claim 59 or 60, wherein the processor is configured to derive spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

64. The UE of claim 63 wherein the processor is configured to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

65. The UE of claim 59 or 60, wherein one of the Tx beam candidate IDs is indicated by the BS for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

66. The UE of claim 65, wherein the higher layer signaling comprises a media Access control element (MAC CE) message and wherein the physical layer signaling comprises Downlink Control Information (DCI).

67. The UE of claim 60, 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.

68. The UE of claim 67, 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.

69. The UE of claim 67 or 68, wherein deriving spatial domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission from a reference signal, RS ID, a control resource set, CORESET, ID, or a physical uplink control channel, PUCCH, resource ID.

70. The UE of claim 67 or 68, wherein deriving spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

71. The UE of claim 64, wherein the processor is configured to use the spatial domain transmit filter information to calculate a pathloss when calculating an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

72. The UE of claim 59 or 60, wherein the fallback PUSCH is scheduled by DCI format 0_0.

73. A method for transmitting a Physical Uplink Shared Channel (PUSCH) of a Base Station (BS) comprises the following steps:

configuring uplink transmission Tx candidate configuration to User Equipment (UE);

indicating one of the uplink Tx candidate configurations to the UE for each PUSCH transmission; and

74. The method of claim 73, wherein the uplink Tx candidate configuration comprises at least one of:

spatial relationship information;

an uplink transmission configuration indication; or

The Tx beam candidate identification ID.

75. The method of claim 73 or 74, further comprising indicating one of the Tx beam candidate IDs to the UE for each PUSCH transmission.

76. The method according to claim 73 or 74, wherein the PUSCH transmission is according to a Physical Downlink Control Channel (PDCCH) with Downlink Control Information (DCI) or is semi-statically configured.

77. The method of claim 73 or 74, further comprising requesting the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

78. The method of claim 77 further comprising requesting the UE to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

79. The method according to claim 73 or 74, wherein one of the Tx beam candidate IDs is indicated to the UE for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

80. The method of claim 79, wherein the higher layer signaling comprises a media access control element (MAC CE) message and the physical layer signaling comprises Downlink Control Information (DCI).

81. The method of claim 77, wherein each Tx beam candidate ID is associated with a reference signal (RS ID), a control resource set (CORESET ID), or a Physical Uplink Control Channel (PUCCH) resource ID.

82. The method of claim 81, 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.

83. The method of claim 81 or 82, 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.

84. The method of claim 81 or 82 wherein deriving the spatial domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

85. The method of claim 78, further comprising requesting the UE to use the spatial domain transmit filter information to calculate a pathloss when calculating uplink Tx power parameters for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

86. The method of claim 73 or 74, wherein the fallback PUSCH is scheduled via DCI format 0_0.

87. A Base Station (BS) for Physical Uplink Shared Channel (PUSCH) transmission comprises:

a memory;

a transceiver; and

a processor coupled with the memory and the transceiver;

wherein the processor is configured to:

88. The BS of claim 87, wherein the uplink Tx candidate configuration comprises at least one of:

spatial relationship information;

an uplink transmission configuration indication; or

The Tx beam candidate identification ID.

89. The BS of claim 87 or 88, wherein the PUSCH transmission is according to a physical downlink control channel, PDCCH, with downlink control information, DCI, or is semi-statically configured.

90. The BS of claim 87 or 88, wherein the processor is configured to request the UE to derive spatial domain transmit filter information for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

91. The BS of claim 90, wherein the processor is configured to request the UE to calculate an uplink Tx power parameter for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

92. The BS of claim 87 or 88, wherein one of the Tx beam candidate IDs is indicated to the UE for each PUSCH transmission by one of higher layer signaling and physical layer signaling.

93. The BS of claim 92, wherein the higher layer signaling comprises a medium access control element, MAC CE, message and wherein the physical layer signaling comprises downlink control information, DCI.

94. The BS of claim 88, 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.

95. The BS of claim 94, wherein the RS ID comprises a channel state information reference signal, CSI-RS, resource, sounding reference signal, SRS, resource, or synchronization signal/physical broadcast channel, SS/PBCH, block.

96. The BS of claim 94 or 95, wherein deriving spatial-domain transmit filter information for each PUSCH transmission comprises deriving a Tx beam for each PUSCH transmission from a reference signal, RS ID, a control resource set, CORESET, ID, or a physical uplink control channel, PUCCH, resource ID.

97. The BS of claim 94 or 95, wherein deriving spatial-domain transmit filter information for each PUSCH transmission comprises deriving at least one of Tx precoder and antenna port information from one of the indicated Tx beam candidate IDs.

98. The BS of claim 90, wherein the processor is configured to request the UE to use the spatial domain transmit filter information to calculate pathloss when calculating uplink Tx power parameters for each PUSCH transmission corresponding to one of the indicated Tx beam candidate IDs.

99. The BS of claim 87 or 88, wherein the fallback PUSCH is scheduled by DCI format 0_0.

100. A non-transitory machine-readable storage medium having instructions stored thereon, which when executed by a computer, cause the computer to perform the method of any one of claims 1-11, 23-33, 45-58, and 73-86.

101. A chip, comprising:

a processor configured to invoke and run a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any of claims 1 to 11, 23 to 33, 45 to 58 and 73 to 86.

102. A computer-readable storage medium, in which a computer program is stored, characterized in that the computer program causes a computer to execute the method according to any one of claims 1 to 11, 23 to 33, 45 to 58 and 73 to 86.