Data transmission methods, communication device and storage medium

Abstract

The present application provides data transmission methods, a communication device and a storage medium. A data transmission method, applied to a first communication device, comprises: receiving resource bundling indication information configured by a second communication device, wherein the resource bundling indication information is used for indicating a resource block group associated with each second-type carrier comprised in a first-type carrier (S110); and performing data transmission on the basis of frequency domain resources bundled on the basis of the resource bundling indication information (S120).

Description

Data transmission methods, communication equipment and storage media Technical Field

[0001] This application relates to the field of communication technology, specifically to a data transmission method, communication device, and storage medium. Background Technology

[0002] The introduction of the virtual carrier concept necessitates merging the resources of multiple carriers and processing them uniformly in the baseband. Generally, it can be assumed that the virtualized carriers of multiple physical carriers are scheduled uniformly. However, in reality, for the terminal, reception and transmission occur on different physical carriers. If the virtual carrier bandwidth is uniformly bundled with relevant frequency domain resources, boundary issues will arise. Summary of the Invention

[0003] This application provides a data transmission method applied to a first communication device, including:

[0004] Receive resource bundling indication information configured by the second communication device; wherein the resource bundling indication information is used to indicate resource block groups associated with the second type of carrier contained in the first type of carrier;

[0005] Data transmission is performed based on the frequency domain resources bundled according to the resource bundling indication information.

[0006] This application provides a data transmission method applied to a second communication device, including:

[0007] Generate resource bundling indication information; wherein, the resource bundling indication information is used to indicate resource block groups associated with the second type of carrier contained in the first type of carrier;

[0008] The resource bundling instruction information is sent to the first communication device.

[0009] This application provides a communication device, including: a memory, and one or more processors;

[0010] The memory is configured to store one or more programs;

[0011] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0012] This application provides a storage medium storing a computer program, which, when executed by a processor, implements the methods described in any of the above embodiments. Attached Figure Description

[0013] Figure 1 is a schematic diagram of an implementation of a related technology that virtualizes multiple physical carriers into one carrier and processes them using a baseband processing unit.

[0014] Figure 2 is a schematic diagram of another implementation provided by related technologies, which virtualizes multiple physical carriers into one carrier and processes them using a baseband processing unit.

[0015] Figure 3 is a schematic diagram of a VRB to PRB interleaving mapping configuration provided by related technologies;

[0016] Figure 4 is a schematic diagram of a CORESET frequency domain resource bundling implementation provided by related technologies;

[0017] Figure 5 is a flowchart of a data transmission method provided in an embodiment of this application;

[0018] Figure 6 is a flowchart of another data transmission method provided in an embodiment of this application;

[0019] Figure 7 is a schematic diagram of the quantity configuration between physical carriers and virtual carriers provided by related technologies;

[0020] Figure 8 is a schematic diagram of the implementation of RBG determination in different physical carriers provided by related technologies;

[0021] Figure 9 is a schematic diagram of the binding between a physical carrier and an RBG according to an embodiment of this application;

[0022] Figure 10 is a schematic diagram of another binding between a physical carrier and an RBG provided in an embodiment of this application;

[0023] Figure 11 is a schematic diagram of another type of binding between a physical carrier and an RBG provided in an embodiment of this application;

[0024] Figure 12 is a schematic diagram of another type of binding between a physical carrier and an RBG provided in an embodiment of this application;

[0025] Figure 13 is a schematic diagram of a boundary problem that occurs when PRG segmentation crosses physical carriers, provided by related technologies;

[0026] Figure 14 is a schematic diagram of the binding between a physical carrier and a PRG provided in an embodiment of this application;

[0027] Figure 15 is a schematic diagram of the boundary problem that occurs in the RB binding of a VRB to PRB interleaving mapping provided by related technologies;

[0028] Figure 16 is a schematic diagram of the binding between a physical carrier and a resource block binding group provided in an embodiment of this application;

[0029] Figure 17 is a schematic diagram of a boundary problem that occurs when subband division crosses physical carriers, provided by related technologies;

[0030] Figure 18 is a schematic diagram of the bundling between a physical carrier and a subband provided in an embodiment of this application;

[0031] Figure 19 is a schematic diagram of a boundary problem that occurs across physical carriers in CORESET, provided by related technologies;

[0032] Figure 20 is a structural block diagram of a data transmission device provided in an embodiment of this application;

[0033] Figure 21 is a structural block diagram of another data transmission device provided in an embodiment of this application;

[0034] Figure 22 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0035] In the field of communications, a virtual carrier concept has been proposed for application in future communication systems such as 6G. This concept allows discrete physical carriers to be virtualized into a single carrier and processed by a single baseband processing unit. Figure 1 illustrates one implementation of this technique, where multiple physical carriers are virtualized into one carrier and processed by a single baseband processing unit. Figure 2 illustrates another implementation of this technique. As shown in Figures 1 and 2, three physical carriers (carrier #1, carrier #2, and carrier #3) are virtualized into one carrier and processed by a single baseband processing unit (i.e., Medium Access Control (MAC) and Physical Layer (PHY)). This approach reduces the number of baseband processing units and allows for joint scheduling optimizations within the virtual carrier, reducing overhead and complexity.

[0036] In 5G New Radio (NR) systems, there may be some resource bundling operations. Therefore, how to solve the boundary problem caused by virtual carriers is an urgent issue to be addressed.

[0037] To facilitate the explanation of the scheme, the relevant parameters involved in this application are explained.

[0038] For resource allocation mode 0, both Long-Term Evolution (LTE) and NR systems have discrete resource allocation modes. Under this mode, multiple consecutive resource blocks (RBs) can be bundled into a resource block group (RBG). The number of RBs in an RBG can vary depending on the size and configuration of the bandwidth portion, as shown in Table 1. The configuration type is determined by the RBG size field in the PDSCH configuration (PDSCH-Config) of the Radio Resource Control (RRC) message. The Downlink Control Information (DCI) uses a bitmap to indicate the RBG number carrying the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) data. The bitmap is arranged from low to high, with RBG0 in the highest bit, indicating discontinuous scheduling.

[0039] Table 1. RBG Size under Different BWP Sizes and Configurations

[0040]

[0041] For a size of For the uplink or downlink bandwidth portion (BWP) of an RB, the total number of RBGs contained within a BWP can be denoted as: ,and, The formula for calculating can be expressed as follows: ,in, This refers to the total number of RBs contained in the i-th BWP; P represents the number of RBs contained in the RBG under different BWP sizes and configurations, or the size of the RBG under different BWP sizes and configurations, as determined by Table 1. The logic for partitioning the RBG can then include the following three points:

[0042] - Size of the first RBG, ;in, Indicates the starting position of the RB contained in the i-th BWP; This indicates the number of RBs contained in the first RBG;

