CN115804187A

CN115804187A - System and method for determining transmission information

Info

Publication number: CN115804187A
Application number: CN202080102595.5A
Authority: CN
Inventors: 潘煜; 蒋创新; 张淑娟; 鲁照华
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-06-30
Filing date: 2020-06-30
Publication date: 2023-03-14
Also published as: WO2022000262A1

Abstract

The embodiment of the invention provides a system and a method for determining wireless communication. The wireless communication device determines whether a condition is satisfied and, if it is determined that the condition is satisfied, the wireless communication device performs an uplink repeat transmission, such as a Physical Uplink Shared Channel (PUSCH) repeat transmission.

Description

System and method for determining transmission information

Technical Field

The embodiment of the invention relates to the field of communication, in particular to uplink repeated transmission.

Background

The demand for fifth generation mobile communication technology (5G) is rapidly increasing. The provision of enhanced mobile broadband, ultra-high reliability, ultra-low latency transmission and large-scale connectivity in 5G systems is under development.

Disclosure of Invention

Example embodiments of the present disclosure are directed to solving problems associated with one or more of the problems set forth in the prior art, and providing additional features that will be readily apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, apparatus, and computer program products are disclosed herein. It is to be understood, however, that these embodiments are presented by way of example, and not limitation, and that various modifications to the disclosed embodiments, while remaining within the scope of the invention, will be apparent to those skilled in the art upon reading this disclosure.

In some embodiments, the wireless communication device determines that a condition has been met and, in response, performs an uplink repeat transmission based on the repeat information.

In some embodiments, the network sends condition information to the wireless communication device and receives an uplink duplicate transmission from the wireless communication device. The uplink repeat transmission is sent by the wireless communication device based on the repetition information (which is determined based on the condition information).

The above and other aspects and implementations thereof are described in more detail in the accompanying drawings, embodiments and claims.

Drawings

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

Fig. 1 is a schematic diagram of a UE and a base station in accordance with some embodiments of the present invention.

Fig. 2 is an SRI indicator table for non-codebook based PUSCH transmission in accordance with some embodiments of the present invention.

Fig. 3 is a SRI indication look-up table for non-codebook based PUSCH transmissions in accordance with some embodiments of the present invention.

Fig. 4 is a schematic diagram illustrating methods for wireless communication in accordance with some embodiments of the present invention.

Fig. 5 is a schematic diagram illustrating a method for wireless communication in accordance with some embodiments of the present invention.

Fig. 6A illustrates a block diagram of an example base station in accordance with some embodiments of the invention; and

fig. 6B illustrates a block diagram of an example UE in accordance with some embodiments of the invention.

Detailed Description

Various example embodiments of the present solution are described below with reference to the drawings to enable one of ordinary skill in the art to make and use the present solution. It will be apparent to those of ordinary skill in the art that, after reading this disclosure, various changes or modifications may be made to the examples described herein 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 particular order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based upon design preferences, the particular order or hierarchy of steps in the methods or processes disclosed may be rearranged while remaining within the scope of the present solution. Accordingly, one of ordinary skill in the art will understand that the methods and techniques disclosed herein present the various steps or actions in a sample order, and unless otherwise explicitly stated, the present solutions are not limited to the specific order or hierarchy presented.

The development of 5G wireless communication systems is oriented toward achieving higher data communication rates (e.g., in Gbps), large numbers of communication links (e.g., 1M/Km) ² ) Ultra-low latency (e.g., less than 1 ms), higher reliability, and higher energy efficiency (e.g., at least 100 times more efficient than previous systems). In order to achieve such an improvement, joint transmission has been developed in a wireless communication system under the 5G standard.

Joint transmission or reception of multiple transmit-receive points (Multi-TRP) is an important technology in wireless communications. Multiple TRPs play an important role in improving wireless communication throughput and are supported by long term evolution advanced (LTE-a) and New Radio Access Technology (NR). NR describes a Multi-Panel (Multi-Panel) transmission. Multi-panel transmission refers to mounting a plurality of antenna panels at a receiving and/or transmitting end to improve the spectral efficiency of a wireless communication system. In addition, in a high frequency scene, multi-TRP or multi-panel multi-beam transmission or reception is an effective way to improve reliability and can improve transmission reliability of a wireless communication system, especially ultra-reliable low-latency communication (URLLC).

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

