WO2022000262A1

WO2022000262A1 - Systems and methods for determining transmission information

Info

Publication number: WO2022000262A1
Application number: PCT/CN2020/099254
Authority: WO
Inventors: Yu Pan; Chuangxin JIANG; Shujuan Zhang; Zhaohua Lu
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-06-30
Filing date: 2020-06-30
Publication date: 2022-01-06
Anticipated expiration: 2022-12-30
Also published as: CN115804187B; CN115804187A

Abstract

Systems and methods for wireless communications are disclosed herein. A wireless communication device determines whether a condition has been satisfied. In response to determining that the condition has been satisfied, the wireless communication device performs uplink repetition such as Physical Uplink Shared Channel (PUSCH) repetition.

Description

SYSTEMS AND METHODS FOR DETERMINING TRANSMISSION INFORMATION

TECHNICAL FIELD

The present disclosure relates to the field of telecommunications, and in particular, uplink repetition.

BACKGROUND

Demands for the 5th Generation Mobile Communication Technology (5G) are increasing at a rapid pace. Developments are taking place to provide enhanced mobile broadband, ultra-high reliability, ultra-low-latency transmission, and massive connectivity in 5G systems.

SUMMARY

The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.

In some embodiments, a wireless communication device determines that a condition has been satisfied and, in response, performs uplink repetition based on repetition information.

In some embodiments, a network transmits, to a wireless communication device, condition information and receives, from the wireless communication device, uplink repetition. The uplink repetition is transmitted by the wireless communication device based on repetition information, which is determined based on the condition information.

The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

FIG. 1 is a schematic diagram of a UE and base stations, in accordance with some embodiments of the present disclosure.

FIG. 2 is an SRI indication table for non-codebook-based PUSCH transmissions, in accordance with some embodiments of the present disclosure.

FIG. 3 is an SRI indication comparison table based on non-codebook-based PUSCH transmissions, in accordance with some embodiments of the present disclosure.

FIG. 4 is a schematic diagram illustrating a method for wireless communication, in accordance with some embodiments of the present disclosure.

FIG. 5 is a schematic diagram illustrating a method for wireless communication, in accordance with some embodiments of the present disclosure.

FIG. 6A illustrates a block diagram of an example base station, in accordance with some embodiments of the present disclosure; and

FIG. 6B illustrates a block diagram of an example UE, in accordance with some embodiments of the present disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Various example embodiments of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.

Developments in 5G wireless communication systems are directed to achieving higher data communication rate (e.g., in Gbps) , massive number of communication links (e.g., 1 M/Km ²) , ultra-low latency (e.g., under 1 ms) , higher reliability, and improved energy efficiency (e.g., at least 100 times more efficient than previous systems) . To achieve such improvements, in wireless communication systems under the 5G standard, joint transmission has been developed.

Joint transmission or reception of Multiple Transmission and Reception Point (Multi-TRP) is an important technology in wireless communication. Multi-TRP plays a significant role in increasing the throughput of wireless communication, and is supported by Long Term Evolution-Advanced (LTE-A) and New Radio Access Technology (NR) . The multi-panel (Multi-Panel) transmission has been introduced by NR. Multi-Panel transmission refers to the installation of multiple antenna panels at the receiving and/or transmitting ends to improve the spectrum efficiency of the wireless communication system. In addition, in the high-frequency scenario, the multi-beam transmission or receiving of multi-TRP or multi-panel is an effective way of improving reliability and can improve the wireless communication system, especially the transmission reliability of Ultra-reliable and Low Latency Communications (URLLC) .

In non-codebook-based Physical Uplink Shared Channel (PUSCH) transmission, each Sounding Reference Signal (SRS) resource indicated by SRS Resource Indicator (SRI) corresponds to 1 PUSCH transmission layer. Therefore, the SRI indicates the transmission layers of PUSCH implicitly by indicating several SRS resources. However, when applying multi-TRP and multi-panel transmission with multiple beams, SRI index cannot indicate PUSCH transmission layers implicitly.

For multi-TRP transmission, when gNodeB (gNB) schedules an Uplink (UL) transmission, the gNB may transmit different Physical Downlink Control Channel (PDCCH) with downlink control information (DCI) format 0-0 or 0-1 through different TRPs. The two DCIs are associated with different CORESETPoolIndex in order for the User Equipment (UE) to distinguish from which TRP the DCIs came.

FIG. 1 shows an example UE 101 performing PUSCH repetition, which is illustrated by the plurality of beams 110/120. The UE 101 is sending uplink transmissions over a plurality of beams 110, which includes

beam

111, 112, 113, and 114, in communication with base station 102. The UE 101 is also sending uplink transmissions over a plurality of beams 120, which includes

beam