[0043] - The size of the last RBG, if ,but Otherwise, the size of the last RBG is P; where, This indicates the number of RBs contained in the last RBG;

[0044] - The size of other RBGs is P.

[0045] Regarding Physical Resource Block (PRB) bundling: In LTE, the downlink PDSCH channel uses the same precoding across all allocated frequency domain resources; in NR, due to the larger frequency domain bandwidth of the PDSCH channel, frequency-selective precoding is supported, meaning different PRB ranges in the frequency domain can use different precoding matrices. A group of PRBs using the same precoding matrix is ​​called a Precoding Resource Block Group (PRG). Within the i-th BWP, the precoding granularity is expressed as... ,in, It can be configured through higher-level signaling, including both static and dynamic binding types. The value range is {2, 4, wideband}.

[0046] exist When the value is configured as wideband, the UE only receives consecutive RB allocations, assuming that all resources (i.e., RBs) within the BWP use the same precoding matrix, meaning the BWP contains a single PRG; When configured as 2 or 4, BWP will follow the instructions. RB grouping is performed, and one RB group is equivalent to one PRG. That is, a BWP contains at least two PRGs. The division of PRGs is similar to that of RBGs, and the division logic can include the following three points:

[0047] - Size of the first PRG ;in, Indicates the starting position of the RB contained in the i-th BWP; This indicates the number of RBs contained in the first PRG;

[0048] - The size of the last PRG, if ,but Otherwise, the size of the last PRG is ;in, This indicates the number of RBs contained in the last PRG;

[0049] - The size of other PRGs is... .

[0050] For a PDSCH carrying System Information Block 1 (SIB1), the PRG is divided starting from the smallest sequence number of the RB in the Control Resource Set (CORESET) indicated by the Physical Broadcast Channel (PBCH); within a PRG, any consecutive downlink PRBs use the same precoding matrix. Assuming no explicit configuration, the UE defaults to... When using dynamic bundling, then It can be specified by the bundle size set 1 (bundleSizeSet1) and the bundle size set 2 (bundleSizeSet2).

[0051] - bundleSizeSet1 can take one or two values ​​from {2, 4, wideband}, for example (n2-wideband);

[0052] - bundleSizeSet2 can take a value from {2, 4, wideband}.

[0053] Furthermore, the bundled size indicator field in the DCI can be used for size indication via the PRB binding.

[0054] - If this field is set to 0, the UE uses the value indicated by bundleSizeSet2 as... ;

[0055] - If this field is set to 1, and bundleSizeSet1 is configured with only one value, the UE will use that value;

[0056] - If this field is set to 1, and bundleSizeSet1 is configured with two values, n2-wideband or n4-wideband.

[0057] The UE should determine that the scheduled PRBs are consecutive and the number of scheduled PRBs is greater than 1. ,but The total number of PRBs must be the same as the total number of PRBs scheduled; otherwise It should be set to a value other than wideband: 2 or 4.

[0058] For Virtual Resource Block (VRB) to PRB mapping: Resources allocated by PDSCH (e.g., VRBs) are mapped to PRBs. NR supports both interleaved and non-interleaved mapping methods. When using resource allocation method 0, the non-interleaved method can be used, meaning there is a one-to-one correspondence between VRBs and PRBs. When using resource allocation method 1, the VRB-to-PRB field in DCI indicates whether to use an interleaved method. When using interleaved mapping, the interleaved block size can be configured using the higher-level parameter vrb-ToPRB-Interleaver {n2, n4}. Within the BWP, RBs are bundled according to the size of the interleaving block, similar to the principle of RBG / PRG, and highly correlated with PRG. For example, if the PRG value is 4, then... It must also be set to 4. The number of interleaving blocks and the division of interleaving blocks fall into three categories:

[0059] The first scenario involves PDSCH transmission with SI-RNTI scrambling, scheduled in DCI format 1-0 under CORESET0. Where L=2, This indicates the size of CORESET0, that is, the number of RBs contained in CORESET0;

[0060] - The size of the last interlacing block, if ,include One RB, otherwise it includes L RBs.

[0061] - The size of other interlacing blocks is L;

[0062] The second scenario is if it's in BWP i and the starting position is... Any common search space is transmitted via PDSCH using DCI format 1-0 scheduling. Where L=2, This indicates that the PRB with the lowest PRB number in the CORESET where the DCI is located has been received;

[0063] - Size of the first interlacing block ;

[0064] - The size of the last interlacing block, if Then it includes One RB, otherwise including L RBs;

[0065] - Other interlacing block sizes are L;

[0066] The third type refers to other PDSCH transmissions besides those mentioned above. , Configure via high-level parameters;

[0067] - Size of the first interlacing block ;

[0068] - The size of the last interlacing block, if Then it includes One RB, otherwise including L RBs;

[0069] - Other interlacing block sizes are L;

[0070] The interleaving algorithm is shown in the following formula:

[0071] ;

[0072] For a simple example, Figure 3 is a schematic diagram of a VRB-PRB interleaving mapping configuration provided by related technologies. Assuming VRB-PRB interleaving mapping... R refers to the PDSCH interleaving line number being fixed at 2, as shown in Figure 3. At the same time, the last VRB interleaving block corresponds to the last PRB interleaving block, as shown in interleaving block 8 in Figure 3. Further, according to the above formula, the interleaved result is the output of the final PRB interleaving block.

[0073] For CORESET frequency domain indication: In NR, CORESET frequency domain indication is provided through a 45-bit bitmap. The starting RB number must be a multiple of 6. Figure 4 is a schematic diagram of a CORESET frequency domain resource bundling implementation provided by related technologies. As shown in Figure 4, it can be seen that this is also a form of frequency domain resource bundling.

[0074] Regarding the Channel State Information (CSI) reporting issue: Based on the current NR protocol, the CSI subband division can be seen in Table 2 below:

[0075] Table 2. Configured Subband Sizes

[0076]

[0077] - Size of the first sub-band ;in, This indicates the number of PRBs occupied by the synchronization signal block (SB); where the SB includes at least the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH).

[0078] - The size of the last sub-band, if Then it includes One RB, otherwise including RB.

[0079] In one embodiment, FIG5 is a flowchart of a data transmission method provided by an embodiment of this application. This embodiment is applied to situations where boundaries occur when performing a binding operation on frequency domain resources. This embodiment can be executed by a first communication device. Exemplarily, the first communication device can be a terminal side (e.g., a user equipment). As shown in FIG5, this embodiment includes: S110-S120.

[0080] S110, Receive resource bundling indication information configured by the second communication device; wherein the resource bundling indication information is used to indicate the resource block group associated with each second type carrier contained in the first type carrier.