For multiple TRP transmissions, when a gandeb (gNB) schedules Uplink (UL) transmissions, the gNB may send different Physical Downlink Control Channels (PDCCHs) with Downlink Control Information (DCI) formats 0-0 or 0-1 through different TRPs. The two DCIs are associated with different coresetpoilndex in order for the User Equipment (UE) to distinguish which TRP the DCI comes from.

Fig. 1 shows an example UE101 performing PUSCH repetition, illustrated by multiple beams 110/120. UE101 is transmitting uplink transmissions over a plurality of beams 110, including

beams

111, 112, 113, and 114, in communication with base station 102. UE101 also transmits uplink transmissions on a plurality of beams 120, including

beams

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

base stations

102 and 103 may be a TRP. As described herein, a UE101 configured with multiple beams corresponds to a UE101 that transmits and/or receives data using multiple beams, e.g., performs uplink repetition transmission (e.g., PUSCH repetition).

The UE may perform PUSCH repetition under certain specific conditions. In one embodiment, if the UE receives two DCI formats 0-0 or 0-1 that have the same Hybrid Automatic Repeat Request (HARQ) process Identification (ID) and the same New Data Indicator (NDI) but are associated with different coresetpoilndex, it is expected that the UE sends a PUSCH repetition to the gNB. In another embodiment, if the UE receives two DCI formats 0-0 or 0-1 with the same HARQ ID but associated with different coresetpoilndex, the UE is expected to send a PUSCH repetition. In another embodiment, the UE is expected to send a PUSCH repetition if the UE receives a beam indication indicating multiple beams corresponding to a single PUSCH transmission layer in an uplink repetition transmission. In another embodiment, if the UE is configured with multiple repetitions and then receives the beam indication, it is desirable for the UE to send a PUSCH repetition.

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

The PUSCH repetition refers to a process in which the UE transmits the same data information with multiple beams multiple times through 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 repeats have overlapping time and frequency domain resources and are configured within a CDM group, the UE determines the transmit power as the maximum calculated UE transmit power, the lowest calculated UE transmit power, or an average of all calculated transmit powers.

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

In some implementations, the DCI may indicate multiple PUSCH beams corresponding to the same layer. Upon receiving DCI indicating a plurality of PUSCH beams corresponding to the same layer, the UE may determine that the PUSCH repetition is indicated by the DCI. If the transmission layer is explicitly configured, to determine (distinguish) multiple PUSCH beams in the same layer for non-codebook based uplink transmission, the UE determines whether to transmit a 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, to determine (distinguish) multiple PUSCH beams in the same layer for non-codebook based uplink transmission, the UE determines whether to transmit a PUSCH repetition in multiple beams according to whether the beam diversity command is "on". In another embodiment, to determine (distinguish) multiple PUSCH beams in the same layer for non-codebook based uplink transmission, the UE determines whether to transmit a PUSCH repetition in multiple beams according to the number of indicated TCI states or the number of SRS resources in 1 TCI codepoint.

For codebook-based uplink Transmission, in order to determine (distinguish) a plurality of PUSCH beams in the same layer for codebook-based uplink Transmission, the UE determines whether or not a PUSCH repetition is transmitted in a plurality of beams according to whether or not a different Transmission Precoding Matrix Indicator (TPMI) is indicated in a single DCI. In another embodiment, to determine (distinguish) multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit a PUSCH repetition in multiple beams according to whether the beam diversity command is "on". In another embodiment, to determine (distinguish) multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit a PUSCH repetition with multiple beams depending on whether the SRI indicates multiple SRS resources (where the number of SRS resources is greater than the indicated transmission layer). In another embodiment, to determine (distinguish) multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit a PUSCH repetition in multiple beams depending on whether the UE is configured with multiple TCI states (where the number of TCI states is greater than the indicated transmission layer). The UE uses different beams to correspond to different PUSCH repetition transmission scenarios, each PUSCH repetition transmission scenario being associated with a different time and/or frequency domain resource.

For non-codebook based PUSCH transmissions, the gNB may explicitly configure a transmission layer indicator, a beam diversity indicator, or a number of beams corresponding to a single layer for PUSCH transmissions. If the beam diversity indicator is configured to be "on" or "on," the UE assumes that different PUSCH repeated transmission scenarios are associated with different transmit beams. If the beam diversity indicator is not, the UE assumes that the PUSCH repeated transmission scenario is associated with the same indicated transmit beam. In non-codebook transmission, 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 each having one port may correspond to a single PUSCH transmission layer.

