Method for control signaling for multi-beam pusch repeative transmission

By configuring different number of SRS resource ports and exporting uplink precoders, the indication difficulties and non-periodic SRS resource set triggering methods when enabling fullpowerMode2 in multi-beam PUSCH repetition are solved, and the transmission efficiency and consistent UE behavior is improved. sex.

CN119095180APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411462028.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2021-09-24
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In codebook-based and non-codebook-based multi-beam PUSCH repetitive transmission, the prior art has difficulties in indicating SRI and TPMI, and the triggering mode of a non-periodic SRS resource set may lead to UE behavior problems.

Method used

By configuring the UE to avoid uplink transmission mode fullpowerMode2, different number of SRS resource ports are allowed to be used, and the uplink preencoder is configured according to the instructions; for non-codebook-based transmissions, non-periodic SRS and CSI-RS are triggered Resource set to optimize PUSCH duplication.

Benefits of technology

It solves the problem of indication difficulties when enabling fullpowerMode2 and the non-periodic SRS resource set triggering method, and improves the efficiency of multi-beam PUSCH repetition and UE behavior consistency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095180A_ABST
    Figure CN119095180A_ABST
Patent Text Reader

Abstract

A method for a base station (BS) to communicate with a user equipment (UE) is provided. The UE is configured with either a codebook-based transmission or a non-codebook-based transmission for multi-beam physical uplink shared channel (PUSCH) repetition. Various options are provided to cause the UE to derive an uplink precoder for the multi-beam PUSCH repetition.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the application with international application number PCT / CN2021 / 120267, international application date September 24, 2021, entry into the Chinese national phase date September 15, 2022, national application number 202180022096.X, and invention name “Method for control signaling for repeated transmission of multi-beam PUSCH”. Technical Field

[0002] The present disclosure relates to the field of wireless communications, and more particularly, to control signaling for multi-beam PUSCH repetitive transmission. Background Art

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE); the fifth generation (5G) 3GPP New Radio (NR) standard; the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly referred to by industry organizations as Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLANs), which is commonly referred to by industry organizations as Wi-Fi. In the 3GPP radio access network (RAN) in the LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, enhanced Node B, eNodeB, or eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device called a user equipment (UE). In fifth generation (5G) wireless RAN, RAN nodes may include 5G nodes, new radio (NR) nodes, or gNode Bs (gNBs), which communicate with wireless communication devices (also known as user equipment (UE)). Summary of the Invention

[0004] According to some embodiments of the present disclosure, a method is provided for a base station (BS) to communicate with a user equipment (UE). The UE is configured with codebook-based transmission or non-codebook-based transmission for multi-beam physical uplink shared channel (PUSCH) repetition. The method includes: performing at least one item selected from the group consisting of the following items: for codebook-based transmission, according to determining to configure the UE with multi-beam PUSCH repetition, the UE is not configured with uplink transmission mode fullpowerMode2 (full power mode 2), in which uplink transmission mode, the UE is allowed to use different numbers of ports for different sounding reference signal (SRS) resources for codebook-based transmission; for codebook-based transmission, according to determining to configure the UE with uplink transmission mode fullpowerMode2, operating according to the indication configuration to enable the UE to derive an uplink precoder for multi-beam PUSCH repetition; and for non-codebook-based transmission, operating according to a triggering configuration, the triggering configuration being used to trigger a first pair of aperiodic SRS resource sets and associated aperiodic channel state information reference signals (CSI-RS) and a second pair of aperiodic SRS resource sets and associated aperiodic CSI-RS, the first pair and the second pair being configured to enable the UE to derive an uplink precoder for multi-beam PUSCH repetition.

[0005] According to some embodiments of the present disclosure, a method for a user equipment (UE) to communicate with a base station (BS) is provided. The UE is configured with codebook-based transmission or non-codebook-based transmission for multi-beam physical uplink shared channel (PUSCH) repetition. The method includes: performing at least one item selected from the group consisting of the following items: for codebook-based transmission, according to determining to configure multi-beam PUSCH repetition, not enabling uplink transmission mode fullpowerMode2, in which uplink transmission mode, the UE is allowed to use different numbers of ports for different sounding reference signal (SRS) resources for the codebook-based transmission; for codebook-based transmission, according to determining to enable uplink transmission mode fullpowerMode2, operating according to the indication configuration to derive an uplink precoder for multi-beam PUSCH repetition; and for non-codebook-based transmission, operating according to a triggering configuration, which is used to trigger a first pair of aperiodic SRS resource sets and associated aperiodic channel state information reference signals (CSI-RS) and a second pair of aperiodic SRS resource sets and associated aperiodic CSI-RS, the first pair and the second pair being configured to enable the UE to derive an uplink precoder for multi-beam PUSCH repetition.

[0006] According to some embodiments of the present disclosure, a device for a base station is provided, comprising one or more processors configured to execute any of the methods described above.

[0007] According to some embodiments of the present disclosure, there is provided an apparatus for a user equipment (UE), comprising one or more processors configured to perform any of the methods described above.

[0008] According to some embodiments of the present disclosure, an apparatus for a communication device is provided, wherein the apparatus includes means for executing the steps of the method described above.

[0009] According to some embodiments of the present disclosure, a computer readable medium having a computer program stored thereon is provided. When the computer program is executed by a device having one or more processors, the device performs any of the methods described above.

[0010] According to some embodiments of the present disclosure, a computer program product is provided, which includes a computer program, and when the computer program is executed by a device having one or more processors, causes the device to perform any of the methods described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Features and advantages of the present disclosure will be apparent from the following detailed description taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the present disclosure.

[0012] Figure 1 is a block diagram of a system including a base station and user equipment (UE) according to some embodiments.

[0013] Figure 2 A schematic diagram of an exemplary method according to some embodiments is shown.

[0014] Figures 3A to 3C A schematic diagram of an SRS+CSI-RS pair is shown according to some embodiments.

[0015] Figure 4 A schematic diagram of an exemplary method according to some embodiments is shown.

[0016] Figure 5 is a block diagram illustrating a communication device (eg, a UE or a base station) according to some embodiments.

[0017] Figure 6 An exemplary interface of a baseband circuit according to some embodiments is shown.

[0018] Figure 7 Components according to some embodiments are shown. DETAILED DESCRIPTION

[0019] In the present disclosure, a "base station" may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly expressed as an evolved Node B, enhanced Node B, eNodeB or eNB) and / or a Radio Network Controller (RNC) and / or a 5G node, a New Radio (NR) node or a gNode B (gNB), which communicates with a wireless communication device also referred to as a user equipment (UE).

[0020] As used herein, unless otherwise noted, the terms "user equipment" and "base station" are not specific to or otherwise limited to any particular radio access technology (RAT). Generally speaking, such a UE can be any wireless communication device used by a user (e.g., a mobile phone, router, tablet, laptop, tracking device, Internet of Things (IoT) device, etc.). A UE can be mobile or can be stationary (e.g., at a particular time) and can communicate with a radio access network (RAN).