[0081] In one embodiment, the first type of carrier includes at least two second type of carriers. Exemplarily, the first type of carrier refers to a virtual carrier; the second type of carrier refers to a physical carrier. In one embodiment, a resource block group consists of multiple resource blocks, and each second type of carrier may include one or more resource block groups. In one embodiment, a resource block group is characterized by one of the following: a resource block group; a precoded resource block group; a resource block bundle group; a subband; or a control resource set. In one example, each second type of carrier may include one or more resource block groups, one or more precoded resource block groups, one or more resource block bundle groups, one or more subbands, or one or more control resource sets.

[0082] S120. Data transmission is performed based on the frequency domain resources bundled according to the resource bundling instruction information.

[0083] In this embodiment, after the first communication device receives the resource bundling indication information configured by the second communication device, the first communication device bundles the resource blocks according to the resource block groups associated with each second type carrier included in the first type carrier indicated by the resource bundling indication information. Then, data transmission is performed based on the bundled frequency domain resources to avoid a resource block group spanning two adjacent second type carriers. This reduces resource scheduling overhead and complexity while also avoiding boundary problems that may occur during resource bundling operations. The data transmission includes data sending or data receiving processes.

[0084] In one embodiment, when a resource block group contains resource blocks belonging to two adjacent different second-type carriers, the partitioning method of the resource block group contained in the two adjacent different second-type carriers includes at least one of the following: splitting the residual resource block into a new resource block group at the boundary of the two adjacent different second-type carriers; merging the residual resource block into the last resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; merging the residual resource block into the first resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; adjusting the starting position offset value (also referred to as the starting position, starting position offset, or RB starting position) of each second-type carrier. In one embodiment, a residual resource block refers to all resource blocks shared by two adjacent different second-type carriers; a residual resource block may include one resource block or may consist of multiple resource blocks. In one embodiment, if a residual resource block exists at the boundary of two adjacent different second-type carriers, the residual resource block can be used as a new resource block group, that is, the number of resource block groups contained in a first-type carrier increases by one. For example, if the first type of carrier originally contained 'a' resource block groups, then after splitting the remaining resource blocks into new resource block groups, the number of resource block groups contained in the first type of carrier becomes 'a+1'. In one embodiment, if there are residual resource blocks at the boundary between two adjacent different second type carriers, the residual resource blocks can be merged into the last resource block group contained in the second type carrier with the smaller carrier identifier among the two adjacent different second type carriers. For example, if the first type of carrier contains three second type carriers (e.g., carrier 1, carrier 2, and carrier 3), and there are residual resource blocks (e.g., 2 RBs) at the boundary between carrier 1 and carrier 2, and carrier 1 contains 3 resource block groups (group 1, group 2, and group 3), then these 2 RBs can be merged into group 3 of carrier 1. In one embodiment, if there are residual resource blocks at the boundary between two adjacent different second type carriers, the residual resource blocks can be merged into the first resource block group contained in the second type carrier with the smaller carrier identifier among the two adjacent different second type carriers. For example, if a first-type carrier contains three second-type carriers (e.g., carrier 1, carrier 2, and carrier 3), and there are residual resource blocks (e.g., 2 RBs) at the boundary between carrier 1 and carrier 2, and carrier 1 contains 3 resource block groups (group 1, group 2, and group 3), then these 2 RBs can be merged into group 1 of carrier 1. In one embodiment, if there are residual resource blocks at the boundary between two adjacent different second-type carriers, the starting position offset value of the second-type carrier with the smaller carrier identifier among the two adjacent different second-type carriers can be dynamically adjusted based on the number of RBs contained in the residual resource block.For example, if a first-type carrier contains three second-type carriers (e.g., carrier 1, carrier 2, and carrier 3), and there are residual resource blocks (e.g., 2 RBs) at the boundary between carrier 1 and carrier 2, and carrier 1 contains 3 resource block groups (group 1, group 2, and group 3), and the starting position offset of carrier 1 is 0 RBs, then the starting position offset of carrier 1 can be adjusted from 0 to 2 RBs. In the second-type carriers, the frequency domain position of the second-type carrier with the smaller carrier identifier is lower than the frequency domain position of the second-type carrier with the larger carrier identifier.

[0085] In one embodiment, the method of dividing resource block groups contained in two adjacent different second-type carriers further includes: adjusting only the division method of resource block groups contained in second-type carriers at odd-numbered or even-numbered positions. In one embodiment, when residual resource blocks exist at the boundary of two adjacent different second-type carriers, the starting position offset value of the second-type carrier at the odd-numbered position can be adjusted only, or the residual resource blocks can be merged into the first resource block group of the second-type carrier at the odd-numbered position, or the residual resource blocks can be merged into the last resource block group of the second-type carrier at the odd-numbered position. In one embodiment, when residual resource blocks exist at the boundary of two adjacent different second-type carriers, the starting position offset value of the second-type carrier at the even-numbered position can be adjusted only, or the residual resource blocks can be merged into the first resource block group of the second-type carrier at the even-numbered position, or the residual resource blocks can be merged into the last resource block group of the second-type carrier at the even-numbered position. In one embodiment, if the carrier identifier of the second type carrier included in a first type carrier starts from 1, then the second type carriers at odd positions are carrier 1, carrier 3, carrier 5, carrier 7..., and the second type carriers at even positions are carrier 2, carrier 4, carrier 6, carrier 8... In another embodiment, if the carrier identifier of the second type carrier included in a first type carrier starts from 0, then the second type carriers at odd positions are carrier 0, carrier 2, carrier 4, carrier 6, carrier 8..., and the second type carriers at even positions are carrier 1, carrier 3, carrier 5, carrier 7...

[0086] In one embodiment, the number of second-type carriers included in each first-type carrier is determined by one of the following: terminal capability; maximum value of the Fourier transform. The maximum value of the Fourier transform is determined by the processing capability of the baseband processing unit. In one embodiment, the number of second-type carriers included in the first-type carrier is limited; for example, the number of second-type carriers included in the first-type carrier can be limited based on terminal capability and / or the maximum value of the Fourier transform.

