WO2023283907A1

WO2023283907A1 - Default beam and default pathloss reference rs determination

Info

Publication number: WO2023283907A1
Application number: PCT/CN2021/106642
Authority: WO
Inventors: Wei Ling; Chenxi Zhu; Bingchao LIU; Yi Zhang; Lingling Xiao
Original assignee: Lenovo (Beijing) Limited
Priority date: 2021-07-16
Filing date: 2021-07-16
Publication date: 2023-01-19

Abstract

Methods and apparatuses for determining default beam and default pathloss reference RS of PUSCH transmission with repetition in single DCI based multiple TRPs are disclosed. A method at an UE comprises receiving a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is transmitted in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as 'enable', each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; determining a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and transmitting repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS.

Description

DEFAULT BEAM AND DEFAULT PATHLOSS REFERENCE RS DETERMINATION

FIELD

The subject matter disclosed herein generally relates to wireless communications, and more particularly relates to methods and apparatuses for determining default beam and default pathloss reference RS of PUSCH transmission with repetition in single DCI based multiple TRPs.

BACKGROUND

The following abbreviations are herewith defined, at least some of which are referred to within the following description: New Radio (NR) , Very Large Scale Integration (VLSI) , Random Access Memory (RAM) , Read-Only Memory (ROM) , Erasable Programmable Read-Only Memory (EPROM or Flash Memory) , Compact Disc Read-Only Memory (CD-ROM) , Local Area Network (LAN) , Wide Area Network (WAN) , User Equipment (UE) , Evolved Node B (eNB) , Next Generation Node B (gNB) , Uplink (UL) , Downlink (DL) , Central Processing Unit (CPU) , Graphics Processing Unit (GPU) , Field Programmable Gate Array (FPGA) , Orthogonal Frequency Division Multiplexing (OFDM) , Radio Resource Control (RRC) , User Entity/Equipment (Mobile Terminal) , Transmitter (TX) , Receiver (RX) , Sounding Reference Signal (SRS) , SRS resource indicator (SRI) , Downlink control information (DCI) , Physical Uplink Shared Channel (PUSCH) , control resource set (CORESET) , band width part (BWP) , transmission configuration indication or transmission configuration indicator (TCI) , reference signal (RS) , Physical Downlink Shared Channel (PDSCH) , Media Access Control (MAC) , control element (CE) , Transmission Reference Point (TRP) , quasi co-location (QCL) , frequency range 2 (FR2) , Information Element (IE) , Physical Uplink Control Channel (PUCCH) .

In NR Release 16, when the associated SRS resource (s) indicated by SRI field in a DCI scheduling a PUSCH transmission is/are not configured with spatial relation information and pathloss reference RS, a default beam and a default pathloss reference RS are determined for the SRS resource set containing the SRS resource (s) associated with the PUSCH transmission. When CORESETs are configured in an activated BWP of a serving cell where the PUSCH transmission is performed, the default beam and the default pathloss reference RS are determined according to the TCI state of a CORESET with a lowest ID in the activated BWP of the serving cell. When CORESETs are not configured in the activated BWP of the serving cell where the PUSCH transmission is performed, the default beam and the default pathloss reference RS are determined according to the TCI state with a lowest codepoint contained in an MAC CE for PDSCH TCI state activation.

In addition, the beam for PUSCH transmission is the same as its associated SRS resource (s) ; and the default pathloss reference RS of for PUSCH transmission is the same as its associated SRS resource set. It can be seen that only one default beam and only one default pathloss reference RS are determined for PUSCH transmission.

In NR Release 17, up to 2 beams can be used for a PUSCH transmission with repetition; and up to 2 power control parameter sets are determined for the PUSCH transmission with repetition. Therefore, the default beam determination and default pathloss reference RS determination should be enhanced considering the PUSCH transmission with repetition that targets to multiple TRPs (e.g. two TRPs) .

This invention targets determination of the default beam and the default pathloss reference RS for a PUSCH transmission with repetition in single DCI based multiple TRPs.

BRIEF SUMMARY

Methods and apparatuses for determination of the default beam and the default pathloss reference RS for a PUSCH transmission in single DCI based multiple TRPs are disclosed.

In one embodiment, a method at an UE comprises receiving a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is transmitted in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; determining a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and transmitting repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS. The method may further comprise determining a first default beam for any SRS resource in the first SRS resource set and a second default beam for any SRS resource in the second SRS resource set, wherein, the repetition (s) of the PUSCH transmission associated with the first SRS resource set are transmitted according to the first default beam and the first default pathloss reference RS, and the repetition (s) of the PUSCH transmission associated with the second SRS resource set are transmitted according to the second default beam and the second default pathloss reference RS. When CORESETs are configured in the BWP of the cell and two CORESET group indices which are not two CORESETPoolIndex values are configured for the CORESETs and each of the CORESETs is activated or configured with one transmission configuration indicator (TCI) state, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to TCI states of two CORESETs; when CORESETs are configured in the BWP of the cell and at least one CORESET is activated with two TCI states and CORESETPoolIndex values are not configured, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to the two TCI states of one of the at least one CORESET; and when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in a MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to two TCI states pointed to by one of the at least one codepoint.

In one embodiment, when CORESETs are configured and two CORESET group indices are configured for the CORESETs and each of the CORESETs is activated or configured with one TCI state, the first default beam is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a first CORESET group index, and the second default beam is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a second CORESET group index; and the first default pathloss reference RS is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a first CORESET group index, and the second default pathloss reference RS is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a second CORESET group index.