[0021] As used herein, the term "and / or" or "at least one of" includes any and all combinations of one or more of the associated listed items.

[0022] In 3GPP Release 17, PUSCH repetition with multi-beam operation is supported, where repetitions with different beams can be received by different transmission reception points (TRPs). The base station can configure two sounding reference signal (SRS) resource sets for codebook-based uplink transmission and another two SRS resource sets for non-codebook-based uplink transmission. For codebook-based transmission, the base station can indicate two SRS resource indicators (SRIs), precoder indicators (including a first transmission precoder matrix indicator (TPMI) and a transmission rank indicator (TRI)) and a second TPMI to the UE so that the UE can determine the corresponding precoders for the two PUSCH repetitions. For non-codebook-based transmission, the base station can provide CSI-RS associated with the SRS resource set to enable the UE to derive the precoder for the SRS. In the case of multi-beam PUSCH repetition, the base station can therefore trigger two non-periodic SRS resource sets and the associated two CSI-RS resources to enable the UE to derive the corresponding precoders for the two PUSCH repetitions.

[0023] However, in some cases, PUSCH repetition with multi-beam operation may present problems. For example, in the case of codebook-based transmission, when uplink full power mode 2 is enabled, how to indicate the SRI and the second TPMI may be a problem (hereinafter referred to as "Issue 1"). In the case of non-codebook-based transmission, if two aperiodic SRS resource sets and two associated CSI-RS resources are triggered simultaneously, the UE behavior for aperiodic SRS transmission may be another problem (hereinafter referred to as "Issue 2").

[0024] The embodiments of the present disclosure propose a solution for control signaling for repeated transmission of multi-beam PUSCH to alleviate, mitigate or eliminate at least one of the above-mentioned problems. The principles and specific implementations of the present disclosure will be described in detail below with reference to the figures.

[0025] Figure 1 is a block diagram of a system including a base station and user equipment (UE) according to some embodiments. Figure 1 A wireless network 100 is shown according to some embodiments. The wireless network 100 comprises a UE 101 and a base station 150 connected via an air interface 190.

[0026] UE 101 and any other UEs in the system may be, for example, laptops, smartphones, tablets, printers, machine-type devices such as smart meters or specialized devices for healthcare monitoring, remote safety monitoring, intelligent transportation systems, or any other wireless device with or without a user interface. Base station 150 provides network connectivity to a wider network (not shown) to UE 101 via an air interface 190 within the base station service area provided by base station 150. In some embodiments, such a wider network may be a wide area network operated by a cellular network provider, or may be the Internet. Each base station service area associated with base station 150 is supported by an antenna integrated with base station 150. The service area is divided into a plurality of sectors associated with certain antennas. Such sectors may be physically associated with fixed antennas, or may be assigned to a physical area with a tunable antenna or antenna setting that can be adjusted in a beamforming process for directing signals to a particular sector. For example, one embodiment of the base station 150 includes three sectors, each sector covering a 120 degree area, with antenna arrays pointed toward each sector to provide 360 ​​degree coverage around the base station 150 .

[0027] UE 101 includes control circuitry 105 coupled to transmit circuitry 110 and receive circuitry 115. Transmit circuitry 110 and receive circuitry 115 may each be coupled to one or more antennas. Control circuitry 105 may be adapted to perform operations associated with MTC. In some embodiments, control circuitry 105 of UE 101 may perform calculations or initiate measurements associated with air interface 190 to determine the channel quality of an available connection to base station 150. These calculations may be performed in conjunction with control circuitry 155 of base station 150. Transmit circuitry 110 and receive circuitry 115 may be adapted to transmit and receive data, respectively. Control circuitry 105 may be adapted or configured to perform various operations, such as the various UE-related operations described elsewhere in this disclosure. Transmit circuitry 110 may transmit multiple multiplexed uplink physical channels. The multiple uplink physical channels may be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM). Transmit circuitry 110 may be configured to receive block data from control circuitry 105 for transmission across air interface 190. Similarly, the receive circuitry 115 may receive multiple multiplexed downlink physical channels from the air interface 190 and relay these physical channels to the control circuitry 105. The uplink and downlink physical channels may be multiplexed according to TDM or FDM. The transmit circuitry 110 and the receive circuitry 115 may transmit and receive control data and content data (e.g., messages, images, video, etc.) structured within data blocks carried by the physical channels.

[0028] Figure 1 Also shown is a base station 150 according to various embodiments. The base station 150 circuitry may include control circuitry 155 coupled to transmit circuitry 160 and receive circuitry 165. The transmit circuitry 160 and receive circuitry 165 may each be coupled to one or more antennas that may be used to enable communication over an air interface 190.

[0029] Control circuitry 155 may be adapted to perform operations associated with MTC. Transmit circuitry 160 and receive circuitry 165 may be adapted to transmit and receive data, respectively, within a narrow system bandwidth that is narrower than a standard bandwidth used for personal communications. In some embodiments, for example, the transmission bandwidth may be set to or near 1.4 MHz. In other embodiments, other bandwidths may be used. Control circuitry 155 may perform various operations, such as base station-related operations described elsewhere in this disclosure.

[0030] Within the narrow system bandwidth, the transmission circuit 160 can transmit multiple multiplexed downlink physical channels. The multiple downlink physical channels can be multiplexed according to TDM or FDM. The transmission circuit 160 can transmit the multiple multiplexed downlink physical channels in a downlink superframe composed of multiple downlink subframes.

[0031] Within the narrow system bandwidth, the receiving circuit 165 can receive multiple multiplexed uplink physical channels. The multiple uplink physical channels can be multiplexed according to TDM or FDM. The receiving circuit 165 can receive the multiple multiplexed uplink physical channels in an uplink superframe composed of multiple uplink subframes.

[0032] As described further below, control circuits 105 and 155 may be involved in measuring the channel quality of air interface 190. Channel quality may be based on, for example, physical obstacles between UE 101 and base station 150, electromagnetic signal interference from other sources, reflections, or indirect paths between UE 101 and base station 150, or other such signal noise sources. Based on the channel quality, multiple retransmissions of a data block may be scheduled so that transmit circuit 110 may transmit multiple copies of the same data and receive circuit 115 may receive multiple copies of the same data.

[0033] Figure 2 Schematic diagram of an exemplary method 200 according to some embodiments is shown. The method 200 may be performed by a base station (BS) communicating with a UE. For the purpose of discussion, the method 200 will be combined with Figure 1 The method 200 is described. For example, the base station and the UE may be respectively as follows Figure 1 Shown are a base station 150 and a UE 101. The UE 101 is configured with either codebook-based transmission or non-codebook-based transmission for multi-beam physical uplink shared channel (PUSCH) repetition.