[0087] In one embodiment, the resource block groups contained in each second type carrier within the first type carrier are divided in the same way, or the resource block groups contained in each second type carrier within the first type carrier are divided in different ways. In one embodiment, the resource block groups contained in some second type carriers within the first type carrier may be divided in the same way, while the resource block groups contained in other second type carriers may be divided in different ways. In one embodiment, one of the above-mentioned division methods for resource block groups contained in two adjacent different second type carriers can be uniformly applied to all second type carriers contained in the first type carrier, so that the resource block groups contained in each second type carrier within the first type carrier are divided in the same way. For example, if a first type carrier contains three second type carriers (carrier 1, carrier 2, and carrier 3), and there are residual resource blocks between carrier 1 and carrier 2, and between carrier 2 and carrier 3, then the residual resource blocks between carrier 1 and carrier 2 can be split into a new resource block group, and the residual resource blocks between carrier 2 and carrier 3 can be split into another new resource block group. In one embodiment, a method for grouping resource blocks contained in two adjacent different second-type carriers can be independently applied to a second-type carrier contained in a first-type carrier, such that the method for grouping resource blocks contained in each second-type carrier in the first-type carrier is different. For example, if a first-type carrier contains three second-type carriers (carrier 1, carrier 2, and carrier 3), and there are residual resource blocks between carrier 1 and carrier 2, and between carrier 2 and carrier 3, then the residual resource blocks between carrier 1 and carrier 2 can be split into a new resource block group, and the residual resource blocks between carrier 2 and carrier 3 can be merged into the first resource block group of carrier 2. In one embodiment, when the resource block grouping method of each second type carrier in the first type carrier is different, the number of resource block grouping methods associated with the first type carrier is equal to the number of residual resource blocks. For example, if the first type carrier contains 3 second type carriers (carrier 1, carrier 2 and carrier 3), and there are residual resource blocks between carrier 1 and carrier 2, and between carrier 2 and carrier 3, that is, the first type carrier contains two residual resource blocks, then the number of resource block grouping methods associated with the first type carrier is 2.

[0088] In one embodiment, the resource block groups contained in the second type carriers with odd-numbered carrier identifiers in the first type carrier are divided in the same way, and the resource block groups contained in the second type carriers with even-numbered carrier identifiers in the first type carrier are also divided in the same way. In one embodiment, the above-mentioned method of dividing resource block groups contained in two adjacent different second type carriers can be uniformly applied to the second type carriers at odd positions contained in the first type carrier, so that the resource block groups contained in the second type carriers at odd positions in the first type carrier are divided in the same way. For example, if a first type carrier contains three second type carriers (carrier 1, carrier 2, and carrier 3), and there are residual resource blocks between carrier 1 and carrier 2, and between carrier 2 and carrier 3, then the residual resource blocks between carrier 1 and carrier 2 can be merged into the last resource block group of carrier 1, and the residual resource blocks between carrier 2 and carrier 3 can be merged into the last resource block group of carrier 3. In one embodiment, a method for grouping resource blocks contained in two adjacent different second-type carriers can be uniformly applied to even-numbered positions of second-type carriers contained in the first-type carrier, resulting in different methods for grouping resource blocks contained in even-numbered positions of the second-type carriers in the first-type carrier. For example, if a first-type carrier contains three second-type carriers (carrier 1, carrier 2, and carrier 3), and there are residual resource blocks between carrier 1 and carrier 2, and between carrier 2 and carrier 3, then the residual resource blocks between carrier 1 and carrier 2 can be merged into the first resource block group of carrier 2, and the residual resource blocks between carrier 2 and carrier 3 can also be merged into the first resource block group of carrier 2.

[0089] In one embodiment, when the resource block group is a precoded resource block group, the precoding granularity of the precoded resource block group includes at least one of the following: 2; 4; subband; wideband.

[0090] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that all second-type carriers contained in the first-type carrier use the same precoding. In another embodiment, when the precoding granularity of the precoding resource block group is wideband, it can be directly determined that all second-type carriers contained in the first-type carrier use the same precoding.

[0091] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that the second type carriers included in the first type carrier use the same precoding if the first condition is met. In another embodiment, when the precoding granularity of the precoding resource block group is wideband, it can be directly determined that the second type carriers included in the first type carrier that meet the first condition use the same precoding, that is, some of the second type carriers included in the first type carrier use the same precoding.

[0092] In one embodiment, the first condition includes at least one of the following: a test metric; a frequency domain spacing between different second-type carriers that is less than a first threshold; and UE capability. In one example, the test metric may be a metric from Radio Access Network Working Group 4 (RAN4). In one example, if the second-type carriers included in the first-type carrier satisfy at least one of the following: the RAN4 metric, the frequency domain spacing between different second-type carriers that is less than a first threshold, and UE capability, the second-type carriers included in the first-type carrier employ the same precoding.

[0093] In one embodiment, FIG6 is a flowchart of another data transmission method provided by an embodiment of this application. This embodiment is applied to situations where boundaries occur when performing a binding operation on frequency domain resources. This embodiment can be executed by a second communication device. Exemplarily, the second communication device can be a network side (e.g., a base station). As shown in FIG6, this embodiment includes: S210-S220.

[0094] S210, Generate resource bundling indication information; wherein, the resource bundling indication information is used to indicate the resource block group associated with each second type carrier contained in the first type carrier.

[0095] S220, Send the resource bundling instruction information to the first communication device.

[0096] In one embodiment, when a resource block group contains resource blocks belonging to two adjacent different second-type carriers, the partitioning method of the resource block group contained in the two adjacent different second-type carriers includes at least one of the following: splitting the remaining resource block into a new resource block group at the boundary of the two adjacent different second-type carriers; merging the remaining resource block into the last resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; merging the remaining resource block into the first resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; and adjusting the starting position offset value of each second-type carrier.

[0097] In one embodiment, the method of dividing resource block groups contained in two adjacent different second type carriers further includes: adjusting the method of dividing resource block groups contained in second type carriers at odd or even positions only.

[0098] In one embodiment, resource block groups are characterized by one of the following: resource block groups; precoded resource block groups; resource block bundles; subbands; control resource sets.

[0099] In one embodiment, the first type of carrier includes at least two second type carriers.

[0100] In one embodiment, the number of second-type carriers included in each first-type carrier is determined by one of the following: terminal capability; maximum value of the Fourier transform.

[0101] In one embodiment, the resource block groups contained in each second type carrier in the first type carrier are divided in the same way, or the resource block groups contained in each second type carrier in the first type carrier are divided in different ways.

[0102] In one embodiment, the resource block groups contained in the second type of carrier with odd carrier identifiers in the first type of carrier are divided in the same way, and the resource block groups contained in the second type of carrier with even carrier identifiers in the first type of carrier are divided in the same way.

[0103] In one embodiment, when the resource block group is a precoded resource block group, the precoding granularity of the precoded resource block group includes at least one of the following: 2; 4; subband; wideband.

[0104] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that all second-type carriers contained in the first-type carrier use the same precoding.

[0105] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that the second type of carrier contained in the first type of carrier uses the same precoding if the first condition is met.

[0106] In one embodiment, the first condition includes at least one of the following: test indicators; frequency domain spacing between different second-type carriers is less than a first threshold; UE capability.

[0107] It should be noted that the relevant parameters involved in the data transmission method applied to the second communication device can be found in the explanation of the corresponding parameters in the data transmission method applied to the first communication device, and will not be repeated here.