121, 122, 123, and 124, in communication with base station 103. In some examples, each of

base station

102 and 103 can be a TRP. As referred to herein, the UE 101 being configured with a plurality of beams corresponds to the UE 101 using the plurality of beams to transmit and/or receive data, e.g., to perform uplink repetition (e.g., PUSCH repetition) .

UE can perform PUSCH repetition under some specific conditions. In one embodiment, if the UE receives two DCI format 0-0 or 0-1 that have the same Hybrid Automatic Repeat Request (HARQ) process Identity (ID) and the same New Data Indicator (NDI) but are associated with different CORESETPoolIndex, the UE is expected to transmit PUSCH repetitions to the gNB. In another embodiment, if the UE receives two DCI format 0-0 or 0-1 that have the same HARQ ID but are associated with different CORESETPoolIndex, the UE is expected to transmit PUSCH repetitions. In another embodiment, if the UE receives a beam indication indicating multiple beams corresponding to a single PUSCH transmission layer in the uplink repetition, the UE is expected to transmit PUSCH repetitions. In another embodiment, if the UE is configured with a number of repetitions and then receives a beam indication, the UE is expected to transmit PUSCH repetitions.

In each of these embodiments, the UE also determines repetition information, which includes at least one of the beam indication, the transmission pre-coding matrix, power control information, SRS port, PUSCH port, or SRI field size. The UE determines the beam indication using at least one of SRI, the largest rank supported by the UE, the number of beams corresponding to a single PUSCH transmission layer, or the beam diversity indicator. The UE determines the SRI field size according to the largest rank UE can support and the number of beams corresponding to a single layer. The UE determines the transmission precoding matrix based on at least one of the largest rank UE can support, the number of beam indications corresponding to a single layer, the PUSCH transmission time and frequency domain resources, or the number of PUSCH CDM groups. The UE determines the SRS port and PUSCH port based on at least one of the largest rank UE can support, the number of beams corresponding to a single PUSCH transmission layer, the PUSCH transmission time and frequency domain resources, or the number of PUSCH CDM groups.

PUSCH repetition refers to the process in which the UE transmits the same data information several times with multiple beams, via at least one of different time domain resources, different frequency domain resources, different CDM groups, or different transmission layers. The beams correspond to one or more of different time domain resources, frequency domain resources, CDM groups, or transmission layers. When the PUSCH repetitions have overlapping time and frequency domain resources and are configured within a CDM group, the UE determines the transmit power as the largest calculated UE transmit power, the lowest calculated UE transmit power, or the average value of all calculated transmit power.

The beam used above refers to a spatial domain transmission filter that can be determined by at least one of Transmission Configuration Indicator (TCI) state, a SRI, a Quasi Co-Location (QCL) assumption, an SRS index, a Channel State Information (CSI) Reference Signal (RS) index, or a Synchronization Signal Block (SSB) index.

In some arrangements, a DCI can indicate multiple PUSCH beams corresponding to a same layer. Upon receiving a DCI indicating multiple PUSCH beams corresponding to a same layer, the UE can determine that PUSCH repetition is indicated by the DCI. If the transmission layer is configured explicitly, in order to determine (distinguish) the multiple PUSCH beams in the same layer for non-codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetition with multiple beams according to whether the number of SRSs indicated by the SRI is greater than the number of layers. In another embodiment, in order to determine (distinguish) the multiple PUSCH beams in the same layer for non-codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetition with multiple beams according to whether the beam diversity command is “on” . In another embodiment, in order to determine (distinguish) the multiple PUSCH beams in the same layer for non-codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetition with multiple beams according to the number of the indicated TCI states, or the number of SRS resources in 1 TCI codepoint.

For codebook-based uplink transmission, in order to determine (distinguish) the multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetition with multiple beams according to whether different Transmitted Precoding Matrix Indicators (TPMIs) are indicated in a single DCI. In another embodiment, in order to determine (distinguish) the multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetition with multiple beams according to whether the beam diversity command is “on. ” In another embodiment, in order to determine (distinguish) the multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetition with multiple beams according to whether the SRI indicates multiple SRS resources, with the number of SRS resources being larger than the indicated transmission layer. In another embodiment, in order to determine (distinguish) the multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetition with multiple beams according to whether the UE is configured with multiple TCI states, with the number of TCI states being larger than the indicated transmission layer. The UE uses different beams to correspond to a different PUSCH repetition occasion, each PUSCH repetition occasion associates with different time domain resources and/or frequency domain resources,