[0034] At block 210, UE 101 is configured with codebook-based transmission. If multi-beam PUSCH repetition is configured for UE 101, base station 150 will not operate UE 101 in uplink transmission mode fullpowerMode2, in which UE 101 is allowed to use different numbers of antenna ports (hereinafter referred to as "ports") for different sounding reference signal (SRS) resources. Block 210 can be implemented by specifying in the 3GPP technical specification that the base station should not configure both fullpowerMode2 and multi-beam PUSCH repetition at the same time. In this case, base station 150 can alternatively configure other transmission modes for UE 101, such as fullpowerMode0 and fullpowerMode1. In one embodiment, uplink transmission mode fullpowerMode2 can be full power Mode 2 defined in 3GPP 5G NR standard Release 16.

[0035] Using the method provided in block 210, previously identified problem 1 may be avoided because full power mode 2 is not enabled just for multi-beam PUSCH repetition.

[0036] At block 220, UE 101 is configured for codebook-based transmission. Furthermore, uplink transmission mode fullpowerMode2 is enabled for UE 101. In this case, base station 150 may operate according to the indicated configuration, which causes UE 101 to derive an uplink precoder for multi-beam PUSCH repetition.

[0037] Codebook-based transmission requires the base station 150 to indicate the following indicators to the UE 101:

[0038] - two SRIs associated with two SRS resource sets respectively,

[0039] - a precoder indicator comprising a first TPMI and a transmission rank indicator (TRI), and

[0040] -Second TPMI.

[0041] Here, only one TRI is required for two PUSCH repetitions because both repetitions should be transmitted based on the same number of layers (i.e., TRI). Two TPMIs and TRIs are indicated to UE 101 so that UE 101 can derive two precoders for the two PUSCH repetitions, respectively. The first TPMI together with the TRI is used to determine the first precoder from the codebook identified by the first SRI, and the second TPMI together with the TRI is used to determine the second precoder from the codebook identified by the second SRI.

[0042] The indication configuration includes an SRI indication associated with the two SRIs and a TPMI indication associated with the second TPMI.

[0043] In some embodiments, the SRI indication may specify that the SRS resources within two SRS resource sets be configured with the same number of SRS ports. For example, when the uplink transmission mode fullpowerMode2 is enabled for multi-beam PUSCH repetition, up to two SRS resources per SRS resource set may be configured, for example, to support two spatial relationship indications, where the resources across the two resource sets are configured with the same number of SRS ports. It should be noted that in this case, the number of SRS resources in each resource set may be different.

[0044] In some embodiments, the TPMI indication may specify that the total size of the second TPMI (which may also be referred to as the "bit width") is based on the maximum number of TPMI code points between each rank of the precoder indicator. In addition, the first K bits (K is a natural number) of the second TPMI respectively indicate one or more TPMI values ​​corresponding to the rank indicated by the precoder indicator, and the remaining bits of the second TPMI may be reserved.

[0045] Take the case of 4 antenna ports and codebookSubset=noncoherent as an example. According to the rightmost column of Table 1 shown below (which replicates Table 7.3.1.1.2-2 in 3GPP TS 38.212), in the case of rank 0 (i.e., 1 layer), four TPMI code points (TPMI=0, 1, 2, 3) are available, which corresponds to a bit width of 2, because 2 bits are required to encode these four TPMI values. Similarly, in the case of rank 1 (i.e., 2 layers), six TPMI code points (TPMI=0, 1, 2, 3, 4, 5) are available, which corresponds to a bit width of 3, because 3 bits are required to encode the six TPMI values. In the case of rank 2 (i.e., 3 layers), one TPMI code point (TPMI=0) is available, which corresponds to a bit width of 1. In the case of rank 3 (i.e., 4 layers), one TPMI code point (TPMI=0) is available, which corresponds to a bit width of 1. Therefore, the total size of the second TPMI can be determined to be a maximum of {2, 3, 1, 1} = 3 bits, which means that the indication of the second TPMI will have 2 3 =8 entries. If the TRI indicated by the precoder indicator is 0 (i.e., TRI+1=1 layer), four TPMI values ​​(TPMI=0, 1, 2, 3) are available according to the rightmost column of Table 1. Therefore, the indication of the second TPMI can be {TPMI=0, TPMI=1, TPMI=2, TPMI=3, reserved, reserved, reserved, reserved}.

[0046] Table 1: Precoding information and number of layers for 4 antenna ports if the conversion precoder is disabled. maxRank = 2 or 3 or 4, and ul-FullPowerTransmission is not configured or configured Set to fullpowerMode2 or configure to fullpower

[0047]

[0048]

[0049] In some embodiments, the SRI indication may specify that each SRS resource within the two SRS resource sets is to be configured with a different number of SRS ports. For example, when the uplink transmission mode fullpowerMode2 is enabled for multi-beam PUSCH repetition, the first of the two SRS resource sets may be configured with a 1-port SRS resource, and the second of the two SRS resource sets may be configured with a 2-port SRS resource and a 4-port SRS resource.

[0050] In such an embodiment, the number of ports of the two SRS resources indicated by the two SRIs can be the same. In other words, the two SRS resources indicated by the two SRIs in the two SRS resource sets are to be configured with the same number of SRS ports. For example, if a 2-port SRS resource is indicated by an SRI associated with the first SRS resource set, then the 2-port SRS resource must also be indicated by an SRI associated with the second SRS resource set. In such an embodiment, the TPMI indication described above still applies. That is, the total size of the second TPMI is based on the maximum number of TPMI code points between each rank of the precoder indicator, and the first K bits of the second TPMI respectively indicate one or more TPMI values ​​corresponding to the rank indicated by the precoder indicator, and the remaining bits are reserved.

[0051] Alternatively, the number of ports for the two SRS resources indicated by the two SRIs may be different. In other words, the two SRS resources indicated by the two SRIs and within the two SRS resource sets are to be configured with corresponding different numbers of SRS ports. As an option, the two SRS resource sets are to be configured with the same number of SRS resources. For example, if the first SRS resource set is configured with two SRS resources, the second SRS resource set must also be configured with two SRS resources. As another option, the number of configured SRS ports for one SRS resource set in the two SRS resource sets is to be the same as the number of configured SRS ports for the other SRS resource set in the two SRS resource sets. For example, if a 1-port SRS resource and a 2-port SRS resource are configured in the first SRS resource set, then a 1-port SRS resource and a 2-port SRS resource must also be configured in the second resource set.

[0052] In addition, the TPMI indication may specify that the total size of the second TPMI is based on the maximum number of TPMI code points between each rank of the precoder indicator and each SRS resource in the second SRS resource set. In addition, the first one or more bits of the second TPMI may respectively indicate one or more TPMI values ​​corresponding to the rank indicated by the precoder indicator and the number of SRS ports indicated by the second SRS. The remaining bits of the second TPMI may be reserved.