[0108] After introducing the concept of virtual carriers, a virtual carrier can include multiple physical carriers. However, the number of physical carriers available for virtualization cannot be unlimited; there needs to be an upper limit based on UE capabilities, base station capabilities, RAN4 performance evaluation, etc. Figure 7 is a schematic diagram of the number configuration between physical and virtual carriers provided by related technologies. As shown in Figure 7, taking two physical carriers as an example to form a new virtual carrier, the bandwidths of different physical carriers can be different. Based on the bandwidth of the virtualized carrier, information related to carrier bandwidth, such as RBG and subband size, is determined. At the same time, the original RB bundling method will have boundary issues and needs to be redesigned.

[0109] For example, Figure 8 is a schematic diagram of the implementation of RBG determination in different physical carriers provided by related technologies. Taking RBG determination as an example, RBs can be uniformly determined based on the virtualized carrier bandwidth. For example, if the bandwidth of physical carrier 1 is 50 RBs and the bandwidth of physical carrier 2 is 100 RBs, then the virtualized carrier bandwidth is 150 RBs. According to Table 1, P is 16 RBs under configuration 1. If RBG is divided according to 16 RBs, the problem shown in Figure 8 will occur. This figure assumes... Starting from RB0, RBG3 will span resources on physical carrier 1 and physical carrier 2. However, in reality, the actual operating frequencies of different physical carriers are different, so it is better to separate the resources on different physical carriers.

[0110] In the following example, taking Figure 7 as an example, the first type of carrier is a virtual carrier, and the second type of carrier is a physical carrier. The virtual carrier contains two physical carriers (physical carrier 1 and physical carrier 2). This example illustrates the boundary issue between physical carrier 1 and physical carrier 2. Example 1: When a resource block group contains resource blocks belonging to two adjacent different second type carriers, at the boundary between the two adjacent different second type carriers, the remaining resource block is split into a new resource block group.

[0111] At the boundary between physical carrier 1 and physical carrier 2, the remaining resource block is split into a new RBG, ensuring that every position starting from the second physical carrier is a new RBG.

[0112] Figure 9 is a schematic diagram of the binding between a physical carrier and an RBG provided in an embodiment of this application. One approach is to split a new RBG at the boundary of different physical carriers, as shown in Figure 9. The total number of RBGs contained in the virtual carrier changes from 10 to 11, where RBG3 only includes 2 RBs. However, for physical carrier 2, there are multiple ways to split it. For example, in Figure 9 (B), it can be understood as physical carrier 2 having a starting offset of 2 RBs; it can also be understood as the original RBG3 being split into 2 RBGs based on different physical carriers. In addition, if the starting RB is not 0, it will affect the size of the first RBG. This requires an updated bitmap (11 bits) for RBG indication in resource allocation mode 0. For more virtualization cases of physical carriers, different physical carriers need to be processed according to the above method.

[0113] For Figure 9(B), the partitioning logic for RBG changes as follows:

[0114] - Size of the first RBG, For example, in the case shown in Figure 8, P=16. ;

[0115] - The size of the last RBG corresponding to the smaller physical carrier identifier at the physical carrier boundary, if ,but Otherwise, the size of the last RBG corresponding to the smaller physical carrier identifier is P; where, This refers to the physical carrier bandwidth, where n is the number of physical carriers aggregated in a virtual carrier aggregation. For example, in the case shown in Figure 8, n=2.

[0116] - The size of the first RBG corresponding to the larger physical carrier identifier at the physical carrier boundary is ;

[0117] - The size of the last RBG, if ,but Otherwise, the size of the last RBG is P;

[0118] - The size of other RBGs is P.

[0119] For Figure 9(A), the partitioning logic for RBG changes as follows:

[0120] - Size of the first RBG, ;

[0121] - The size of the last RBG corresponding to the smaller physical carrier identifier at the physical carrier boundary, if ,but Otherwise, the size of the last RBG corresponding to the smaller physical carrier identifier is P, where This refers to the physical carrier bandwidth, where n is the number of aggregated physical carriers.

[0122] - The size of the first RBG corresponding to the larger physical carrier identifier at the physical carrier boundary is P;

[0123] - The size of the last RBG, if ,but Otherwise, the size of the last RBG is P;

[0124] - The size of other RBGs is P.

[0125] Example 2: When a resource block group contains resource blocks belonging to two adjacent different second-type carriers, at the boundary between the two adjacent different second-type carriers, the remaining resource blocks are merged into the last resource block group of the second-type carrier.

[0126] Figure 10 is a schematic diagram illustrating another type of binding between physical carriers and RBGs provided in an embodiment of this application. Another approach is to merge residual resource blocks at the boundaries of different physical carriers into the last RBG of the physical carrier with the smaller physical carrier identifier, as shown in Figure 10. This merges the number of RBs spanning multiple physical carriers into the last RBG. For example, the number of RBs in RBG2 changes from 16 RBs to 18 RBs. Similarly, there can be various cases for RBG partitioning on physical carrier 2. The number of RBGs in this method remains essentially unchanged from the original. For more virtualized physical carriers, the above method needs to be applied between different physical carriers.

[0127] For Figure 10(B), the partitioning logic for RBG changes as follows:

[0128] - Size of the first RBG, ;

[0129] - The size of the last RBG corresponding to the smaller physical carrier identifier at the physical carrier boundary, if ,but Otherwise, the size of the last RBG corresponding to the smaller physical carrier identifier is P, where This refers to the physical carrier bandwidth, where n is the number of aggregated physical carriers.

[0130] - The size of the first RBG corresponding to the larger physical carrier identifier at the physical carrier boundary is ;

[0131] - The size of the last RBG, if ,but Otherwise, the size of the last RBG is P;

[0132] - The size of other RBGs is P.

[0133] For Figure 10(A), the partitioning logic for RBG changes as follows:

[0134] - Size of the first RBG, ;

[0135] - The size of the last RBG corresponding to the smaller physical carrier identifier at the physical carrier boundary, if ,but Otherwise, the size of the last RBG corresponding to the smaller physical carrier identifier is P, where This refers to the physical carrier bandwidth, where n is the number of aggregated physical carriers.

[0136] - The size of the first RBG corresponding to the larger physical carrier identifier at the physical carrier boundary is P;

[0137] - The size of the last RBG, if ,but Otherwise, the size of the last RBG is P;

[0138] - The size of other RBGs is P.

[0139] Example 3: When a resource block group contains resource blocks belonging to two adjacent different second-type carriers, at the boundary between the two adjacent different second-type carriers, the remaining resource blocks are merged into the first resource block group of the second-type carrier.

[0140] Figure 11 is a schematic diagram illustrating another type of binding between physical carriers and RBGs provided in an embodiment of this application. Another approach is to merge residual resource blocks at the boundaries of different physical carriers into the first RBG of the physical carrier with the smaller physical carrier identifier, as shown in Figure 11. This merges the number of RBs spanning multiple physical carriers into the first RBG (RBG0) in physical carrier 1. As shown, the number of RBs in RBG0 changes from 16 to 18. Similarly, there are multiple possible RBG partitioning scenarios on physical carrier 2. The number of RBGs remains essentially unchanged from the original. For more virtualized physical carriers, the above method needs to be applied between different physical carriers.