For non-codebook-based PUSCH transmission, gNB can configure, for PUSCH transmission explicitly, the transmission layer indicator, beam diversity indicator, or the number of beams corresponding to a single layer. If the beam diversity indicator is configured as ‘on’ or ‘open, ’ the UE assumes that the different PUSCH repetition occasions associate with different sending beams. If the beam diversity indicator is otherwise, the UE assumes that the PUSCH repetition occasions associate with the same indicated sending beam. In non-codebook transmissions, the number of beams corresponding to a single layer means that several SRS resources may correspond to a single Demodulation Reference Signal (DMRS) port, or several SRS resources with one port each may correspond to a single PUSCH transmission layer.

PUSCH repetition with different indicated beams refers to the UE transmitting the same data information several times with multiple sending beams to the gNB, with each indicated beam associated either to a non-overlapping frequency and/or time domain resource allocation, or to an overlapping frequency and time domain resource allocation. When the UE is configured for a number of PUSCH repetitions, the UE is expected to transmit PUSCH repetitions with different indicated beams in several situations. In one situation, the UE transmits PUSCH repetitions with different indicated beams if the UE receives a transmission layers indicator and a SRI indicating multiple SRS resources, with the number of indicated SRS resources being greater than the indicated transmission layers. In another situation, the UE transmits PUSCH repetitions with different indicated beams if the UE receives a transmission layer indicator and beam diversity indicator. In another situation, the UE transmits PUSCH repetitions with different indicated beams if the UE receives a transmission layer indicator and is configured with multiple TCI states, with the number of TCI states being greater than the transmission layers. In another situation, the UE transmits PUSCH repetitions with different indicated beams if the UE receives a transmission layer indicator and one TCI state codepoint associated with several SRS resources, with the number of SRS resources being greater than the transmission layers. In these situations, the UE determines the beam indication of PUSCH based on at least one of the SRI, the largest rank the UE can support, the beam indication corresponding to a single layer, or the beam diversity indicator.

The beams referred to above are configured by TCI state, SRI, QCL assumption, SRS index, CSI-RS index, SSB index, spatialrelationinfo, and spatial domain transmission filter.

For codebook-based PUSCH transmissions, gNB can configure multiple TPMIs to the UE through a single DCI or beam diversity indicator via higher layer signaling. When the UE is configured for a number of PUSCH repetitions, the UE is expected to transmit PUSCH repetitions with different indicated beams in the following situations. In one situation, the UE is expected to transmit PUSCH repetitions with different indicated beams if the UE receives different TPMIs in one TPMI codepoint in the scheduling DCI. In another situation, the UE is expected to transmit PUSCH repetitions with different indicated beams if the UE receives the first TPMI in the scheduling DCI and UE is configured the relationship between the first TPMI and the second TPMI. In another situation, the UE is expected to transmit PUSCH repetitions with different indicated beams if the UE receives different TPMIs in two TPMI fields in the scheduling DCI. In another situation, the UE is expected to transmit PUSCH repetitions with different indicated beams if the UE receives a beam diversity indicator. In another situation, the UE is expected to transmit PUSCH repetitions with different indicated beams if the UE receives the SRI indicating multiple SRS resources, with the number of SRS resources being greater than the indicated transmission layer. In another situation, the UE is expected to transmit PUSCH repetitions with different indicated beams if the UE is configured with multiple TCI states, with the number of TCI states being greater than the indicated transmission layer.

The DCI indicates the Modulation and Coding Scheme (MCS) of the first PUSCH transmission occasion, and the UE determines the MCS and Transport Block Size (TBsize) of the second PUSCH transmission according to the first PUSCH transmission occasion. For example, the second PUSCH transmission occasion can have the same MCS and TBsize as the first PUSCH transmission occasion. In some examples, the first PUSCH transmission occasion is the PUSCH repetition associated with one transport block, and the second PUSCH transmission occasion is the PUSCH repetition associated with another transport block. In some examples, the first PUSCH transmission occasion is the PUSCH repetition associated with the first indicated beam, and the second PUSCH transmission occasion is the PUSCH repetition associated with the second indicated beam.

The beam used above refers to a spatial domain transmission filter that can be determined by at least one of the TCI states, spatialrelationinfo, SRI, QCL, SRS index, CSI RS index, or SSB index.

If UE is indicated a SRI index by a base station, and the UE is configured with one of the following: the number of beams corresponding to one layer, the transmission layers, and beam diversity command, the rest two parameters can be determined accordingly. The above SRI index indicates one or multiple SRS resources. For example, the number of layers and the SRI index can be used to determine the number of beams corresponding to a layer. In addition, the number of beams corresponding to a layer and the SRI index can be used to determine the number of layers. Moreover, the beam diversity and the SRI index can be used to determine that, for example, a layer corresponds to two beams, and the number of layers can be determined based on the SRI index and the number of beams corresponding to a layer. The network can transmit a SRI index to the UE to indicate the number of layers used to transmit PUSCHs, whether to use beam diversity, and so on. Accordingly, the network (e.g., a base station, plurality of base stations) can indicate different SRI indexes to allow the UE to flexibly switch to different layers and/or beam diversity settings. The SRI index can also be a SRI codepoint.