PUSCH repetition with different indication beams means that the UE transmits the same data information to the gNB multiple times with multiple transmit beams, where each indication beam is associated with a non-overlapping frequency and/or time domain resource allocation, or with an overlapping frequency and time domain resource allocation. When the UE is configured with multiple PUSCH repetitions, it is desirable for the UE to transmit PUSCH repetitions in different indication beams in several cases. In one case, if the UE receives a transmission layer indicator and SRI indicating multiple SRS resources (where the number of SRS resources indicated is greater than the indicated transmission layer), the UE transmits a PUSCH repetition with a different indication beam. In another case, if the UE receives the transport layer indicator and the beam diversity indicator, the UE transmits the PUSCH repetition with a different indication beam. In another case, if the UE receives the transmission layer indicator and is configured with multiple TCI states (where the number of TCI states is greater than the transmission layer), the UE transmits PUSCH repetitions in different indication beams. In another case, if the UE receives transmission layer indicators associated with several SRS resources and one TCI status codepoint (where the number of SRS resources is greater than the transmission layer), the UE sends PUSCH repetitions with different indication beams. In these cases, the UE determines a beam indication for the PUSCH based on at least one of the SRI, a maximum rank that the UE can support, a beam indication corresponding to a single layer, or a beam diversity indicator.

The beam is configured by a TCI state, SRI, QCL hypothesis, SRS index, CSI-RS index, SSB index, spatial relationship information (spatiallationsinfo), and spatial transmission filter.

For codebook-based PUSCH transmission, the gNB may configure multiple TPMIs to the UE through higher layer signaling through a single DCI or beam diversity indicator. When the UE is configured with multiple PUSCH repetitions, it is desirable for the UE to transmit PUSCH repetitions in different indication beams in the following cases. In one case, if the UE receives a different TPMI in one TPMI code point in the scheduling DCI, the UE is expected to transmit a PUSCH repetition with a different indication beam. In another case, if the UE receives the first TPMI in the scheduling DCI and the UE configures a relationship between the first TPMI and the second TPMI, it is desirable that the UE transmits the PUSCH repetition in a different indication beam. In another case, if the UE receives different TPMI in two TPMI fields in the scheduling DCI, the UE is expected to transmit a PUSCH repetition with a different indication beam. In another case, if the UE receives the beam diversity indicator, the UE is expected to transmit a PUSCH repetition with a different indication beam. In another case, if the UE receives an SRI indicating multiple SRS resources (where the number of SRS resources is greater than the indicated transmission layer), the UE is expected to send PUSCH repetitions in different indicated beams. In another case, if the UE is configured with multiple TCI states, where the number of TCI states is greater than the indicated transmission layer, the UE is expected to transmit PUSCH repetitions in different indicated beams.

The DCI indicates a 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 may have the same MCS and TBsize as the first PUSCH transmission occasion. In some examples, the first PUSCH transmission occasion is a PUSCH repetition associated with one transport block and the second PUSCH transmission occasion is a PUSCH repetition associated with another transport block. In some examples, the first PUSCH transmission occasion is a PUSCH repetition associated with the first indication beam and the second PUSCH transmission occasion is a PUSCH repetition associated with the second indication beam.

The beam used above refers to a spatial transmission filter that may be determined by at least one of a TCI state, spatial relationship info, SRI, QCL, SRS index, CSI RS index, or SSB index.

If the base station indicates the SRI index to the UE, and the UE is configured with one of the following: the number of beams corresponding to one layer, the transmission layer and the beam diversity command, the remaining two parameters can be determined accordingly. The SRI index indicates one or more SRS resources. For example, the number of layers and the SRI index may 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 may be used to determine the number of layers. Further, a layer corresponding to two beams, for example, may be determined using the beam diversity and the SRI index, and the number of layers may be determined based on the SRI index and the number of beams corresponding to a layer. The network may send an SRI index to the UE to indicate the number of layers used to send the PUSCHs, whether beam diversity is used, etc. Thus, the network (e.g., base station, base stations) may indicate different SRI indices to allow the UE to flexibly switch to different layer and/or beam diversity settings. The SRI index may also be an SRI codepoint.

