System and Method for Determining Transmission Information

Abstract

An embodiment of the present invention provides a determination system and method for wireless communication. A wireless communication device determines whether a condition is satisfied. If it is determined that the condition has been satisfied, the wireless communication device performs uplink retransmission, such as physical uplink shared channel (PUSCH) retransmission.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of communications, and in particular, to an uplink retransmission. Background Art

[0002] The demand for fifth-generation mobile communication technology (5G) is growing rapidly. Providing enhanced mobile broadband, ultra-high reliability, ultra-low latency transmission, and massive connectivity in 5G systems is under development. Summary of the Invention

[0003] Example embodiments disclosed in the present invention are intended to solve problems related to one or more problems raised in the prior art, and to provide additional features that become readily understood by reference to the following detailed description and in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art reading the present invention that various modifications can be made to the disclosed embodiments while remaining within the scope of the present invention.

[0004] In some embodiments, a wireless communication device determines that a condition has been met, and in response, performs an uplink retransmission based on retransmission information.

[0005] In some embodiments, a network sends condition information to a wireless communication device and receives an uplink retransmission from the wireless communication device. The uplink retransmission is sent by the wireless communication device based on retransmission information (which is determined based on the condition information).

[0006] The above and other aspects and their implementations are described in more detail in the drawings, embodiments, and claims. Brief Description of the Drawings

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

[0008] Figure 1 is a schematic diagram of a UE and a base station according to some embodiments of the present invention.

[0009] Figure 2 is an SRI indication table for non-codebook-based PUSCH transmission according to some embodiments of the present invention.

[0010] Figure 3SRI indication comparison table for non-codebook-based PUSCH transmission according to some embodiments of the present invention.

[0011] Figure 4 It is a schematic diagram showing a method for wireless communication according to some embodiments of the present invention.

[0012] Figure 5 It is a schematic diagram showing a method for wireless communication according to some embodiments of the present invention.

[0013] Figure 6A A block diagram showing an example base station according to some embodiments of the present invention; and

[0014] Figure 6B A block diagram showing an example UE according to some embodiments of the present invention. Detailed implementation manners

[0015] Various example embodiments of the present solution are described below with reference to the accompanying drawings so that those of ordinary skill in the art can make and use the present solution. It is obvious to those of ordinary skill in the art that after reading the present invention, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and shown herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein is merely an exemplary method. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged while remaining within the scope of the present solution. Therefore, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise clearly stated, the present solution is not limited to the specific order or hierarchy presented.

[0016] The development direction of 5G wireless communication systems is to achieve higher data communication rates (e.g., in Gbps), a large number of communication links (e.g., 1M / Km 2 ), ultra-low latency (e.g., below 1 ms), higher reliability, and higher energy efficiency (e.g., at least 100 times more efficient than previous systems). To achieve such improvements, joint transmission has been developed in wireless communication systems under the 5G standard.

[0017] Joint transmission or reception of multiple transmit - receive points (Multi - TRP) is an important technology in wireless communication. Multi - TRP plays an important role in improving the throughput of wireless communication and is supported by Long - Term Evolution - Advanced (LTE - A) and New Radio Access Technology (NR). NR introduces multi - panel transmitters. Multi - panel transmission refers to installing multiple antenna panels at the receiving and / or transmitting end to improve the spectral efficiency of wireless communication systems. In addition, in high - frequency scenarios, multi - beam transmission or reception of multi - TRP or multi - panel is an effective way to improve reliability and can improve the transmission reliability of wireless communication systems, especially for Ultra - Reliable Low - Latency Communication (URLLC).

[0018] In non - codebook - based Physical Uplink Shared Channel (PUSCH) transmission, each Sounding Reference Signal (SRS) resource indicated by the SRS Resource Indicator (SRI) corresponds to 1 PUSCH transmission layer. Therefore, the SRI implicitly indicates the PUSCH transmission layer by indicating several SRS resources. However, when multi - TRP and multi - beam multi - panel transmission are applied, the SRI metric cannot implicitly indicate the PUSCH transmission layer.

