WO2013029430A1

WO2013029430A1 - Rbg process method and system thereof

Info

Publication number: WO2013029430A1
Application number: PCT/CN2012/078448
Authority: WO
Inventors: 夏树强; 陈华夏; 苟伟; 金圣峣; 戴博; 左志松
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-09-01
Filing date: 2012-07-10
Publication date: 2013-03-07
Also published as: CN102970753A; CN102970753B

Abstract

A RBG (Resource Block Group) process method and system thereof are provided by the present invention. Both the method and the system regard the carrier segment and the backward compatible carrier used by couple as two independent parts, and can determine their own RBG sizes based on their own bandwidths (410); divide the backward compatible carrier and the carrier segment by RBG based on the determined RBG size (420), and number the RBG of the backward compatible carrier and the RBG of the carrier segment (430). The present invention solves the problem of the disorder of resource allocation caused by the different size of RBG with different version of UE after allocating the carrier segment, and are useful for compatibility of the LTE-Advanced and the LTE, and are useful for realizing the LTE-Advanced system.

Description

RBG processing method and system

The present invention relates to the field of communications, and in particular, to a resource block group (RBG) processing method and system. Background technique

With the development of the mobile communication industry and the growing demand for mobile data services, people are increasingly demanding the speed and quality of service (Qos) of mobile communications, so there is no big third-generation mobile communication (3G). Before the scale of commercial use, research and development work on next-generation mobile communication systems has begun. The most typical one is the Long Term Evolution (LTE) project initiated by the 3rd Generation Partnership Project (3GPP), the highest spectrum that the LTE system can provide. The bandwidth is 20MHz (megahertz). With the further evolution of the network, LTE-A (Evolved LTE), as an evolution system of LTE, can provide spectrum bandwidth of up to 100MHz, support more flexible and higher quality communication, and has good backward compatibility. In an LTE-A system, there are multiple component carriers (CCs), one LTE terminal can only work on one backward compatible CC, and a strong LTE-A terminal can simultaneously on multiple CCs. Transfer.

In the LTE system, when the subcarrier spacing is 15 kHz, one subframe in the time domain and 12 consecutive or non-contiguous subcarriers in the frequency domain are used as one RB (Resource Block). The RB is divided into two types (types) of PRB (physical resource block) and VRB (virtual resource block) according to whether the frequency is continuously, and is the smallest resource unit for uplink and downlink scheduling.

When the enhanced base station (eNB, enhanced Node B) performs resource scheduling, the resource scheduling information is transmitted to the user equipment (UE, User Equipment) through downlink control information (DCI, Downlink Control Information). The physical channel through which the DCI is transmitted is called a physical downlink control channel (PDCCH, Physical Downlink Control CHannel). UE DCI through PDCCH Type to explain the contents of the resource allocation field. In each PDCCH, the resource allocation field is composed of two parts: a resource allocation header and resource block allocation information. There are three types of resource allocation: Type 0, Type 1 and Type 2. Type 0 and Type 1 use the same number of bits. When transmitting through DCI Types 1, 2, 2A, 2B, 2C, both have exactly the same format. At this time, the first bit of the resource allocation is used to distinguish, 0 means Type 0, 1 means type 1. The DCI formats 1A, 1B, 1C, and ID are used for Type 2 transmission. The resource allocation type 0/1 uses the PRB to indicate the resource, and the resource allocation type 2 uses the VRB to indicate the allocated resource.

When the eNB performs resource scheduling, the following situations exist:

The DCI is transmitted by type 1, 2, 2A, 2B, 2C, and the resource allocation header (Resource Allocation Header) has a bit value of 0:

In resource allocation type 0, the resource block allocation information includes a resource group allocation bitmap, which represents RBG information allocated by the eNB to a specific UE. The size of the RBG depends on the system bandwidth. The corresponding relationship is shown in Table 1. Table 1 shows the resource allocation RBG size and downlink system bandwidth mapping table defined by 3GPP Release 10 (Rdease-10):