The configuration of the transmission layer, the plurality of beams (the plurality of SRS resources) corresponding to the layer, or the beam diversity command may be previously configured. By expanding L in the table _max =2, dynamic switching of L =1 and L =2 can be supported. In some examples, N _SRS "4, SRI indicates code points including '0, 1', '0, 2', '0, 3', '1, 2', '1, 3', and '2, 3'. Responsive to determining that the number of SRS resources corresponding to each DMRS port is 2The number of layers (L) is 1, or the beam diversity command is "on", the UE determines that the PUSCH transmission is a single-layer transmission, and different PUSCH repeated transmission scenarios correspond to different indicated beams. In response to determining that the number of SRS resources corresponding to each DMRS port is 1, the number of layers (L) is 2, or the beam diversity command is "off", the UE determines that the number of transmission layers of the PUSCH is 2, each layer corresponds to a beam, and the beams of all PUSCH repeated transmission scenarios are the same.

For L _max Greater than 1, gnb explicitly configures at least one of: the layer indicator L is transmitted such that 1 < L ≦ 4, the beam diversity indicator q, whose value is 0 or 1, or corresponds to the number of beams s for a single layer such that s ≧ 1. The above parameters may be configured through Radio Resource Control (RRC), MAC-CE, or DCI.

Fig. 2 is a SRI indication table for non-codebook based PUSCH transmission according to an example embodiment. As shown in FIG. 2, L _max SRI table of =2 is extended by several entries to support multi-beam PUSCH repetition of L = 2. To extend the entry of the SRI table, the size of the SRI field in DCI format 0-1 may be changed, for example, as shown in the following equation:

wherein L is _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.

For L when the UE receives the SRI index indicating 2 SRS resources or the UE is indicated by 2 beams for PUSCH transmission _max ≧ 1, various values of the correlation parameter indicate PUSCH repetition and different layers of the beam. If L =1, the UE is expected to transmit a 1-layer PUSCH repetition with 2 beams. If q =1, the UE is expected to transmit a 1-layer PUSCH repetition with 2 beams. If s =2, the UE is expected to transmit a 1-layer PUSCH repetition with 2 beams. If L =2, the UE is expected to transmit a 2-layer PUSCH repetition with 2 beams, each corresponding to 1 layer. If q =0, the UE is expected to transmit a 2-layer PUSCH repetition with 2 beams,each beam corresponds to 1 layer. If s =1, the UE is expected to transmit a 2-layer PUSCH repetition with 2 beams, each corresponding to 1 layer.

The beam used above refers to a spatial transmission filter that may be determined by at least one of a TCI state, SRI, QCL hypothesis, spatiallationsinfo, SRS index, CSI-RS index, or SSB index.

The R15 table is used if the beam diversity indicator is configured to be "off" or if the number of beams corresponding to a single layer is 1. However, if the beam diversity indicator is configured to be "on", or if the number of beams corresponding to a single layer is equal to 2, the table shown in fig. 3 should be used. Fig. 3 is a table comparing SRI indications for non-codebook based PUSCH transmissions. As shown in fig. 3, if 1 SRI code point indicates 2 SRS resources, the UE assumes PUSCH transmission is layer 1, and if RRC or DCI indicates PUSCH repetition number, 2 SRS beams are associated with different PUSCH transmission occasions. If 1 SRI code point indicates 4 SRS resources, the UE assumes PUSCH transmission is layer 2, and if RRC or DCI indicates PUSCH repetition number, 4 SRS beams are grouped and associated with different PUSCH transmission occasions, respectively. For N _SRS An example of =4, if the UE receives an SRI between 0 and 5, the UE employs single-layer PUSCH transmission (with 2 SRS beams corresponding to different PUSCH transmission occasions). If the UE receives an SRI between 6 and 8, the UE employs a layer 2 PUSCH transmission of 4 SRS beams (where the first 2 beams and the last 2 beams correspond to different PUSCH transmission occasions).

For non-codebook based PUSCH transmission, when the PUSCH is repeatedly configured with multiple beams corresponding to a single layer or DMRS ports, if the PUSCH DMRS ports are indicated with one Code Division multiple access (CDM) group in the DCI field "antenna port", and if the PUSCH repeated transmission scenario has 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 the PUSCH using the same antenna port as the SRS port in the SRS resource indicated by the SRI given by DCI format 0-1 or 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, SRS ports corresponding to a single layer PUSCH transmission have the same port index. In another embodiment, PUSCH ports corresponding to a single layer of PUSCH transmissions have the same port index. The precoding matrix for PUSCH transmission is equal to the identity matrix.