Transmission layers, a number of beams corresponding to a layer (a number of SRS resources) , or configuration of beam diversity commands can be preconfigured. By expanding on the table for L _max = 2, L=1 and L=2 dynamic switching can be supported. In some examples, N _SRS=4, SRI indicates the codepoint including ‘0, 1’ , ‘0, 2’ , ‘0, 3’ , ‘1, 2’ , ‘1, 3’ , and ‘2, 3’ . In response to determining that the number of SRS resources corresponding to each DMRS port is 2, that the number of layers (L) is 1, or that beam diversity command is “on, ” the UE determines that the PUSCH transmission is a single-layer transmission, and that different PUSCH repetition occasions correspond to different indicated beams. In response to determining that the number of SRS resources corresponding to each DMRS port is 1, that the number of layers (L) is 2, or that beam diversity command is “off, ” the UE determines that the number of transmission layers of the PUSCH is 2, that each layer corresponds to a beam, and that the beams of all PUSCH repetition occasions are the same.

For L _max greater than 1, gNB configures at least one of the following explicitly: the transmission layer indicator L such that 1<L≤4, the beam diversity indicator q with the

value

0 or 1, or the number of beams s corresponding to a single layer, such that s≥1. The above parameters can be configured through Radio Resource Control (RRC) , MAC-CE, or DCI.

FIG. 2 is a SRI indication table for non-codebook-based PUSCH transmissions, according to an example embodiment. The SRI table of L _max=2, as shown in FIG. 2, is extended with several entries to support L=2 multiple beam PUSCH repetition. To extend the entries of the SRI table, the size of the SRI field in DCI format 0-1 can be changed, for example, as the following equation:

where L _max refers to the maximum number of transmission layers, s refers to the number of beams corresponding to a single layer, N _SRS refers to the number of SRS resources indicated by the SRI index.

When the UE receives a SRI index indicating 2 SRS resources or the UE is indicated by 2 beams for PUSCH transmission, for L _max ≥1, various values for associated parameters indicate different layers of PUSCH repetitions and beams. If L=1, the UE is expected to transmit 1 layer PUSCH repetitions with 2 beams. If q=1, the UE is expected to transmit 1 layer PUSCH repetitions with 2 beams. If s=2, the UE is expected to transmit 1 layer PUSCH repetitions with 2 beams. If L=2, the UE is expected to transmit 2 layer PUSCH repetitions with 2 beams, with each beam corresponding to 1 layer. If q=0, the UE is expected to transmit 2 layer PUSCH repetitions with 2 beams, with each beam corresponding to 1 layer. If s=1, the UE is expected to transmit 2 layer PUSCH repetitions with 2 beams, with each beam corresponding to 1 layer.

The beam used above refers to the spatial domain transmission filter that can be determined by at least one of TCI states, SRI, QCL assumption, spatialrelationinfo, SRS index, CSI-RS index, or SSB index.

If the beam diversity indicator is configured as ‘off, ’ or if the number of beams corresponding to a single layer is 1, the R15 table is used. However, if the beam diversity indicator is configured as ‘on, ’ or if the number of beams corresponding to a single layer equals 2, the table shown in FIG. 3 should be used. FIG. 3 is a SRI indication comparison table based on non-codebook-based PUSCH transmissions. As shown in FIG. 3, if 1 SRI codepoint indicates 2 SRS resources, the UE assumes the PUSCH transmission is 1 layer, and if RRC or DCI indicates the number of PUSCH repetitions, the 2 SRS beams are associated with different PUSCH transmission occasions. If 1 SRI codepoint indicates 4 SRS resources, the UE assumes the PUSCH transmission is 2 layers, and if RRC or DCI indicates the number of PUSCH repetitions, the 4 SRS beams are grouped and associated with different PUSCH transmission occasions, respectively. For an example in which N _SRS=4, if the UE receives SRI between 0 and 5, the UE assumes single layer PUSCH transmission with 2 SRS beams corresponding to different PUSCH transmission occasions. If the UE receives SRI between 6 and 8, the UE assumes 2 layer PUSCH transmission with 4 SRS beams, with the first 2 beams and the second 2 beams corresponding to different PUSCH transmission occasions.