Table 1 The number of resource groups is determined by the system bandwidth and the resource group size: ^ ⁷ ^^^ , which contains "A / resource groups of size p, and a size of

group. Resource groups are numbered starting from the low frequency. The RBG number is from 0 to ^^. ^_1 maps to the most significant bit to the least significant bit, respectively. The DCI is transmitted by type 1, 2, 2A, 2B, 2C, and the bit value of the resource allocation header is 1. In the resource allocation type 1, the resource block allocation information is within the range of the RBGs, and the assigned one is specified for the scheduled UE. RB. The scheme groups the PRBs according to Table 1, and each RBG contains P physical resource blocks. These resource blocks are numbered from 0 to P-1. A physical resource numbered p in a continuous RBG is selected to form an RBG subset. The eNB allocates resources to the UE within a subset.

In Type 1, the resource block allocation information is divided into three fields: The first field uses "^{1<3⁄42(Ρ)Ί} bits to mark the position of the selected RB in the RBG; the second field uses the 1-bit flag to use. Offset

The third field contains a bitmap with each bit of the bitmap used to represent one PRB in the selected RBG subset. The resource block is mapped onto the bitmap from the most significant bit as the frequency increases.

TYPE1

Ν·

The size of this bitmap is defined as: RB / - flog

Since the bitmap is smaller than " ^{1 (3⁄42(Ρ)", the} bitmap cannot cover all the RBGs, causing the RBG to be offset when numbering.

When the tag uses the second field of the offset to be 0, ^{Δ = ()} does not use the offset. At this time, the number of the resource block starts from the lowest frequency and increases from zero. When the second field is 1,

-RBG subset

The offset will be introduced at the resource block number, and the offset value is: A _S ^W ⁼ RB (Ρ) - Ν^ , which

, x rRBGsubset / , , . _ a " , , a subset / , a , , ^N RB (P) represents the number of RBs in the subset of resource groups p. ^N RB (P) can be obtained by the following formula:

Child

- 1

■P + P LB - 1

Mod corpse

P ² P

Subset \ - 1

P + (N^ -l) mod F + l , p : iB - 1

Mod corpse

2 P mod corpse

At the UE side, by PDCCH decoding, the UE obtains the value of the ith bit in the bitmap, and the root According to the subset flag p, the relocation of the RB is done by the following formula:

RBG subset , + ^A shift (P)

«VRB (P): P ² + p - P + (i + A _shift (p)) mod P

P

The DCI is transmitted by type 1A, 1B, 1C, ID, and resource allocation type 2 is adopted. The resource allocation type 0/1 uses the PRB to indicate the resource, and the resource allocation type 2 uses the VRB to indicate the allocated resource.

As can be seen from Table 1, the size of the carrier bandwidth determines the size of the RBG, which in turn determines the number of resource allocation bits in the DCI and the overall bit length of the DCI.

The Carrier Segment is an incompatible carrier. The fragmented carrier cannot be used independently. It can only be used as part of the bandwidth of a backward compatible carrier to increase the transmission capability of the backward compatible carrier. The sum of the bandwidth of the slice carrier and the paired backward compatible carrier does not exceed HORBSo

When the fragment carrier is configured, considering its characteristics (the PDCCH is still used to indicate the resources of the backward compatible carrier and the fragment carrier as a whole after the fragment carrier is added), the addition of the fragment carrier will increase the total number of PRBs. The RBGs corresponding to the number of PRBs of the backward compatible carrier, the fragmented carrier, and the aggregated carrier may be different. That is, the RBG size determined by the lower version UE and the new version of the UE configured with the fragmented carrier according to the number of PRBs is inconsistent. Since the existing standard does not support allocating resources for two or more users of different RBG sizes at the same time, after configuring the fragment carrier, there will be a problem of how to determine the RBG size to explicitly indicate the resource allocation information; but obviously, due to the above The existence of the case where the RBG sizes are inconsistent, the problem cannot be solved at present. Summary of the invention