[0053] For example, if the two SRS resources in the second SRS resource set are configured with 2 and 4 SRS ports, respectively, and codebookSubset=nonCoherent, then according to Table 2 shown below (which replicates Table 7.3.1.1.2-4 in 3GPP TS 38.212 and corresponds to the case of 2 ports) and Table 1 shown above (which corresponds to the case of 4 antenna ports), the total size of the second TPMI can be determined as max{{1,1},{2,3,1,1}}=3 bits (or equivalently 8 entries). If TRI=0 (corresponding to 1 layer) and the second SRI=0 (corresponding to 2 ports), the indication of the second TPMI can be {TPMI=0, TPMI=1, reserved, reserved, reserved, reserved, reserved, reserved} (note that according to the rightmost column of Table 2, there are two TPMI values ​​(TPMI=0, 1) available for the case of 1 layer).

[0054] Table 2: Precoding information and number of layers for 2 antenna ports if the conversion precoder is disabled. maxRank = 2, and ul-FullPowerTransmission is not configured or is configured as fullpowerMode2 or configured as fullpower

[0055]

[0056] At block 230, UE 101 is configured with non-codebook-based transmission. Base station 150 operates according to a triggering configuration to trigger a first pair of aperiodic SRS resource sets and associated aperiodic channel state information reference signals (CSI-RSs) and a second pair of aperiodic SRS resource sets and associated aperiodic CSI-RSs. The first and second pairs are configured for UE 101 to derive an uplink precoder for the multi-beam PUSCH repetition.

[0057] In some embodiments (option 1), the trigger configuration may specify that the first and second pairs of aperiodic SRS resource sets and associated aperiodic CSI-RS will not be triggered by a single downlink control information (DCI). In other words, the two pairs of aperiodic SRS resource sets and associated aperiodic CSI-RS will not be triggered simultaneously but will be triggered sequentially. Figures 3A to 3C Describes more options.

[0058] Figures 3A to 3C A schematic diagram of an SRS+CSI-RS pair according to some embodiments is shown. As previously mentioned in the opening paragraph of the detailed description, in the case of non-codebook based transmission, if two aperiodic SRS resource sets and two associated CSI-RS resources are triggered together, the UE behavior for aperiodic SRS transmission may be an issue. Figures 3A to 3C Various options are provided to resolve this issue.

[0059] In some embodiments (option 2), such as Figure 3A As shown, the first pair 301 and the second pair 302 of aperiodic SRS resource sets and associated aperiodic CSI-RS are triggered without overlap in the time domain. For example, the first pair 301 and the second pair 302 may be triggered simultaneously, but they do not overlap in the time domain. The duration of each pair of aperiodic SRS resource sets and associated aperiodic CSI-RS is counted from the first or last symbol of the associated aperiodic CSI-RS to the first or last symbol of the aperiodic SRS resource set. Figure 3A As noted, no overlap between the durations of the first pair 301 and the second pair 302 is allowed in this option.

[0060] In some embodiments (option 3), such as Figure 3B As shown, the aperiodic SRS resource sets and the associated aperiodic CSI-RSs of the first pair 301 and the second pair 302 are triggered to overlap in the time domain, and an additional gap is provided between the associated aperiodic CSI-RSs and the aperiodic SRS resource sets in each of the first and second pairs, in addition to a predefined minimum offset (e.g., 42 symbols). Figure 3B As shown, the offset between the associated aperiodic CSI-RS and aperiodic SRS resource sets in each pair can be configured to a value greater than 42 + the gap. The additional gap enables UE 101 to process PUSCH repetitions. In some embodiments, the additional gap can be predefined in the 3GPP technical specifications. Alternatively, the additional gap can be determined by base station 150 based on the UE capabilities reported by UE 101. In some embodiments, the length of the additional gap depends on how much symbol overlap there is between the duration of the aperiodic SRS resource sets and the associated aperiodic CSI-RS of the two pairs or on the UE capabilities. For example, the greater the symbol overlap, the longer the additional gap.

[0061] In some embodiments (option 4), as Figure 3CAs shown, the aperiodic SRS resource sets and associated aperiodic CSI-RSs of the first and second pairs 301, 302 are triggered with overlap in the time domain, and no additional gap is required between the associated aperiodic CSI-RSs and aperiodic SRS resource sets in each of the first and second pairs 301, 302, except for a predefined minimum offset. In some implementations, the trigger configuration specifies that the UE 101 is to provide two CSI processing units (CPUs) for processing the first and second pairs 301, 302. In this way, the first and second pairs 301, 302 can be processed in parallel by the UE 101 using different CPUs. The CPUs can be defined as in 3GPP TS 38.214, Section 5.2.1.6. The CPUs are occupied for a duration from the first or last symbol of the associated aperiodic CSI-RS to the first or last symbol of the aperiodic SRS resource set.

[0062] exist Figure 1 In the wireless network 100, there may be various UEs 101, but for clarity, only one UE is shown. Some of the UEs 101 may have parallel processing capabilities, while others of the UEs 101 may not have such capabilities. Figures 3A to 3C Whether the described options 2, 3, and 4 are supported by UE 101 can be determined based on UE capabilities. If UE 101 reports that it can support both options 3 and 4, base station 150 can indicate to UE 101 whether to use option 3 or 4 through higher layer signaling (e.g., RRC signaling). Alternatively, whether to use option 3 or 4 can be determined by whether the first pair 301 and the second pair 302 are triggered by the same DCI or by different DCIs. For example, if UE 101 can support both options 3 and 4, and the aperiodic SRS resource sets and associated aperiodic SRS resource sets of the two pairs are triggered by the same DCI, option 4 can be used. Alternatively, if UE 101 can support both options 3 and 4, and the aperiodic SRS resource sets and associated aperiodic SRS resource sets of the two pairs are triggered by different DCIs, option 3 can be used. It should be understood that the embodiments are given for illustrative purposes only and do not limit the present disclosure.

[0063] Figure 4 4 shows a schematic diagram according to some exemplary methods 400. The method 400 is performed by a UE communicating with a base station. Blocks 410, 420, and 430 are equivalent to the following. Figure 2 Blocks 210, 220, and 230 are shown, except that blocks 410, 420, and 430 are performed by the UE rather than the base station.

[0064] At block 410, the UE is configured with multi-beam PUSCH repetition in case of codebook based transmission and will not be configured with uplink transmission mode fullpowerMode2.

[0065] At block 420, in case of codebook based transmission, the UE is configured with uplink transmission mode fullpowerMode2 and the UE operates according to the indicated configuration to derive the uplink precoder for multi-beam PUSCH repetition. Figure 2 The details of the indication configuration are discussed in conjunction with FIG. 3 and will not be repeated here for the sake of brevity.

[0066] At block 430, in the case of non-codebook based transmission, the UE operates according to a triggering configuration for triggering a first pair of aperiodic SRS resource sets and associated aperiodic channel state information reference signals (CSI-RS) and a second pair of aperiodic SRS resource sets and associated aperiodic CSI-RS. The first pair and the second pair are configured to cause the UE to derive an uplink precoder for multi-beam PUSCH repetition. Reference has been made above to Figure 2 The details of the trigger configuration are discussed in detail in FIG. 3 and will not be repeated here for the sake of brevity.