For non-codebook-based PUSCH transmission when PUSCH repetitions are configured with multiple beams corresponding to a single layer or a DMRS port, if the PUSCH DMRS port (s) is indicated with one Code Division Multiplexing (CDM) group in the DCI field “Antenna Port (s) , ” and if PUSCH repetition occasions have at least one of non-overlapping time domain resources, non-overlapping frequency domain resources, or non-overlapping frequency and time domain resources, the UE will transmit PUSCH using the same antenna port (s) as the SRS port (s) in the SRS resource (s) indicated by SRI (s) given by the DCI format 0-1 or by a configured grant, where the SRS port in the SRS resource set is the same for a single layer or DMRS port. In one embodiment, the SRS ports of the PUSCH transmissions that correspond to a single layer have a same port index. In another embodiment, the PUSCH ports of the PUSCH transmissions that correspond to a single layer have a same port index. The precoding matrix of PUSCH transmissions is equal to the identity matrix.

If the PUSCH transmission is 1 layer, the layer is indicated with 2 beams, such that the layer corresponds to 2 SRS resources with the same SRS port index, or 1 DMRS port corresponds to 2 SRS resources with the same SRS port index. If the PUSCH transmission is 2 layers, each layer is indicated with 2 beams, such that each layer corresponds to 2 SRS resources with the same SRS port index, with a different layer corresponding to different SRS port indexes.

For example, layer 1 may correspond to SRS0 and SRS1 with SRS port index 1000, and layer 2 may correspond to SRS2 and SRS3 with SRS port index 1001. The first PUSCH transmission occasion has 2 layers, with sending beams of SRS0 and SRS2 and SRS port index 1000 and 1001, respectively. The second PUSCH transmission occasion has 2 layers, with sending beams of SRS1 and SRS3, SRS port index 1000 and 1001. Different PUSCH transmission occasions correspond to non-overlapping time and/or frequency domain resources.

The UE decides the precoding matrix for PUSCH transmission according to rank information and beam indication. For non-codebook-based PUSCH transmission, when the PUSCH repetitions are configured with multiple beams corresponding to a single layer or DMRS port, if the PUSCH DMRS port (s) is indicated within one CDM group in the DCI field “Antenna Port (s) , ” if PUSCH repetition occasions have non-overlapping time and/or frequency domain resources, or in in response to determining that PUSCH repetition occasions have overlapping time and frequency domain resources, the precoding matrix W is no longer the identity matrix and is to be expanded. For example, the number of rows in W is equal to a product of the number of beam indications per layer and the number of transmission layers, and the number of columns is equal to the number of transmission layers. The SRS port here remains the same as [6, TS 38.214] , i.e., the UE shall transmit the PUSCH using the same antenna ports as the SRS port (s) in the SRS resource (s) indicated by SRI (s) given by DCI format 0-1 or by a higher layer configuration, where the SRS port in the i+1 ^th SRS resource in the SRS resource set is indexed as: p _i = 1000+i

For example, if the PUSCH transmission is 1 layer and the number of beams per layer is 2, the precoding matrix can be given as

If the PUSCH transmission is 2 layers and the number of beams per layer is 2, the precoding matrix can be given as:

or

If the PUSCH DMRS port (s) is indicated within one CDM group in the DCI field “Antenna Port (s) ” and the PUSCH is configured with multiple beams, and if every PUSCH repetition occasion has the same frequency and time domain resources allocation, then the different transmitting power of different beams towards 2 TRPs is determined as 1 transmitting power for the PUSCH transmitting to 2 TRPs using the same time and frequency resources as the same DMRS port (s) .

The UE determines the transmit power of the PUSCH transmitting to 2 TRPs using the same time and frequency resources and the same DMRS port (s) according to different sets of power control parameters. These power control parameters include pathloss reference RS id, p0, and a closed-loop power control parameter. For example, when multiple beams are configured, each beam is associated with a set of power control parameters, and the final transmit power can be determined by at least one of the largest calculated UE transmit power, the lowest calculated UE transmit power, or the average value of all calculated transmit power. The calculated UE transmit power can be determined by the set of power control parameters mentioned above.

The final sending slot of SRS resources or Channel State Information Reference Signal (CSI-RS) is determined as a sum of the configured triggering offset and the slot offset. The triggering offset, between the slot containing the DCI that triggers a set of aperiodic non-zero-power (NZP) CSI-RS and the slot in which the CSI-RS resource set is transmitted, is defined as aperiodicTriggeringOffset or aperiodicTriggeringOffsetExt-r16 in NZP-CSI-RS-ResourceSet. slotOffset in SRS-ResourceSet defines the triggering offset as the number of slots between the triggering DCI and the actual transmission of the SRS-ResourceSet.

The slot offset, which can also be associated with CORESETPoolIndex, is determined by DCI using high-level parameters and is adjusted to ensure the same reference signal triggering time when multiple DCIs are configured. For example, the slot offset can be configured directly in DCI command, or the slot offset can be configured directly in a higher layer parameter. In another example, the higher layer parameter can configure a slot offset pool indicating multiple slot offset values, and the DCI chooses one of these slot offset values for the scheduling reference signal. These higher layer parameters can be RRC parameters such as ControlResourceSet, SearchSpace, NZP-CSI-RS-Resource, SRS-Resource, NZP-CSI-RS-ResourceSet, or SRS-ResourceSet.