In view of this, the main purpose of the present invention is to provide an RBG processing method and system, which solves the problem of resource allocation confusion caused by inconsistent RBG sizes of different versions of UEs after configuring a fragment carrier.

In order to achieve the above object, the technical solution of the present invention is achieved as follows: A resource block group RBG processing method, the method comprising:

Treating the paired slice carrier and the backward compatible carrier as two independent parts, respectively determining respective resource block group RBG sizes according to respective bandwidths; according to the determined RBG size, the backward compatible carrier The resource block RB and the RB of the fragment carrier perform RBG division, and number the divided RBG of the backward compatible carrier and the RBG of the slice carrier.

Wherein, when determining the RBG size:

When the aggregation uses the backward compatible carrier and the fragment carrier, the mapping table is separately checked according to the number of RBs included in each carrier to obtain a corresponding RBG size; and/or,

For the fragmented carrier, redefine the mapping table between the dedicated RBG size and the downstream system bandwidth. Wherein, when the RBG is divided, the RBs of the backward compatible carrier and the fragment carrier are not simultaneously included in one RBG.

When the RBG is numbered, if the total number of RBs is not an integer multiple of the RBG size, the following conditions are allowed: The number of RBs included in the RBG with the highest number is smaller than the RBG size.

The method for numbering the RBG is:

The RBG for the backward compatible carrier is numbered from 0; for the RBG of the fragment carrier, the maximum value of the RBG number from the backward compatible carrier continues to be numbered backwards, from the low frequency to the high frequency, or from the high frequency to Low frequency

When multiple slice carriers are used for backward compatible carrier aggregation, they are numbered according to the frequency of each slice carrier from low frequency to high frequency, or from high frequency to low frequency.

The method further includes:

When the RBG allocation status is indicated, the working mode of the resource allocation type 0, 1, and 2 is applied, and the RBG size corresponding to the carrier of different types and bandwidths is different; the backward compatible carrier and the fragment carrier are independently mapped according to the respective RBG sizes, and are downlinked. In the resource allocation bits included in the control information DCI, The indication bit of the backward compatible carrier corresponds to the RBG of the backward compatible carrier, and the indication bit of the fragment carrier corresponds to the RBG of the fragment carrier.

The method for numbering the RBG is:

The RBG for the backward compatible carrier is numbered from 0; the RBG for the fragment carrier is also numbered from 0, and the numbering sequence is from low frequency to high frequency, or high frequency to low frequency;

When multiple slice carriers are used for backward compatible carrier aggregation, the RBG number is performed from low frequency to high frequency or high frequency to low frequency according to the frequency of each slice carrier.

The method further includes:

In the case of indicating the RBG allocation, the working mode of the resource allocation type 0, 1, and 2 is applied. When the RBG numbers of the different carriers are the same, a DCI format including the carrier indicator bit is added to indicate that the scheduled resource belongs to Backward compatible carrier and slice carrier;

Corresponding to the resources on different carriers, there are cases where the RBG size is different.

An RBG processing system, the system includes an RBG size defining unit, an RBG dividing unit, and an RBG numbering unit;

The RBG size defining unit is configured to treat the fragment carrier used by the pairing and the backward compatible carrier as two independent parts, and respectively determine respective RBG sizes according to respective bandwidths;

The RBG dividing unit is configured to perform RBG division on the RB of the backward compatible carrier and the RB of the fragment carrier according to the determined RBG size;

The RBG numbering unit is configured to number the RBG of the backward backward compatible carrier and the RBG of the fragment carrier.

The RBG size defining unit is configured to: when the backward-compatible carrier and the fragment carrier are used for aggregation, check the mapping table according to the number of RBs included in each carrier to obtain a corresponding RBG size; and / or,

For the slice carrier, redefine the mapping table between the dedicated RBG size and the downlink system bandwidth. The RBG dividing unit is configured to: different in one RBG when dividing the RBG An RB containing a backward compatible carrier and a slice carrier.

Wherein, when the RBG numbering unit numbers the RBG, it is used to:

If the total number of RBs is not an integer multiple of the RBG size, the following conditions are allowed: Number The number of RBs included in the largest RBG is smaller than the RBG size.

Wherein, when the RBG numbering unit numbers the RBG, it is used to:

The RBG dividing unit is configured to: when indicating an RBG allocation situation:

The working mode of the resource allocation type 0, 1, and 2, the RBG size corresponding to the carrier of different types and bandwidths is different; the backward compatible carrier and the fragment carrier are mapped independently according to the respective RBG sizes;

In the resource allocation bits included in the DCI, the indication bit of the backward compatible carrier corresponds to the RBG of the backward compatible carrier, and the indication bit of the fragment carrier corresponds to the RBG of the fragment carrier.

Wherein, when the RBG numbering unit numbers the RBG, it is used to:

The working mode of the resource allocation type 0, 1, and 2, when the RBG numbers of the different carriers are the same, the DCI format including the carrier indicator bit is added to indicate the backward compatible carrier and the sub-group to which the scheduled resource belongs. Chip carrier Corresponding to the resources on different carriers, there are cases where the RBG size is different.

The RBG processing technique of the present invention treats the RBs of the backward compatible carrier and the fragment carrier as two independent parts, respectively defining the RBG size and dividing the RBG. Therefore, the problem of resource allocation confusion caused by inconsistent RBG sizes of different versions of UEs after the fragment carrier is configured is solved, which is beneficial to the compatibility of LTE-Advanced and LTE, and is beneficial to the implementation of the LTE-Advanced system. DRAWINGS

1 is a schematic diagram of an RBG number according to Embodiment 1 of the present invention;

2 is a schematic diagram of an RBG numbering according to Embodiment 2 of the present invention;

3 is a schematic diagram of resource allocation bits according to an embodiment of the present invention;

4 is a schematic diagram of an RBG processing flow according to an embodiment of the present invention;

FIG. 5 is a diagram of an RBG processing system according to an embodiment of the present invention. detailed description

In order to solve the problem of resource allocation confusion caused by inconsistent RBG sizes of different versions of UEs after configuring the fragment carrier, it is beneficial to the compatibility of LTE-Advanced and LTE, and is beneficial to the implementation of the LTE-Advanced system; The RBs that are compatible with the carrier and the fragment carrier are treated as two independent parts, respectively defining the RBG size and dividing the RBG. In practical applications, the backward compatible carrier and the fragment carrier are usually paired.

The above solution is also applicable to the two-carrier joint scheduling, that is, the resources of the two carriers are combined to be regarded as one carrier resource for scheduling. The present invention takes the two carriers corresponding to the fragment carrier and the backward compatible carrier as an example. In practical applications, only two carriers need to be paired to perform corresponding processing according to the following fragment carrier and its paired backward compatible carrier.

Generally, an RB in a RBG cannot contain both backward compatible carriers and fragment carriers. For the backward compatible carrier, refer to the RBG size determination method in 3GPP Release-10, and follow the mapping table of the RBG size and the downlink system bandwidth as shown in Table 1. For the fragment carrier, The mapping table of the RBG size and the downlink system bandwidth shown in Table 1 can also be used to redefine the mapping table of the dedicated RBG size and the downlink system bandwidth.

When the user aggregates the backward compatible carrier and the fragment carrier, the mapping table is separately checked according to the number of RBs included in each carrier to obtain the corresponding RBG size. According to the RBG size, the RBs of the backward compatible carrier and the fragment carrier are respectively divided into RBGs. If the total number of RBs is not an integer multiple of the RBG size, the 3GPP Rdease-10 stipulates that the number of RBs included in the RBG with the highest number may be smaller than the RBG size.