[0019] For multi - TRP transmission, when the gNodeB (gNB) schedules uplink (UL) transmission, the gNB can send different Physical Downlink Control Channels (PDCCHs) with Downlink Control Information (DCI) format 0 - 0 or 0 - 1 through different TRPs. These two DCIs are associated with different CORESETPoolIndex so that the User Equipment (UE) can distinguish which TRP the DCI comes from.

[0020] Figure 1An example UE 101 performing PUSCH repetition is shown, which is shown by multiple beams 110 / 120. The UE 101 is sending an uplink transmission via multiple beams 110 including beams 111, 112, 113, and 114 communicating with the base station 102. The UE 101 is also sending an uplink transmission on multiple beams 120 including beams 121, 122, 123, and 124 communicating with the base station 103. In some examples, each of the base stations 102 and 103 may be a TRP. As described herein, the UE 101 configured with multiple beams corresponds to a UE 101 that uses multiple beams to send and / or receive data, e.g., a UE 101 performing uplink repeated transmission (e.g., PUSCH repetition).

[0021] 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 identifier (ID) and the same New Data Indicator (NDI), but are associated with different CORESETPoolIndex, it is expected that the UE sends PUSCH repetition to the gNB. In another embodiment, if the UE receives two DCI formats 0-0 or 0-1 that have the same HARQ ID but are associated with different CORESETPoolIndex, it is expected that the UE sends PUSCH repetition. In another embodiment, if the UE receives a beam indication in an uplink repeated transmission that indicates multiple beams corresponding to a single PUSCH transmission layer, it is expected that the UE sends PUSCH repetition. In another embodiment, if the UE is configured with multiple repetitions and then receives a beam indication, it is expected that the UE sends PUSCH repetition.

[0022] In each of these embodiments, the UE also determines repetition information, which includes 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 an SRI, the maximum rank supported by the UE, the number of beams corresponding to a single PUSCH transmission layer, or a beam diversity indicator. The UE determines the SRI field size based on the maximum rank supported by the UE and the number of beams corresponding to a single layer. The UE determines the transmission precoding matrix based on at least one of the maximum rank supported by the UE, the number of beam indications corresponding to a single layer, the PUSCH transmission time domain and frequency domain resources, or the number of PUSCH CDM groups. The UE determines the SRS port and the PUSCH port based on at least one of the maximum rank supported by the UE, the number of beams corresponding to a single PUSCH transmission layer, the PUSCH transmission time domain and frequency domain resources, or the number of PUSCH CDM groups.

[0023] PUSCH repetition refers to the process in which the UE transmits the same data information multiple times with multiple beams through at least one of different time-domain resources, different frequency-domain resources, different CDM groups, or different transport layers. A beam corresponds to one or more of different time-domain resources, frequency-domain resources, CDM groups, or transport layers. When PUSCH repetition has overlapping time-domain and frequency-domain resources and is configured within a CDM group, the UE determines the transmit power as the maximum calculated UE transmit power, the minimum calculated UE transmit power, or the average of all calculated transmit powers.

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

[0025] In some implementations, the DCI can indicate multiple PUSCH beams corresponding to the same layer. When receiving the DCI indicating multiple PUSCH beams corresponding to the same layer, the UE can determine that PUSCH repetition is indicated by the DCI. If the transport layer is explicitly configured, to determine (distinguish) multiple PUSCH beams for non-codebook-based uplink transmission in the same layer, the UE determines whether to send 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 PUSCH repetition with 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 PUSCH repetition with multiple beams according to the number of indicated TCI states or the number of SRS resources in one TCI code point.

[0026] For codebook-based uplink transmission, to determine (distinguish) multiple PUSCH beams in the same layer for codebook-based uplink transmission, the UE determines whether to transmit PUSCH repetitions with multiple beams based on whether different transmission precoding matrix indicators (TPMIs) are 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 PUSCH repetitions with multiple beams based on 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 PUSCH repetitions with multiple beams based 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 PUSCH repetitions with multiple beams based 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, and each PUSCH repetition transmission scenario is associated with different time-domain resources and / or frequency-domain resources.