[0067] Figure 5 Example components of a device 500 according to some embodiments are shown. In some embodiments, the device 500 may include application circuitry 502, baseband circuitry 504, radio frequency (RF) circuitry (shown as RF circuitry 520), front-end module (FEM) circuitry (shown as FEM circuitry 530), one or more antennas 532, and power management circuitry (PMC) (shown as PMC 534) (at least coupled together as shown). The components of the illustrated device 500 may be included in a UE or a RAN node. In some embodiments, the device 500 may include fewer components (e.g., a RAN node may not utilize application circuitry 502 but instead include a processor / controller to process IP data received from an EPC). In some embodiments, the device 500 may include additional components such as, for example, memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device (e.g., the circuitry may be included separately in more than one device for a cloud-RAN (C-RAN) implementation).

[0068] The application circuitry 502 may include one or more application processors. For example, the application circuitry 502 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and specialized processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 500. In some embodiments, the processors of the application circuitry 502 may process IP data packets received from the EPC.

[0069] The baseband circuitry 504 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 504 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of the RF circuitry 520 and generate baseband signals for the transmit signal path of the RF circuitry 520. The baseband circuitry 504 may interact with the application circuitry 502 to generate and process baseband signals and control the operation of the RF circuitry 520. For example, in some embodiments, the baseband circuitry 504 may include a third generation (3G) baseband processor (3G baseband processor 506), a fourth generation (4G) baseband processor (4G baseband processor 508), a fifth generation (5G) baseband processor (5G baseband processor 510), or other baseband processors 512 of other existing generations, generations under development, or generations to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). Baseband circuitry 504 (e.g., one or more of the baseband processors) may handle various radio control functions that enable communication with one or more radio networks via RF circuitry 520. In other embodiments, some or all of the functions of the illustrated baseband processor may be included in modules stored in memory 518 and executed via central processing ETnit (CPET 514). Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, and the like. In some embodiments, the modulation / demodulation circuitry of baseband circuitry 504 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuitry of baseband circuitry 504 may include convolution, tail-biting, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples and may include other suitable functions in other embodiments.

[0070] In some embodiments, the baseband circuitry 504 may include a digital signal processor (DSP), such as one or more audio DSPs 516. The one or more audio DSPs 516 may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, the components of the baseband circuitry may be appropriately combined in a single chip, a single chipset, or provided on the same circuit board. In some embodiments, some or all of the components of the baseband circuitry 504 and the application circuitry 502 may be implemented together, such as on a system on a chip (SOC).

[0071] In some embodiments, the baseband circuitry 504 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 504 can support communications with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other wireless metropolitan area network (WMAN), wireless local area network (WLAN), or wireless personal area network (WPAN). Embodiments in which the baseband circuitry 504 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0072] RF circuitry 520 can enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuitry 520 can include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. RF circuitry 520 can include a receive signal path that can include circuitry for downconverting RF signals received from FEM circuitry 530 and providing baseband signals to baseband circuitry 504. RF circuitry 520 can also include a transmit signal path that can include circuitry for upconverting baseband signals provided by baseband circuitry 504 and providing an RF output signal for transmission to FEM circuitry 530.

[0073] In some embodiments, the receive signal path of RF circuitry 520 may include mixer circuitry 522, amplifier circuitry 524, and filter circuitry 526. In some embodiments, the transmit signal path of RF circuitry 520 may include filter circuitry 526 and mixer circuitry 522. RF circuitry 520 may also include synthesizer circuitry 528 for synthesizing frequencies for use by mixer circuitry 522 of the receive signal path and the transmit signal path. In some embodiments, mixer circuitry 522 of the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 530 based on the synthesized frequency provided by synthesizer circuitry 528. Amplifier circuitry 524 may be configured to amplify the downconverted signal, and filter circuitry 526 may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 504 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, although this is not required. In some embodiments, mixer circuit 522 of the receive signal path may include a passive mixer, although the scope of the embodiments is not limited in this respect.

[0074] In some embodiments, mixer circuitry 522 of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuitry 528 to generate an RF output signal for FEM circuitry 530. The baseband signal can be provided by baseband circuitry 504 and can be filtered by filter circuitry 526.

[0075] In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 522 of the receive signal path and the mixer circuit 522 of the transmit signal path may be configured for superheterodyne operation.

[0076] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 520 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 504 may include a digital baseband interface to communicate with RF circuitry 520.

[0077] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0078] In some embodiments, synthesizer circuit 528 may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 528 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0079] The synthesizer circuit 528 can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by the mixer circuit 522 of the RF circuit 520. In some embodiments, the synthesizer circuit 528 can be a fractional-N / N+1 synthesizer.

[0080] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 504 or application circuitry 502 (such as an application processor) depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 502.

[0081] The synthesizer circuit 528 of the RF circuit 520 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0082] In some embodiments, the synthesizer circuit 528 can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple different phases relative to each other. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 520 can include an IQ / polarity converter.

[0083] The FEM circuitry 530 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 532, amplify the receive signals, and provide an amplified version of the receive signals to the RF circuitry 520 for further processing. The FEM circuitry 530 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by the RF circuitry 520 for transmission by one or more of the one or more antennas 532. In various embodiments, amplification by either the transmit or receive signal path may be performed only in the RF circuitry 520, only in the FEM circuitry 530, or in both the RF circuitry 520 and the FEM circuitry 530.

[0084] In some embodiments, the FEM circuitry 530 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry 530 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 530 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 520). The transmit signal path of the FEM circuitry 530 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 520), and one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more of the one or more antennas 532).

[0085] In some embodiments, PMC 534 can manage the power provided to baseband circuitry 504. Specifically, PMC 534 can control power source selection, voltage scaling, battery charging, or DC-DC conversion. PMC 534 is typically included when device 500 is capable of being powered by a battery, for example, when device 500 is included in an EGE. PMC 534 can improve power conversion efficiency while providing the desired implementation size and heat dissipation characteristics.

[0086] Figure 5PMC 534 is shown coupled only to baseband circuitry 504. However, in other embodiments, PMC 534 may additionally or alternatively be coupled to other components (such as, but not limited to, application circuitry 502, RF circuitry 520, or FEM circuitry 530) and perform similar power management operations for these components.

[0087] In some embodiments, the PMC 534 can control or otherwise be part of various power saving mechanisms of the device 500. For example, if the device 500 is in an RRC connected state, in which the device remains connected to a RAN node because it expects to receive communications soon, the device can enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, the device 500 can be powered off for short intervals, thereby saving power.

[0088] If there is no data traffic activity for an extended period of time, the device 500 may transition to an RRC idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handovers, etc. The device 500 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers down again. The device 500 cannot receive data in this state, and in order to receive data, the device transitions back to the RRC connected state.

[0089] An additional power saving mode can disable the device from using the network for periods exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device is completely unable to connect to the network and can be completely powered down. Any data sent during this period will incur significant latency, assuming that latency is acceptable.