After the RBG is divided, the RBG for the backward compatible carrier continues to be numbered starting from 0 according to the 3GPP Rdease-10, and the RBG of the fragment carrier is continuously numbered from the backward RBG number of the compatible carrier, and the number order can be It is from low frequency to high frequency, or from high frequency to low frequency. When multiple fragment carriers are used in backward-compatible carrier aggregation, the above rules can also be followed. After looking up the table to obtain the RBG size, the frequency of each fragment carrier is from low frequency to high frequency, or high frequency to low frequency. Numbering. When the RBG allocation status is indicated, the operation mode of the resource allocation type 0, 1, and 2 in the 3GPP Rdease-10 is used, and the RBG sizes corresponding to the carriers of different types and bandwidths are different. The backward compatible carrier and the fragment carrier are independently mapped according to respective RBG sizes. In the resource allocation bits included in the DCI, the indication bit of the backward compatible carrier corresponds to the RBG of the backward compatible carrier, and the indication bit of the fragment carrier Corresponding to the RBG of the fragment carrier, the UE demaps separately.

Of course, after the RBG division is completed, the following operations may also be performed: The RBG for the backward compatible carrier continues to be numbered starting from 0 according to the 3GPP Rdease-10 specification; the RBG for the fragment carrier is also numbered starting from 0 according to the 3GPP Rdease-10 specification. The numbering sequence can be from low frequency to high frequency, or from high frequency to low frequency. When multiple fragment carriers are used for backward compatible carrier aggregation, the above rules may also be followed, respectively, to obtain the corresponding RBG size, and then according to the frequency of each fragment carrier from low frequency to high frequency, or high frequency to low frequency. Carry out the RBG number. When the RBG allocation status is indicated, the working mode of the resource allocation type 0, 1, and 2 in 3GPP Release-10 is used, and different carriers are corresponding. The RBG number may be the same, and a DCI format including a carrier indicator bit needs to be added to indicate the backward compatible carrier and the fragment carrier to which the scheduled resource belongs. The RBG sizes may be different according to resources on different carriers, and the UEs are respectively mapped.

Embodiments of the present invention will be described in detail below with reference to the embodiments.

In a specific embodiment, a scenario in which a backward compatible carrier and a slice carrier are aggregated in an LTE-A system can be considered. It is assumed that two component carriers are configured in the LTE-A system and can be used in aggregate. One of the backward compatible carriers is 5MHz and contains 25 RBs; the other fragmented carrier is 1.4MHz and contains 6 RBs.

Specific embodiment 1

Assume that some new versions of UE aggregate use a 5MHz backward compatible carrier and a 1.4MHz slice carrier. In the resource allocation, for the backward compatible carrier, the mapping table of bandwidth and RBG size in 3GPP Rdease-10 is used. As shown in Table 1, the 5 MHz backward compatible carrier corresponds to an RBG size of 2. For the fragmented carrier, the mapping table of bandwidth and RBG size in 3GPP Rdease-10 is redefined or used. It is assumed that the 3GPP Rdease-10 mapping table is used, and the RBG size corresponding to the 1.4 MHz fragment carrier aggregation is 1.

After determining the RBG size corresponding to each carrier, the RBs of the slice carrier and the backward compatible carrier are regarded as two independent parts, and the RBGs are respectively divided according to the respective RBG sizes, and the backward compatible carriers and the points cannot be included in one RBG at the same time. The RB of the slice carrier. If the total number of RBs is not an integer multiple of the RBG size, then the 3GPP Release-10 is used: The number of RBs included in the RBG with the highest number can be smaller than the RBG size.

The rule of the RBG number is: the RBG for the backward compatible carrier is numbered starting from 0 according to the 3GPP Rdease-10 specification; the RBG for the fragment carrier continues to be numbered from the maximum value of the RBG number of the backward compatible carrier, and the number order may be It is from low frequency to high frequency, or from high frequency to low frequency. This is followed by the 3GPP Rdease-10 specification, which is numbered from low frequency to high frequency. As shown in Figure 1, the backward compatible carrier has an RBG number from 0 to 12 (where the 12th RBG contains only the backward compatible carrier 1) RB), the RBG number of the fragment carrier is from 13 to 15. When the RBG allocation status is indicated, the RBG sizes corresponding to the carriers of different types and bandwidths are different according to the working mode of the resource allocation types 0, 1, and 2 in 3GPP Release-10.