If the PUSCH transmission is layer 1, the layer is indicated with 2 beams such that the layer corresponds to 2 SRS resources having the same SRS port index, or 1 DMRS port corresponds to 2 SRS resources having 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, and different layers correspond to different SRS port indices.

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 SRS0 and SRS2 transmit beams, and SRS port indices 1000 and 1001, respectively. The second PUSCH transmission scenario has 2 layers with SRS1 and SRS3 transmit beams, SRS port indices 1000 and 1001. Different PUSCH transmission occasions correspond to non-overlapping time and/or frequency domain resources.

And the UE determines a precoding matrix of the PUSCH transmission according to the rank information and the beam indication. For non-codebook based PUSCH transmissions, when the PUSCH is repeatedly configured with multiple beams corresponding to a single layer or DMRS ports, the precoding matrix W is no longer an identity matrix and will be extended if the PUSCH DMRS ports are indicated within one CDM group in the DCI field "antenna ports", if the PUSCH repeated transmission scenario has non-overlapping time and/or frequency domain resources, or in response to determining that the PUSCH repeated transmission scenario has overlapping time and frequency domain resources. For example, the number of rows in W is equal to the product of the number of beam indicators per layer and the number of transmission layers, and the number of columns is equal to the number of transmission layers. Here the SRS port is kept with [6,TS 38.214 ]]The same, i.e. the UE shall transmit PUSCH using the same antenna port as the SRS port in the SRS resource indicated by DCI format 0 _ 1 or SRI given by higher layer configuration, where the index of the SRS port in the i +1 th SRS resource in the SRS resource set is: p is a radical of _i ＝1000+i。

For example, if the PUSCH transmission is layer 1,and the number of beams per layer is 2, a 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 may be:

or

If the PUSCH DMRS port is indicated in the DCI field "antenna port" within one CDM group, and the PUSCH is configured with multiple beams, and if each PUSCH repeated transmission scenario has the same frequency and time domain resource allocation, different transmission power of different beams for 2 TRPs is determined as 1 transmission power of the PUSCH transmitting to 2 TRPs using the same time and frequency resources as the same DMRS port.

And the UE determines the transmission power of the PUSCH transmitted to the 2 TRPs by using the same time and frequency resources and the same DMRS port according to the power control parameters of different groups. These power control parameters include the path loss reference RS id, p0 and the closed loop power control parameters. For example, when multiple beams are configured, each beam is associated with a set of power control parameters, and the final transmit power may be determined by at least one of a maximum calculated UE transmit power, a lowest calculated UE transmit power, or an average of all calculated transmit powers. The calculated UE transmit power may be determined by the set of power control parameters described above.

A final transmission slot of an SRS resource or a channel state information reference signal (CSI-RS) is determined as a sum of a configured trigger offset and a slot offset. A trigger offset between a slot containing DCI triggering a set of aperiodic non-zero power (NZP) CSI-RSs and a slot transmitting a set of CSI-RS resources is defined as aperiodicTriggeringOffset or aperiodicTriggeringOffseExt-r 16 in the NZP-CSI-RS-ResourceSeet. slotOffset in SRS-ResourceSet defines the trigger offset as the number of slots between the trigger DCI and the actual transmission of SRS-ResourceSet.

The slot offset (which may also be associated with coresetpoolndex) is determined by DCI using advanced parameters and adjusted to ensure the same reference signal trigger time when configuring multiple DCIs. For example, the slot offset may be configured directly in the DCI command, or may be configured directly in a higher layer parameter. In another example, the higher layer parameters may configure a slot offset pool representing a plurality of slot offset values, and the DCI selects one of the slot offset values for the scheduling reference signal. These higher layer parameters may be RRC parameters such as ControlResourceSeet, searchSpace, NZP-CSI-RS-Resource, SRS-Resource, NZP-CSI-RS-Resource Seet or SRS-Resource Seet.

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 corresponding to the UE101 of FIG. 1.

In step 410, the ue determines that the condition has been satisfied. These conditions are evaluated at

steps

412, 414, 416 and 418. In step 412, the ue receives DCI having different coresetpoilndex values but the same HARQ ID and the same NDI from the network. In step 414, the ue receives DCI having different coresetpoilndex values but the same HARQ ID from the network. In step 416, the ue receives a beam indication indicating a plurality of beams corresponding to a single PUSCH transmission layer used in uplink repetition transmission. In step 418, the ue receives a beam indication including parameters defining a plurality of beams. If any of the conditions evaluated at