[0090] The processor of the application circuitry 502 and the processor of the baseband circuitry 504 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 504 can be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuitry 502 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., transport communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 may include a radio resource control (RRC) layer, which is described in further detail below. As mentioned herein, layer 2 may include a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, which are described in further detail below. As mentioned herein, layer 1 may include a physical (PHY) layer of the UE / RAN node, which is described in further detail below.

[0091] Figure 66 shows an exemplary interface 600 of a baseband circuit according to some embodiments. As described above, Figure 5 The baseband circuit 504 may include a 3G baseband processor 506, a 4G baseband processor 508, a 5G baseband processor 510, other baseband processors 512, a CPU 514, and a memory 518 used by the processors. As shown, each of the processors may include a corresponding memory interface 602 for sending / receiving data to / from the memory 518.

[0092] The baseband circuit 504 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 604 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 504); an application circuit interface 606 (e.g., an interface for sending / receiving data to / from a memory external to the baseband circuit 504); Figure 5 RF circuit interface 608 (for example, for sending / receiving data to / from the application circuit 502); Figure 5 an interface for transmitting / receiving data to / from a RF circuit 520); a wireless hardware connection interface 610 (eg, for transmitting / receiving data to / from a near field communication (NFC) component, Components (e.g. Low power consumption), components and other communication components to send / receive data); and a power management interface 612 (eg, an interface for sending / receiving power or control signals to / from the PMC 534).

[0093] Figure 7 is a block diagram illustrating a component 700 capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Figure 7 A diagrammatic representation of hardware resources 702 is shown, including one or more processors 712 (or processor cores), one or more memory / storage devices 718, and one or more communication resources 720, each of which may be communicatively coupled via a bus 722. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 704 may be executed to provide an execution environment in which one or more network slices / sub-slices utilize the hardware resources 702.

[0094] Processor 712 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 714 and processor 716.

[0095] The memory / storage device 718 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 718 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0096] The communication resources 720 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 706 or one or more databases 708 via the network 710. For example, the communication resources 720 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Components (e.g. Low power consumption), components and other communication components.

[0097] The instructions 724 may include software, a program, an application, an applet, an application, or other executable code for causing at least any one of the processors 712 to perform any one or more of the methods discussed herein. The instructions 724 may reside, in whole or in part, within at least one of the processor 712 (e.g., within a cache memory of the processor), the memory / storage device 718, or any suitable combination thereof. In addition, any portion of the instructions 724 may be transmitted to the hardware resources 702 from any combination of the peripheral devices 706 or the database 708. Thus, the memory of the processor 712, the memory / storage device 718, the peripheral devices 706, and the database 708 are examples of computer-readable and machine-readable media.

[0098] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the following Examples section. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following Examples. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0099] Additional Examples

[0100] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the following Examples section. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following Examples. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0101] The following examples relate to additional embodiments.

[0102] Embodiment 1 is a method for a base station (BS) to communicate with a user equipment (UE), wherein the UE is configured for multi-beam physical uplink shared channel (PUSCH) repetition with codebook-based transmission or non-codebook-based transmission, the method comprising: performing at least one item selected from the group consisting of the following items: for codebook-based transmission, configuring the UE with multi-beam PUSCH repetition according to a determination, without configuring the UE with uplink transmission mode fullpowerMode2, in which the UE is allowed to use different numbers of ports for different sounding reference signal (SRS) resources for the codebook-based transmission; for For codebook-based transmission, according to determining to configure the uplink transmission mode fullpowerMode2 for the UE, operating according to the indicated configuration to enable the UE to derive an uplink precoder for multi-beam PUSCH repetition; and for non-codebook-based transmission, operating according to the triggering configuration, which is used to trigger a first pair of non-periodic SRS resource sets and associated non-periodic channel state information reference signals (CSI-RS) and a second pair of non-periodic SRS resource sets and associated non-periodic CSI-RS, the first pair and the second pair being configured to enable the UE to derive an uplink precoder for multi-beam PUSCH repetition.

[0103] Embodiment 2 is a method according to embodiment 1, wherein for multi-beam PUSCH repetition, codebook-based transmission requires the BS to indicate to the UE: two SRS resource indicators (SRIs) associated with two SRS resource sets, respectively, including a precoder indicator of a first transmission precoder matrix indicator (TPMI) and a transmission rank indicator (TRI), and a second TPMI, and wherein the indication configuration includes an SRI indication associated with the two SRIs and a TPMI indication associated with the second TPMI.

[0104] Embodiment 3 is a method according to embodiment 2, wherein the SRI indication specifies that the SRS resources in the two SRS resource sets are to be configured with the same number of SRS ports.

[0105] Embodiment 4 is a method according to embodiment 2, wherein the SRI indication specifies that each SRS resource in two SRS resource sets is to be configured with a different number of SRS ports.

[0106] Embodiment 5 is a method according to embodiment 4, wherein the SRI indication specifies that two SRS resources indicated by two SRIs in two SRS resource sets are to be configured with the same number of SRS ports.

[0107] Embodiment 6 is a method according to embodiment 4, wherein the SRI indication specifies that two SRS resources indicated by two SRIs in two SRS resource sets are to be configured with corresponding different numbers of SRS ports.

[0108] Embodiment 7 is a method according to embodiment 6, wherein the SRI indication specifies that two SRS resource sets are to be configured with the same number of SRS resources.

[0109] Embodiment 8 is a method according to embodiment 6, wherein the SRI indication specifies that the configured number of SRS ports used for one of the two SRS resource sets is to be the same as the configured number of SRS ports used for the other of the two SRS resource sets.

[0110] Embodiment 9 is a method according to embodiment 3 or 5, wherein the TPMI indication specifies: the total size of the second TPMI is based on the maximum number of TPMI code points between each rank of the precoder indicator, and the first one or more bits of the second TPMI respectively indicate one or more TPMI values ​​corresponding to the rank indicated by the precoder indicator, and the remaining bits of the second TPMI are reserved.

[0111] Embodiment 10 is a method according to any one of embodiments 6 to 8, wherein the two SRIs include a first SRI and a second SRI associated with a first SRS resource set and a second SRS resource set, respectively, of two SRS resource sets, and wherein the TPMI indication specifies: the total size of the second TPMI is based on the maximum number of TPMI code points between each SRS resource in each rank of the precoder indicator and the second SRS resource set, and the first one or more bits of the second TPMI respectively indicate one or more TPMI values ​​corresponding to the rank indicated by the precoder indicator and the number of SRS ports indicated by the second SRI, and the remaining bits of the second TPMI are reserved.