[0027] For non-codebook-based PUSCH transmission, the gNB can explicitly configure a transmission layer indicator, a beam diversity indicator, or the number of beams corresponding to a single layer for PUSCH transmission. If the beam diversity indicator is configured as "on" or "enabled", the UE assumes that different PUSCH repetition transmission scenarios are associated with different transmit beams. If the beam diversity indicator is not, the UE assumes that the PUSCH repetition 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 can correspond to a single demodulation reference signal (DMRS) port, or several SRS resources each with one port can correspond to a single PUSCH transmission layer.

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

[0029] The above beams are determined by TCI state, SRI, QCL assumption, SRS index, CSI-RS index, SSB index, spatial relation information (spatialrelationinfo), and airspace transmission filter configuration.

[0030] For codebook-based PUSCH transmission, the gNB may configure multiple TPMIs to the UE via a single DCI or beam diversity indicator via higher layer signaling. When the UE is configured for multiple PUSCH repetitions, it is expected that the UE transmits PUSCH repetitions with different indicated beams in the following cases. In one case, if the UE receives different TPMIs in one TPMI code point in the scheduling DCI, it is expected that the UE transmits PUSCH repetitions with different indicated beams. In another case, if the UE receives a first TPMI in the scheduling DCI and the UE is configured with the relationship between the first TPMI and the second TPMI, it is expected that the UE transmits PUSCH repetitions with different indicated beams. In another case, if the UE receives different TPMIs in two TPMI fields in the scheduling DCI, it is expected that the UE transmits PUSCH repetitions with different indicated beams. In another case, if the UE receives a beam diversity indicator, it is expected that the UE transmits PUSCH repetitions with different indicated beams. In another case, if the UE receives an SRI indicating multiple SRS resources (where the number of SRS resources is greater than the indicated transport layer), it is expected that the UE transmits PUSCH repetitions with 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 transport layer, it is expected that the UE transmits PUSCH repetitions with different indicated beams.

[0031] 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 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 a first indicated beam, and the second PUSCH transmission occasion is a PUSCH repetition associated with a second indicated beam.

[0032] The beam used above refers to an airspace transmission filter that can be determined by at least one of the TCI state, spatialrelationinfo, SRI, QCL, SRS index, CSI RS index, or SSB index.

[0033] If the base station indicates an 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 other two parameters can be determined accordingly. The above SRI index indicates one or more SRS resources. For example, the number of layers and the SRI index can be used to determine the number of beams corresponding to the layer. In addition, the number of beams corresponding to the layer and the SRI index can be used to determine the number of layers. In addition, beam diversity and the SRI index can be used to determine, for example, one layer corresponding to two beams, and the number of layers can be determined based on the SRI index and the number of beams corresponding to one layer. The network can send an SRI index to the UE to indicate the number of layers for transmitting PUSCHs, whether beam diversity is used, etc. Therefore, the network (e.g., a base station, multiple base stations) can indicate different SRI indexes to allow the UE to flexibly switch to different layer and / or beam diversity settings. The SRI index can also be an SRI code point.

[0034] The configuration of the transmission layer, multiple beams (multiple SRS resources) corresponding to the layer, or the beam diversity command can be pre-configured. By expanding L max = 2 in the table, dynamic switching between L = 1 and L = 2 can be supported. In some examples, N SRS = 4, and the SRI indication includes code points of '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, the 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 retransmission 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 for all PUSCH retransmission scenarios are the same.

[0035] For L max greater than 1, the gNB explicitly configures at least one of the following: a transmission layer indicator L such that 1 < L ≤ 4, a beam diversity indicator q with a value of 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.

[0036] Figure 2 is an SRI indication table for non-codebook-based PUSCH transmission according to an example embodiment. As Figure 2 shown, L maxThe SRI table with L = 2 is extended by several entries to support multi-beam PUSCH repetition with L = 2. 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 shown in the following equation:

[0037]

[0038] where L max refers to the maximum number of transmission layers, s refers to the number of beams corresponding to a single layer, and N SRS refers to the number of SRS resources indicated by the SRI index.