FIG. 4 is a schematic diagram illustrating a method 400 for wireless communication, in accordance with some embodiments. The method 400A is performed by a UE, which corresponds to UE 101 of FIG. 1.

At 410, the UE determines that a condition has been satisfied. These conditions are evaluated at 412, 414, 416, and 418. At 412, the UE receives DCIs from the network that have different CORESETPoolIndex values but the same HARQ ID and the same NDI. At 414, the UE receives DCIS from the network that have different CORESETPoolIndex values but the same HARQ ID. At 416, the UE receives a beam indication indicating multiple beams corresponding to a single PUSCH transmission layer used in uplink repetition. At 418, the UE receives a beam indication comprising parameters that define multiple beams. If any one of the conditions evaluated at 412, 414, 416, or 418 is met, the UE performs uplink repetition based on repetition information at step 420. The uplink repetition at 420 corresponds to the plurality of

beams

110 and 120 of FIG. 1. The repetition information is given at 421 and includes beam information, transmission precoding matrix, transmission precoding matrix indicator (TPMI) , power control information, SRS port, PUSCH port, or SRI field size.

FIG. 5 is a schematic diagram illustrating a method 500 for wireless communication, in accordance with some embodiments. The method 500 is performed by a base station or TRP, which corresponds to

base station

102 and 103 from FIG. 1. At 510, the base station transmits condition information. This condition information is established at 512, 514, 516, and 518. At 512, the base station transmits DCIs having different CORESETPoolIndex values but the same HARQ ID and the same NDI. At 514, the base station transmits DCIs having different CORESETPoolIndex values but the same HARQ ID. At 516, the base station transmits a beam indication indicating multiple beams corresponding to a single PUSCH transmission layer used in uplink repetition. At 518, after configuring the UE with a number of repetitions for the uplink repetition, the base station transmits a beam indication indicating multiple beams used in the uplink repetition. After at least one of the condition information is transmitted, the base station receives uplink repetition from the UE at 520. The uplink repetition at 520 corresponds to the plurality of

beams

110 and 120 from FIG. 1. The uplink repetition at 520 is based on repetition information, which is itself determined based on the condition information from 512, 514, 516, or 518.

FIG. 6A illustrates a block diagram of an example base station 602, in accordance with some embodiments of the present disclosure. FIG. 6B illustrates a block diagram of an example UE 601, in accordance with some embodiments of the present disclosure. Referring to FIGS. 1-6B, the UE 601 (e.g., a wireless communication device, a terminal, a mobile device, a mobile user, and so on) is an example implementation of the UEs described herein, and the base station 602 is an example implementation of the base station (s) described herein.

The base station 602 and the UE 601 can include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, the base station 602 and the UE 601 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, as described above. For instance, the base station 602 can be a base station (e.g., gNB, eNB, and so on) , a server, a node, or any suitable computing device used to implement various network functions.

The base station 602 includes a transceiver module 610, an antenna 612, a processor module 614, a memory module 616, and a network communication module 618. The

module

610, 612, 614, 616, and 618 are operatively coupled to and interconnected with one another via a data communication bus 620. The UE 601 includes a UE transceiver module 630, a UE antenna 632, a UE memory module 634, and a UE processor module 636. The

modules

630, 632, 634, and 636 are operatively coupled to and interconnected with one another via a data communication bus 640. The base station 602 communicates with the UE 601 or another base station via a communication channel, which can be any wireless channel or other medium suitable for transmission of data as described herein.

As would be understood by persons of ordinary skill in the art, the base station 602 and the UE 601 can further include any number of modules other than the modules shown in FIGS. 6A and 6B. The various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. The embodiments described herein can be implemented in a suitable manner for each particular application, but any implementation decisions should not be interpreted as limiting the scope of the present disclosure.

In accordance with some embodiments, the UE transceiver 630 includes a radio frequency (RF) transmitter and a RF receiver each including circuitry that is coupled to the antenna 632. A duplex switch (not shown) may alternatively couple the RF transmitter or receiver to the antenna in time duplex fashion. Similarly, in accordance with some embodiments, the transceiver 610 includes an RF transmitter and a RF receiver each having circuity that is coupled to the antenna 612 or the antenna of another base station. A duplex switch may alternatively couple the RF transmitter or receiver to the antenna 612 in time duplex fashion. The operations of the two

transceiver modules