[0112] Embodiment 11 is a method according to embodiment 1, wherein the trigger configuration includes at least one of the following items: a first option, the first option specifying that the first pair and the second pair are not to be triggered by a single downlink control information (DCI), a second option, the second option specifying that the first pair and the second pair are to be triggered with no overlap in the time domain, a third option, the third option specifying that the first pair and the second pair are to be triggered with overlap in the time domain and that an additional gap is to be provided between the associated aperiodic CSI-RS and aperiodic SRS resource sets in each of the first pair and the second pair in addition to a predefined minimum offset, a fourth option, the fourth option specifying that the first pair and the second pair are to be triggered with an overlap in the time domain. There is overlap in the time domain to trigger the first pair and the second pair, and no additional gap is provided between the associated aperiodic CSI-RS and the aperiodic SRS resource set in each of the first pair and the second pair, except for a predefined minimum offset, or a fifth option, the fifth option specifying that: whether the second option to the fourth option are to be supported by the UE is determined based on the UE capability reported by the UE, and if the UE supports both the third option and the fourth option, whether to use the third option or the fourth option is to be configured by higher layer signaling or determined by whether the first pair and the second pair are triggered by the same DCI or by different DCI.

[0113] Embodiment 12 is a method according to embodiment 11, wherein for the third option, the additional gap is predefined.

[0114] Embodiment 13 is a method according to embodiment 11, wherein for the third option, the additional gap is determined based on UE capabilities or the number of symbols overlapping between durations of the first and second pairs of aperiodic SRS resource sets and associated aperiodic CSI-RS.

[0115] Embodiment 14 is a method according to claim 13, wherein the duration for each pair of an aperiodic SRS resource set and an associated aperiodic CSI-RS is from the first or last symbol of the associated aperiodic CSI-RS to the first or last symbol of the aperiodic SRS resource set.

[0116] Embodiment 15 is a method according to embodiment 11, wherein for the fourth option, the trigger configuration specifies that the UE is to provide two CSI processing units (CPUs) for processing the first pair and the second pair, wherein a corresponding one of the two CPUs is occupied during the duration of the aperiodic SRS resource set and the associated aperiodic CSI-RS for each pair.

[0117] Embodiment 16 is a method according to any one of embodiments 1 to 15, wherein the uplink transmission mode fullpowerMode2 is defined in 3GPP 5G NR standard release 16.

[0118] Embodiment 17 is a method for a user equipment (UE) to communicate with a base station (BS), wherein the UE is configured with codebook-based transmission or non-codebook-based transmission for multi-beam physical uplink shared channel (PUSCH) repetition, the method comprising: performing at least one item selected from the group consisting of: for codebook-based transmission, configuring multi-beam PUSCH repetition according to determining, not enabling uplink transmission mode fullpowerMode2, in which the UE is allowed to use different numbers of ports for different sounding reference signal (SRS) resources for the codebook-based transmission; for For codebook-based transmission, based on determining to enable the uplink transmission mode fullpowerMode2, operate according to the indication configuration to derive an uplink precoder for multi-beam PUSCH repetition; and for non-codebook-based transmission, operate according to the trigger configuration, which is used to trigger a first pair of non-periodic SRS resource sets and associated non-periodic channel state information reference signals (CSI-RS) and a second pair of non-periodic SRS resource sets and associated non-periodic CSI-RS, the first pair and the second pair being configured to enable the UE to derive an uplink precoder for multi-beam PUSCH repetition.

[0119] Embodiment 18 is a method according to embodiment 17, wherein for multi-beam PUSCH repetition, codebook-based transmission requires the BS to indicate to the UE: two SRS resource indicators (SRIs) associated with two SRS resource sets, respectively, a precoder indicator including a first transmission precoder matrix indicator (TPMI) and a transmission rank indicator (TRI), and a second TPMI, and wherein the indication configuration includes an SRI indication associated with the two SRIs and a TPMI indication associated with the second TPMI.

[0120] Embodiment 19 is a method according to embodiment 18, wherein the SRI indication specifies that the SRS resources in the two SRS resource sets are to be configured with the same number of SRS ports.

[0121] Embodiment 20 is a method according to embodiment 18, wherein the SRI indication specifies that each SRS resource configuration within two SRS resource sets has a different number of SRS ports.

[0122] Embodiment 21 is a method according to embodiment 20, wherein the SRI indication specifies that two SRS resources indicated by two SRIs in two SRS resource sets are to be configured with the same number of SRS ports.

[0123] Embodiment 22 is a method according to embodiment 20, wherein the SRI indication specifies that two SRS resources indicated by two SRIs in two SRS resource sets are to be configured with different numbers of SRS ports.

[0124] Embodiment 23 is a method according to embodiment 22, wherein the SRI indication specifies that two SRS resource sets are to be configured with the same number of SRS resources.

[0125] Embodiment 24 is a method according to embodiment 22, wherein the SRI indication specifies that the configured number of SRS ports used for one of the two SRS resource sets is to be the same as the configured number of SRS ports used for the other of the two SRS resource sets.

[0126] Embodiment 25 is a method according to embodiment 3 or 5, wherein the TPMI indication specifies: the total size of the second TPMI is based on the maximum number of TPMI code points between each rank of the precoder indicator, and the first one or more bits of the second TPMI respectively indicate one or more TPMI values ​​corresponding to the rank indicated by the precoder indicator, and the remaining bits of the second TPMI are reserved.

[0127] Embodiment 26 is a method according to any one of embodiments 22 to 24, wherein the two SRIs include a first SRI and a second SRI associated with a first SRS resource set and a second SRS resource set, respectively, of two SRS resource sets, and wherein the TPMI indication specifies: the total size of the second TPMI is based on the maximum number of TPMI code points between each SRS resource in each rank of the precoder indicator and the second SRS resource set, and the first one or more bits of the second TPMI indicate one or more TPMI values ​​corresponding to the rank indicated by the precoder indicator and the number of SRS ports indicated by the second SRI, respectively, and the remaining bits of the second TPMI are reserved.

[0128] Embodiment 27 is a method according to any one of embodiments 17 to 26, wherein the trigger configuration includes at least one of the following items: a first option, the first option specifying that the first pair and the second pair are not to be triggered by a single downlink control information (DCI), a second option, the second option specifying that the first pair and the second pair are to be triggered with no overlap in the time domain, a third option, the third option specifying that: the first pair and the second pair are to be triggered with overlap in the time domain, and in addition to a predefined minimum offset, an additional gap is to be provided between the associated aperiodic CSI-RS and aperiodic SRS resource sets in each of the first pair and the second pair, a fourth option, the fourth option Specifying: triggering the first pair and the second pair with overlap in the time domain, and not providing an additional gap between the associated aperiodic CSI-RS and the aperiodic SRS resource set in each of the first pair and the second pair, except for a predefined minimum offset, or a fifth option, the fifth option specifying: whether the second option to the fourth option are to be supported by the UE is determined based on the UE capability reported by the UE, and if the UE supports both the third option and the fourth option, whether to use the third option or the fourth option is to be configured by higher layer signaling or determined by whether the first pair and the second pair are triggered by the same DCI or by different DCI.

[0129] Embodiment 28 is a method according to embodiment 27, wherein for the third option, the additional gap is predefined.