The backward compatible carrier and the fragment carrier are independently mapped according to the respective RBG size. In the resource allocation bits included in the DCI, the indication bit of the backward compatible carrier corresponds to the RBG of the backward compatible carrier, and the indication bit of the fragment carrier corresponds to The RBG of the fragment carrier is demapped by the UE. Moreover, the number of resource allocation bits included in the DCI needs to be increased, so that the eNB can indicate the scheduling information of the RBG on the backward compatible carrier and the fragment carrier by using the resource allocation bits included in the DCI. If resource allocation type 0 is used, the resource allocation bit corresponding to RBG 1, 5, 12, and 16 is 01000100000010001. The UE can learn that the RBGs 1, 5, 12 on the backward compatible carrier and the RBG 16 on the fragment carrier are called, and at the same time, according to the bandwidth lookup table, the RBG size corresponding to the backward compatible carrier is 2, and the fragment carrier corresponds to The RBG size is 1, so the resource allocation can be clearly known.

Specific embodiment 2

Assume that some new versions of UE aggregate use a 5MHz backward compatible carrier and a 1.4MHz slice carrier. In the resource allocation, for the backward compatible carrier, the mapping table of bandwidth and RBG size in 3GPP Rdease-10 is used. As shown in Table 1, the 5 MHz backward compatible carrier corresponds to an RBG size of 2. For the fragment carrier, the mapping table of bandwidth and RBG size in 3GPP Rdease-10 is redefined or used. Here, a mapping table of bandwidth and RBG size as shown in Table 2 is newly defined. Table 2 is newly defined in the embodiment of the present invention. The resource allocation RBG size is related to the downlink system bandwidth mapping table. In Table 2, the RBG size corresponding to the 1.4 MHz fragment carrier aggregation is 1.

System bandwidth RBG size

( P )

<8 1

8-30 2 31-63 3

64-110 4

Table 2

The RBG numbering rules are: RBGs for backward compatible carriers are numbered starting from 0 according to 3GPP Rdease-10; RBGs for fragmented carriers are numbered starting from 0 according to 3GPP Rdease-10, and the numbering sequence can be from low frequency to High frequency, or from high frequency to low frequency. This is followed by the 3GPP Rdease-10 specification, which is numbered from low frequency to high frequency. As shown in Figure 2, the RBG number of the backward compatible carrier is from 0 to 12 (where the 12th RBG contains only 1 RB of the backward compatible carrier), and the RBG number of the fragment carrier is from 0 to 5. When the RBG allocation is indicated, the RBG size of the carrier of different types and bandwidths is different according to the working mode of the resource allocation type 0, 1, and 2 in the 3GPP Rdease-10, and the RBG number may be repeated after the aggregation of different types of carriers. Therefore, a DCI format including a carrier indication bit needs to be added to indicate a backward compatible carrier and a fragment carrier to which the scheduled resource belongs.

It can be assumed that the carrier indicator bit is 2 bits, located in the first two bits of the resource indicator bit, the backward compatible carrier number is 0, and the slice carrier number is 1. Then, when the resource allocation type 0 is used, the resource allocation bits corresponding to the RBGs 1, 5, 12 of the compatible carrier and the RBG 2 of the fragment carrier are as shown in FIG. 3. According to the resource allocation bits included in the DCI, the UE may learn to call the RBGs 1, 5, 12 on the backward compatible carrier and the RBG 2 on the fragment carrier, and at the same time, learn the RBG corresponding to the backward compatible carrier according to the bandwidth lookup table. The size is 2, and the RBG size corresponding to the fragment carrier is 1, so that the resource allocation can be clearly known. According to the foregoing embodiments, the operation of the RBG of the present invention may represent a process as shown in FIG. 4, and the path includes the following steps:

Step 410: The paired used carrier carrier and the backward compatible carrier are regarded as two independent parts, and the respective RBG sizes are determined according to respective bandwidths.