[0039] When the UE receives an SRI index indicating 2 SRS resources or is indicated by 2 beams for PUSCH transmission, for L max ≥ 1, various values of the relevant parameters indicate different layers of PUSCH repetition and beams. If L = 1, it is expected that the UE transmits 1-layer PUSCH repetition with 2 beams. If q = 1, it is expected that the UE transmits 1-layer PUSCH repetition with 2 beams. If s = 2, it is expected that the UE transmits 1-layer PUSCH repetition with 2 beams. If L = 2, it is expected that the UE transmits 2-layer PUSCH repetition with 2 beams, with each beam corresponding to 1 layer. If q = 0, it is expected that the UE transmits 2-layer PUSCH repetition with 2 beams, with each beam corresponding to 1 layer. If s = 1, it is expected that the UE transmits 2-layer PUSCH repetition with 2 beams, with each beam corresponding to 1 layer.

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

[0041] 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 is equal to 2, the Figure 3 shown table should be used. Figure 3 is a comparison table of SRI indications for non-codebook-based PUSCH transmission. As Figure 3 shown, if 1 SRI code point indicates 2 SRS resources, the UE assumes that the PUSCH transmission is 1 layer, and if the RRC or DCI indicates the PUSCH repetition times, 2 SRS beams are associated with different PUSCH transmission occasions. If 1 SRI code point indicates 4 SRS resources, the UE assumes that the PUSCH transmission is 2 layers, and if the RRC or DCI indicates the PUSCH repetition times, the 4 SRS beams are grouped and associated with different PUSCH transmission occasions respectively. For N SRSFor an example where SRI = 4, if the SRI received by the UE is between 0 and 5, the UE uses single-layer PUSCH transmission (where there are 2 SRS beams corresponding to different PUSCH transmission occasions). If the SRI received by the UE is between 6 and 8, the UE uses two-layer PUSCH transmission with 4 SRS beams (where the first 2 beams and the last 2 beams correspond to different PUSCH transmission occasions).

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

[0043] If the PUSCH transmission is one layer, two beams are used to indicate the layer 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 two layers, each layer is indicated by two 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.

[0044] For example, layer 1 can correspond to SRS0 and SRS1 with an SRS port index of 1000, and layer 2 can correspond to SRS2 and SRS3 with an SRS port index of 1001. The first PUSCH transmission occasion has two layers, where beams are sent for SRS0 and SRS2 respectively, and the SRS port indices are 1000 and 1001. The second PUSCH transmission occasion has two layers, where beams are sent for SRS1 and SRS3, and the SRS port indices are 1000 and 1001. Different PUSCH transmission occasions correspond to non-overlapping time and / or frequency-domain resources.

[0045] The UE determines the precoding matrix for PUSCH transmission according to the rank information and beam indication. For non-codebook-based PUSCH transmission, when the PUSCH is repetitively configured with multiple beams corresponding to a single layer or DMRS ports, if the PUSCH DMRS ports are indicated within one CDM group in the DCI field "antenna port", if the PUSCH repetitive transmission scenario has non-overlapping time and / or frequency domain resources, or in response to determining that the PUSCH repetitive transmission scenario has overlapping time and frequency domain resources, the precoding matrix W is no longer the identity matrix and will be extended. For example, the number of rows in W is equal to the product of the number of beam indications per layer and the number of transmission layers, while the number of columns is equal to the number of transmission layers. The SRS ports here remain the same as in [6, TS 38.214], that is, the UE shall send the PUSCH using the same antenna ports as the SRS ports in the SRS resources indicated by the SRI given by DCI format 0_1 or configured by a higher layer, where the index of the SRS port in the (i + 1)-th SRS resource in the SRS resource set is: p i = 1000 + i.

[0046] For example, if the PUSCH transmission is for 1 layer and the number of beams per layer is 2, the precoding matrix can be given as If the PUSCH transmission is for 2 layers and the number of beams per layer is 2, the precoding matrix can be:

[0047] or