[0130] Embodiment 29 is a method according to embodiment 27, wherein for the third option, the additional gap is determined based on UE capabilities or the number of symbols overlapping between durations of the first and second pairs of aperiodic SRS resource sets and associated aperiodic CSI-RS.

[0131] Embodiment 30 is a method according to embodiment 29, wherein the duration for each pair of an aperiodic SRS resource set and an associated aperiodic CSI-RS is from the first or last symbol of the associated aperiodic CSI-RS to the first or last symbol of the aperiodic SRS resource set.

[0132] Embodiment 31 is a method according to embodiment 27, wherein for the fourth option, the trigger configuration specifies that the UE is to provide two CSI processing units (CPUs) for processing the first pair and the second pair, wherein a corresponding one of the two CPUs is occupied during the duration of the aperiodic SRS resource set and the associated aperiodic CSI-RS for each pair.

[0133] Embodiment 32 is a method according to any one of embodiments 17 to 31, wherein the uplink transmission mode fullpowerMode2 is defined in 3GPP 5G NR standard release 16.

[0134] Embodiment 33 is a device for a base station, comprising one or more processors configured to execute the method according to any one of embodiments 1 to 16.

[0135] Embodiment 34 is an apparatus for a user equipment (UE), comprising one or more processors configured to perform the method according to any one of embodiments 17 to 32.

[0136] Embodiment 35 is an apparatus for a communication device, comprising means for executing the method according to any one of embodiments 1 to 32.

[0137] Embodiment 36 is a computer-readable medium having a computer program stored thereon, which, when executed by a device having one or more processors, causes the device to perform the method according to any one of embodiments 1 to 32.

[0138] Embodiment 37 is a computer program product comprising a computer program, which, when executed by a device having one or more processors, causes the device to perform the method according to any one of embodiments 1 to 32.

[0139] Unless expressly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0140] It should be understood that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into a single system, partially integrated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be understood that unless otherwise stated herein, these parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, etc. of another embodiment.

[0141] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0142] Although the foregoing has been described in considerable detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. The embodiments of the present invention are therefore to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method comprising: generating information for configuring a user equipment (UE) with a plurality of sounding reference signal (SRS) resources; identifying a first SRS resource indicator (SRI) to indicate a first SRS resource among the plurality of SRS resources, wherein the first SRS resource is configured to have a first number of SRS ports; determining that a second SRS resource must be selected from at least one SRS resource of the plurality of SRS resources configured with the first number of SRS ports; selecting the second SRS resource from the at least one SRS resource; identifying a second SRI to indicate the second SRS resource; and Generate downlink control information (DCI) to be transmitted to the UE for scheduling the transmission of multiple physical uplink shared channel (PUSCH) repetitions, wherein the DCI includes the first SRI and the second SRI, the first SRS resource is associated with the first PUSCH repetition among the multiple PUSCH repetitions, and the second SRS resource is associated with the second PUSCH repetition among the multiple PUSCH repetitions.

2. The method according to claim 1, further comprising: The UE is configured to repeatedly transmit the plurality of PUSCHs to at least two transmission reception points (TRPs) based on codebook transmission.

3. The method according to claim 1, further comprising: The uplink full power mode 2 transmission mode of the UE is enabled.

4. The method according to claim 3, wherein: The plurality of SRS resources include a first plurality of SRS resources associated with a first SRS resource set and a second plurality of SRS resources associated with a second SRS resource set.

5. The method according to claim 4, wherein: The first plurality of SRS resources include the first SRS resources, and the second plurality of SRS resources include the second SRS resources.

6. The method according to claim 4, wherein: The second plurality of SRS resources includes at least two SRS resources having different numbers of SRS ports.

7. The method according to claim 4, wherein: The first plurality of SRS resources and the second plurality of SRS resources have the same number of resources.

8. The method according to claim 4, wherein: The same number of SRS ports is configured for the first SRS resource set and the second SRS resource set.

9. The method according to claim 1, wherein: The DCI also includes a transmission rank indicator to indicate the number of layers to be transmitted for the first PUSCH repetition and the second PUSCH repetition.

10. The method according to claim 1, wherein: The DCI also includes a first transmission precoding matrix indicator (TPMI) and a second TPMI, wherein the first TPMI indicates a first precoder used for transmitting the first PUSCH repetition, and the second TPMI indicates a second precoder used for transmitting the second PUSCH repetition.

11. One or more computer-readable media having instructions that, when executed, cause one or more processors to: receiving a configuration of a plurality of sounding reference signal (SRS) resources; receiving downlink control information (DCI) to schedule repeated transmission of a plurality of physical uplink shared channels (PUSCHs), wherein: The DCI includes: a first SRS resource indicator (SRI) for indicating a first SRS resource among the multiple SRS resources, wherein the first SRS resource is configured to have a first number of SRS ports, and the first SRS resource is associated with a first PUSCH repetition among the multiple PUSCH repetitions; and a second SRI for indicating a second SRS resource among the multiple SRS resources, wherein the one or more processors determine that the second SRS resource must include the first number of SRS ports, and the second SRS resource is associated with a second PUSCH repetition among the multiple PUSCH repetitions; Based on the DCI, a first precoder for the first PUSCH repetition and a second precoder for the second PUSCH repetition are selected.

12. One or more computer-readable media according to claim 11, wherein: When executed, the instructions further cause the one or more processors to: A configuration for repeatedly transmitting the plurality of PUSCHs to at least two transmission reception points (TRPs) based on a codebook is received.

13. One or more computer-readable media according to claim 11, wherein: When executed, the instructions further cause the one or more processors to: Enable uplink full power mode 2 transmission mode.

14. One or more computer-readable media according to claim 13, wherein: The plurality of SRS resources include a first plurality of SRS resources associated with a first SRS resource set and a second plurality of SRS resources associated with a second SRS resource set.

15. One or more computer-readable media according to claim 14, wherein: The first plurality of SRS resources includes the first SRS resources, and the second plurality of SRS resources includes the second SRS resources.

16. One or more computer-readable media according to claim 14, wherein: The second plurality of SRS resources includes at least two SRS resources having different numbers of SRS ports.

17. One or more computer-readable media according to claim 14, wherein: The first plurality of SRS resources and the second plurality of SRS resources have the same number of resources.

18. One or more computer-readable media according to claim 14, wherein: The same number of SRS ports is configured for the first SRS resource set and the second SRS resource set.

19. One or more computer-readable media according to claim 11, wherein: The DCI also includes a transmission rank indicator to indicate the number of layers to be transmitted for the first PUSCH repetition and the second PUSCH repetition.

20. The one or more computer-readable media of claim 11, wherein: The DCI also includes a first transmission precoding matrix indicator (TPMI) and a second TPMI, wherein the first TPMI indicates a first precoder used for transmitting the first PUSCH repetition, and the second TPMI indicates a second precoder used for transmitting the second PUSCH repetition.