Step 420: Perform RBG division on the RB of the backward compatible carrier and the RB of the fragment carrier according to the determined RBG size.

Step 430: Number the divided RBG of the backward compatible carrier and the RBG of the fragment carrier.

In order to ensure that the above embodiments and operation ideas can be smoothly implemented, the settings shown in FIG. 5 can be performed. Referring to FIG. 5, FIG. 5 is a diagram of an RBG processing system according to an embodiment of the present invention, where the system includes a connected RBG size defining unit, an RBG dividing unit, and an RBG numbering unit.

In practical applications, the RBG size defining unit can treat the fragmented carrier and the backward compatible carrier used in the pairing as two independent parts, and determine the respective RBG sizes according to the respective bandwidths. The RBG dividing unit is configured to perform RBG division on the RB of the backward compatible carrier and the RB of the fragment carrier according to the determined RBG size. The RBG numbering unit is capable of numbering the divided RBG of the backward compatible carrier and the RBG of the fragment carrier.

In summary, the RBG processing technique of the present invention treats the RBs of the backward compatible carrier and the fragment carrier as two independent parts, respectively, and defines the RBG size and divides the RBG, whether it is a method or a system. Therefore, the problem of resource allocation confusion caused by inconsistent RBG sizes of different versions of UEs after the fragment carrier is configured is solved, which is beneficial to the compatibility of LTE-Advanced and LTE, and is beneficial to the implementation of the LTE-Advanced system.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

1. A resource block group RBG processing method, the method comprising:

2. The method according to claim 1, wherein, when determining the RBG size: when the backward-compatible carrier and the fragment carrier are used for aggregation, respectively, the mapping table is respectively checked according to the number of RBs included in each carrier to obtain a corresponding RBG size. ; and / or,

For the fragmented carrier, redefine the mapping table between the dedicated RBG size and the downstream system bandwidth.

3. The method according to claim 1, wherein, when the RBG is divided, the RBs of the backward compatible carrier and the fragment carrier are not included in one RBG.

4. The method according to claim 1, wherein, when the RBG is numbered, if the total number of RBs is not an integer multiple of the RBG size, the following conditions are allowed: The number of RBs included in the RBG with the highest number is smaller than the RBG. size.

The method according to any one of claims 1 to 4, wherein the method of numbering the RBG is:

6. The method according to claim 5, wherein the method further comprises: When the RBG allocation status is indicated, the working mode of the resource allocation type 0, 1, and 2 is applied, and the RBG size corresponding to the carrier of different types and bandwidths is different; the backward compatible carrier and the fragment carrier are independently mapped according to the respective RBG sizes, and are downlinked. In the resource allocation bits included in the control information DCI, the indication bit of the backward compatible carrier corresponds to the RBG of the backward compatible carrier, and the indication bit of the fragment carrier corresponds to the RBG of the fragment carrier.

8. The method according to claim 7, wherein the method further comprises:

9. An RBG processing system, the system comprising an RBG size defining unit, an RBG dividing unit, and an RBG numbering unit; wherein

10. The system according to claim 9, wherein the RBG size defining unit is When the RBG size is determined, it is used to:

The system according to claim 9, wherein the RBG dividing unit is configured to: when not dividing an RBG, RBs that include a backward compatible carrier and a fragment carrier in one RBG.

The system according to claim 9, wherein when the RBG numbering unit numbers the RBG, it is used to:

The system according to any one of claims 9 to 12, wherein, when the RBG numbering unit numbers the RBG, it is used to:

14. The system according to claim 13, wherein, when indicating an RBG allocation situation, the RBG dividing unit is configured to:

The system according to any one of claims 9 to 12, wherein the RBG number When the unit numbers the RBG, it is used to:

The system according to claim 15, wherein, when indicating an RBG allocation situation, the RBG dividing unit is configured to:

The working mode of the resource allocation type 0, 1, and 2, when the RBG numbers of the different carriers are the same, the DCI format including the carrier indicator bit is added to indicate the backward compatible carrier and the sub-group to which the scheduled resource belongs. Chip carrier