[0048] If the PUSCH DMRS ports are indicated within one CDM group in the DCI field "antenna port", and the PUSCH is configured with multiple beams, and if each PUSCH repetitive transmission scenario has the same frequency and time domain resource allocation, the different transmit powers of different beams for 2 TRPs are determined as the 1 transmit power with which the PUSCH transmits to 2 TRPs using the same time and frequency resources as the same DMRS port.

[0049] The UE determines the transmit power of the PUSCH transmitted to 2 TRPs 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 can be determined by at least one of the maximum calculated UE transmit power, the minimum calculated UE transmit power, or the average of all calculated transmit powers. The calculated UE transmit power can be determined by the above-mentioned set of power control parameters.

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

[0051] The slot offset (which can also be associated with the CORESETPoolIndex) is determined by the DCI using high-level parameters and adjusted when multiple DCIs are configured to ensure the same reference signal triggering time. For example, the slot offset can be configured directly in the DCI command or directly in the higher-layer parameters. In another example, the higher-layer parameters can configure a slot offset pool representing multiple slot offset values, and the DCI selects one of these slot offset values for scheduling the 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.

[0052] Figure 4 is a schematic diagram showing a method 400 for wireless communication according to some embodiments. Method 400A is performed by a UE corresponding to Figure 1 the UE 101.

[0053] In step 410, the UE determines that the conditions have been met. These conditions are evaluated at steps 412, 414, 416, and 418. At step 412, the UE receives DCI from the network with different CORESETPoolIndex values but the same HARQ ID and the same NDI. At step 414, the UE receives DCI from the network with different CORESETPoolIndex values but the same HARQ ID. At step 416, the UE receives a beam indication indicating multiple beams corresponding to a single PUSCH transport layer used in uplink repeated transmission. At step 418, the UE receives a beam indication including parameters defining multiple beams. If any of the conditions evaluated at steps 412, 414, 416, or 418 are met, then at step 420, the UE performs an uplink repeated transmission based on the repetition information. The uplink repeated transmission at step 420 corresponds to Figure 1 multiple beams 110 and 120. The repetition information is given at step 421 and includes beam information, a transmission precoding matrix, a transmission precoding matrix indicator (TPMI), power control information, an SRS port, a PUSCH port, or an SRI field size.

[0054] Figure 5 is a schematic diagram showing a method 500 for wireless communication according to some embodiments. Method 500 is performed by a base station or a TRP, which corresponds to Figure 1 base stations 102 and 103 in. At step 510, the base station sends condition information. The condition information is established at steps 512, 514, 516, and 518. At step 512, the base station sends DCI with different CORESETPoolIndex values but the same HARQ ID and the same NDI. At step 514, the base station sends DCI with different CORESETPoolIndex values but the same HARQ ID. At step 516, the base station sends a beam indication that indicates multiple beams corresponding to a single PUSCH transport layer used in uplink repeated transmission. At step 518, after configuring the number of repetitions for the UE for uplink repeated transmission, the base station sends a beam indication indicating the multiple beams used in the uplink repeated transmission. After at least one condition information is sent, at step 520, the base station receives an uplink repeated transmission from the UE. The uplink repeated transmission at step 520 corresponds to Figure 1 multiple beams 110 and 120 in. The uplink repeated transmission at step 520 is based on the repetition information, which is itself determined based on the condition information from steps 512, 514, 516, or 518.

[0055] Figure 6A shows a block diagram of an example base station 602 according to some embodiments of the present invention. Figure 6BA block diagram of an example UE 601 in accordance with some embodiments of the present invention is shown. Referring to Figure 1 -6B, UE 601 (e.g., a wireless communication device, a terminal, a mobile device, a mobile user, etc.) is an example implementation of the UE described herein, and base station 602 is an example implementation of the base station described herein.

[0056] Base station 602 and UE 601 may include components and elements configured to support known or conventional operating features not described in detail herein. In one illustrative embodiment, as described above, base station 602 and UE 601 may be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment. For example, base station 602 may be a base station (e.g., a gNB, an eNB, etc.), a server, a node, or any suitable computing device for implementing various network functions.