In another embodiment, when CORESETs are configured and at least one CORESET is activated with two TCI states, the first default beam is the QCL-TypeD RS of a first TCI state of a CORESET with a lowest index of the CORESETs activated with two TCI states, and the second default beam is the QCL-TypeD RS of a second TCI state of the CORESET with the lowest index of the CORESETs activated with two TCI states; and the first default pathloss reference RS is the QCL-TypeD RS of a first TCI state of a CORESET with a lowest index of the CORESETs activated with two TCI states, and the second default pathloss reference RS is the QCL-TypeD RS of a second TCI state of the CORESET with the lowest index of the CORESETs activated with two TCI states.

In still another embodiment, when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in the MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam is the QCL-TypeD RS of a first TCI state contained in a codepoint with a lowest index of the at least one codepoint, and the second default beam is the QCL-TypeD RS of a second TCI state contained in the codepoint with the lowest index of the at least one codepoint; and the first default pathloss reference RS is the QCL-TypeD RS of a first TCI state contained in a codepoint with a lowest index of the at least one codepoint, and the second default pathloss reference RS is the QCL-TypeD RS of a second TCI state contained in the codepoint with the lowest index of the at least one codepoint.

In some embodiment, the single/multiple beam transmission indication is received in a DCI if the PUSCH transmission is scheduled or activated by the DCI, and is received in a RRC configuration if the PUSCH transmission is a configured grant Type 1 PUSCH transmission. In some embodiment, the method further comprise receiving a beam mapping pattern, and each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on the single/multiple beam transmission indication and the beam mapping pattern.

In one embodiment, an UE comprises a receiver that receives a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is transmitted in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; a processor that determines a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and a transmitter that transmits repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and transmits repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS.

In another embodiment, a method at a base unit comprises transmitting a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is received in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; determining a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and receiving repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS. The method may further comprise determining a first default beam for any SRS resource in the first SRS resource set and a second default beam for any SRS resource in the second SRS resource set, wherein, the repetition (s) of the PUSCH transmission associated with the first SRS resource set are received according to the first default beam and the first default pathloss reference RS, and the repetition (s) of the PUSCH transmission associated with the second SRS resource set are received according to the second default beam and the second default pathloss reference RS. When CORESETs are configured in the BWP of the cell and two CORESET group indices which are not two CORESETPoolIndex values are configured for the CORESETs and each of the CORESETs is activated or configured with one transmission configuration indicator (TCI) state, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to TCI states of two CORESETs; when CORESETs are configured in the BWP of the cell and at least one CORESET is activated with two TCI states and CORESETPoolIndex values are not configured, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to the two TCI states of one of the at least one CORESET; and when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in a MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to two TCI states pointed to by one of the at least one codepoint.

In some embodiment, the single/multiple beam transmission indication is transmitted in a DCI if the PUSCH transmission is scheduled or activated by the DCI, and is transmitted in a RRC configuration if the PUSCH transmission is a configured grant Type 1 PUSCH transmission. In some embodiment, the method may further comprise transmitting a beam mapping pattern, and each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on the single/multiple beam transmission indication and the beam mapping pattern.

In yet another embodiment, a base unit comprises a transmitter that transmits a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is received in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; a processor that determines a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and a receiver that receives repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and receives repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments, and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

Figure 1 illustrates an example of a first embodiment;

Figure 2 illustrates an example of a second embodiment;

Figure 3 illustrates an example of a third embodiment;

Figure 4 is a schematic flow chart diagram illustrating an embodiment of a method;

Figure 5 is a schematic flow chart diagram illustrating a further embodiment of a method; and

Figure 6 is a schematic block diagram illustrating apparatuses according to one embodiment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art that certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit” , “module” or “system” . Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” . The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

Certain functional units described in this specification may be labeled as “modules” , in order to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM) , read-only memory (ROM) , erasable programmable read-only memory (EPROM or Flash Memory) , portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .

Reference throughout this specification to “one embodiment” , “an embodiment” , or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment” , “in an embodiment” , and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including” , “comprising” , “having” , and variations thereof mean “including but are not limited to” , unless otherwise expressly specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, otherwise unless expressly specified. The terms “a” , “an” , and “the” also refer to “one or more” unless otherwise expressly specified.

Furthermore, described features, structures, or characteristics of various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid any obscuring of aspects of an embodiment.

Aspects of different embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .

It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may substantially be executed concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures.

Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each Figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

In NR Release 17, two SRS resource sets are configured for a PUSCH transmission with repetition targeting two TRPs in an activated BWP of a serving cell, where each of the two SRS resource set is associated with a different one TRP of the two TRPs. Both SRS resource sets are configured with usage as either ‘codebook’ or ‘non-codebook’ . In the following description, all SRS resource sets are configured with usage as either ‘codebook’ or ‘non-codebook’ , unless explicitly identified.

The default beam of a PUSCH transmission is the same as the default beam of the associated SRS resource (s) of an associated SRS resource set indicated by the SRI field in the DCI scheduling the PUSCH transmission. It is assumed that all SRS resource (s) contained in a SRS resource set have the same default beam. So, the default beam of the associated SRS resource (s) of the associated SRS resource set is the same as the default beam of the associated SRS resource set. The default pathloss reference RS of the PUSCH transmission is the same as the default pathloss reference RS of its associated SRS resource set. Therefore, when the UE is configured with enableDefaultBeamPlForSRS which is set as ‘enable’ (i.e. the UE is enabled to have a default beam and a default pathloss reference RS for SRS resources (or for SRS resource set) ) , the default beam and the default pathloss reference RS of the associated SRS resource set to the PUSCH transmission can be first determined. Accordingly, based on at least the single/multiple beam indication (which may be contained in a DCI field or in a RRC configuration) and optionally a configured beam mapping pattern, the default beam and the default pathloss reference RS of the PUSCH transmission can be determined according to the default beam and the default pathloss reference RS of one of the SRS resource sets associated with the PUSCH transmission.