[0141] For Figure 11(B), the partitioning logic for RBG changes as follows:

[0142] - The size of the first RBG, if The size of the first RGB is ,otherwise ;

[0143] - The size of the first RBG corresponding to the larger physical carrier identifier at the physical carrier boundary, if ,but Otherwise, the size of the first RBG corresponding to the larger physical carrier identifier is P, where This refers to the physical carrier bandwidth, where n is the number of aggregated physical carriers.

[0144] - The size of the last RBG, if ,but Otherwise, the size of the last RBG is P;

[0145] - The size of other RBGs is P.

[0146] For Figure 11(A), the partitioning logic for RBG changes as follows:

[0147] - The size of the first RBG, if The size of the first RGB is ,otherwise ;

[0148] - The size of the first RBG corresponding to the larger physical carrier identifier at the physical carrier boundary, if ,but Otherwise, the size of the first RBG corresponding to the larger physical carrier identifier is P, where This refers to the physical carrier bandwidth, where n is the number of aggregated physical carriers.

[0149] - The size of the last RBG, if ,but Otherwise, the size of the last RBG is P;

[0150] - The size of other RBGs is P.

[0151] Example 4: When a resource block group contains resource blocks belonging to two adjacent different second-type carriers, adjust the starting position offset value of each second-type carrier.

[0152] Figure 12 is a schematic diagram illustrating another type of binding between physical carriers and RBGs provided in an embodiment of this application. Another approach is to change the starting position on the physical carrier, as shown in Figure 12. Consider adding a starting position offset, which can be used to address implementation-level issues, such as resource avoidance by the base station when defining the BWP. This starting position offset can be implemented by adding signaling indications for additional starting position offsets. Based on the number of RBs contained in the residual resource block between physical carrier 1 and physical carrier 2, the starting position offset value of physical carrier 1 is adjusted from 0RB to 2RB. For example, further virtualization of 3 or 4 physical carriers requires additional indications for the starting position offset value between physical carrier 2 and physical carrier 3, and for the starting position offset value between physical carrier 3 and physical carrier 4.

[0153] Another approach is to consider a combination of Examples 1-4 above. For example, if physical carriers 1, 2, and 3 are virtualized, the boundary between physical carrier 1 and physical carrier 2 can be guaranteed by offsetting the starting position of the first physical carrier. However, the boundary between physical carrier 2 and physical carrier 3 can be solved using other methods, such as dividing the new RBG or merging the remaining RBs into the last RBG of the physical carrier.

[0154] Furthermore, if the test indicators (some conditions of RAN4), UE capabilities, etc. are met, such as when the frequency domain spacing between different physical carriers is less than a certain first threshold, cross-physical carrier RB bundling can be supported. In this case, there may be multiple RBG partitioning methods (including the original partitioning method). Further, the switching of RBG partitioning methods will be set up, which can be done through semi-static or dynamic signaling.

[0155] Furthermore, the above method requires the UE to be aware of and to receive or send data based on a determined method.

[0156] Furthermore, the above method supports n physical carriers contained in a virtual carrier, where n > 2. The upper limit of the value of n depends on at least one of the UE capabilities and the maximum value of the FFT, etc.

[0157] Furthermore, the division method in the above method can be the default method, that is, it can be constrained in the standard by formula. Both the UE and gNB perform RB binding operation and / or data transmission and indication based on the formula method. Furthermore, the gNB needs to inform the UE of the number of the second type carriers and the bandwidth of each second type carrier.

[0158] Furthermore, the partitioning of PRGs, interleaving blocks, CORESET resources, and CSI feedback subbands can all be processed using the methods described above.

[0159] Example 5

[0160] Since the virtual carriers obtained after virtualizing multiple physical carriers may not guarantee continuous PRBs and the use of the same precoding, it is impossible to indicate a wideband configuration. However, when certain test indicators are met, such as RAN4 indicators, or when the frequency domain spacing between different physical carriers is less than a certain first threshold, wideband configuration can be configured. How to indicate this is a problem. One method is explicit notification, such as introducing a subband indicator, with the value range changed to {2, 4, subband, wideband}. When the precoding granularity of the precoding resource block group is indicated as wideband, it indicates that the test indicators are met, and the same precoding can be used on multiple physical carriers. When the precoding granularity of the precoding resource block group is indicated as subband, it indicates that wideband precoding is used on each independent physical carrier, but different precoding can be used on different physical carriers. Of course, it can also be determined by the UE. The information of each physical carrier in the virtual carrier needs to be informed to the UE, including the virtualization order. For example, if the signaling notification is wideband, the UE can determine whether the same or different precoding is used on all or some physical carriers based on the relationship between the information of each physical carrier and the constraints.

[0161] In the case of dynamic bundling, the precoding granularity of the precoding resource block group is... Specifies by bundleSizeSet1 and bundleSizeSet2.

[0162] - bundleSizeSet1 can take one or two values ​​from {2, 4, wideband} or {2, 4, subband, wideband}, for example (n2-wideband);

[0163] - bundleSizeSet2 can take a value from {2, 4, wideband} or {2, 4, subband, wideband}.

[0164] Furthermore, the PRB bundling size indicator field in the DCI indicates that if this field is set to 1 and bundleSizeSet1 is configured with two values, such as n2-wideband, n4-wideband, n2-subband, or n4-subband, the UE should determine that the PRBs scheduled on a certain physical carrier are consecutive and the number of scheduled PRBs is greater than half the bandwidth of each physical carrier. The total number of PRBs must be the same as the total number of PRBs scheduled; otherwise It should be set to a value other than wideband / subband: 2 or 4. If subband-wideband is configured, the UE determines whether to use the same precoding or different precoding on all or some physical carriers based on the relationship between the information of each physical carrier and the constraints.

[0165] Figure 13 is a schematic diagram illustrating a boundary problem that arises when PRG segmentation crosses physical carriers, as provided by related technologies. As shown in Figure 13, if the precoding granularity of the precoding resource block group... Even with the configuration of {2,4}, i.e., PRG, there can still be cases where the PRG spans multiple physical carriers. As shown in Figure 13, the RBs contained in PRG7 belong to both physical carrier 1 and physical carrier 2. For example, physical carrier 1 has a bandwidth of 30 RBs, physical carrier 2 has a bandwidth of 20 RBs, the PRG size is 4 RBs (i.e., the PRG contains 4 RBs), and the RB starting offset is 0.