[0057] 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. Modules 610, 612, 614, 616, and 618 are operably coupled and interconnected to each other via a data communication bus 620. UE 601 includes a UE transceiver module 630, a UE antenna 632, a UE memory module 634, and a UE processor module 636. Modules 630, 632, 634, and 636 are operably coupled and interconnected to each other via a data communication bus 640. Base station 602 communicates with UE 601 or another base station via a communication channel, which may be any wireless channel or other medium suitable for data transmission as described herein.

[0058] As will be understood by those of ordinary skill in the art, base station 602 and UE 601 may further include any number of modules other than Figure 6A and 6B the modules shown in. The various illustrative blocks, modules, circuits, and processing logics described in connection with the embodiments disclosed herein may 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 generally described in terms of their functionality. Whether this functionality is implemented as hardware, firmware, or software depends on 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 decision should not be construed as limiting the scope of the present invention.

[0059] According to some embodiments, the UE transceiver 630 includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to an antenna 632. A duplexer switch (not shown) alternatively couples the RF transmitter or receiver to the antenna in a time-division duplexing manner. Similarly, according to some embodiments, the transceiver 610 includes an RF transmitter and an RF receiver, each having circuitry coupled to an antenna 612 or an antenna of another base station. The duplexer switch alternatively couples the RF transmitter or receiver to the antenna 612 in a time-division duplexing manner. 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 to receive transmissions over a wireless transmission link while the transmitter is coupled to the antenna 612. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0060] The UE transceiver 630 and the transceiver 610 are configured to communicate via a 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 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 specific standards and related protocols. Instead, the UE transceiver 630 and the base station transceiver 610 can be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0061] The transceiver 610 and the transceiver of another base station (e.g., 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 LTE and emerging 5G standards. However, it can be understood that the present invention is not necessarily limited to the application of specific standards and related protocols. Instead, the transceiver 610 and the transceiver of another base station can be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0062] According to various embodiments, the base station 602 can be a base station, such as but not limited to an eNB, a serving eNB, a target eNB, a femtocell, or a picocell. The base station 602 can be an RN, a conventional, a DeNB, or a gNB. In some embodiments, the UE 601 can be embodied in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. The processor modules 614 and 636 can be implemented or realized using 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 way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.

[0063] In addition, the methods or algorithms disclosed in the present invention can be directly embodied in hardware, firmware, software modules executed by the processor modules 614 and 636 respectively, or any practical combination thereof. The memory modules 616 and 634 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. In this regard, the memory modules 616 and 634 can be coupled to the processor modules 614 and 636 respectively, such that the processor modules 614 and 636 can read information from and write information to the memory modules 616 and 634 respectively. The memory modules 616 and 634 can also be integrated into their respective processor modules 614 and 636. In some embodiments, the memory modules 616 and 634 can each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions to be executed by the processor modules 614 and 636 respectively. The memory modules 616 and 634 can also each include a non-volatile memory for storing the instructions to be executed by the processor modules 614 and 636 respectively.

[0064] The network communication module 618 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 602 that enable two-way communication between the transceiver 610 and other network components as well as communication nodes communicating with the base station 602. For example, the network communication module 618 may be configured to support Internet or WiMAX services. In an unrestricted deployment, the network communication module 618 provides an 802.3 Ethernet interface that enables the transceiver 610 to communicate with a traditional Ethernet-based computer network. In this way, the network communication module 618 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). In some embodiments, the network communication module 618 includes an optical fiber transmission connection configured to connect the base station 602 to a core network. As used herein, the terms “configured for,” “configured to,” and their conjugates 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 that particular operation or function.

[0065] Although various embodiments of the present solution have been described above, it should be understood that they are given by way of example and not limitation. Similarly, the various figures may depict example architectures or configurations provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present solution. However, those skilled in the art will understand that the present solution is not limited to the example architectures or configurations shown, but rather may be implemented using a variety of alternative architectures and configurations. Additionally, as those of ordinary skill in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present invention should not be limited by any of the above exemplary embodiments.