610 and 630 can be coordinated in time such that the receiver circuitry is coupled to the antenna 632 for reception of transmissions over a wireless transmission link at the same time that the transmitter is coupled to the antenna 612. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.

The UE transceiver 630 and the transceiver 610 are configured to communicate via the wireless data communication link, and cooperate with a suitably configured RF antenna arrangement 612/632 that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 610 and the transceiver 610 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 630 and the base station transceiver 610 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

The transceiver 610 and the transceiver of another base station (such as but not limited to, the transceiver 610) are configured to communicate via a wireless data communication link, and cooperate with a suitably configured RF antenna arrangement that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the transceiver 610 and the transceiver of another base station are configured to support industry standards such as the LTE and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the transceiver 610 and the transceiver of another base station may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

In accordance with various embodiments, the base station 602 may be a base station such as but not limited to, an eNB, a serving eNB, a target eNB, a femto station, or a pico station, for example. The base station 602 can be an RN, a regular, a DeNB, or a gNB. In some embodiments, the UE 601 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc. The

processor modules

614 and 636 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Furthermore, the method or algorithm disclosed herein can be embodied directly in hardware, in firmware, in a software module executed by

processor modules

614 and 636, respectively, or in any practical combination thereof. The

memory modules

616 and 634 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard,

memory modules

616 and 634 may be coupled to the

processor modules

614 and 636, respectively, such that the

processors modules

614 and 636 can read information from, and write information to,

memory modules

616 and 634, respectively. The

memory modules

616 and 634 may also be integrated into their

respective processor modules

614 and 636. In some embodiments, the

memory modules

616 and 634 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by

processor modules

614 and 636, respectively.

Memory modules

616 and 634 may also each include non-volatile memory for storing instructions to be executed by the

processor modules

614 and 636, respectively.

The network communication module 618 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 602 that enable bi-directional communication between the transceiver 610 and other network components and communication nodes in communication with the base station 602. For example, the network communication module 618 may be configured to support internet or WiMAX traffic. In a deployment, without limitation, the network communication module 618 provides an 802.3 Ethernet interface such that the transceiver 610 can communicate with a conventional Ethernet based computer network. In this manner, the network communication module 618 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) . In some embodiments, the network communication module 618 includes a fiber transport connection configured to connect the base station 602 to a core network. The terms “configured for, ” “configured to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function.

While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architectural or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

It is also understood that any reference to an element herein using a designation such as "first, " "second, " and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.

Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, for example, which may be referenced in the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

A person of ordinary skill in the art would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software" or a "software module) , or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this document, the term "module" as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.

Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present solution. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.

Claims

A wireless communication method, comprising:

determining, by a wireless communication device, that a condition has been satisfied; and

in response to determining that the condition has been satisfied, performing, by the wireless communications, uplink repetition based on repetition information.
The method of claim 1, wherein

the uplink repetition is a Physical Uplink Shared Channel (PUSCH) repetition; and

the PUSCH repetition corresponds to transmitting same data a plurality of times, via at least one of the following: different time domain resources, different frequency domain resources, different CDM group, or different transmission layers, the wireless communication device is configured with multiple beams.
The method of claim 1, the condition corresponds to receiving Downlink Control Informations (DCIs) from a network, the DCIs having different CORESETPoolIndex, the DCIs having a same Hybrid Automatic Repeat Request (HARQ) Identity (ID) , the DCIs having a same New Data Indicator (NDI) .
The method of claim 1, the condition corresponds to receiving Downlink Control Informations (DCIs) from a network, the DCIs having different CORESETPoolIndex and a same Hybrid Automatic Repeat Request (HARQ) Identity (ID) .
The method of claim 1, the condition corresponds to receiving Downlink Control Informations (DCI) from a network, the DCI having multiple TPMIs.
The method of claim 1, the condition corresponds to receiving a beam indication, and one of:

the beam indication indicates multiple beams corresponding to a single Physical Uplink Shared Channel (PUSCH) transmission layer used in the uplink repetition, or

the beam indication indicates multiple beams corresponding to the Physical Uplink Shared Channel (PUSCH) repetition occasion.
The method of claim 6, the wireless communication determines the beam indication using at least one of a Sounding Reference Signal (SRS) Resource Indicator (SRI) , a largest rank supported by the wireless communication device, a number of beams corresponding to the single PUSCH transmission layer, or a beam diversity indicator.
The method of claim 6, wherein each beam of the multiple beams is configured by one or more of a Transmission Configuration Indicator (TCI) state, a Sounding Reference Signal (SRS) Resource Indicator (SRI) , a Quasi Co-Location (QCL) assumption, an SRS index, a Channel State Information (CSI) Reference Signal (RS) index, a Synchronization Signal Block (SSB) index, spatialrelationinfo, or a spatial domain transmission filter.
The method of claim 1, the condition corresponds to:

the wireless communication device being configured with a number of repetitions for the uplink repetition; and

the wireless communication device receiving a beam indication, the beam indication comprises parameters defining multiple beams.
The method of claim 1, wherein the repetition information comprises at least one of: beam indication, a transmission precoding matrix, a transmission precoding matrix indicator, power control information, a Sounding Reference Signal (SRS) port, a Physical Uplink Shared Channel (PUSCH) port, or an SRS Resource Indicator (SRI) field size.
The method of claim 1, further comprising determining the repetition information.
The method of claim 11, wherein

determining the repetition information comprises determining a Sounding Reference Signal (SRS) Resource Indicator (SRI) field size according to a largest rank supported by the wireless communication device; and

a number of beams used in the uplink repetition corresponds to a single Physical Uplink Shared Channel (PUSCH) transmission layer.
The method of claim 12, wherein determining the repetition information comprises determining a transmission precoding matrix according to at least one of: a largest rank supported by the wireless communication device, a number of beams corresponding to a single Physical Uplink Shared Channel (PUSCH) transmission layer, PUSCH transmission time and frequency domain resources, or a number of PUSCH Code-Division Multiplexing (CDM) group.
The method of claim 11, wherein determining the repetition information comprises determining a Sounding Reference Signal (SRS) port and a Physical Uplink Shared Channel (PUSCH) port according to at least one of: a largest rank supported by the wireless communication device, a number of beams corresponding to a single Physical Uplink Shared Channel (PUSCH) transmission layer, PUSCH transmission time and frequency domain resources, or a number of PUSCH Code-Division Multiplexing (CDM) group.
The method of claim 14, wherein

the uplink repetition corresponds to a plurality of PUSCH transmissions of same data;

the PUSCH transmissions are configured with one CDM group;

a number of rows of a precoding matrix equals to a number of beams corresponding to a single Physical Uplink Shared Channel (PUSCH) transmission layer multiplied by transmission layers; and

a number of columns of the precoding matrix equals to transmission layers.
The method of claim 14, wherein

the uplink repetition corresponds to a plurality of PUSCH transmissions of same data;

the plurality of PUSCH transmissions are configured within one CDM group; and at least one of:

SRS ports of the plurality of PUSCH transmissions that correspond to a single layer have a same port index; or

PUSCH ports of the plurality of PUSCH transmissions that correspond to a single layer have a same port index.
The method of claim 15, wherein

the plurality of PUSCH transmissions have at least one of non-overlapping time domain resources, or non-overlapping frequency domain resources, or non-overlapping frequency and time domain resources, or overlapping time and frequency domain resources.
The method of claim 16, wherein

the plurality of PUSCH transmissions have at least one of non-overlapping time domain resources, or non-overlapping frequency domain resources, or non-overlapping frequency and time domain resources.
The method of claim 11, wherein

the uplink repetition corresponds to a plurality of PUSCH transmissions of same data;

determining the repetition information comprises in response to determining that the plurality of PUSCH transmissions have overlapping time domain resources and frequency domain resources, and that the plurality of PUSCH transmissions are configured with one Code-Division Multiplexing (CDM) group, determining, by the wireless communication device, a transmission power.
The method of claim 19, wherein the transmission power comprises one of a largest calculated transmit power of the wireless communication device, a lowest calculated transmit power of the wireless communication device, or an average value of all calculated transmit power of the wireless communication device.
A wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method recited in any of claims 1 to 20.
A computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 20.
A wireless communication method, comprising:

transmitting, by a network to a wireless communication device, condition information; and

receiving, by the network from the wireless communication device, uplink repetition, wherein the uplink repetition is transmitted by the wireless communication device based on repetition information, the repetition information being determined based on the condition information.
The wireless communication method of claim 23, wherein the condition information comprises Downlink Control Informations (DCIs) , the DCIs having different CORESETPoolIndex, a same Hybrid Automatic Repeat Request (HARQ) Identity (ID) , and a same New Data Indicator (NDI) .
The wireless communication method of claim 23, wherein the condition information comprises Downlink Control Informations (DCIs) , the DCIs having different CORESETPoolIndex and a same Hybrid Automatic Repeat Request (HARQ) Identity (ID) .
The wireless communication method of claim 23, wherein the condition information comprises beam indication, the beam indication indicates multiple beams corresponding to a single Physical Uplink Shared Channel (PUSCH) transmission layer used in the uplink repetition.
The wireless communication method of claim 23, further comprising configuring the wireless communication device with a number of repetitions for the uplink repetition, wherein wherein the condition information comprises beam indication, the beam indication indicates multiple beams used in the uplink repetition.
A wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method recited in any of claims 23 to 27.
A computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a method recited in any of claims 23 to 27.