Data transmission method, communication device, and storage medium
By configuring resource unit (RE) groups for PUSCH and designing a dedicated format, the problem of low UCI transmission efficiency was solved, achieving efficient utilization of PUSCH resources and UCI multiplexing, and simplifying the signaling process.
Patent Information
- Application Number
- PCT/CN2025/073947
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-06-28
- Filing Date
- 2025-01-22
- Publication Date
- 2026-01-02
AI Technical Summary
In existing technologies, UCI transmission efficiency on PUSCH is low, it cannot support UCI multiplexing of multiple user devices, and the multiplexing process is complex and has many dependent conditions, resulting in low data transmission efficiency.
By identifying and configuring the resource unit (RE) group corresponding to the PUSCH, a PUSCH format dedicated to UCI is designed so that it can carry UCI like PUCCH. This includes configuring RBs and dividing them into RE groups, using predefined rules and signaling to optimize signaling overhead, and supporting UCI multiplexing for different UEs.
It improves data transmission efficiency, simplifies the UCI multiplexing process, reduces signaling overhead, and ensures efficient utilization of PUSCH resources.
Smart Images

Figure CN2025073947_02012026_PF_FP_ABST
Abstract
Description
Data transmission method, communication device and storage medium TECHNICAL FIELD
[0001] The present application relates to the technical field of communication, for example, to a data transmission method, a communication device and a storage medium. BACKGROUND
[0002] In the related art, uplink control information (UCI) is mainly carried through a physical uplink control channel (PUCCH). However, when the following conditions occur, the channel carrying the UCI will be changed by a multi-channel multiplexing rule.
[0003] If a PUCCH carrying a hybrid automatic repeat request acknowledgement (HARQ-ACK) overlaps in time domain with a physical uplink shared channel (PUSCH) carrying uplink data, the HARQ-ACK is multiplexed in the PUSCH by performing multiplexing between the PUCCH and the PUSCH. That is, the HARQ-ACK is transmitted in part of the resources of the PUSCH, and part of the resources originally allocated for uplink data are used to carry the HARQ-ACK. Finally, the PUCCH is not transmitted, and the PUSCH is transmitted.
[0004] Since the PUCCH and the PUSCH overlap in time domain to transmit the UCI in the PUSCH, this method can also transmit the UCI, but since the characteristics of the UCI are not designed, it cannot support multiplexing of UCI of multiple user equipments (UEs) in the same PUSCH, resulting in low data transmission efficiency.
[0005] In addition, this method relies on many conditions, for example, the UE needs to have both a PUCCH and a PUSCH, and they overlap in time domain. In the above multiplexing process, the multiplexing between PUCCHs, and the multiplexing rules and processes between PUCCHs and PUSCHs are complex. Therefore, how to design a PUSCH format and mechanism dedicated to UCI so that the PUSCH can carry UCI like the PUCCH and ensure high efficiency is a problem to be solved. SUMMARY
[0006] The embodiments of the present application provide a data transmission method, a communication device and a storage medium, which realize the effect of carrying uplink control information by using PUSCH resources, and improve the data transmission efficiency.
[0007] The embodiment of the present application provides a data transmission method, which is applied to a first communication device and comprises the following steps:
[0008] A resource element (RE) group corresponding to a physical uplink shared channel (PUSCH) for carrying uplink control information is determined; and the PUSCH is transmitted in the RE group.
[0009] The embodiment of the present application provides a data transmission method, which is applied to a second communication device and comprises the following steps:
[0010] A resource element (RE) group corresponding to a physical uplink shared channel (PUSCH) for carrying uplink control information is configured; and the PUSCH is received in the RE group.
[0011] The embodiment of the present application provides a data transmission device, which is applied to a first communication device and comprises the following steps:
[0012] A determining module is configured to determine a resource element (RE) group corresponding to a physical uplink shared channel (PUSCH) for carrying uplink control information; and a transmitting module is configured to transmit the PUSCH in the RE group.
[0013] The embodiment of the present application provides a data transmission device, which is applied to a second communication device and comprises the following steps:
[0014] A configuring module is configured to configure a resource element (RE) group corresponding to a physical uplink shared channel (PUSCH) for carrying uplink control information; and a receiver is configured to receive the PUSCH in the RE group.
[0015] The embodiment of the present application provides a communication device, which comprises a memory and one or more processors.
[0016] The memory is configured to store one or more programs; and when the one or more programs are executed by the one or more processors, the one or more processors implement the data transmission method in any of the above embodiments.
[0017] The embodiment of the present application provides a storage medium, which stores a computer program; and when the computer program is executed by a processor, the data transmission method in any of the above embodiments is implemented. BRIEF DESCRIPTION OF DRAWINGS
[0018] FIG. 1 is a flowchart of a data transmission method according to an embodiment of the present application;
[0019] FIG. 2 is a flowchart of another data transmission method according to an embodiment of the present application;
[0020] FIG. 3 is a structural block diagram of a data transmission device according to an embodiment of the present application;
[0021] FIG. 4 is a structural block diagram of another data transmission apparatus provided in an embodiment of the present application;
[0022] FIG. 5 is a structural schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0023] In an embodiment, FIG. 1 is a flowchart of a data transmission method provided in an embodiment of the present application. The present embodiment is applied to the case of designing PUSCH format dedicated to UCI. The present embodiment can be executed by a first communication device. Exemplarily, the first communication device is a terminal side. As shown in FIG. 1, the present embodiment comprises S110-S120.
[0024] S110, determining an RE group corresponding to a PUSCH for carrying uplink control information.
[0025] S120, transmitting the PUSCH in the RE group.
[0026] The first communication device determines some RE groups for the PUSCH carrying UCI, and transmits the PUSCH in the RE group to the second communication device, so that the PUSCH can carry UCI as PUCCH, thereby ensuring the data transmission efficiency.
[0027] In an embodiment, determining an RE group corresponding to a PUSCH for carrying uplink control information comprises:
[0028] determining at least one resource block (RB) of the PUSCH for carrying uplink control information configured by the second communication device; dividing the RB into at least one RE group according to a predefined rule; and determining at least one RE group allocated by the second communication device from the divided at least one RE group as the RE group corresponding to the PUSCH for carrying uplink control information.
[0029] The second communication device can configure at least one RB for carrying UCI of the PUSCH, and then the second communication device and the first communication device agree and divide the RB into one or more RE groups according to a predefined rule; and then the second communication device allocates one or more RE groups to the first communication device as a PUSCH resource for carrying UCI. The second communication device directly uses the originally pre-configured RB, reducing signaling overhead, and according to the predefined rule, the RB is divided into one or more RE groups without signaling overhead, that is, on the basis of reducing signaling overhead as much as possible, the effect of using one or more RE groups to carry UCI of the PUSCH is achieved. In an example, the second communication device can configure at least one RB for carrying UCI of the PUSCH through Radio Resource Control (RRC) signaling or a system broadcast message; and then the second communication device and the first communication device divide the configured RB into one or more RE groups according to a predefined rule, or the second communication device configures the RB into one or more RE groups. In an example, the second communication device can select an RE group from the pre-configured RB through a parameter indication of DCI. Specifically, the second communication device configures at least one RB for carrying UCI of the PUSCH, and divides the REs in the configured RB into at least one RE group. The second communication device indicates at least one RE group for carrying UCI of the PUSCH through a parameter of DCI scheduling the PDSCH, so that the first communication device uses the at least one RE group to transmit the PUSCH for carrying UCI to the second communication device.
[0030] In an embodiment, determining the RE group corresponding to the PUSCH for carrying uplink control information comprises: determining that at least one RE group is allocated by the second communication device from the configured or predefined RE groups as the RE group corresponding to the PUSCH for carrying uplink control information.
[0031] The second communication device directly configures or pre-defines at least one RE group, and then the second communication device directly indicates or allocates one or more RE groups to the first communication device as the RE group corresponding to the PUSCH for carrying UCI through signaling.
[0032] In an embodiment, the uplink control information at least includes one of the following: a hybrid automatic repeat request acknowledgement (HARQ-ACK); a scheduling request (SR); beam recovery information; and channel state information (CSI).
[0033] In an embodiment, the time-frequency domain resource size and the time-frequency domain resource location of each RE group are predefined or preconfigured. In an example, in the case that the time-frequency domain resource size and the time domain resource location of one RE group are predefined, a rule can be uniformly defined, i.e., without separately configuring each time-frequency domain resource size and location of different RE groups, signaling overhead can be reduced. In an example, in the case that the time-frequency domain resource size and the time domain resource location of one RE group are preconfigured, the time domain size and the time domain location of different RE groups are both configured, flexible symbol quantity and symbol location can be obtained; the frequency domain size and the frequency domain location of different RE groups are also both configured, flexible subcarrier quantity and subcarrier location can be obtained, in this pre-configuration manner, the resource size and location of the RE group are flexible, but the signaling message is relatively large.
[0034] In an embodiment, each RE group contains the same time domain resource size, time domain resource location and frequency domain resource size. The time domain resource size refers to the resource size in the time domain; the time domain resource location refers to the resource location in the time domain; and the frequency domain resource size refers to the resource size in the frequency domain. In an example, each RE group has the same resource size and resource location in the time domain. In an example, each RE group has the same resource size in the frequency domain.
[0035] In an embodiment, each RE group contains the same number of subcarriers and symbols, and the same symbol location. In an example, each RE group has the same resource size and resource location in the time domain, such as the same symbol quantity and the same symbol location. In an example, each RE group has the same resource size in the frequency domain, such as each RE group contains the same number of subcarriers. In an example, it is assumed that the time domain resource size of one RE group is equal to the symbol quantity in one slot that can be used for UCI (i.e., excluding the demodulation reference signal (DMRS) symbol in one slot for UCI). In an example, it is assumed that one RE group contains n subcarriers in the frequency domain (n is an integer greater than or equal to 1), the value of n can be predefined by the first communication device and the second communication device, or can be directly configured by the second communication device.
[0036] In an example, one orthogonal cover code (OCC) code word is configured for each RE group. The first communication device generates information of the PUSCH resource transmission based on the OCC code word of the indicated RE group, and transmits the information in the RE group as the PUSCH resource.
[0037] In an embodiment, the at least one RE group serving as the PUSCH resource carrying the uplink control information comprises: each of the at least one RE group serving as the PUSCH resource carrying the uplink control information has the same size and position in the time domain and the same size in the frequency domain. The second communication device can configure a set of PUSCH resources carrying the UCI and indicate the set of PUSCH resources to the first communication device, and then the first communication device determines one PUSCH resource from the set of configured PUSCH resources as the at least one RE group carrying the UCI, the at least one RE group corresponding to the one PUSCH resource having the same resource size in the frequency domain and the same resource size and resource position in the time domain.
[0038] In an embodiment, the data transmission method applied to the first communication device further comprises: determining a set of PUSCH resources of a PUSCH carrying uplink control information configured by the second communication device; wherein the set of PUSCH resources comprises at least one PUSCH resource carrying uplink control information. In an example, based on the set of PUSCH resources, the second communication device can explicitly or implicitly indicate one PUSCH resource in the set of PUSCH resources for carrying the UCI through a parameter in the DCI. In an example, the second communication device can allocate the same PUSCH resource to different first communication devices, such as having the same time domain resource and frequency domain resource, the same OCC code word length, the same modulation mode, and configuring different OCC indexes, so that different first communication devices can be multiplexed in the PUSCH resource, thereby improving the efficiency of the PUSCH resource carrying the UCI. In an example, the first communication device and the second communication device can agree that m RE groups are allocated as one PUSCH resource, and then the first communication device repeats the PUSCH resource m times in the m RE groups, respectively. Wherein m is an integer greater than or equal to 1.
[0039] In an embodiment, one PUSCH resource carrying uplink control information comprises at least one of the following: a starting RE group; a number of RE groups; a frequency hopping enabled parameter; a starting RE group of a second frequency hopping; an orthogonal cover code (OCC) code word length; an OCC index; a starting symbol; a number of consecutive symbols; demodulation reference signal (DMRS) configuration information; a number of repetitions; a PUSCH format; code rate information; modulation and coding strategy (MCS) level; modulation information; and MCS table information.
[0040] The starting RE group is used to determine the starting RE of the PUSCH resource. The RE group number is used to determine the number of consecutive RE groups starting from the indicated starting RE group. The frequency hopping enable parameter is used to determine whether the PUSCH resource is frequency hopping or not. The second frequency hopping starting RE group is used to determine the starting RE group of the second frequency hopping, and the RE group number of the second frequency hopping is also determined based on the RE group number. The OCC code word length is used to determine the information corresponding to the PUSCH, i.e., the OCC code word used when the PUSCH is transmitted in the allocated RE group, so that the PUSCHs of different UEs carrying UCI can be transmitted in the same RE group. The OCC index is used to determine which group of OCC code words is used, for example, the OCC code word with a length of 2 contains 2 groups of OCC code words, and the OCC index describes which group of the 2 groups of OCC code words is used; for example, the OCC code word with a length of 4 contains 4 groups of OCC code words, and the OCC index describes which group of the 4 groups of OCC code words is used. The starting symbol is used to determine the starting symbol of the PUSCH. The symbol number is used to determine the number of consecutive symbols of the PUSCH starting from the determined starting symbol. The DMRS configuration information is used to determine which symbols of the symbols of the PUSCH are DMRS symbols, or the type of DMRS. The repetition number is used to determine the number of repetitions of the PUSCH. The PUSCH format is used to determine the transmission mode of the PUSCH. The code rate information is used to determine the code rate used by the PUSCH resource. The MCS level is used to determine the MCS used by the PUSCH. The modulation information is used to determine the modulation mode of the PUSCH. The MCS table information is used to determine which MCS table the MCS level of the PUSCH comes from.
[0041] In an example, in the case of the frequency hopping enable parameter being 0, it indicates that the PUSCH resource does not perform frequency hopping, and correspondingly, the second frequency hopping starting RE group and the RE group number of the second frequency hopping do not need to be configured; in the case of the frequency hopping enable parameter being 1, it indicates that the PUSCH resource performs frequency hopping, and correspondingly, the second frequency hopping starting RE group and the RE group number of the second frequency hopping need to be configured.
[0042] In an embodiment, one RE group is defined to contain only frequency domain information, or, is defined to contain both frequency domain and time domain information. In an example, for the case that one RE group is defined to contain only frequency domain information, one PUSCH resource carrying UCI includes at least one of the following: a starting RE group; a number of RE groups; a frequency hopping enabled parameter; a starting RE group of a second frequency hopping; an OCC code word length; an OCC index; a starting symbol; a number of consecutive symbols; DMRS configuration information; a number of repetitions; a PUSCH format; a code rate information; an MCS level; a modulation information; an MCS table information. In an example, for the case that one RE group is defined to contain both frequency domain and time domain information, one PUSCH resource carrying uplink control information includes at least one of the following: a starting RE group; a number of RE groups; a frequency hopping enabled parameter; a starting RE group of a second frequency hopping; an OCC code word length; an OCC index; DMRS configuration information; a number of repetitions; a PUSCH format; a code rate information; an MCS level; a modulation information; an MCS table information.
[0043] In an embodiment, the first communication device is indicated by one PUSCH resource from a set of PUSCH resources for carrying uplink control information to transmit uplink control information. The second communication device can indicate one PUSCH resource from a set of PUSCH resources for carrying UCI to the first communication device for transmission of UCI.
[0044] In an embodiment, a number of subcarriers contained in one RE group in frequency domain includes at least one of the following: 1 subcarrier, Q subcarriers; where Q is greater than 1, and Q is predefined or configured.
[0045] In an embodiment, in response to one PUSCH resource containing one RE group, one RE group contains k subcarriers; the value of k is determined based on at least one of the following parameters: an OCC code word length associated with the PUSCH resource, a number of bits of uplink control information to be transmitted. Assuming that the first communication device and the second communication device agree that one RE group contains k consecutive subcarriers, the value of k is determined based on the OCC code word length configured for the PUSCH resource and / or the number of bits of UCI to be transmitted. For example, assuming that the OCC code word length associated with the PUSCH resource is L, and the number of bits of UCI to be transmitted is H, then k = H*L. In an example, the value of H is predefined by the first communication device and the second communication device, or the value of H is determined based on the number of bits of UCI to be transmitted. For example, if the number of bits of UCI to be transmitted is within a range A, then H is equal to 1; if the number of bits of UCI to be transmitted is within a range B, then H is equal to 2; if the number of bits of UCI to be transmitted is within a range C, H is equal to 3, and so on.
[0046] In one embodiment, in response to a PUSCH resource containing multiple RE groups, the number of RE groups is determined based on at least one of the following: the OCC codeword length associated with the PUSCH resource, and the number of bits of uplink control information to be transmitted. Assume the first and second communication devices agree that a PUSCH resource contains k1 RE groups, where the value of k1 is determined based on the OCC codeword length configured for the PUSCH resource and / or the number of bits of UCI to be transmitted. For example, assuming the OCC codeword length associated with the PUSCH resource is L1 and the number of bits of UCI to be transmitted is H1, then k1 = H1 * L1. In one example, the value of H1 is predefined by the first and second communication devices, or the value of H1 is determined based on the number of bits of UCI to be transmitted. For example, if the number of bits of UCI to be transmitted is in the range A1, then H1 equals 1; if the number of bits of UCI to be transmitted is in the range B1, then H1 equals 2; if the number of bits of UCI to be transmitted is in the range C1, then H1 equals 3, and so on. In one example, the first and second communication devices can agree on the number of RE groups occupied by a PUSCH resource to reduce signaling overhead. For example, the number of RE groups occupied by a PUSCH resource in the PUSCH resource set is m; where m is a positive integer greater than or equal to 1.
[0047] In one example, the second communication device can directly indicate RE groups via DCI. For instance, the second communication device can directly allocate RE groups carrying UCI PUSCH resources to the first communication device through the frequency domain resource allocation field in the DCI. For example, for several RE groups obtained for the configured RB carrying UCI PUSCH, a starting RE group and the number of consecutive RE groups are notified in the DCI (or RIV encoding can be used to encode the starting RE group and the number of consecutive RE groups into a parameter, thereby reducing signaling). The first communication device parses this parameter in the DCI to obtain the PUSCH resources used to carry UCI. In this method, the PUSCH resources of the PUSCH resource set do not need to be configured with a starting RE group and a number of RE groups. Alternatively, the second communication device can configure multiple RE groups through RRC signaling or system broadcast information; then, it can indicate one or more RE groups to the first communication device via DCI as PUSCH resources to carry UCI.
[0048] In one embodiment, the PUSCH includes a first PUSCH format, wherein the first PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain. To better support PUSCH resources for carrying UCI and to support the multiplexing of UCI for different UEs within the same PUSCH resource, a new PUSCH format can be designed to carry UCI; for example, this new PUSCH format can be denoted as the first PUSCH format.
[0049] The first PUSCH format may contain one or more consecutive symbols in the time domain and at least one RE group (i.e., one or more subcarriers) or one RB (i.e., 12 subcarriers) in the frequency domain. In one example, the first and second communication devices agree that the size of the time domain resource corresponding to the first PUSCH format can be extended to less than or equal to 14 symbols. The time domain resource is used to carry 1-2 bits of HARQ-ACK or beam recovery information. For example, when the first communication device is scheduled to transmit 1-2 bits of HARQ-ACK, the first communication device can determine a PUSCH resource of the first PUSCH format to carry the HARQ-ACK. For example, after the beam of the first communication device fails, the first communication device can use a PUSCH resource corresponding to the first PUSCH format to send a beam recovery request to the second communication device. After receiving the request, the second communication device reconfigures the beam information of the first communication device. Furthermore, the symbol position of the PUSCH can also be configured by the second communication device.
[0050] In one embodiment, the PUSCH resource corresponding to the first PUSCH format is configured with an initial cyclic shift; the data transmission method applied to the first communication device further includes:
[0051] A sequence cyclic shift is obtained based on the HARQ-ACK information state to be transmitted and a pre-configured state mapping table. The state mapping table represents the mapping relationship between the sequence cyclic shift and the HARQ-ACK information state. Based on the initial cyclic shift, the sequence cyclic shift and the index of the first symbol of the PUSCH resource in the scheduling unit determine a corresponding cyclic shift value for each symbol of the PUSCH resource. Based on the cyclic shift value corresponding to each symbol, the sequence of the PUSCH resource corresponding to each symbol is obtained. The corresponding sequence is transmitted in each symbol of the PUSCH resource corresponding to the first PUSCH format. An initial cyclic shift is configured for the PUSCH corresponding to the first PUSCH format. The first and second communication devices agree on a state mapping table that maps the sequence cyclic shift to the HARQ-ACK information state. A sequence cyclic shift can be obtained from this state mapping table based on the HARQ-ACK information state to be transmitted.
[0052] A cyclic shift value can be determined based on the initial cyclic shift and the obtained sequence cyclic shift. Specifically, the symbol index of the first symbol of a PUSCH resource in the first PUSCH format within a scheduling unit (e.g., a time slot) is further determined. Based on the symbol index of the first symbol, the aforementioned initial cyclic shift, and the aforementioned sequence cyclic shift obtained from the state mapping table, a cyclic shift value is determined for each symbol of the PUSCH resource, and the sequence corresponding to each symbol of the PUSCH resource is obtained based on the cyclic shift value. The corresponding sequence is transmitted in each symbol of the PUSCH resource in the first PUSCH format. The second communication device can configure the PUSCH resources in the time domain corresponding to the first PUSCH format, for example, configuring the starting symbol position and the number of symbols.
[0053] In one embodiment, at least one PUSCH resource set is configured, and the PUSCH resource set is configured with a corresponding index; wherein, the PUSCH resource set with the smallest index contains at least one of the following: PUSCH resources in a first PUSCH format, and PUSCH resources in a second PUSCH format.
[0054] In one example, the second communication device can be configured with multiple PUSCH resource sets for UCI transmission. The first PUSCH resource set is the PUSCH resource set with the smallest index; the second PUSCH resource set is the PUSCH resource set with an index greater than that of the first PUSCH resource set and is contiguous with it; the third PUSCH resource set is the PUSCH resource set with an index greater than that of the second PUSCH resource set and is contiguous with it, and so on.
[0055] The second communication device configures the PUSCH resource set with the smallest index to include at most n1 PUSCH resources, and agrees with the first communication device that the size of a PUSCH resource in the first PUSCH resource set is fixed at 1 RB in the frequency domain. That is, a predefined RB is a PUSCH resource used for UCI. The second communication device configures other PUSCH resource sets besides the PUSCH resource set with the smallest index to include at most n2 PUSCH resources, and the starting RB and the number of RBs of a PUSCH resource in the frequency domain in other PUSCH resource sets are configured. Other PUSCH resource sets have the same maximum PUSCH resource. Correspondingly, the first communication device also complies with the configuration signaling of the second communication device. Here, n1 is one of 8, 16, or 32; n2 is one of 8 or 16.
[0056] In one example, within the minimum indexed PUSCH resource set, a PUSCH resource can be configured in the time domain to include two cases: first, a maximum of two symbols; second, a maximum of 14 symbols. In one example, both the first and second PUSCH formats require the second communication device to configure the starting symbol and the number of symbols for a PUSCH resource. Furthermore, the PUSCH resources corresponding to these two formats use the same antenna port for information transmission. In another example, the second communication device configures the PUSCH resources corresponding to the first and second PUSCH formats within the minimum indexed PUSCH resource set. Each PUSCH resource is configured with a corresponding PUSCH format to help the first communication device determine the transmission method corresponding to that PUSCH resource, such as the symbol positions for DMRS and UCI, to indicate the generation of UCI information.
[0057] In one embodiment, the second PUSCH format includes at least one of the following: for carrying at least one bit of HARQ_ACK or carrying beam recovery information; the DMRS symbols and the symbols carrying uplink control information are alternately placed with a one-symbol interval between them; wherein, the second PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain. In one example, the second PUSCH format may include symbols for DMRS and symbols carrying UCI in the time domain, and the DMRS symbols and the symbols carrying UCI are alternately placed with a one-symbol interval between them; assuming the symbol index of a PUSCH resource is m1 to m2, if m1 is even, then m1 is a DMRS symbol, followed by a UCI symbol, and then the two types of symbols are alternately placed; otherwise, m1 is a UCI symbol, followed by a DMRS symbol, and then the two types of symbols are alternately placed.
[0058] In one embodiment, a PUSCH resource in the set of PUSCH resources with the minimum index is allowed to be configured to contain at least one RE or one RB in the frequency domain and at least one symbol in the time domain.
[0059] In one embodiment, the PUSCH carrying uplink control information and the PUSCH carrying uplink data are transmitted using different antenna ports. The first PUSCH format is a PUSCH for transmitting UCI. For convenience, the PUSCH for transmitting uplink data is defined here as the third PUSCH format. The original PUSCH also carries UCI, but its antenna port is the same as that of the PUSCH carrying uplink data. However, the first PUSCH format is dedicated to UCI, so to better support the performance of the first PUSCH format, the first communication device and the second communication device can agree to make the antenna port corresponding to the PUSCH resource of the first PUSCH format independent from the antenna port corresponding to the PUSCH resource carrying uplink data, that is, they use different antenna ports.
[0060] The PUSCH resources in the aforementioned PUSCH resource set for UCI can also be configured based on RB.
[0061] For example, a second communication device can be configured with multiple Resource Blocks (RBs) forming an RB set. The corresponding configuration signaling can be sent via system broadcast information. In this way, the configured RB set can be used by all first communication devices within the cell to determine a PUSCH resource carrying a UCI from the configured RB set. That is, all first communication devices within the cell share this RB set. Multiple such RB sets can exist. For example, during the initial random access process, if a first communication device needs to transmit UCI information, such as HARQ-ACK information during random access, it can determine a PUSCH resource from the configured RB set to carry the HARQ-ACK. This RB set can also be configured based on RRC signaling specific to the first communication device. In this way, each first communication device is configured with an independent RB set, and different first communication devices can determine the PUSCH resource for UCI from the configured RB set.
[0062] For example, a PUSCH resource for UCI occupies only one RB; then the second communication device can indicate a PUSCH resource or RB from the RB set through parameters in the DCI; after receiving the DCI, the first communication device parses the parameters and determines the corresponding RB from the RB set as a PUSCH resource for UCI transmission.
[0063] In one embodiment, FIG2 is a flowchart of another data transmission method provided by an embodiment of this application. This embodiment is applied to a case where a PUSCH format dedicated to uplink control information is designed. This embodiment can be executed by a second communication device. Exemplarily, the first communication device is a base station. As shown in FIG2, this embodiment includes: S210-S220.
[0064] S210. Configure the RE group corresponding to the PUSCH used to carry uplink control information.
[0065] S220, Receive PUSCH in RE group.
[0066] The second communication device can be directly or indirectly configured with the RE group corresponding to the PUSCH used to carry UCI, and receive the PUSCH carrying UCI through the RE group, thereby enabling the PUSCH to carry UCI like the PUCCH, thus ensuring data transmission efficiency.
[0067] In one embodiment, configuring the RE group corresponding to the PUSCH for carrying uplink control information includes:
[0068] Configure at least one RB for carrying uplink control information in the PUSCH; divide the RB into at least one RE group according to predefined rules; allocate at least one RE group from the divided at least one RE group to the first communication device as the RE group corresponding to the PUSCH carrying uplink control information.
[0069] The second communication device can configure at least one RB for carrying UCI PUSCH. Then, the second and first communication devices agree and divide the RB into one or more RE groups according to predefined rules. The second communication device then allocates one or more RE groups from the divided RE groups to the first communication device for carrying UCI PUSCH. The second communication device directly uses the pre-configured RBs, reducing signaling overhead. Furthermore, dividing the RB into one or more RE groups according to predefined rules requires no signaling overhead, thus achieving the effect of using one or more RE groups to carry UCI PUSCH while minimizing signaling overhead. In one example, the second communication device can configure at least one RB for carrying UCI PUSCH via Radio Resource Control (RRC) signaling or system broadcast messages; then, the second and first communication devices divide the configured RB into one or more RE groups according to predefined rules, or the second communication device configures the RB into one or more RE groups. In one example, the second communication device can select a RE group from a pre-configured RB by the parameter indication of the DCI. Specifically, the second communication device configures at least one RB for carrying the PUSCH of the UCI and divides the REs in the configured RB into at least one RE group. The second communication device indicates at least one RE group for carrying the PUSCH of the UCI by the parameter indication of the DCI of the scheduling PDSCH, so that the first communication device uses the at least one RE group to transmit the PUSCH for carrying the UCI to the second communication device.
[0070] In one embodiment, configuring the RE group corresponding to the PUSCH for carrying uplink control information includes:
[0071] The first communication device allocates at least one RE group from the configured or predefined RE groups as the RE group corresponding to the PUSCH carrying uplink control information. The second communication device directly configures or predefines at least one RE group, and instructs or allocates one or more RE groups to the first communication device via signaling as the RE group corresponding to the PUSCH carrying UCI.
[0072] In one embodiment, at least one RE group serves as a PUSCH resource carrying uplink control information, comprising: each RE group in at least one RE group for a PUSCH resource having the same size and location in the time domain and the same size in the frequency domain. A second communication device may configure a set of PUSCH resources carrying UCI and indicate this set of PUSCH resources to a first communication device. The first communication device then determines a PUSCH resource from the configured PUSCH resource set as at least one RE group for carrying UCI, wherein the at least one RE group corresponding to this PUSCH resource has the same resource size in the frequency domain and the same resource size and location in the time domain.
[0073] In one embodiment, the data transmission method applied to the second communication device further includes:
[0074] Configure a PUSCH resource set for carrying uplink control information (UCI); wherein the PUSCH resource set includes at least one PUSCH resource carrying uplink control information. In one example, based on the PUSCH resource set, the second communication device can explicitly or implicitly indicate, through parameters in the DCI, that a PUSCH resource in the PUSCH resource set is used to carry UCI. In one example, the second communication device can allocate the same PUSCH resource to different first communication devices, for example, having the same time-domain and frequency-domain resources, the same OCC codeword length, the same modulation scheme, and configuring different OCC indices. This allows different first communication devices to reuse the PUSCH resource, thereby improving the efficiency of carrying UCI using the PUSCH resource. In one example, the first and second communication devices can, according to an agreement, allocate m RE groups as one PUSCH resource, and the first communication device will repeat the PUSCH resource m times in each of the m RE groups. Here, m is an integer greater than or equal to 1.
[0075] In one embodiment, a PUSCH resource carrying uplink control information includes at least one of the following: an initial RE group; the number of RE groups; frequency hopping enable parameters; the initial RE group for the second frequency hopping; the orthogonal coverage code (OCC) codeword length; the OCC index; the start symbol; the number of consecutive symbols; demodulation reference signal (DMRS) configuration information; the number of repetitions; the PUSCH format; the code rate information; the modulation and coding scheme (MCS) level; modulation information; and MCS table information. The initial RE group is used to determine the starting RE corresponding to the PUSCH resource. The number of RE groups is used to determine the number of consecutive RE groups starting from the indicated initial RE group. The frequency hopping enable parameters are used to determine whether the PUSCH is frequency hopping. The initial RE group for the second frequency hopping is used to determine the starting RE group for the second frequency hopping, and the number of RE groups corresponding to the second frequency hopping is also determined based on the number of RE groups. The OCC codeword length is used to determine the information corresponding to the PUSCH, that is, the OCC codeword is used when the PUSCH is transmitted in the allocated RE group, thus supporting the transmission of PUSCHs carrying UCI from different UEs in the same RE group. The OCC index is used to determine which set of OCC codewords is used. For example, an OCC codeword of length 2 contains 2 sets of OCC codewords, and the OCC index describes which set of 2 sets of OCC codewords is used; similarly, an OCC codeword of length 4 contains 4 sets of OCC codewords, and the OCC index describes which set of 4 sets of OCC codewords is used. The start symbol is used to determine the start symbol of the PUSCH. The number of symbols is used to determine the number of consecutive symbols in the PUSCH starting from the determined start symbol. DMRS configuration information is used to determine which symbols in the PUSCH are DMRS symbols, or the type of DMRS. The repetition count is used to determine the number of times the PUSCH is retransmitted. The PUSCH format is used to determine the transmission method of the PUSCH. The code rate information is used to determine the code rate used by the PUSCH resources. The MCS level is used to determine the MCS used by the PUSCH. The modulation information is used to determine the modulation method of the PUSCH. The MCS table information is used to determine which MCS table the MCS level of the PUSCH comes from.
[0076] In one example, when the frequency hopping enable parameter is 0, it means that the PUSCH resource does not perform frequency hopping. Correspondingly, there is no need to configure the starting RE group for the second frequency hopping and the number of RE groups corresponding to the second frequency hopping. When the frequency hopping enable parameter is 1, it means that the PUSCH resource performs frequency hopping. Correspondingly, it is necessary to configure the starting RE group for the second frequency hopping and the number of RE groups corresponding to the second frequency hopping.
[0077] In one embodiment, a RE group is defined to contain only frequency domain information, or it is defined to contain both frequency domain and time domain information. In one example, for the case where a RE group is defined to contain only frequency domain information, a PUCSH resource carrying UCI includes at least one of the following: initial RE group; number of RE groups; frequency hopping enable parameters; initial RE group for the second frequency hopping; orthogonal coverage code (OCC) codeword length; OCC index; start symbol; number of consecutive symbols; demodulation reference signal (DMRS) configuration information; repetition count; PUSCH format; code rate information; modulation and coding scheme (MCS) level; modulation information; and MCS table information. In one example, for the case where a RE group is defined to contain both frequency domain and time domain information, a PUSCH resource carrying uplink control information includes at least one of the following: initial RE group; number of RE groups; frequency hopping enable parameters; initial RE group for the second frequency hopping; OCC codeword length; OCC index; DMRS configuration information; repetition count; PUSCH format; code rate information; MCS level; modulation information; and MCS table information.
[0078] In one embodiment, the number of subcarriers included in a RE group in the frequency domain includes at least one of the following: 1 subcarrier, Q subcarriers; wherein Q is greater than 1, and the value of Q is predefined or configured.
[0079] In one embodiment, in response to a PUSCH resource comprising a RE group, and an RE group comprising k subcarriers, the value of k is determined based on at least one of the following parameters: the OCC codeword length associated with the PUSCH resource, and the number of bits of uplink control information to be transmitted. Assuming the first and second communication devices agree that an RE group comprises k consecutive subcarriers, the value of k is determined based on the OCC codeword length configured for the PUSCH resource and / or the number of bits of UCI to be transmitted. For example, assuming the OCC codeword length associated with the PUSCH resource is L, and the number of bits of UCI to be transmitted is H, then k = H * L. In one example, the value of H is predefined between the first and second communication devices, or the value of H is determined based on the number of bits of UCI to be transmitted. For example, if the number of bits of UCI to be transmitted is in range A, then H equals 1; if the number of bits of UCI to be transmitted is in range B, then H equals 2; if the number of bits of UCI to be transmitted is in range C, then H equals 3, and so on.
[0080] In one embodiment, in response to a PUSCH resource containing multiple RE groups, the number of RE groups is determined based on at least one of the following: the OCC codeword length associated with the PUSCH resource, and the number of bits of uplink control information to be transmitted. Assume that the first and second communication devices agree that a PUSCH resource contains k1 RE groups, where the value of k1 is determined based on the OCC codeword length configured for the PUSCH resource and / or the number of bits of UCI to be transmitted. For example, assuming the OCC codeword length associated with the PUSCH resource is L1 and the number of bits of UCI to be transmitted is H1, then k1 = H1 * L1. In one example, the value of H1 is predefined between the first and second communication devices, or the value of H1 is determined based on the number of bits of UCI to be transmitted. For example, if the number of bits of UCI to be transmitted is in the range A1, then H1 equals 1; if the number of bits of UCI to be transmitted is in the range B1, then H1 equals 2; if the number of bits of UCI to be transmitted is in the range C1, then H1 equals 3, and so on. In one example, the first and second communication devices can agree on the number of RE groups occupied by a PUSCH resource to reduce signaling overhead. For example, the number of RE groups occupied by a PUSCH resource in the PUSCH resource set is m; where m is a positive integer greater than or equal to 1.
[0081] In one example, the second communication device can directly indicate RE groups via DCI. For instance, the second communication device can directly allocate RE groups carrying UCI PUSCH resources to the first communication device through the frequency domain resource allocation field in the DCI. For example, for several RE groups obtained for the configured RB carrying UCI PUSCH, a starting RE group and the number of consecutive RE groups are notified in the DCI (or RIV encoding can be used to encode the starting RE group and the number of consecutive RE groups into a parameter, thereby reducing signaling). The first communication device parses this parameter in the DCI to obtain the PUSCH resources used to carry UCI. In this method, the PUSCH resources of the PUSCH resource set do not need to be configured with a starting RE group and a number of RE groups. Alternatively, the second communication device can configure multiple RE groups through RRC signaling or system broadcast information; then, it can indicate one or more RE groups to the first communication device via DCI as PUSCH resources to carry UCI.
[0082] In one embodiment, the PUSCH includes a first PUSCH format, wherein the first PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain. To better support PUSCH resources for carrying UCI and to support the multiplexing of UCI for different UEs within the same PUSCH resource, a new PUSCH format can be designed to carry UCI; for example, this new PUSCH format can be denoted as the first PUSCH format.
[0083] The first PUSCH format may contain one or more consecutive symbols in the time domain and at least one RE group (i.e., one or more subcarriers) or one RB (i.e., 12 subcarriers) in the frequency domain. In one example, the first and second communication devices agree that the size of the time domain resource corresponding to the first PUSCH format can be extended to less than or equal to 14 symbols. The time domain resource is used to carry 1-2 bits of HARQ-ACK or beam recovery information. For example, when the first communication device is scheduled to transmit 1-2 bits of HARQ-ACK, the first communication device can determine a PUSCH resource of the first PUSCH format to carry the HARQ-ACK. For example, after the beam of the first communication device fails, the first communication device can use a PUSCH resource corresponding to the first PUSCH format to send a beam recovery request to the second communication device. After receiving the request, the second communication device reconfigures the beam information of the first communication device. Furthermore, the symbol position of the PUSCH can also be configured by the second communication device.
[0084] In one embodiment, an initial cyclic shift is configured for the PUSCH resource corresponding to the first PUSCH format; the data transmission method applied to the second communication device further includes:
[0085] A sequence cyclic shift is determined based on the state of the HARQ-ACK information to be transmitted and a pre-configured state mapping table. The state mapping table represents the mapping relationship between the sequence cyclic shift and the HARQ-ACK information state. Based on the initial cyclic shift, the sequence cyclic shift, and the index of the first symbol of the PUSCH resource in the scheduling unit, a corresponding cyclic shift value is determined for each symbol of the PUSCH resource. Based on the cyclic shift value corresponding to each symbol, the sequence corresponding to each symbol of the PUSCH resource is obtained. The corresponding sequence is received in each symbol of the PUSCH resource corresponding to the first PUSCH format.
[0086] An initial cyclic shift is configured for the PUSCH corresponding to the first PUSCH format. The first and second communication devices agree on a state mapping table that maps the sequence cyclic shift to the HARQ-ACK information state. A sequence cyclic shift can be obtained from this state mapping table based on the HARQ-ACK information state to be transmitted.
[0087] A cyclic shift value can be determined based on the initial cyclic shift and the obtained sequence cyclic shift. Specifically, the symbol index of the first symbol of a PUSCH resource in the first PUSCH format within a scheduling unit (e.g., a time slot) is further determined. Based on the symbol index of the first symbol, the aforementioned initial cyclic shift, and the aforementioned sequence cyclic shift obtained from the state mapping table, a cyclic shift value is determined for each symbol of the PUSCH resource, and the sequence corresponding to each symbol of the PUSCH resource is obtained based on the cyclic shift value. The corresponding sequence is transmitted in each symbol of the PUSCH resource in the first PUSCH format. The second communication device can configure the PUSCH resources in the time domain corresponding to the first PUSCH format, for example, configuring the starting symbol position and the number of symbols.
[0088] In one embodiment, at least one PUSCH resource set is configured, and the PUSCH resource set is configured with a corresponding index; wherein, the PUSCH resource set with the smallest index contains at least one of the following: PUSCH resources in a first PUSCH format, and PUSCH resources in a second PUSCH format.
[0089] In one example, the second communication device can be configured with multiple PUSCH resource sets for UCI transmission. The first PUSCH resource set is the PUSCH resource set with the smallest index; the second PUSCH resource set is the PUSCH resource set with an index greater than that of the first PUSCH resource set and is contiguous with it; the third PUSCH resource set is the PUSCH resource set with an index greater than that of the second PUSCH resource set and is contiguous with it, and so on.
[0090] The second communication device configures the PUSCH resource set with the smallest index to include at most n1 PUSCH resources, and agrees with the first communication device that the size of a PUSCH resource in the first PUSCH resource set is fixed at 1 RB in the frequency domain. That is, a predefined RB is a PUSCH resource used for UCI. The second communication device configures other PUSCH resource sets besides the PUSCH resource set with the smallest index to include at most n2 PUSCH resources, and the starting RB and the number of RBs of a PUSCH resource in the frequency domain in other PUSCH resource sets are configured. Other PUSCH resource sets have the same maximum PUSCH resource. Correspondingly, the first communication device also complies with the configuration signaling of the second communication device. Here, n1 is one of 8, 16, or 32; n2 is one of 8 or 16.
[0091] In one example, within the minimum indexed PUSCH resource set, a PUSCH resource can be configured in the time domain to include two cases: first, a maximum of two symbols; second, a maximum of 14 symbols. In one example, both the first and second PUSCH formats require the second communication device to configure the starting symbol and the number of symbols for a PUSCH resource. Furthermore, the PUSCH resources corresponding to these two formats use the same antenna port for information transmission. In another example, the second communication device configures the PUSCH resources corresponding to the first and second PUSCH formats within the minimum indexed PUSCH resource set. Each PUSCH resource is configured with a corresponding PUSCH format to help the first communication device determine the transmission method corresponding to that PUSCH resource, such as the symbol positions for DMRS and UCI, to indicate the generation of UCI information.
[0092] In one embodiment, the second PUSCH format includes at least one of the following: for carrying at least one bit of HARQ_ACK or carrying beam recovery information; the DMRS symbols and the symbols carrying uplink control information are alternately placed with a one-symbol interval between them; wherein, the second PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain. In one example, the second PUSCH format may include symbols for DMRS and symbols carrying UCI in the time domain, and the DMRS symbols and the symbols carrying UCI are alternately placed with a one-symbol interval between them; assuming the symbol index of a PUSCH resource is m1 to m2, if m1 is even, then m1 is a DMRS symbol, followed by a UCI symbol, and then the two types of symbols are alternately placed; otherwise, m1 is a UCI symbol, followed by a DMRS symbol, and then the two types of symbols are alternately placed.
[0093] In one embodiment, a PUSCH resource in the set of PUSCH resources with the minimum index is allowed to be configured to contain at least one RE or one RB in the frequency domain and at least one symbol in the time domain.
[0094] In one embodiment, the PUSCH carrying uplink control information and the PUSCH carrying uplink data are transmitted using different antenna ports. The first PUSCH format is a PUSCH for transmitting UCI. For convenience, the PUSCH for transmitting uplink data is defined here as the third PUSCH format. The original PUSCH also carries UCI, but its antenna port is the same as that of the PUSCH carrying uplink data. However, the first PUSCH format is dedicated to UCI, so to better support the performance of the first PUSCH format, the first communication device and the second communication device can agree to make the antenna port corresponding to the PUSCH resource of the first PUSCH format independent from the antenna port corresponding to the PUSCH resource carrying uplink data, that is, they use different antenna ports.
[0095] The PUSCH resources in the aforementioned PUSCH resource set for UCI can also be configured based on RB.
[0096] For example, a second communication device can be configured with multiple Resource Blocks (RBs) forming an RB set. The corresponding configuration signaling can be sent via system broadcast information. In this way, the configured RB set can be used by all first communication devices within the cell to determine a PUSCH resource carrying a UCI from the configured RB set. That is, all first communication devices within the cell share this RB set. Multiple such RB sets can exist. For example, during the initial random access process, if a first communication device needs to transmit UCI information, such as HARQ-ACK information during random access, it can determine a PUSCH resource from the configured RB set to carry the HARQ-ACK. This RB set can also be configured based on RRC signaling specific to the first communication device. In this way, each first communication device is configured with an independent RB set, and different first communication devices can determine the PUSCH resource for UCI from the configured RB set.
[0097] For example, a PUSCH resource for UCI occupies only one RB; then the second communication device can indicate a PUSCH resource or RB from the RB set through parameters in the DCI; after receiving the DCI, the first communication device parses the parameters and determines the corresponding RB from the RB set as a PUSCH resource for UCI transmission.
[0098] To further illustrate the specific implementation and basic ideas of this application, the following embodiments are provided but are not limited to the above embodiments. In the following examples, the first communication device is a UE and the second communication device is a base station.
[0099] In one example, the base station configures PUSCH resources for the UE to carry UCI, and these PUSCH resources are configured in the following two ways:
[0100] The first approach involves the base station configuring at least one redundancy block (RB) for carrying UCI PUSCH, which reduces signaling overhead. The base station and the UE agree, according to predefined rules, to identify these configured RBs as multiple RE groups, thus eliminating signaling overhead. The base station can then allocate one or more RE groups to the UE as resources for transmitting UCI PUSCH. That is, the UCI-carrying PUSCH is transmitted within these allocated RE groups. This achieves the effect of PUSCH carrying UCI like PUCCH while reducing signaling overhead, ensuring high transmission efficiency.
[0101] The second approach involves the base station directly configuring RE groups for carrying UCI PUSCH. For example, the base station directly instructs or allocates one or more RE groups to a UE via signaling as resources for the UE to transmit UCI PUSCH.
[0102] UCI includes at least one of the following: HARQ-ACK, SR, CSI, and beam recovery.
[0103] In one example, the definition of an RE group includes at least one of the following:
[0104] In Method 1, the resource size and location of an RE group are predefined. Each RE group has the same size and location in the time domain, such as an equal number of symbols and the same symbol locations; each RE group also has the same size in the frequency domain, for example, each RE group contains an equal number of subcarriers. For example, an RE group in the time domain is always equal to the number of symbols available for UCI in a slot (excluding DMRS symbols used for UCI in the slot). In the frequency domain, an RE group contains n subcarriers (n is 1, 2, 3, ...). The value of n can be predefined by the base station and the UE, or the value of n can also be configured by the base station. Alternatively, RE groups can be defined only in the frequency domain, as described above. If an RE group is defined only for its corresponding frequency resources, without defining corresponding time domain resources, then the time domain resources of the RE group are configured based on signaling. In this case, different RE groups can have different time domain sizes and / or locations.
[0105] Method 2 involves configuring the size and location of a RE group. In this case, the time-domain size and location of different RE groups are configured, allowing for flexible symbol counts and locations. The frequency-domain size and location of different RE groups are also configured, allowing for flexible subcarrier counts and locations. While this method offers flexibility in RE group size and location, it incurs significant signaling overhead.
[0106] In one example, the process of obtaining the RE group includes the following:
[0107] The base station configures at least one redundancy block (RB) via signaling and indicates RE groups from the configured RBs using DCI parameters. Specifically, the base station configures at least one RB for transmitting PUSCH carrying UCI, and according to convention, divides the REs in the configured RBs into at least one RE group. The base station indicates at least one RE group as a resource for the UE to transmit the PUSCH carrying UCI using the DCI parameters for scheduling PDSCH. Further, an RE group is configured with an OCC codeword and an OCC index. The UE generates the PUSCH transmission information based on the OCC codeword of the indicated RE group and performs the PUSCH transmission within that RE group.
[0108] The DCI format here refers to the DCI format for scheduling PDSCH, not the DCI format for scheduling PUSCH.
[0109] Specific design:
[0110] The base station configures the RBs used to carry the PUSCH for UCI via RRC signaling or system broadcast messages. The base station and UE divide the configured RBs into multiple RE groups according to the predefined RE group definitions, or the base station reconfigures the configured RBs into multiple RE groups.
[0111] The base station configures a set of PUSCH resources to carry UCI. This set of PUSCH resources contains at least one PUSCH resource carrying UCI, determined based on RE groups. A PUSCH resource carrying UCI contains at least one of the following: starting RE group, number of RE groups, frequency hopping enable parameters, starting RE group for the second frequency hopping, OCC codeword length, OCC index (describing which OCC codeword group), start symbol, number of consecutive symbols, DMRS configuration information, repetition count, PUSCH format, code rate information, MCS level, modulation information, and MCS table information.
[0112] The starting RE group is used to determine the starting RE for this PUSCH.
[0113] The RE group number is used to determine the number of consecutive RE groups starting from the indicated initial RE group.
[0114] The frequency hopping enable parameter is used to determine whether the PUSCH is frequency hopping.
[0115] The starting RE group for the second frequency hopping is used to determine the starting RE group for the second frequency hopping, and the number of RE groups corresponding to the second frequency hopping is also determined based on the number of RE groups.
[0116] The OCC codeword length is used to determine the information corresponding to the PUSCH, that is, the OCC codeword is used when the PUSCH is transmitted in the allocated RE group. This can support the transmission of PUSCHs carrying UCI of different UEs in the same RE group.
[0117] The OCC index is used to determine which set of OCC codewords is used. For example, an OCC codeword of length 2 contains 2 sets of OCC codewords, and the OCC index describes which of these 2 sets of OCC codewords is used. For example, an OCC codeword of length 4 contains 4 sets of OCC codewords, and the OCC index describes which of these 4 sets of OCC codewords is used.
[0118] The start symbol is used to determine the start symbol of the PUSCH.
[0119] The number of symbols is used to determine the number of consecutive symbols in the PUSCH, starting from the determined starting symbol.
[0120] DMRS configuration information is used to determine which symbols in the PUSCH are DMRS symbols, or the type of DMRS.
[0121] The repetition count is used to determine the number of times the PUSCH is transmitted repeatedly.
[0122] The PUSCH format is used to determine how the PUSCH is transmitted.
[0123] Rate information is used to determine the rate of the PUSCH resource.
[0124] The MCS rating is used to determine the MCS used by the PUSCH.
[0125] Modulation information is used to determine the modulation scheme of the PUSCH.
[0126] MCS table information is used to determine which MCS table the PUSCH's MCS rating comes from.
[0127] Based on the PUSCH resource set, the parameters in the base station (via DCI) explicitly indicate / imply a PUSCH resource for the UE. The base station and the UE agree to transmit UCI in the determined PUSCH resource.
[0128] The base station can allocate the same PUSCH resources to different UEs, such as having the same time-domain and frequency-domain resources, the same OCC codeword length, and the same modulation, but configuring different OCC indexes. In this way, different UEs can reuse the same PUSCH resources, thereby improving the efficiency of PUSCH carrying UCI.
[0129] Furthermore, the base station and the UE can agree that if m RE groups are allocated as one PUSCH resource, the UE can repeat the PUSCH m times in each of the m RE groups.
[0130] Furthermore, the base station and the UE can agree on the number of RE groups, thereby reducing signaling overhead. For example, the number of RE groups occupied by a PUSCH resource in the PUSCH resource set is always m. m can be one of 1, 2, 3, 4, 5, 6, ...
[0131] Furthermore, the base station and UE can also consider the following methods to obtain the number of RE groups. For example, the base station and UE agree that an RE group contains k consecutive subcarriers. The value of k for an RE group can be determined based on the OCC codeword length L configured for the PUSCH resource. For example, k = H * L; where the value of H is predefined by the base station and UE, or the value of H can be determined based on the number of bits of the UCI to be transmitted. For example, if the number of UCI bits is in range A, then H equals 1; if the number of UCI bits is in range B, then H equals 2; if the number of UCI bits is in range C, then H equals 3, and so on.
[0132] Furthermore, the base station can also directly instruct RE groups via DCI. For example, the base station can directly allocate RE groups carrying UCI PUSCH resources to the UE via the frequency domain resource allocation field in the DCI. For instance, for several RE groups obtained for the configured RB carrying UCI PUSCH, a starting RE group and the number of consecutive RE groups are notified in the DCI (or RIV encoding can be used to encode the starting RE group and the number of consecutive RE groups into a parameter, thereby reducing signaling). The UE parses this parameter in the DCI to obtain the PUSCH resources used to carry UCI. In the above method, the PUSCH resources of the PUSCH resource set do not need to be configured with a starting RE group and the number of RE groups. Alternatively, the base station can configure multiple RE groups via RRC signaling or system broadcast information. Then, it can instruct one or more RE groups to the UE via DCI to be used as resources for carrying UCI PUSCH.
[0133] In one example, in order to better support PUSCH for carrying UCI and to support the multiplexing of UCI of different UEs in the same PUSCH, a new PUSCH format can be used to carry UCI, for example, referred to as the first PUSCH format.
[0134] A PUSCH time-domain resource corresponding to a first PUSCH format includes one or two consecutive symbols (the base station and UE can also agree that the time-domain resource of the PUSCH can be extended to 1 to 14 symbols). It is used to carry 1 to 2 bits of HARQ-ACK, or beam recovery information. For example, when the UE schedules the transmission of 1 to 2 bits of HARQ-ACK, the UE can determine a PUSCH resource of the first PUSCH format to carry the HARQ-ACK. For example, after the UE's beam fails, the UE can use a PUSCH resource corresponding to the first PUSCH format to send a beam recovery request to the base station. After receiving the request, the base station reconfigures the UE's beam information. The base station can configure the symbol position of the PUSCH.
[0135] The frequency domain resources of the PUSCH corresponding to the first PUSCH format include 12 subcarriers, which is one RB.
[0136] The PUSCH corresponding to the first PUSCH format is configured with an initial cyclic shift. The base station and UE agree on a mapping table between the sequence cyclic shift and the HARQ-ACK information state. Based on the HARQ-ACK information state to be transmitted, a sequence cyclic shift can be obtained from this table.
[0137] A cyclic shift value can be determined based on the initial cyclic shift and the obtained sequence cyclic shift. Specifically, the symbol index of the first symbol of a PUSCH resource in a first PUSCH format within a scheduling unit (e.g., a time slot) is further determined. Based on the symbol index of the first symbol, the aforementioned initial cyclic shift, and the aforementioned sequence cyclic shift obtained from the table, a cyclic shift value is determined for each symbol of the PUSCH resource, and the sequence corresponding to each symbol of the PUSCH resource is obtained based on the cyclic shift value. The corresponding sequence is transmitted in each symbol of the first PUSCH format. The resources of the first PUSCH format in the time domain can be configured, for example, configuring the starting symbol position and the number of symbols.
[0138] The first PUSCH format is used for transmitting UCI. For convenience, the PUSCH for transmitting uplink data is defined here as the third PUSCH format. The original PUSCH also carries UCI, but its antenna port is the same as that of the PUSCH carrying uplink data. However, the first PUSCH format is dedicated to UCI, so to better support the performance of the first PUSCH format, the base station and UE agree that the antenna port of the first PUSCH format PUSCH is independent of the antenna port of the PUSCH carrying uplink data; that is, they use different antenna ports.
[0139] The PUSCH resources in the aforementioned PUSCH resource set for UCI can also be configured based on RB.
[0140] For example, a base station can configure multiple Resource Blocks (RBs) to form an RB set. The corresponding configuration signaling can be sent via system broadcast information, allowing all UEs within the cell to determine a PUSCH resource carrying UCI from the configured RB set. In other words, all UEs within the cell share this RB set. Multiple such RB sets can exist. For example, during the initial random access procedure, if a UE needs to transmit UCI information, such as HARQ-ACK information during random access, the UE can determine a PUSCH resource from the configured RB set to carry the HARQ-ACK. This RB set can also be configured based on UE-specific RRC signaling, in which case each UE is configured with an independent RB set, and different UEs can determine the PUSCH resource for UCI from the configured RB set.
[0141] For example, a PUSCH resource for UCI occupies only one RB. The base station can then use parameters in the DCI to indicate a PUSCH resource or RB from the RB set. After receiving the DCI, the UE parses the parameters and determines the corresponding RB from the RB set as a PUSCH resource for UCI.
[0142] Multiple PUSCH resource sets (including RE group sets or RB sets) for UCI can be configured. The first PUSCH resource set is the PUSCH resource set with the smallest index. The second PUSCH resource set is an index with an index greater than that of the first PUSCH resource set and is contiguous with it. The third PUSCH resource set is an index with an index greater than that of the second PUSCH resource set and is contiguous with it, and so on.
[0143] The base station configures the PUSCH resource set with the smallest index, which includes at most n1 PUSCH resources. It is agreed with the UE that the size of a PUSCH resource in the first PUSCH resource set is fixed at 1 RB in the frequency domain; that is, a predefined RB is a PUSCH resource used for UCI. The base station configures other PUSCH resource sets besides the one with the smallest index, which include at most n2 PUSCH resources. The starting RB and the number of RBs for a PUSCH resource in the frequency domain are configured for each PUSCH resource in these other sets, and these other PUSCH resource sets have the same maximum PUSCH resource. Correspondingly, the UE also complies with the base station's configuration signaling. Here, n1 is one of 8, 16, or 32, and n2 is one of 8 or 16.
[0144] Within the smallest set of PUSCH resources, a PUSCH resource can be configured in the time domain in two ways: First, a maximum of 2 symbols; second, a maximum of 14 symbols. These two cases are distinguishable based on two predefined PUSCH formats, such as the first PUSCH format mentioned above and the second PUSCH format described below. Both the first and second PUSCH formats require the base station to configure the starting symbol and the number of symbols for a PUSCH resource. The PUSCHs corresponding to these two formats are transmitted using the same antenna port.
[0145] In one example, the second PUSCH format has at least one of the following properties:
[0146] Used to carry 1-2 bits of HARQ-ACK, or to carry beam recovery information; the DMRS symbol and the symbol carrying UCI information satisfy the following: DMRS symbols and UCI symbols are alternated with a one-symbol interval; assuming the symbol index of a PUSCH resource is m1-m2. If m1 is even, then m1 is the DMRS symbol, followed by the UCI symbol, and then the two types of symbols alternate; otherwise, m1 is the UCI symbol, followed by the DMRS symbol, and then the two types of symbols alternate.
[0147] The base station can configure the PUSCH resources corresponding to the first and second PUSCH formats within the set of PUSCH resources with the smallest index. Each PUSCH resource is configured with a corresponding PUSCH format to help the UE determine the transmission mode corresponding to that PUSCH resource, such as the symbol positions of DMRS and UCI, and the generation of information indicating UCI.
[0148] In one embodiment, FIG3 is a structural block diagram of a data transmission device provided in this application. This embodiment is applied to a first communication device. As shown in FIG3, the data transmission device in this embodiment includes: a determining module 310 and a transmitting module 320.
[0149] The determination module 310 is configured to determine the resource unit (RE) group corresponding to the physical uplink shared channel (PUSCH) used to carry uplink control information; the transmission module 320 is configured to transmit the PUSCH in the RE group.
[0150] In one embodiment, the determining module 310 includes:
[0151] The determining unit is configured to determine at least one resource block (RB) of a PUSCH configured by the second communication device to carry uplink control information; the partitioning unit is configured to partition the RB into at least one RE group according to a predefined rule; the determining unit is further configured to determine at least one RE group allocated by the second communication device from the partitioned at least one RE group as the RE group corresponding to the PUSCH carrying uplink control information.
[0152] In one embodiment, the determining module 310 includes:
[0153] The determining unit is further configured to determine at least one RE group allocated by the second communication device from a configured or predefined RE group as the RE group corresponding to the PUSCH carrying uplink control information.
[0154] In one embodiment, the uplink control information includes at least one of the following: Hybrid Automatic Repeat Request Response (HARQ-ACK); Scheduling Request (SR); Beam Recovery Information; Channel State Information (CSI).
[0155] In one embodiment, the time-frequency domain resource size and time-frequency domain resource location of each RE group are predefined or preconfigured.
[0156] In one embodiment, each RE group contains the same time-domain resource size, time-domain resource location, and frequency-domain resource size.
[0157] In one embodiment, each RE group contains the same number of subcarriers and symbols, as well as the same symbol locations.
[0158] In one instance, each RE group is configured with an orthogonal overlay code (OCC) codeword.
[0159] In one embodiment, at least one RE group serves as a PUSCH resource carrying uplink control information, comprising: each RE group in at least one RE group for a PUSCH resource having the same size and location in the time domain and the same size in the frequency domain.
[0160] In one embodiment, the data transmission apparatus applied to the first communication device further includes:
[0161] The determining module is further configured to determine a set of PUSCH resources that carry uplink control information and are configured by the second communication device; wherein the set of PUSCH resources includes at least one PUSCH resource that carries uplink control information.
[0162] In one embodiment, a PUSCH resource carrying uplink control information includes at least one of the following: starting RE group; number of RE groups; frequency hopping enable parameters; starting RE group for second frequency hopping; orthogonal coverage code (OCC) codeword length; OCC index; starting symbol; number of consecutive symbols; demodulation reference signal (DMRS) configuration information; number of repetitions; PUSCH format; code rate information; modulation and coding scheme (MCS) level; modulation information; and MCS table information.
[0163] In one embodiment, an RE group is defined to contain only frequency domain information, or it is defined to contain both frequency domain and time domain information.
[0164] In one embodiment, the first communication device transmits uplink control information from a PUSCH resource indicated in a set of PUSCH resources used to carry uplink control information.
[0165] In one embodiment, the number of subcarriers included in a RE group in the frequency domain includes at least one of the following: 1 subcarrier, Q subcarriers; wherein Q is greater than 1, and the value of Q is predefined or configured.
[0166] In one embodiment, in response to a PUSCH resource comprising a RE group, and a RE group comprising k subcarriers; the value of k is determined based on at least one of the following parameters: the OCC codeword length associated with the PUSCH resource, and the number of bits of uplink control information to be transmitted.
[0167] In one embodiment, in response to a PUSCH resource containing multiple RE groups, the number of multiple RE groups is determined based on at least one of the following: the OCC codebook length associated with the PUSCH resource, and the number of bits of uplink control information to be transmitted.
[0168] In one embodiment, the PUSCH includes a first PUSCH format, wherein the first PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain.
[0169] In one embodiment, the PUSCH resource corresponding to the first PUSCH format is configured with an initial cyclic shift; the data transmission apparatus applied to the first communication device further includes:
[0170] The determining module is further configured to obtain a sequence cyclic shift based on the state of the HARQ-ACK information to be transmitted and a pre-configured state mapping table; wherein, the state mapping table is used to characterize the mapping relationship between the sequence cyclic shift and the HARQ-ACK information state; the determining module is further configured to determine a corresponding cyclic shift value for each symbol of the PUSCH resource based on the initial cyclic shift, the sequence cyclic shift, and the index of the first symbol of the PUSCH resource in the scheduling unit; the determining module is further configured to obtain the sequence of the PUSCH resource corresponding to each symbol based on the cyclic shift value corresponding to each symbol; the transmitting module is further configured to transmit the corresponding sequence in each symbol of the PUSCH resource corresponding to the first PUSCH format.
[0171] In one embodiment, the second PUSCH format includes at least one of the following: for carrying at least one bit of HARQ_ACK or carrying beam recovery information; the DMRS symbol and the symbol carrying uplink control information are alternately placed with a one-symbol interval between them; wherein the second PUSCH format includes: in the time domain: at least one symbol; in the frequency domain: at least one RE group, or one RB.
[0172] In one embodiment, at least one PUSCH resource set is configured, and the PUSCH resource set is configured with a corresponding index; wherein, the PUSCH resource set with the smallest index contains at least one of the following: PUSCH resources in a first PUSCH format, and PUSCH resources in a second PUSCH format.
[0173] In one embodiment, a PUSCH resource in the set of PUSCH resources with the minimum index is allowed to be configured to contain at least one RE or one RB in the frequency domain and at least one symbol in the time domain.
[0174] In one embodiment, the PUSCH carrying uplink control information and the PUSCH carrying uplink data are transmitted using different antenna ports.
[0175] The data transmission device provided in this embodiment is configured to implement the data transmission method applied to the first communication device in the embodiment shown in FIG1. The implementation principle and technical effect of the data transmission device provided in this embodiment are similar, and will not be described again here.
[0176] In one embodiment, FIG4 is a structural block diagram of another data transmission device provided in this application. This embodiment is applied to a second communication device. As shown in FIG4, the data transmission device in this embodiment includes: a configuration module 410 and a receiver 420.
[0177] Configuration module 410 is configured to configure the resource unit (RE) group corresponding to the physical uplink shared channel (PUSCH) used to carry uplink control information; receiver 420 is configured to receive PUSCH in the RE group.
[0178] In one embodiment, the configuration module 410 includes:
[0179] The configuration unit is configured to configure at least one RB for carrying uplink control information in the PUSCH; the partitioning unit is configured to partition the RB into at least one RE group according to a predefined rule; and the allocation unit is configured to allocate at least one RE group from the partitioned at least one RE group to the first communication device as the RE group corresponding to the PUSCH carrying uplink control information.
[0180] In one embodiment, the configuration module 410 includes:
[0181] The allocation unit is also configured to allocate at least one RE group from the configured or predefined RE groups as the RE group corresponding to the PUSCH carrying uplink control information.
[0182] In one embodiment, at least one RE group serves as a PUSCH resource carrying uplink control information, comprising: each RE group in at least one RE group for a PUSCH resource having the same size and location in the time domain and the same size in the frequency domain.
[0183] In one embodiment, the data transmission apparatus applied to the second communication device further includes:
[0184] The configuration module is further configured to configure a set of PUSCH resources for carrying uplink control information; wherein the set of PUSCH resources includes at least one PUSCH resource carrying uplink control information.
[0185] In one embodiment, a PUSCH resource carrying uplink control information includes at least one of the following: starting RE group; number of RE groups; frequency hopping enable parameters; starting RE group for second frequency hopping; orthogonal coverage code (OCC) codeword length; OCC index; starting symbol; number of consecutive symbols; demodulation reference signal (DMRS) configuration information; number of repetitions; PUSCH format; code rate information; modulation and coding scheme (MCS) level; modulation information; and MCS table information.
[0186] In one embodiment, an RE group is defined to contain only frequency domain information, or it is defined to contain both frequency domain and time domain information.
[0187] In one embodiment, the PUSCH includes a first PUSCH format, wherein the first PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain.
[0188] In one embodiment, an initial cyclic shift is configured for the PUSCH resource corresponding to the first PUSCH format; the data transmission apparatus applied to the second communication device further includes:
[0189] The determining module is configured to determine a sequence cyclic shift based on the state of the HARQ-ACK information to be transmitted and a pre-configured state mapping table; wherein the state mapping table is used to characterize the mapping relationship between the sequence cyclic shift and the HARQ-ACK information state; the determining module is further configured to determine a corresponding cyclic shift value for each symbol of the PUSCH resource based on the initial cyclic shift, the sequence cyclic shift, and the index of the first symbol of the PUSCH resource in the scheduling unit; the determining module is further configured to obtain the sequence of the PUSCH resource corresponding to each symbol based on the cyclic shift value corresponding to each symbol; the receiver is further configured to receive the corresponding sequence in each symbol of the PUSCH resource corresponding to the first PUSCH format.
[0190] In one embodiment, the second PUSCH format includes at least one of the following: for carrying at least one bit of HARQ_ACK or carrying beam recovery information; the DMRS symbol and the symbol carrying uplink control information are alternately placed with a one-symbol interval between them; wherein the second PUSCH format includes: in the time domain: at least one symbol; in the frequency domain: at least one RE group, or one RB.
[0191] In one embodiment, at least one PUSCH resource set is configured, and the PUSCH resource set is configured with a corresponding index; wherein, the PUSCH resource set with the smallest index contains at least one of the following: PUSCH resources in a first PUSCH format, and PUSCH resources in a second PUSCH format.
[0192] In one embodiment, a PUSCH resource in the set of PUSCH resources with the minimum index is allowed to be configured to contain at least one RE or one RB in the frequency domain and at least one symbol in the time domain.
[0193] The data transmission device provided in this embodiment is configured to implement the data transmission method applied to the second communication device in the embodiment shown in FIG2. The implementation principle and technical effect of the data transmission device provided in this embodiment are similar, and will not be described again here.
[0194] In one embodiment, FIG5 is a schematic diagram of the structure of a communication device provided in this application. As shown in FIG5, the device provided in this application includes: a processor 510, a memory 520, and a communication module 530. The number of processors 510 in the device can be one or more; FIG5 shows one processor 510 as an example. The number of memories 520 in the device can be one or more; FIG5 shows one memory 520 as an example. The processor 510, memory 520, and communication module 530 of the device can be connected via a bus or other means; FIG5 shows a connection via a bus as an example. In this embodiment, the device can be a first communication device or a second communication device.
[0195] The memory 520, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the device in any embodiment of this application (e.g., the determining module 310 and the transmission module 320 applied in the data transmission apparatus of the first communication device). The memory 520 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required for at least one function; the data storage area may store data created according to the use of the device, etc. Furthermore, the memory 520 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include memory remotely located relative to the processor 510, and these remote memories can be connected to the device via a network. Examples of such networks include the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0196] When the communication device is a first communication device, the device provided above can be configured to execute the data transmission method applied to the first communication device provided in any of the above embodiments, and has corresponding functions and effects.
[0197] When the communication device is a second communication device, the device provided above can be configured to execute the data transmission method for the second communication device provided in any of the above embodiments, and has the corresponding functions and effects.
[0198] This application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a data transmission method applied to a first communication device. The method includes: determining a resource unit (RE) group corresponding to a physical uplink shared channel (PUSCH) for carrying uplink control information; and transmitting the PUSCH in the RE group.
[0199] This application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a data transmission method applied to a second communication device. The method includes: configuring a resource unit (RE) group corresponding to a physical uplink shared channel (PUSCH) for carrying uplink control information; and receiving the PUSCH in the RE group.
[0200] Those skilled in the art will understand that the term user equipment covers any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.
[0201] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.
[0202] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.
[0203] Any block diagram of logical flow in the accompanying drawings of this application may represent program operations, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program operations and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and a processor based on a multi-core processor architecture.
[0204] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the data transmission method provided in any embodiment of this application.
[0205] In the implementation of the computer program product, computer program code for performing the operations of this application can be written in one or more programming languages or a combination thereof. Programming languages include object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
Claims
1. A data transmission method, applied to a first communication device, comprising: Determine the resource element (RE) group corresponding to the Physical Uplink Shared Channel (PUSCH) used to carry uplink control information; The PUSCH is transmitted in the RE group.
2. The method according to claim 1, wherein, The step of determining the RE group corresponding to the PUSCH used to carry uplink control information includes: Identify at least one resource block RB configured by the second communication device for carrying uplink control information in the PUSCH. The RB is divided into at least one RE group according to predefined rules; The at least one RE group allocated by the second communication device from the at least one divided RE group is determined as the RE group corresponding to the PUSCH carrying uplink control information.
3. The method according to claim 1, wherein, The step of determining the RE group corresponding to the PUSCH used to carry uplink control information includes: The second communication device determines that at least one RE group is allocated from the configured or predefined RE groups as the RE group corresponding to the PUSCH carrying uplink control information.
4. The method according to claim 1, wherein, The uplink control information includes at least one of the following: Hybrid Automatic Repeat Request Response (HARQ-ACK); Scheduling Request (SR); Beam Recovery Information; Channel State Information (CSI).
5. The method according to claim 1, wherein, The size and location of time-frequency domain resources for each RE group are predefined or preconfigured.
6. The method according to claim 1, wherein, Each RE group contains the same time-domain resource size, time-domain resource location, and frequency-domain resource size.
7. The method according to claim 1, wherein, Each RE group contains the same number of subcarriers and symbols, as well as the same symbol positions.
8. The method according to claim 1, wherein, Each RE group is configured with an orthogonal overlay code (OCC) codeword.
9. The method according to claim 2 or 3, wherein, The at least one RE group serves as a PUSCH resource carrying uplink control information, comprising: each RE group in at least one RE group for a PUSCH resource having the same size and location in the time domain and the same size in the frequency domain.
10. The method according to claim 1, further comprising: Determine the set of PUSCH resources configured by the second communication device to carry uplink control information; wherein the set of PUSCH resources includes at least one PUSCH resource carrying uplink control information.
11. The method according to claim 1, wherein, A PUSCH resource carrying uplink control information includes at least one of the following: starting RE group; number of RE groups; frequency hopping enable parameters; starting RE group for the second frequency hopping; OCC codeword length; OCC index; starting symbol; number of consecutive symbols; demodulation reference signal (DMRS) configuration information; number of repetitions; PUSCH format; code rate information; modulation and coding scheme (MCS) level; modulation information; and MCS table information.
12. The method according to claim 1, wherein, An RE group is defined to contain only frequency domain information, or it is defined to contain both frequency domain and time domain information.
13. The method according to claim 10, wherein, The first communication device is instructed to use a PUSCH resource from the set of PUSCH resources used to carry uplink control information to transmit uplink control information.
14. The method according to claim 1, wherein, An RE group contains at least one of the following number of subcarriers in the frequency domain: 1 subcarrier, Q subcarriers; wherein Q is greater than 1, and the value of Q is predefined or configured.
15. The method according to claim 14, wherein, In response to a PUSCH resource containing a RE group, the RE group containing k subcarriers; the value of k is determined based on at least one of the following parameters: the OCC codeword length associated with the PUSCH resource, and the number of bits of uplink control information to be transmitted.
16. The method of claim 14, wherein, In response to a PUSCH resource containing multiple RE groups, the number of the multiple RE groups is determined based on at least one of the following: the OCC codebook length associated with the PUSCH resource, and the number of bits of uplink control information to be transmitted.
17. The method according to claim 1, wherein, The PUSCH includes a first PUSCH format, wherein the first PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain.
18. The method according to claim 17, wherein, The PUSCH resource corresponding to the first PUSCH format is configured with an initial cyclic shift; the method further includes: A sequence cyclic shift is obtained based on the state of the HARQ-ACK information to be transmitted and a pre-configured state mapping table; wherein, the state mapping table is used to characterize the mapping relationship between the sequence cyclic shift and the HARQ-ACK information state; Based on the initial cyclic shift, the sequence cyclic shift and the index of the first symbol of the PUSCH resource in the scheduling unit determine a corresponding cyclic shift value for each symbol of the PUSCH resource; The sequence of the PUSCH resource corresponding to each symbol is obtained based on the cyclic shift value corresponding to each symbol. Transmit the corresponding sequence in each symbol of the PUSCH resource corresponding to the first PUSCH format.
19. The method according to claim 10, wherein, At least one PUSCH resource set is configured, and the PUSCH resource set is configured with a corresponding index. The set of PUSCH resources with the smallest index contains at least one of the following: PUSCH resources in the first PUSCH format and PUSCH resources in the second PUSCH format.
20. The method according to claim 19, wherein, The second PUSCH format includes at least one of the following: for carrying at least one bit of HARQ_ACK or carrying beam recovery information; the DMRS symbol and the symbol carrying uplink control information are alternately placed with a one-symbol interval between them; wherein the second PUSCH format includes: in the time domain: at least one symbol; in the frequency domain: at least one RE group, or one RB.
21. The method according to claim 19, wherein, A PUSCH resource in the set of PUSCH resources with the minimum index is allowed to be configured to contain at least one RE or one RB in the frequency domain and at least one symbol in the time domain.
22. The method according to claim 1, wherein, The PUSCH used to carry uplink control information and the PUSCH used to carry uplink data are transmitted using different antenna ports.
23. A data transmission method, applied to a second communication device, comprising: Configure the resource element (RE) group corresponding to the Physical Uplink Shared Channel (PUSCH) used to carry uplink control information; The PUSCH is received in the RE group.
24. The method according to claim 23, wherein, The configuration is used for the RE group corresponding to the PUSCH that carries uplink control information, including: Configure at least one resource block RB for the PUSCH to carry uplink control information; The RB is divided into at least one RE group according to predefined rules; At least one RE group is allocated to the first communication device from the at least one RE group that is divided into, as the RE group corresponding to the PUSCH that carries uplink control information.
25. The method according to claim 23, wherein, The configuration is used for the RE group corresponding to the PUSCH that carries uplink control information, including: Allocate at least one RE group from the configured or predefined RE groups as the RE group corresponding to the PUSCH that carries uplink control information.
26. The method according to claim 24 or 25, wherein, The at least one RE group serves as a PUSCH resource carrying uplink control information, comprising: each RE group in at least one RE group for a PUSCH resource having the same size and location in the time domain and the same size in the frequency domain.
27. The method of claim 23, further comprising: Configure a set of PUSCH resources for carrying uplink control information; wherein the set of PUSCH resources includes at least one PUSCH resource carrying uplink control information.
28. The method according to claim 23, wherein, A PUSCH resource carrying uplink control information includes at least one of the following: starting RE group; number of RE groups; frequency hopping enable parameters; starting RE group for the second frequency hopping; orthogonal coverage code (OCC) codeword length; OCC index; starting symbol; number of consecutive symbols; demodulation reference signal (DMRS) configuration information; number of repetitions; PUSCH format; code rate information; modulation and coding scheme (MCS) level; modulation information; and MCS table information.
29. The method according to claim 23, wherein, An RE group is defined to contain only frequency domain information, or it is defined to contain both frequency domain and time domain information.
30. The method according to claim 23, wherein, The PUSCH includes a first PUSCH format, wherein the first PUSCH format includes: at least one symbol in the time domain; and at least one RE group or one RB in the frequency domain.
31. The method according to claim 30, wherein, The method further includes configuring an initial cyclic shift for the PUSCH resource corresponding to the first PUSCH format; A sequence cyclic shift is determined based on the state of the HARQ-ACK information to be transmitted and a pre-configured state mapping table; wherein, the state mapping table is used to characterize the mapping relationship between the sequence cyclic shift and the HARQ-ACK information state; Based on the initial cyclic shift, the sequence cyclic shift and the index of the first symbol of the PUSCH resource in the scheduling unit determine a corresponding cyclic shift value for each symbol of the PUSCH resource; The sequence of the PUSCH resource corresponding to each symbol is obtained based on the cyclic shift value corresponding to each symbol. The corresponding sequence is received in each symbol of the PUSCH resource corresponding to the first PUSCH format.
32. The method according to claim 27, wherein, At least one PUSCH resource set is configured, and the PUSCH resource set is configured with a corresponding index. The set of PUSCH resources with the smallest index contains at least one of the following: PUSCH resources in the first PUSCH format and PUSCH resources in the second PUSCH format.
33. The method according to claim 32, wherein, The second PUSCH format includes at least one of the following: for carrying at least one bit of HARQ_ACK or carrying beam recovery information; the DMRS symbol and the symbol carrying uplink control information are alternately placed with a one-symbol interval between them; wherein the second PUSCH format includes: in the time domain: at least one symbol; in the frequency domain: at least one RE group, or one RB.
34. The method according to claim 32, wherein, A PUSCH resource in the set of PUSCH resources with the minimum index is allowed to be configured to contain at least one RE or one RB in the frequency domain and at least one symbol in the time domain.
35. A communication device, comprising: Memory, and at least one processor; The memory is configured to store at least one program; When the at least one program is executed by the at least one processor, the at least one processor implements the data transmission method as described in any one of claims 1-22 or 23-34.
36. A storage medium storing a computer program that, when executed by a processor, implements the data transmission method as described in any one of claims 1-22 or 23-34.
Citation Information
Patent Citations
Method for transmitting uplink control information and apparatus therefor
CN107210889A
PUCCH transmission method and device, equipment and storage medium
CN114698113A
Uplink control information transmission method and device
CN115474280A
Method for transmitting and receiving uplink demodulation reference signal in wireless communication system, and apparatus therefor
US20210185706A1