[0066] It should also be understood that any reference in this document to elements by names such as “first,” “second,” etc. generally does not limit the number or order of those elements. Rather, these names are used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, the reference to a first and a second element does not mean that only two elements can be employed, or that the first element must be located before the second element in some manner.

[0067] In addition, those of ordinary skill in the art will understand that a variety of different technologies may be used to represent information and signals. For example, the data, instructions, commands, information, signals, bits, and symbols, for instance, that may be referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0068] One of ordinary skill in the art will 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 can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (for convenience, referred to herein as "software" or "software modules"), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been described generally in terms of their functionality. Implementing this functionality as hardware, firmware, or software, or a combination of these techniques, depends on the particular application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in various ways for each particular application, but such implementation decisions do not depart from the scope of the present invention.

[0069] In addition, one of ordinary skill in the art will understand that the various illustrative logical blocks, modules, devices, components, and circuits described herein can be implemented within or performed by an integrated circuit (IC) including 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 an antenna and / or a transceiver to communicate with various components within a network or within a device. The general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.

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

[0071] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements to perform the associated functions described herein. Additionally, for purposes of discussion, the various modules are described as discrete modules; however, it will be apparent to those of ordinary skill in the art that two or more modules can be combined to form a single module that performs the associated functions according to embodiments of the present solution.

[0072] Additionally, memories or other storage and communication components may be employed in embodiments of the present solution. It should be understood 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 functional distribution between different functional units, processing logic elements, or domains can be used without departing from the present solution. For example, functions illustrated as being performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Accordingly, the reference to a particular functional unit is only a reference to a suitable device for providing the described function and does not indicate a strict logical or physical structure or organization.

[0073] Various modifications to the implementations described in this invention will be 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 the inventive concept. Accordingly, the inventive concept is not intended to be limited to the implementations shown herein but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method, characterized in that, Including: A wireless communication device determines that a condition is satisfied; And In response to determining that the condition is satisfied, determining retransmission information based on the condition, and the wireless communication device performs uplink retransmission based on the retransmission information; Wherein, determining the retransmission information includes: determining the size of the sounding reference signal (SRS) resource indicator (SRI) field according to the maximum rank supported by the wireless communication device, and using the number of beams in the transmission layer of a single physical uplink shared channel (PUSCH) for the uplink retransmission.

2. The method according to claim 1, wherein The uplink retransmission is a physical uplink shared channel (PUSCH) retransmission; and The PUSCH retransmission corresponds to transmitting the same data multiple times through at least one of the following: different time domain resources, different frequency domain resources, different CDM groups, or different transmission layers, and the wireless communication device is configured with multiple beams.

3. The method according to claim 1, wherein the condition corresponds to receiving downlink control information (DCI) from the network, the DCI has different CORESET Pool Indexes, the DCI has the same hybrid automatic repeat request identity (HARQ ID), and the DCI has the same new data indicator (NDI).

4. The method according to claim 1, wherein the condition corresponds to receiving downlink control information (DCI) from the network, the DCI has different CORESET Pool Indexes and the same hybrid automatic repeat request identity (HARQ ID).

5. The method according to claim 1, wherein the condition corresponds to receiving downlink control information (DCI) from the network, the DCI has multiple TPMI.

6. The method according to claim 1, wherein the condition corresponds to receiving a beam indication and one of the following: The beam indication is used to indicate multiple beams corresponding to the transmission layer of a single physical uplink shared channel (PUSCH) used for the uplink retransmission, or The beam indication is used to indicate multiple beams corresponding to the physical uplink shared channel (PUSCH) retransmission.

7. The method according to claim 6, wherein the wireless communication device determines the beam indication through at least one of the following: sounding reference signal resource indicator (SRI), the maximum rank supported by the wireless communication device, the number of beams corresponding to the single PUSCH transmission layer, beam diversity indicator.

8. The method according to claim 6, wherein, Each of the multiple beams is configured through one or more of the following: transmission configuration indicator (TCI) state, sounding reference signal resource indicator (SRI), quasi - co - location (QCL) assumption, SRS index, channel state information (CSI) reference signal (RS) index, synchronization signal block (SSB) index, spatial relation information, spatial domain transmission filter.