steps

412, 414, 416 or 418 is satisfied, the ue performs uplink repetition transmission based on the repetition information at step 420. The uplink repeat transmission at step 420 corresponds to the

multiple beams

110 and 120 of fig. 1. The repetition information is given in step 421 and includes beam information, a 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. Method 500 is performed by a base station or TRP, which corresponds to

base stations

102 and 103 in fig. 1. In step 510, the base station transmits condition information. The condition information is established in

steps

512, 514, 516 and 518. In step 512, the base station transmits DCI having different coresetpoilndex values but the same HARQ ID and the same NDI. In step 514, the base station transmits DCI having different coresetpoilndex values but the same HARQ ID. In step 516, the base station transmits a beam indication indicating a plurality of beams corresponding to a single PUSCH transmission layer used in uplink repetition transmission. In step 518, after configuring the UE with the number of repetitions for the uplink repeat transmission, the base station transmits a beam indication indicating a plurality of beams used in the uplink repeat transmission. After the at least one condition information is transmitted, the base station receives an uplink repetition transmission from the UE in step 520. The uplink repeat transmission at step 520 corresponds to the

multiple beams

110 and 120 in fig. 1. The uplink repeat transmission at step 520 is based on the repeat information, which itself is determined based on the condition information from

steps

512, 514, 516 or 518.

Fig. 6A illustrates a block diagram of an example base station 602, in accordance with some embodiments of the invention. Fig. 6B shows a block diagram of an example UE601, in accordance with some embodiments of the present invention. With reference to fig. 1-6b, a UE601 (e.g., a wireless communication device, terminal, mobile device, mobile user, etc.) is an example implementation of a UE described herein and a base station 602 is an example implementation of a base station described herein.

Base station 602 and UE601 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, base station 602 and UE601 can be employed to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, as described supra. For example, base station 602 can be a base station (e.g., a gNB, eNB, etc.), a server, a node, or any suitable computing device for implementing 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

modules

610, 612, 614, 616, and 618 are operatively coupled and interconnected to one another via a data communication bus 620. The UE601 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 and interconnected with each other via a data communication bus 640. Base station 602 communicates with UE601 or another base station via a communication channel, which may be any wireless channel or other medium suitable for data transmission as described herein.

As understood by one of ordinary skill in the art, the base station 602 and UE601 may further include any number of modules in addition to those shown in fig. 6A and 6B. The various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented as 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 have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software depends upon the particular application and design constraints imposed on the overall system. The embodiments described herein may be implemented in a manner suitable for each particular application, but any implementation decisions should not be interpreted as limiting the scope of the present invention.

According to some embodiments, UE transceiver 630 includes a Radio Frequency (RF) transmitter and an RF receiver, each including circuitry coupled to an antenna 632. A duplex switch (not shown) may alternatively couple the RF transmitter or receiver to the antenna in a time-duplex manner. Similarly, in accordance with some embodiments, transceiver 610 includes an RF transmitter and an RF receiver, each having circuitry coupled to antenna 612 or an antenna of another base station. The duplex switch may alternatively couple the RF transmitter or receiver to the antenna 612 in a time-duplex manner. The operation of the two

transceiver modules

610 and 630 can be coordinated in time such that the receiver circuitry is coupled to the antenna 632 in order to receive transmissions over the wireless transmission link while the transmitter is coupled to the antenna 612. In some embodiments, there is tight time synchronization with minimal guard time between changes in duplex direction.

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