[0166] Figure 14 is a schematic diagram of the binding between a physical carrier and a PRG provided in an embodiment of this application. The enhancement scheme is the same as the RBG described above, and may also include at least one of the following: splitting the PRG across multiple physical carriers (A / B in Figure 14); merging the residual RBs after splitting the PRG of each physical carrier into the last PRG of that physical carrier (C / D in Figure 14); merging the residual RBs after splitting the PRG of each physical carrier into the first PRG of that physical carrier (E / F in Figure 14); indicating the starting position offset value of each physical carrier (G / H in Figure 14); or combining multiple of the above schemes.

[0167] Example 6: RB bundling for VRB to PRB interleaving mapping.

[0168] Figure 15 is a schematic diagram illustrating the boundary problem arising from RB bundling in a VRB-to-PRB interleaving mapping provided by related technologies. As shown in Figure 15, if the precoding granularity of the precoding resource block group... Even with {2,4} configured, which is RB bundling, there may be situations where RB bundling spans multiple physical carriers. For example, physical carrier 1 has a bandwidth of 29 RBs, physical carrier 2 has a bandwidth of 20 RBs, the RB bundling size is 4 RBs, and the RB starting offset is 1 RB.

[0169] Figure 16 is a schematic diagram of the binding between physical carriers and resource block bundles provided in an embodiment of this application. The enhancement scheme, similar to the RBG and PRG described above, may also include at least one of the following: splitting RB bundles across multiple physical carriers (A / B in Figure 16); merging the residual RBs after splitting the RB bundles of each physical carrier into the last RB bundle of that physical carrier (C / D in Figure 16); merging the residual RBs after splitting the RB bundles of each physical carrier into the first RB bundle of that physical carrier (E / F in Figure 16); indicating the starting position offset value of each physical carrier (G / H in Figure 16); or combining multiple of the above schemes.

[0170] Example 7: Regarding CSI reporting issues.

[0171] Figure 17 is a schematic diagram of the boundary problem that arises when subband division crosses physical carriers, as provided by related technologies. As shown in Figure 17, the subband division problem can also result in subbands spanning multiple physical carriers. For example, physical carrier 1 has a bandwidth of 20 RBs, physical carrier 2 has a bandwidth of 30 RBs, and physical carrier 3 has a bandwidth of 30 RBs, totaling 80 RBs. According to Table 2, the subband contains 8 RBs, and the starting offset of the RBs is 2 RBs. The subbands divided according to the virtual bandwidth are shown in Figure 17 below.

[0172] Figure 18 is a schematic diagram of the binding between physical carriers and subbands provided in an embodiment of this application. The enhancement scheme, similar to the RBG and PRG described above, may also include at least one of the following: splitting subbands across multiple physical carriers (A / B in Figure 18); merging the residual RBs after subband splitting of each physical carrier into the last subband of that physical carrier (C / D in Figure 18); merging the residual RBs after subband splitting of each physical carrier into the first subband of that physical carrier (E / F in Figure 18); indicating the starting position offset value of each physical carrier (G / H in Figure 18); and combining multiple of the above schemes (I / J in Figure 18).

[0173] For schemes that modify the starting position offset value, it may not be necessary to process the boundary of every physical carrier. It may be possible to adjust only the starting position offset value of the physical carriers at even or odd positions.

[0174] Example 8:

[0175] Regarding CORESET, Figure 19 is a schematic diagram illustrating a boundary problem that occurs when CORESET crosses multiple physical carriers, as provided by related technologies. As shown in Figure 19, CORESET resources spanning multiple physical carrier resources are invalid resources, and gNB scheduling never uses these resources. Of course, these resources can be used under certain conditions.

[0176] In one embodiment, FIG20 is a structural block diagram of a data transmission device provided in an embodiment of this application. This embodiment is applied to a first communication device. As shown in FIG20, the data transmission device in this embodiment includes: a receiving module 310 and a transmitting module 320.

[0177] The receiving module 310 is configured to receive resource bundling indication information configured by the second communication device; wherein the resource bundling indication information is used to indicate the resource block group associated with each second type carrier contained in the first type carrier;

[0178] The transmission module 320 is configured to transmit data based on frequency domain resources bound by resource binding indication information.

[0179] In one embodiment, when a resource block group contains resource blocks belonging to two adjacent different second-type carriers, the partitioning method of the resource block group contained in the two adjacent different second-type carriers includes at least one of the following: splitting the remaining resource block into a new resource block group at the boundary of the two adjacent different second-type carriers; merging the remaining resource block into the last resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; merging the remaining resource block into the first resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; and adjusting the starting position offset value of each second-type carrier.

[0180] In one embodiment, the method of dividing resource block groups contained in two adjacent different second type carriers further includes: adjusting the method of dividing resource block groups contained in second type carriers at odd or even positions only.

[0181] In one embodiment, resource block groups are characterized by one of the following: resource block groups; precoded resource block groups; resource block bundles; subbands; control resource sets.

[0182] In one embodiment, the first type of carrier includes at least two second type carriers.

[0183] In one embodiment, the number of second-type carriers included in each first-type carrier is determined by one of the following: terminal capability; maximum value of the Fourier transform.

[0184] In one embodiment, the resource block groups contained in each second type carrier in the first type carrier are divided in the same way, or the resource block groups contained in each second type carrier in the first type carrier are divided in different ways.

[0185] In one embodiment, the resource block groups contained in the second type of carrier with odd carrier identifiers in the first type of carrier are divided in the same way, and the resource block groups contained in the second type of carrier with even carrier identifiers in the first type of carrier are divided in the same way.

[0186] In one embodiment, when the resource block group is a precoded resource block group, the precoding granularity of the precoded resource block group includes at least one of the following: 2; 4; subband; wideband.

[0187] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that all second-type carriers contained in the first-type carrier use the same precoding.

[0188] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that the second type of carrier contained in the first type of carrier uses the same precoding if the first condition is met.

[0189] In one embodiment, the first condition includes at least one of the following: test indicators; frequency domain spacing between different second-type carriers is less than a first threshold; UE capability.

[0190] 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 FIG5. The implementation principle and technical effect of the data transmission device provided in this embodiment are similar, and will not be described again here.

[0191] In one embodiment, FIG21 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 FIG21, the data transmission device in this embodiment includes: a generation module 410 and a transmission module 420.

[0192] The generation module 410 is configured to generate resource bundling indication information; wherein the resource bundling indication information is used to indicate the resource block grouping associated with each second type carrier contained in the first type carrier;

[0193] The sending module 420 is configured to send resource bundling instruction information to the first communication device.

[0194] In one embodiment, when a resource block group contains resource blocks belonging to two adjacent different second-type carriers, the partitioning method of the resource block group contained in the two adjacent different second-type carriers includes at least one of the following: splitting the remaining resource block into a new resource block group at the boundary of the two adjacent different second-type carriers; merging the remaining resource block into the last resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; merging the remaining resource block into the first resource block group of the second-type carrier at the boundary of the two adjacent different second-type carriers; and adjusting the starting position offset value of each second-type carrier.