According to a first embodiment, the default beam and the default pathloss reference RS of the PUSCH transmission are determined in a first scenario in which (1) CORESETs are configured in an activated BWP of a serving cell where the PUSCH transmission is performed; (2) two CORESET group indices are configured for the CORESETs to group the CORESETs into two groups (i.e. a first group of CORESETs each of which is configured with a first CORESET group index (e.g. a lower index, or 0) and a second group of CORESETs each of which is configured with a second CORESET group index (e.g. a higher index, or 1) ; and (3) no CORESET is activated with more than one TCI state (which means that each CORESET is activated or configured with only one TCI state) .

In the first scenario, there are two CORESET groups. We assume that one CORESET group has a lower index (e.g. 0) and the other CORESET group has a higher index (e.g. 1) . Incidentally, the CORESET group index proposed in this invention is configured in single DCI based multiple TRPs. The CORESET group index is different from CORESETPoolIndex value that is configured in multiple DCI based multiple TRPs.

Each TCI state contains parameters for configuring a quasi co-location (QCL) relationship between one or two downlink reference signals and the DM-RS ports of the PDSCH, the DM-RS port of PDCCH or the CSI-RS port (s) of a CSI-RS resource. The quasi co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS, and qcl-Type2 for the second DL RS (if configured) . For the case of two DL RSs, the QCL types shall not be the same, regardless of whether the references are to the same DL RS or different DL RSs. The quasi co-location types corresponding to each DL RS are given by the higher layer parameter qcl-Type in QCL-Info and may take one of the following values:

‘QCL-TypeA’ : {Doppler shift, Doppler spread, average delay, delay spread}

‘QCL-TypeB’ : {Doppler shift, Doppler spread}

‘QCL-TypeC’ : {Doppler shift, average delay}

‘QCL-TypeD’ : {Spatial Rx parameter}

A QCL-TypeD RS of the TCI state can indicate a spatial relation (or beam) of a downlink signal. Similarly, a QCL-TypeD RS of the TCI state can also indicate a spatial relation (or beam) of an uplink signal.

There are two SRS resource sets, each of which is associated with one of the two TRPs. We assume that each SRS resource set has a different index. In particular, one SRS resource set has a lower index (e.g. 0) and the other SRS resource set has a higher index (e.g. 1) .

According to the first embodiment, the default beam of any SRS resource in a SRS resource set with a lower index (e.g. 0) is the QCL-TypeD RS of the TCI state of a CORESET with a lowest index in the CORESETs associated with a CORESET group with a lower index (e.g. 0) , while the default beam of any SRS resource in a SRS resource set with a higher index (e.g. 1) is the QCL-TypeD RS of the TCI state of a CORESET with a lowest index in the CORESETs associated with a CORESET group with a higher index (e.g. 1) .

Accordingly, the default pathloss reference RS of the SRS resource set can be determined as the same RS as being determined as the default beam of any SRS resource in the SRS resource set. In particular, the default pathloss reference RS of the SRS resource set with the lower index (e.g. 0) is the QCL-TypeD RS of the TCI state of the CORESET with the lowest index in the CORESETs associated with the CORESET group with the lower index (e.g. 0) , and the default pathloss reference RS of the SRS resource set with the higher index (e.g. 1) is the QCL-TypeD RS of the TCI state of the CORESET with the lowest index in the CORESETs associated with the CORESET group with the higher index (e.g. 1) .

Therefore, the spatial relation information of the SRS resource is determined according to the QCL-TypeD RS in the TCI state of the CORESET with the lowest index in the CORESETs associated with the CORESET group with the lower index if the SRS resource is in the SRS resource set with the lower index, and is determined according to the QCL-TypeD RS in the TCI state of the CORESET with the lowest index in CORESETs associated with the CORESET group with the higher index if the SRS resource is in the SRS resource set with the higher index, when the following criteria (1) to (5) are met:

(1) the higher layer parameter enableDefaultBeamPLForSRS is set to ‘enable’ , i.e. the UE is allowed to have a default beam (or default spatial relation) and a default pathloss reference RS;

(2) the higher layer parameter spatialRelationInfo for any SRS resource in the two SRS resource sets is not configured, and in addition, associatedCSI-RS is not configured for the two SRS resource sets configured with usage as ‘nonCodebook’ in FR2, i.e. the spatial relation is not explicitly configured to any SRS resource in the two SRS resource sets;

(3) the UE is not provided with pathloss reference RS for SRS resource sets and PUSCH transmissions;

(4) the UE is not configured with different values of CORESETPoolIndex in ControlResourceSets IE; and

(5) the first scenario as mentioned above.

The pathloss reference RS of the SRS resource set with a lower index is determined as the QCL-TypeD RS of the TCI state of the CORESET with the lowest index in the CORESETs associated with the CORESET group with the lower index, and the pathloss reference RS of the SRS resource set with a higher index is the QCL-TypeD RS of the TCI state of the CORESET with the lowest index in the CORESETs associated with the CORESET group with the higher index, if the above criteria (1) to (5) are met.

A PUSCH transmission (e.g. a PUSCH transmission with repetition) is associated with one of the first SRS resource set and the second SRS resource set based on at least a single/multiple beam indication. The single/multiple beam indication may be a field of the DCI that is used to schedule or activate the PUSCH transmission. The single/multiple beam indication may alternatively be transmitted in a RRC configuration if the PUSCH transmission is a configured grant Type 1 PUSCH transmission.

The single/multiple beam indication has at least three states. The first state which is ‘00’ indicates that a PUSCH transmission is associated with the first SRS resource set. The second state which is ‘01’ indicates that a PUSCH transmission is associated with the second SRS resource set. The third state which is ‘10’ indicates that a PUSCH transmission is associated with two SRS resource sets where the first SRI field and the second SRI field are associated with the first SRS resource set and the second SRS resource set respectively. There may be a fourth state which is ‘11’ indicates that a PUSCH transmission is associated with two SRS resource sets where the first SRI field and the second SRI field are associated with the second SRS resource set and the first SRS resource set respectively. The SRS resource set with a lower index is the first SRS resource set, and the other SRS resource set (e.g. the SRS resource set with a higher index) is the second SRS resource set.

The single/multiple beam indication may be configured as the first state or the second state for a PUSCH transmission whose repetition number is larger than 1. In this condition, each repetition of a PUSCH transmission is associated with one SRS resource set of the two SRS resource sets (either the first SRS resource set or the second SRS resource set) according to its indicated single/multiple beam indication being the first state or the second state.

The single/multiple beam indication may alternatively be configured as the third state or the fourth state for a PUSCH transmission whose repetition number is larger than 1. Each repetition of the PUSCH transmission is associated with one SRS resource set of the two SRS resource sets according to its indicated single/multiple beam indication and a beam mapping pattern.

There are two beam mapping patterns agreed for PUSCH transmission with repetition in NR Release 17: cyclical mapping pattern and sequential mapping pattern. For the cyclical mapping pattern, two beams are used to transmit each repetition of the PUSCH transmission cyclically. For example, if there are four (4) repetitions, the first and the third repetitions are transmitted by the first beam while the second and the fourth repetitions are transmitted by the second beam. For the sequential mapping pattern, the first and second repetitions are transmitted by the first beam while the third and fourth repetitions are transmitted by the second beam. The beam mapping pattern will repeat if the repetition number is larger than 4.

Therefore, the beam of each repetition of the PUSCH transmission is determined as the beam of the SRS resources in the associated SRS resource set based on at least the single/multiple beam indication, and in particular, based on the single/multiple beam indication, or based on the single/multiple beam indication and the beam mapping pattern. Besides, when UE is configured with enableDefaultBeamPlForSRS which is set as ‘enable’ , the pathloss reference RS of each repetition of the PUSCH transmission is also determined as the beam of the associated SRS resource set based on the single/multiple beam indication or based on the single/multiple beam indication and the beam mapping pattern.

Figure 1 illustrates an example of the first embodiment.

As shown in Figure 1, three (3) CORESETs (CORESET 0, CORESET 1 and CORESET2) are configured in the activated BWP of the serving cell. Two (2) CORESET groups (i.e. CORESET group 0 and CORESET group 1) are configured with two (2) indices (i.e. 0 and 1) . In particular, CORESET 0 and CORESET 1 are associated with CORESET group 0, and CORESET 2 is associated with CORESET group 1. TCI state 1, TCI state 2 and TCI state 3 are activated for CORESET 0, CORESET 1 and CORESET 2 respectively (i.e. each CORESET is activated or configured with only one TCI state) . The QCL-TypeD RS of each of TCI state 1, TCI state 2 and TCI state 3 is RS 1, RS 2, and RS 3, respectively. SRS resource set 0 and SRS resource set 1 are configured for PUSCH transmission with repetition.

Besides, the following criteria are met:

the UE is not provided with pathloss reference RS for the two SRS resource sets and PUSCH transmissions,

the UE is not provided with spatialRelationInfo for any SRS resource of SRS resource set 0 and SRS resource set 1,

the UE is configured with enableDefaultBeamPlForSRS which is set as ‘enable’ ,

the UE is not configured with different values of CORESETPoolIndex in ControlResourceSets IE.

For a PUSCH transmission with 4 repetitions, the single/multiple beam indication is set as ‘10’ (i.e. the first SRI field is associated with the first SRS resource set, and the second SRI field is associated with the second SRS resource set) , and a cyclical mapping pattern is configured for the PUSCH repetitions (i.e. two beams are used to transmit each repetition cyclically) .

Therefore, according to the first embodiment, the default beam of any SRS resource of SRS resource set 0 is RS 1 (i.e. QCL-TypeD RS in the TCI state (TCI state 1) of the CORESET with the lowest index (CORESET 0) in the CORESETs (CORESET 0 and CORESET 1) associated with the CORESET group with the lower index (CORESET group 0) ) ; and the default beam of any SRS resource of SRS resource set 1 is RS 3 (QCL-TypeD RS of the TCI state (TCI state 3) of the CORESET with the lowest index (CORESET 2) in the CORESETs (CORESET 2) associated with the CORESET group with the higher index (CORESET group 1) ) . Similarly, the default pathloss reference RSs of SRS resource set 0 and SRS resource set 1 are RS 1 and RS 3, respectively, according to the first embodiment. According to the configured beam mapping pattern (cyclical mapping pattern) and the single/multiple beam indication field ( ‘10’ ) , the first PUSCH repetition and the third PUSCH repetition (PUSCH repetition 0 and PUSCH repetition 2) are associated with SRS resource set 0, and the second PUSCH repetition and the fourth PUSCH repetition (PUSCH repetition 1 and PUSCH repetition 3) are associated with SRS resource set 1. Therefore, the default beam and the default pathloss reference RS of PUSCH repetitions 0 and 2 are RS 1, and the default beam and the default pathloss reference RS of PUSCH repetitions 1 and 3 are RS 3.

According to a second embodiment, the default beam and the default pathloss reference RS of the PUSCH transmission are determined in a second scenario in which (1) CORESETs are configured in the activated BWP of the serving cell where the PUSCH transmission is performed; and (2) at least one CORESET is activated with two TCI states.

According to the second embodiment, the default beam of any SRS resource in a SRS resource set with a lower index (e.g. 0) is the QCL-TypeD RS of a first TCI state of a CORESET with a lowest index in the CORESET (s) which are activated with two TCI states, and the default beam of any SRS resource in a SRS resource set with a higher index (e.g. 1) is the QCL-TypeD RS of a second TCI state of the CORESET with the lowest index in the CORESET (s) which are activated with two TCI states.

Accordingly, the default pathloss reference RS of the SRS resource set can be determined as the same RS as being determined as the default beam of any SRS resource in the SRS resource set. In particular, the default pathloss reference RS of the SRS resource set with the lower index (e.g. 0) is the QCL-TypeD RS of the first TCI state of the CORESET with the lowest index in the CORESET (s) that are activated with two TCI states, and the default pathloss reference RS of the SRS resource set with the higher index (e.g. 1) is the QCL-TypeD RS of the second TCI state of the CORESET with the lowest index in CORESET (s) that are activated with two TCI states.

Therefore, the spatial relation information of the SRS resource is determined according to the QCL-TypeD RS in the first TCI state of the CORESET with the lowest index in the CORESET (s) which are activated with two TCI states if the SRS resource is in the SRS resource set with the lower index, and is determined according to the QCL-TypeD RS in the second TCI state of the CORESET with the lowest index in the CORESET (s) which are activated with two TCI states if the SRS resource is in the SRS resource set with the higher index, when the following criteria (1) to (5) are met:

(2) the higher layer parameter spatialRelationInfo for any SRS resource in the two SRS resource sets is not configured, and in addition, associatedCSI-RS is not configured for the two SRS resource sets configured with usage as ‘nonCodebook’ in FR2, i.e. the spatial relation is not explicitly configured;

(5) the second scenario as mentioned above.

The pathloss reference RS of the SRS resource set with the lower index is the QCL-TypeD RS of the first TCI state of the CORESET with the lowest index in the CORESET (s) which are activated with two TCI states, and the pathloss reference RS of the SRS resource set with the higher index is the QCL-TypeD RS of the second TCI state of the CORESET with the lowest index in the CORESET (s) which are activated with two TCI states, if the above criteria (1) –(5) are met.

Similar to the first embodiment, the beam of each repetition of the PUSCH transmission is determined as the beam of the SRS resources in the associated SRS resource set based on at least the single/multiple beam indication, i.e. based on the single/multiple beam indication or based on the single/multiple beam indication and the beam mapping pattern. Besides, when UE is provided with enableDefaultBeamPlForSRS, the pathloss reference RS of each repetition of the PUSCH transmission is also determined as the beam of the associated SRS resource set based on at least the single/multiple beam indication, i.e. based on the single/multiple beam indication or based on the single/multiple beam indication and the beam mapping pattern.

Figure 2 illustrates an example of the second embodiment.

As shown in Figure 2, three (3) CORESETs (CORESET 0, CORESET 1 and CORESET2) are configured in the activated BWP of the serving cell. CORESET 0 is activated with two TCI states (i.e. TCI state 1 and TCI state 2) ; CORESET 1 is activated with two TCI states (i.e. TCI state 2 and TCI state 3) ; and CORESET 2 is activated with one TCI state (i.e. TCI state 3) . The QCL-TypeD RS of each of TCI state 1, TCI state 2 and TCI state 3 is RS 1, RS 2, and RS 3, respectively. SRS resource set 0 and SRS resource set 1 are configured for PUSCH transmission with repetition.

Besides, the following criteria are met:

the UE is not provided with pathloss reference RS for the two SRS resource sets and PUCCH transmissions,

For a PUSCH transmission with 4 repetitions, the single/multiple beam indication field is set as ‘10’ (i.e. the first SRI field is associated with the first SRS resource set, and the second SRI field is associated with the second SRS resource set) , and a sequential mapping pattern is configured for the repetitions of the PUSCH transmission (i.e. two beams are used to transmit each repetition sequentially) .

Therefore, according to the second embodiment, the default beam of any SRS resource of SRS resource set 0 is RS 1 (i.e. the QCL-TypeD RS of the first TCI state (TCI state 1) of the CORESET with the lowest index (CORESET 0) in the CORESET (s) which are activated with two TCI states (CORESET 0 and CORESET 1) ) ; and the default beam of any SRS resource of SRS resource set 1 is RS 2 (i.e. the QCL-TypeD RS of the second TCI state (TCI state 2) of the CORESET with the lowest index (CORESET 0) in the CORESET (s) which are activated with two TCI states (CORESET 0 and CORESET 1) ) . Similarly, the default pathloss reference RS of SRS resource set 0 and SRS resource set 1 are RS 1 and RS 2, respectively, according to the second embodiment. According to the configured beam mapping pattern (sequential mapping pattern) and the single/multiple beam indication field ( ‘10’ ) , the first PUSCH repetition and the second PUSCH repetition (PUSCH repetition 0 and PUSCH repetition 1) are associated with SRS resource set 0 and the third PUSCH repetition and the fourth PUSCH repetition (PUSCH repetition 2 and PUSCH repetition 3) are associated with SRS resource set 1. Therefore, the default beam and the default pathloss reference RS of

PUSCH repetitions

0 and 1 are RS 1, and the default beam and the default pathloss reference RS of PUSCH repetition 2 and 3 are RS 2.

According to a third embodiment, the default beam and the default pathloss reference RS of the PUSCH transmission are determined in a third scenario in which (1) CORESETs are not configured in the activated BWP of a serving cell where the PUSCH transmission is performed; and (2) at least one codepoint contained in a MAC CE for PDSCH TCI activation points to two TCI states.

According to the third embodiment, the default beam of any SRS resource in a SRS resource set with a lower index is the QCL-TypeD RS of a first TCI state pointed to by a codepoint with a lowest index in codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states, and the default beam of any SRS resource in a SRS resource set with a higher index is the QCL-TypeD RS of a second TCI state pointed to by a codepoint with a lowest index in the codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states.

Accordingly, the default pathloss reference RS of the SRS resource set can be determined as the same RS as being determined as the default beam of any SRS resource in the SRS resource set. In particular, the default pathloss reference RS of the SRS resource set with the lower index (e.g. 0) is the QCL-TypeD RS of the first TCI state pointed to by the codepoint with the lowest index in the codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states, and the default pathloss reference RS of the SRS resource set with the higher index is the QCL-TypeD RS of the second TCI state pointed to by the codepoint with the lowest index in codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states.

Therefore, the spatial relation information of the SRS resource is determined according to the QCL-TypeD RS in the first TCI state pointed to by the codepoint with the lowest index in the codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states if the SRS resource is in the SRS resource set with the lower index, and is determined according to the QCL-TypeD RS in the second TCI state pointed to by the codepoint with the lowest index in the codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states if the SRS resource is in the SRS resource set with the higher index, when the following criteria (1) to (5) are met:

(5) the third scenario as mentioned above.

The pathloss reference RS of the SRS resource set with the lower index is the QCL-TypeD RS of the first TCI state pointed to by the codepoint with the lowest index in the codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states, and the pathloss reference RS of the SRS resource set with the higher index is the QCL-TypeD RS of the second TCI state pointed to by the codepoint with the lowest index in the codepoints contained in the MAC CE for PDSCH TCI activation that point to two TCI states, if the above criteria (1) to (5) are met:

Similar to the first or the second embodiment, the beam of each repetition of the PUSCH transmission is determined as the beam of the SRS resources in the associated SRS resource set based on at least the single/multiple beam indication, i.e. based on the single/multiple beam indication or based on the single/multiple beam indication and the beam mapping pattern. Besides, when UE is configured with enableDefaultBeamPlForSRS which is set as ‘enable’ , the pathloss reference RS of each repetition of the PUSCH transmission is also determined as the beam of the associated SRS resource set based on at least the single/multiple beam indication, i.e. based on the single/multiple beam indication or based on the single/multiple beam indication and the beam mapping pattern.

Figure 3 and Table 1 illustrate an example of the third embodiment.

codepoint index	activated TCI state (s)
000	TCI state 1
001	TCI state 1, TCI state 2
010	TCI state 2
011	TCI state 2, TCI state 3
100	TCI state 3

101	TCI state 3, TCI state 4
110	TCI state 4
111	TCI state 1, TCI state 4

Table 1

As shown in Table 1, the MAC CE for PDSCH TCI activation contains eight (8) codepoints (i.e. ‘000’ , ‘001’ , ‘010’ , ‘011’ , ‘100’ , ‘101’ , ‘110’a nd ‘111’ ) . It can be seen from Table 1 that the lowest codepoint that points to two TCI states is codepoint ‘001’ that points to TCI state 1 and TCI state 2. It is assumed that the QCL-TypeD RSs of TCI state 1 and TCI state 2 are RS 1 and RS 2, respectively.

SRS resource set 0 and SRS resource set 1 are configured for the PUSCH transmission.

Besides, the following criteria are met:

the UE is not configured with any CORESET in the activated BWP of the serving cell.

For a PUSCH transmission with 4 repetitions, the single/multiple beam indication field is set as ‘01’ (i.e. the PUSCH transmission is associated with the second SRS resource set) .

Therefore, according to the third embodiment, the default beam of any SRS resource of SRS resource set 0 is RS 1 (i.e. the QCL-TypeD RS of the first TCI state (TCI state 1) pointed to by the codepoint with the lowest index (codepoint 001) in the codepoints (codepoints 001, 011, 101, and 111) contained in the MAC CE for PDSCH TCI activation that point to two TCI states) ; and the default beam of any SRS resource of SRS resource set 1 is RS 2 (i.e. the QCL-TypeD RS of the second TCI state (TCI state 2) pointed to by the codepoint with the lowest index (codepoint 001) in the codepoints (codepoints 001, 011, 101, and 111) contained in the MAC CE for PDSCH TCI activation that point to two TCI states) . Similarly, the default pathloss reference RSs of SRS resource set 0 and SRS resource set 1 are RS 1 and RS 2, respectively, according to the third embodiment. According to the single/multiple beam indication field ( ‘01’ ) , all four repetitions of the PUSCH transmission are associated with SRS resource set 1 (i.e. the second SRS resource set) . Therefore, the default beam and the default pathloss reference RS of all repetitions of the PUSCH transmission (

PUSCH repetitions

0, 1, 2 and 3) are RS 2.

Except for the scenarios 1, 2 and 3, in all other scenarios, only one default beam and only one default pathloss reference RS are determined for the first SRS resource set by using the legacy determination. In particular, when CORESETs are configured, a default beam and a default pathloss reference RS of the first SRS resource set are determined according to the TCI state of a CORESET with a lowest ID in the CORESETs in the activated BWP of a serving cell; and when CORESETs are not configured, the default beam and the default pathloss reference RS of the first SRS resource set are determined according to the TCI state of a lowest codepoint contained in the MAC CE for PDSCH TCI state activation. In addition, no matter what the single/multiple beam indication is, all repetitions of the PUSCH transmission are associated with the first SRS resource set. Therefore, a default beam and a default pathloss reference RS of all repetitions of the PUSCH transmission are the same as the default beam and the default pathloss reference RS of the associated first SRS resource set.

In some embodiments, the default beam may not have to be determined. For example, when a PUSCH transmission is configured or scheduled to be transmitted in low carrier frequency, beam is not needed to be determined since it will be transmitted omnidirectionally.

Figure 4 is a schematic flow chart diagram illustrating an embodiment of a method 400 according to the present application. In some embodiments, the method 400 is performed by an apparatus, such as a remote unit (UE) . In certain embodiments, the method 400 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 400 may include 402 receiving a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is transmitted in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; 404 determining a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and 406 transmitting repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS. The method may further comprise determining a first default beam for any SRS resource in the first SRS resource set and a second default beam for any SRS resource in the second SRS resource set, wherein, the repetition (s) of the PUSCH transmission associated with the first SRS resource set are transmitted according to the first default beam and the first default pathloss reference RS, and the repetition (s) of the PUSCH transmission associated with the second SRS resource set are transmitted according to the second default beam and the second default pathloss reference RS. When CORESETs are configured in the BWP of the cell and two CORESET group indices which are not two CORESETPoolIndex values are configured for the CORESETs and each of the CORESETs is activated or configured with one transmission configuration indicator (TCI) state, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to TCI states of two CORESETs; when CORESETs are configured in the BWP of the cell and at least one CORESET is activated with two TCI states and CORESETPoolIndex values are not configured, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to the two TCI states of one of the at least one CORESET; and when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in a MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to two TCI states pointed to by one of the at least one codepoint.

In some embodiment, the single/multiple beam transmission indication is received in a DCI if the PUSCH transmission is scheduled or activated by the DCI, and is received in a RRC configuration if the PUSCH transmission is a configured grant Type 1 PUSCH transmission.

In some embodiment, the method further comprise receiving a beam mapping pattern, and each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on the single/multiple beam transmission indication and the beam mapping pattern.

Figure 5 is a schematic flow chart diagram illustrating a further embodiment of a method 500 according to the present application. In some embodiments, the method 500 is performed by an apparatus, such as a base unit. In certain embodiments, the method 500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 500 may include 502 transmitting a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is received in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; 504 determining a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and 506 receiving repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS. The method may further comprise determining a first default beam for any SRS resource in the first SRS resource set and a second default beam for any SRS resource in the second SRS resource set, wherein, the repetition (s) of the PUSCH transmission associated with the first SRS resource set are received according to the first default beam and the first default pathloss reference RS, and the repetition (s) of the PUSCH transmission associated with the second SRS resource set are received according to the second default beam and the second default pathloss reference RS. When CORESETs are configured in the BWP of the cell and two CORESET group indices which are not two CORESETPoolIndex values are configured for the CORESETs and each of the CORESETs is activated or configured with one transmission configuration indicator (TCI) state, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to TCI states of two CORESETs; when CORESETs are configured in the BWP of the cell and at least one CORESET is activated with two TCI states and CORESETPoolIndex values are not configured, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to the two TCI states of one of the at least one CORESET; and when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in a MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to two TCI states pointed to by one of the at least one codepoint.

In some embodiment, the single/multiple beam transmission indication is transmitted in a DCI if the PUSCH transmission is scheduled or activated by the DCI, and is transmitted in a RRC configuration if the PUSCH transmission is a configured grant Type 1 PUSCH transmission.

In some embodiment, the method may further comprise transmitting a beam mapping pattern, and each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on the single/multiple beam transmission indication and the beam mapping pattern.

Referring to Figure 6, the UE (i.e. the remote unit) includes a processor, a memory, and a transceiver. The processor implements a function, a process, and/or a method which are proposed in Figure 4.

The UE comprises a receiver that receives a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is transmitted in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; a processor that determines a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and a transmitter that transmits repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and transmits repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS. The processor may further determine a first default beam for any SRS resource in the first SRS resource set and a second default beam for any SRS resource in the second SRS resource set; and the transmitter may transmit the repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default beam and the first default pathloss reference RS, and transmit the repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default beam and the second default pathloss reference RS. When CORESETs are configured in the BWP of the cell and two CORESET group indices which are not two CORESETPoolIndex values are configured for the CORESETs and each of the CORESETs is activated or configured with one transmission configuration indicator (TCI) state, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to TCI states of two CORESETs; when CORESETs are configured in the BWP of the cell and at least one CORESET is activated with two TCI states and CORESETPoolIndex values are not configured, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to the two TCI states of one of the at least one CORESET; and when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in a MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to two TCI states pointed to by one of the at least one codepoint.

In some embodiment, the receiver may further receive a beam mapping pattern, and each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on the single/multiple beam transmission indication and the beam mapping pattern.

Referring to Figure 6, the gNB (i.e. base unit) includes a processor, a memory, and a transceiver. The processors implement a function, a process, and/or a method which are proposed in Figure 5.

The base unit comprises a transmitter that transmits a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission, wherein the PUSCH transmission is received in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission, the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ , each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication; a processor that determines a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and a receiver that receives repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and receives repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS. The processor may further determine a first default beam for any SRS resource in the first SRS resource set and a second default beam for any SRS resource in the second SRS resource set; and the receiver may receive the repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default beam and the first default pathloss reference RS, and receive the repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default beam and the second default pathloss reference RS. When CORESETs are configured in the BWP of the cell and two CORESET group indices which are not two CORESETPoolIndex values are configured for the CORESETs and each of the CORESETs is activated or configured with one transmission configuration indicator (TCI) state, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to TCI states of two CORESETs; when CORESETs are configured in the BWP of the cell and at least one CORESET is activated with two TCI states and CORESETPoolIndex values are not configured, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to the two TCI states of one of the at least one CORESET; and when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in a MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to two TCI states pointed to by one of the at least one codepoint.

In some embodiment, the transmitter may further transmit a beam mapping pattern, and each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on the single/multiple beam transmission indication and the beam mapping pattern.

Layers of a radio interface protocol may be implemented by the processors. The memories are connected with the processors to store various pieces of information for driving the processors. The transceivers are connected with the processors to transmit and/or receive a radio signal. Needless to say, the transceiver may be implemented as a transmitter to transmit the radio signal and a receiver to receive the radio signal.

The memories may be positioned inside or outside the processors and connected with the processors by various well-known means.

In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.

The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , processors, controllers, micro-controllers, microprocessors, and the like.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects to be only illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

A method at an UE, comprising:

receiving a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission,

wherein the PUSCH transmission is transmitted in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission,

the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ ,

each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication;

determining a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and

transmitting repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS.
The method of claim 1, further comprising:

determining a first default beam for any SRS resource in the first SRS resource set and a second default beam for any SRS resource in the second SRS resource set,

wherein, the repetition (s) of the PUSCH transmission associated with the first SRS resource set are transmitted according to the first default beam and the first default pathloss reference RS, and the repetition (s) of the PUSCH transmission associated with the second SRS resource set are transmitted according to the second default beam and the second default pathloss reference RS.
The method of claim 2, wherein,

when CORESETs are configured in the BWP of the cell and two CORESET group indices which are not two CORESETPoolIndex values are configured for the CORESETs and each of the CORESETs is activated or configured with one transmission configuration indicator (TCI) state, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to TCI states of two CORESETs; or

when CORESETs are configured in the BWP of the cell and at least one CORESET is activated with two TCI states and CORESETPoolIndex values are not configured, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to the two TCI states of one of the at least one CORESET; or

when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in a MAC CE for PDSCH TCI state activation points to two TCI states, the first default beam, the second default beam, the first default pathloss reference RS, and the second default pathloss reference RS are determined according to two TCI states pointed to by one of the at least one codepoint.
The method of claim 3, wherein,

when CORESETs are configured and two CORESET group indices are configured for the CORESETs and each of the CORESETs is activated or configured with one TCI state,

the first default beam is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a first CORESET group index, and the second default beam is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a second CORESET group index.
The method of claim 3, wherein,

when CORESETs are configured and two CORESET group indices are configured for the CORESETs and each of the CORESETs is activated or configured with one TCI state,

the first default pathloss reference RS is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a first CORESET group index, and the second default pathloss reference RS is the QCL-TypeD RS of a TCI state of a CORESET with a lowest index of CORESETs associated with a second CORESET group index.
The method of claim 3, wherein,

when CORESETs are configured and at least one CORESET is activated with two TCI states,

the first default beam is the QCL-TypeD RS of a first TCI state of a CORESET with a lowest index of the CORESETs activated with two TCI states, and the second default beam is the QCL-TypeD RS of a second TCI state of the CORESET with the lowest index of the CORESETs activated with two TCI states.
The method of claim 3, wherein,

when CORESETs are configured and at least one CORESET is activated with two TCI states,

the first default pathloss reference RS is the QCL-TypeD RS of a first TCI state of a CORESET with a lowest index of the CORESETs activated with two TCI states, and the second default pathloss reference RS is the QCL-TypeD RS of a second TCI state of the CORESET with the lowest index of the CORESETs activated with two TCI states.
The method of claim 3, wherein,

when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in the MAC CE for PDSCH TCI state activation points to two TCI states,

the first default beam is the QCL-TypeD RS of a first TCI state contained in a codepoint with a lowest index of the at least one codepoint, and the second default beam is the QCL-TypeD RS of a second TCI state contained in the codepoint with the lowest index of the at least one codepoint.
The method of claim 3, wherein,

when CORESETs are not configured in the BWP of the cell and at least one codepoint contained in the MAC CE for PDSCH TCI state activation points to two TCI states,

the first default pathloss reference RS is the QCL-TypeD RS of a first TCI state contained in a codepoint with a lowest index of the at least one codepoint, and the second default pathloss reference RS is the QCL-TypeD RS of a second TCI state contained in the codepoint with the lowest index of the at least one codepoint.
The method of claim 1, wherein,

the single/multiple beam transmission indication is received in a DCI if the PUSCH transmission is scheduled or activated by the DCI, and

the single/multiple beam transmission indication is received in a RRC configuration if the PUSCH transmission is a configured grant Type 1 PUSCH transmission.
The method of claim 1, further comprising:

receiving a beam mapping pattern,

wherein, each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on the single/multiple beam transmission indication and the beam mapping pattern.
An UE, comprising:

a receiver that receives a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission,

wherein the PUSCH transmission is transmitted in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission,

the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ ,

each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication;

a processor that determines a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and

a transmitter that transmits repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and transmits repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS.
A method at an base unit, comprising:

transmitting a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission,

wherein the PUSCH transmission is received in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission,

the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ ,

each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication;

determining a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and

receiving repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS.
A base unit, comprising:

a transmitter that transmits a single/multiple beam transmission indication for a PUSCH transmission with repetition whose repetition number is 1 or larger than 1, and configuration information for the PUSCH transmission,

wherein the PUSCH transmission is received in a BWP of a cell where no pathloss reference RS is configured for the PUSCH transmission,

the configuration information includes a first SRS resource set and a second SRS resource set, wherein the first SRS resource set and the second SRS resource set are not configured with spatial relation information, are not configured with pathloss reference RS, and are configured with enableDefaultBeamPlForSRS set as ‘enable’ ,

each repetition of the PUSCH transmission is associated with one of the first SRS resource set and the second SRS resource set based on at least the single/multiple beam transmission indication;

a processor that determines a first default pathloss reference RS for the first SRS resource set and a second default pathloss reference RS for the second SRS resource set; and

a receiver that receives repetition (s) of the PUSCH transmission associated with the first SRS resource set according to the first default pathloss reference RS, and receives repetition (s) of the PUSCH transmission associated with the second SRS resource set according to the second default pathloss reference RS.