The transceiver 610 and a transceiver of another base station (e.g., without limitation, 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 demonstrative embodiments, transceiver 610 and the transceiver of another base station are configured to support industry standards, such as the LTE and emerging 5G standards. It will be appreciated, however, that the invention is not necessarily limited to the application of a particular standard and associated protocol. Rather, the transceiver 610 and the transceiver of another base station may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

According to 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. The base station 602 may be an RN, a regular, deNB, or a gNB. In some embodiments, the UE601 may be embodied in various types of user equipment, such as a mobile phone, a smartphone, a Personal Digital Assistant (PDA), a tablet, a laptop, a wearable computing device, and so forth. 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, for performing the functions described herein. In this manner, the processor may be implemented as a microprocessor, controller, microcontroller, 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 methods or algorithms disclosed in the present invention may be embodied directly in hardware, in firmware, in a software module executed by the

processor modules

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

Memory modules

616 and 634 may be implemented 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, the

memory modules

616 and 634 may be coupled to the

processor modules

614 and 636, respectively, such that the

processor modules

614 and 636 may read information from, and write information to, the

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 cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by the

processor modules

614 and 636, respectively. The

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 bidirectional communication between the transceiver 610 and other network components as well as communication nodes in communication with the base station 602. For example, the network communication module 618 may be configured to support internet or WiMAX services. In a non-limiting deployment, 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 connecting to a computer network, such as a Mobile Switching Center (MSC). In some embodiments, the network communication module 618 includes a fiber optic transmission connection configured to connect the base station 602 to a core network. The terms "configured to," "configured to," and their conjugates, as used herein with respect to a particular 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 particular 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 limitation. Likewise, the various figures may depict example architectures or configurations provided to enable one of ordinary skill in the art to understand the example features and functionality of the present solution. However, those skilled in the art will appreciate that the present solution is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, as one of ordinary skill in the art will appreciate, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments.

It will also be understood that any reference herein to elements using a name such as "first," "second," etc., does not generally limit the number or order of those elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to first and second elements does not imply that only two elements are used or that the first element must be somehow before the second element.

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

Those of ordinary skill would further appreciate that any of the various illustrative logical blocks, modules, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two), firmware, various forms of program or design code containing instructions (which may be referred to herein, for convenience, as "software" or a "software module"), or any combination of these technologies. 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 as a combination of such techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

Furthermore, those of ordinary skill in the art will appreciate that the various illustrative logical blocks, modules, devices, components, and circuits described herein may be implemented or performed with Integrated Circuits (ICs) including general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs), or other Programmable logic devices, or any combination thereof. The logic blocks, modules and circuits may further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller or state machine. A processor may 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 may be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein may 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 cause a computer program or code to be transferred from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise 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.

As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements to perform the relevant functions described herein. In addition, for purposes of discussion, the various modules are described as discrete modules; however, it is obvious to a person skilled in the art that two or more modules may be combined to form a single module performing the relevant functions according to embodiments of the present solution.

Additionally, memory or other storage and communication components may be employed in embodiments of the present solution. It should be appreciated that for clarity 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 solution. For example, functionality illustrated to be performed by separate processing logic elements or controllers may be performed by the same processing logic elements or controllers. Thus, references to specific functional units are only to references to 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 generic principles defined herein may be applied to other implementations without departing from the scope of the disclosure. Thus, the present 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 set forth in the following claims.

Claims

1. A method of wireless communication, comprising:

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

in response to determining that the condition has been met, the wireless communication device performs an uplink repeat transmission based on repeat information.

2. The method of claim 1, wherein

The uplink repeated transmission is a Physical Uplink Shared Channel (PUSCH) repeated transmission; and

the PUSCH repetition transmission corresponds to transmitting the same data multiple times by at least one of: different time domain resources, different frequency domain resources, different CDM groups, or different transmission layers, the wireless communication device configured with a plurality of beams.

3. The method of claim 1, the condition corresponding to receiving Downlink Control Information (DCI) from a network, the DCI having different CORESETPoolIndex, the DCI having a same hybrid automatic repeat request identification (HARQ ID), the DCI having a same New Data Indicator (NDI).

4. The method of claim 1, the condition corresponding to receiving Downlink Control Information (DCI) from a network, the DCI having a different CORESETPoolIndex and a same hybrid automatic repeat request identification (HARQ ID).

5. The method of claim 1, the condition corresponding to receiving Downlink Control Information (DCI) from a network, the DCI having a plurality of TPMI.

6. The method of claim 1, the condition corresponding to a receive beam indication and one of:

the beam indication indicates a plurality of beams corresponding to a single physical uplink shared channel, PUSCH, transmission layer using repeated transmissions on the uplink, or

The beam indication is used for indicating a plurality of beams corresponding to the physical uplink shared channel, PUSCH, repeated transmission.

7. The method of claim 6, the wireless communication device determining the beam indication by at least one of: a sounding reference Signal Resource Indicator (SRI), a maximum rank supported by the wireless communication device, a number of beams corresponding to the single PUSCH transmission layer, a beam diversity indicator.

8. The method of claim 6, wherein each beam of the plurality of beams is configured by one or more of: a Transmission Configuration Indicator (TCI) state, a sounding reference Signal (SRI) resource indicator (SRI), a quasi co-located QCL hypothesis, an SRS index, a Channel State Information (CSI) Reference Signal (RS) index, a Synchronization Signal Block (SSB) index, spatial relationship information (spatiallationsinfo), and a spatial domain transmission filter.