[0195] In one embodiment, the method of dividing resource block groups contained in two adjacent different second type carriers further includes: adjusting the method of dividing resource block groups contained in second type carriers at odd or even positions only.

[0196] In one embodiment, resource block groups are characterized by one of the following: resource block groups; precoded resource block groups; resource block bundles; subbands; control resource sets.

[0197] In one embodiment, the first type of carrier includes at least two second type carriers.

[0198] In one embodiment, the number of second-type carriers included in each first-type carrier is determined by one of the following: terminal capability; maximum value of the Fourier transform.

[0199] In one embodiment, the resource block groups contained in each second type carrier in the first type carrier are divided in the same way, or the resource block groups contained in each second type carrier in the first type carrier are divided in different ways.

[0200] In one embodiment, the resource block groups contained in the second type of carrier with odd carrier identifiers in the first type of carrier are divided in the same way, and the resource block groups contained in the second type of carrier with even carrier identifiers in the first type of carrier are divided in the same way.

[0201] In one embodiment, when the resource block group is a precoded resource block group, the precoding granularity of the precoded resource block group includes at least one of the following: 2; 4; subband; wideband.

[0202] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that all second-type carriers contained in the first-type carrier use the same precoding.

[0203] In one embodiment, when the precoding granularity of the precoding resource block group is wideband, it indicates that the second type of carrier contained in the first type of carrier uses the same precoding if the first condition is met.

[0204] In one embodiment, the first condition includes at least one of the following: test indicators; frequency domain spacing between different second-type carriers is less than a first threshold; UE capability.

[0205] 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 FIG6. The implementation principle and technical effect of the data transmission device provided in this embodiment are similar, and will not be described again here.

[0206] In one embodiment, FIG22 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in FIG22, 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; FIG22 shows an example of one processor 510. The number of memories 520 in the device can be one or more; FIG22 shows an example of one memory 520. The processor 510, memory 520, and communication module 530 of the device can be connected via a bus or other means; FIG22 shows an example of connection via a bus. In this embodiment, the device can be a first communication device or a second communication device.

[0207] 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., receiving module 310 and transmitting 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, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0208] 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.

[0209] 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.

[0210] This application embodiment 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: receiving resource bundling indication information configured by a second communication device; wherein the resource bundling indication information is used to indicate resource block groups associated with each second type carrier contained in a first type carrier; and performing data transmission based on the frequency domain resources bundled by the resource bundling indication information.

[0211] This application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a data transmission method applied to a second communication device. The method includes: generating resource bundling indication information; wherein the resource bundling indication information is used to indicate resource block packets associated with each second type carrier contained in a first type carrier; and sending the resource bundling indication information to the first communication device.

[0212] 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.

[0213] 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.

[0214] 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.

[0215] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps 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, but not limited to, 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, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0216] 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.

[0217] 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).

[0218] It should be noted that the carriers involved in the embodiments of this application (e.g., a first type carrier / a second type carrier) can also be replaced by a set of RBs. In the embodiments of this application, the first type carrier may contain at least two second type carriers, and correspondingly, the set of RBs corresponding to the first type carrier contains at least two sets of RBs corresponding to the second type carriers. Furthermore, the number of RBs contained in the set of RBs corresponding to the first type carrier is the sum of the number of RBs contained in the sets of RBs corresponding to at least two second type carriers. Furthermore, the number of RBs contained in the set of RBs corresponding to each second type carrier may be different.

Claims

1. A data transmission method, applied to a first communication device, comprising: Receive resource bundling indication information configured by the second communication device; wherein the resource bundling indication information is used to indicate the resource block group associated with each of the multiple second type carriers included in the first type carrier; Data transmission is performed based on the frequency domain resources bundled according to the resource bundling indication information.

2. The method according to claim 1, wherein, In response to determining that a resource block group contains resource blocks belonging to two adjacent different second-type carriers, the partitioning method of the resource block group contained in the two adjacent different second-type carriers includes at least one of the following: at the boundary of the two adjacent different second-type carriers, splitting the remaining resource block into a new resource block group; at the boundary of the two adjacent different second-type carriers, merging the remaining resource block into the last resource block group of the two adjacent second-type carriers with the smaller carrier identifier; at the boundary of the two adjacent different second-type carriers, merging the remaining resource block into the first resource block group of the two adjacent second-type carriers with the smaller carrier identifier; adjusting the starting position offset value of the second-type carrier with the smaller carrier identifier among the two adjacent different second-type carriers.

3. The method according to claim 2, wherein, The method of dividing resource block groups contained in two adjacent different second-type carriers also includes: adjusting the method of dividing resource block groups contained in second-type carriers with odd or even positions only.

4. The method according to any one of claims 1-3, wherein, The resource block grouping is characterized by one of the following: resource block group; precoded resource block group; resource block bundle; subband; control resource set.

5. The method according to any one of claims 1-3, wherein, The first type of carrier includes at least two second type carriers.

6. The method according to any one of claims 1-3, wherein, The number of second-type carriers included in the first type of carrier is determined by one of the following: terminal capability; maximum value of the Fourier transform.

7. The method according to any one of claims 1-3, wherein, The resource block groups contained in the plurality of second-type carriers in the first type of carrier are divided in the same way, or the resource block groups contained in the plurality of second-type carriers in the first type of carrier are divided in different ways.

8. The method according to any one of claims 1-3, wherein, The resource block groups contained in the second type of carrier with odd-numbered carrier identifiers in the first type of carrier are divided in the same way, and the resource block groups contained in the second type of carrier with even-numbered carrier identifiers in the first type of carrier are divided in the same way.

9. The method according to claim 1, wherein, In response to determining that the resource block group is a precoded resource block group, the precoding granularity of the precoded resource block group includes at least one of the following: 2; 4; subband; wideband.

10. The method according to claim 9, wherein, In response to determining that the precoding granularity of the precoding resource block group is wideband, it indicates that all second-type carriers contained in the first-type carrier use the same precoding.

11. The method according to claim 9, wherein, In response to determining that the precoding granularity of the precoding resource block group is broadband, it indicates that the second type of carrier contained in the first type of carrier uses the same precoding if the first condition is met.

12. The method according to claim 11, wherein, The first condition includes at least one of the following: test indicators; frequency domain spacing between different second-type carriers is less than a first threshold; user equipment (UE) capability.

13. A data transmission method, applied to a second communication device, comprising: Generate resource bundling indication information; wherein, the resource bundling indication information is used to indicate the resource block group associated with each of the multiple second-type carriers contained in the first-type carrier; The resource bundling instruction information is sent to the first communication device.

14. A communication device, comprising: Memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors perform the method as described in any one of claims 1-12 or 13 above.

15. A storage medium storing a computer program that, when executed by a processor, implements the method as described in any one of claims 1-12 or 13.

Images