9. The method according to claim 1, wherein the condition corresponds to: The wireless communication device is configured with the number of repetitions for the uplink retransmission; and The wireless communication device receives a beam indication, the beam indication including parameters defining a plurality of beams.

10. The method according to claim 1, wherein The repeated transmission information includes at least one of the following: beam indication, transmission precoding matrix, 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 according to claim 10, wherein, Determining the repeated transmission information includes: determining a transmission precoding matrix according to at least one of the following: the maximum rank supported by the wireless communication device, the number of beams corresponding to a single physical uplink shared channel PUSCH transmission layer, the time domain and frequency domain resources of the PUSCH transmission, the number of PUSCH code division multiple access CDM groups.

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

13. The method according to claim 12, wherein The uplink repeated 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.

14. The method according to claim 12, wherein The uplink repeated transmission corresponds to multiple PUSCH transmissions of the same data; The multiple PUSCH transmissions are configured within one CDM group; and at least one of the following: The SRS ports corresponding to multiple PUSCH transmissions of a single layer have the same port index; or The PUSCH ports corresponding to multiple PUSCH transmissions of a single layer have the same port index.

15. The method according to claim 13, wherein The multiple PUSCH transmissions have at least one of the following: non-overlapping time domain resources, non-overlapping frequency domain resources, non-overlapping frequency domain and time domain resources, overlapping time domain and frequency domain resources.

16. The method according to claim 14, wherein The multiple PUSCH transmissions have at least one of the following: non-overlapping time domain resources, non-overlapping frequency domain resources, non-overlapping frequency domain and time domain resources.

17. The method according to claim 1, wherein The uplink repeated transmission corresponds to multiple PUSCH transmissions of the same data; Determining that the repeated transmission information includes: In response to determining that the multiple PUSCH transmissions have overlapping time domain resources and frequency domain resources, and the multiple PUSCH transmissions are configured with one code division multiple access CDM group, the wireless communication device determines the transmit power.

18. The method according to claim 17, wherein, The transmit power includes one of the following: the maximum calculated transmit power of the wireless communication device, the minimum calculated transmit power of the wireless communication device, the average value of all calculated transmit powers of the wireless communication device.

19. A wireless communication device, characterized in that, Comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method of any one of claims 1 to 18.

20. A computer program product, characterized in that, Comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method of any one of claims 1 to 18.

21. A wireless communication method, characterized in that, Comprising: Sending condition information to a wireless communication device via a network; And Receiving an uplink repeated transmission from the wireless communication device via the network, wherein the uplink repeated transmission is sent by the wireless communication device based on repeated transmission information, and the repeated transmission information is determined based on the condition information; Wherein determining the repeated transmission information includes: determining the size of a sounding reference signal (SRS) resource indicator (SRI) field according to the maximum rank supported by the wireless communication device, and using the number of beams in a single physical uplink shared channel (PUSCH) transmission layer of the uplink repeated transmission.

22. The wireless communication method according to claim 21, wherein, The condition information includes downlink control information (DCI), and the DCI has different CORESETPoolIndex, the same hybrid automatic repeat request identity (HARQID), and the same new data indicator (NDI).

23. The wireless communication method according to claim 21, wherein, The condition information includes downlink control information (DCI), and the DCI has different CORESETPool Index and the same hybrid automatic repeat request identity (HARQ ID).

24. The wireless communication method according to claim 21, wherein, The condition information includes a beam indication for indicating a plurality of beams corresponding to a single physical uplink shared channel (PUSCH) transmission layer used in the uplink repeated transmission.

25. The wireless communication method according to claim 21, further comprising: Configuring the wireless communication device with the number of repetitions of the uplink repeated transmission, wherein the condition information includes a beam indication for indicating a plurality of beams used in the uplink repeated transmission.

26. A wireless communication device, characterized in that, Comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement the method of any one of claims 21 to 25.

27. A computer program product, characterized in that, Comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement the method of any one of claims 21 to 25.

Images