9. The method of claim 1, the condition corresponding to:

the wireless communication device is configured with a number of repetitions for the uplink repeated transmission; and

the wireless communication device receives a beam indication comprising parameters defining a plurality of beams.

10. The method of claim 1, wherein the repeated transmission of information comprises at least one of: beam indication, transmission precoding matrix indicator, power control information, sounding Reference Signal (SRS) port, physical Uplink Shared Channel (PUSCH) port, SRS Resource Indicator (SRI) field size.

11. The method of claim 1, further comprising:

determining the repeated transmission information.

12. The method of claim 11, wherein determining the repeated transmission information comprises:

determining a Sounding Reference Signal (SRS) resource indicator (SRI) field size according to a maximum rank supported by the wireless communication device; and using the number of beams of a single physical uplink shared channel, PUSCH, transmission layer that is repeatedly transmitted on the uplink.

13. The method of claim 12, wherein determining the repeated transmission information comprises: determining a transmission precoding matrix based on at least one of: a maximum rank supported by the wireless communication device, a number of beams corresponding to a single physical uplink shared channel, PUSCH, transmission time and frequency domain resource, a number of PUSCH code division multiple Access, CDM, groups.

14. The method of claim 11, wherein determining the repeated transmission information comprises: determining a sounding reference signal, SRS, port and a physical uplink shared channel, PUSCH, port according to at least one of: a maximum rank supported by the wireless communication device, a number of beams corresponding to a single physical uplink shared channel, PUSCH, transmission time and frequency domain resources, a number of PUSCH code division multiple Access, CDM, groups.

15. The method of claim 14, wherein

The uplink repeat transmission corresponds to multiple PUSCH transmissions of the same data;

the PUSCH transmission is configured with one CDM group;

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

the number of columns of the precoding matrix is equal to the number of transmission layers.

16. The method of claim 14, wherein

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

SRS ports corresponding to a single layer of multiple PUSCH transmissions have the same port index; or

PUSCH ports corresponding to a single layer of multiple PUSCH transmissions have the same port index.

17. The method of claim 15, wherein

The plurality of PUSCH transmissions have at least one of: non-overlapping time domain resources, non-overlapping frequency and time domain resources, overlapping time and frequency domain resources.

18. The method of claim 16, wherein

The plurality of PUSCH transmissions have at least one of: non-overlapping time domain resources, non-overlapping frequency domains, and time domain resources.

19. The method of claim 11, wherein

determining the duplicate transmission information comprises: determining, by the wireless communication device, a transmit power 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 multiple Access (CDM) group.

20. The method of claim 19, wherein the transmit power comprises one of: a maximum calculated transmit power of the wireless communication device, a minimum calculated transmit power of the wireless communication device, an average of all calculated transmit powers of the wireless communication device.

21. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method of any of claims 1 to 20.

22. A computer program product comprising a computer readable program medium code stored thereon, which when executed by a processor causes the processor to implement the method of any of claims 1 to 20.

23. A method of wireless communication, comprising:

transmitting the condition information to the wireless communication device through the network; and

receiving, by the network, an uplink repeat transmission from the wireless communication device, wherein the uplink repeat transmission is transmitted by the wireless communication device based on repeat transmission information determined based on the condition information.

24. The wireless communication method of claim 23, wherein the condition information comprises Downlink Control Information (DCI) having different CORESETPoolIndex, a same hybrid automatic repeat request identification (HARQID), and a same New Data Indicator (NDI).

25. The wireless communication method of claim 23, wherein the condition information comprises Downlink Control Information (DCI) having different CORESETPoolIndex and same hybrid automatic repeat request identity (HARQ ID).

26. The wireless communication method of claim 23, wherein the condition information comprises a beam indication indicating a plurality of beams corresponding to a single Physical Uplink Shared Channel (PUSCH) transmission layer used in the uplink repetition transmission.

27. The wireless communication method of claim 23, further comprising:

configuring the wireless communication device with a number of repetitions of the uplink repetition transmission, wherein the condition information includes a beam indication indicating a plurality of beams used in the uplink repetition transmission.

28. A wireless communication device comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method of any of claims 23 to 27.

29. A computer program product comprising a computer readable program medium code stored thereon, which when executed by a processor causes the processor to implement the method of any of claims 23 to 27.