CN102970709B - It is a kind of configuration fragment carrier wave after RBG sizes and number determination method and apparatus - Google Patents

It is a kind of configuration fragment carrier wave after RBG sizes and number determination method and apparatus Download PDF

Info

Publication number
CN102970709B
CN102970709B CN201110258014.XA CN201110258014A CN102970709B CN 102970709 B CN102970709 B CN 102970709B CN 201110258014 A CN201110258014 A CN 201110258014A CN 102970709 B CN102970709 B CN 102970709B
Authority
CN
China
Prior art keywords
carrier
rbg
rbgs
backward compatible
rbs
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201110258014.XA
Other languages
Chinese (zh)
Other versions
CN102970709A (en
Inventor
苟伟
戴博
夏树强
左志松
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201110258014.XA priority Critical patent/CN102970709B/en
Priority to PCT/CN2012/077919 priority patent/WO2013029419A1/en
Publication of CN102970709A publication Critical patent/CN102970709A/en
Application granted granted Critical
Publication of CN102970709B publication Critical patent/CN102970709B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention discloses a kind of determination methods of RBG sizes and number after configuration fragment carrier wave, including：Enhancing base station (eNB) is after terminal (UE) configures fragment carrier wave, and eNB and UE determine that resource block group (RBG) size the sum of is equal to fragment carrier wave and matches the bandwidth of backward compatibility carrier wave used with it corresponding RBG sizes；According to determining RBG sizes, the RB of the RB of backward compatibility carrier wave and fragment carrier wave are considered as an entirety or two parts carry out the division of RBG, to after division the RBG of the backward compatibility carrier wave and the RBG of fragment carrier wave be numbered.The invention also discloses the determining devices of RBG sizes and number after a kind of configuration fragment carrier wave, by the invention it is possible to solve after being configured with fragment carrier wave, resource allocation confusion problem caused by the RBG size disunities of different editions UE.

Description

Method and device for determining size and number of RBG (radial basis group) after configuration of fragmented carrier
Technical Field
The present invention relates to the field of mobile wireless communications, and in particular, to a method and an apparatus for determining a size and a number of a Resource Block Group (RBG) after a fragmentation carrier is configured.
Background
With the development of the mobile communication industry and the increasing demand for mobile data services, the demand for mobile communication speed and quality of service (Qos) is higher, and therefore, before the third generation mobile communication (3G) is not yet commercialized in a large scale, research and development work on the next generation mobile communication system has been started, wherein the LTE system can provide the highest carrier bandwidth of 20MHz (megahertz), typically, by the Long Term Evolution (LTE) project initiated by the third generation partnership project (3 GPP).
With the further evolution of the network, the evolution LTE (LTE-a) as an LTE evolution system can provide a carrier bandwidth up to 100MHz, support more flexible and higher quality communication, and have good backward compatibility. In an LTE-a system, there are multiple Component Carriers (CCs), one LTE terminal can only operate on a certain CC that is backward compatible, and an LTE-a terminal with a strong capability can simultaneously transmit on multiple CCs.
In the LTE system, when the uplink carrier interval is 15kHz, one subframe in the time domain and 12 consecutive or non-consecutive subcarriers in the frequency domain are used as one Resource Block (RB). The RB is continuously divided into two types, Physical Resource Block (PRB) and Virtual Resource Block (VRB), according to frequency, and is the minimum resource unit for uplink and downlink scheduling.
When an enhanced base station (eNB) performs resource scheduling, a resource scheduling condition is transmitted to a User Equipment (UE) through Downlink Control Information (DCI). A Physical channel for transmitting DCI is called a Physical Downlink Control Channel (PDCCH). The UE interprets the contents of the resource allocation field by the DCI type of the PDCCH. Depending on the DCI type, the indication of resources is different. In each PDCCH, the resource allocation field consists of two parts: resource allocation header and resource block allocation information. Resource allocation includes three types: type 0, type 1, and type 2. Type 0 and type 1 use the same number of bits, and when transmitting through DCI types 1, 2A, 2B, and 2C, they have the same format, and in this case, they are distinguished by resource allocation header 1 bit, where 0 indicates type 0 and 1 indicates type 1. While DCI formats 1A, 1B, 1C, 1D are used for type 2 transmission. Resource allocation type 0, 1 uses PRBs to indicate resources, and resource allocation type 2 uses VRBs to indicate allocated resources.
When the eNB performs resource scheduling, there are the following situations:
1. the DCI is transmitted by types 1, 2A, 2B and 2C, and when the resource allocation header bit value is 0: in Resource allocation type 0, the Resource Block allocation information includes a Resource Group allocation bitmap indicating Resource Block Group (RBG) information allocated by the eNB to a specific UE. The size P of the RBG depends on the carrier bandwidth, and the corresponding relationship is shown in table 1:
TABLE 1
The number of RBGs is determined by the carrier bandwidth and the size of the RBGs together:which comprisesRBG of size P, and RBG of size PThe RBG of (1). The RBGs are numbered starting from low frequency. RBG numbering from 0 to NRBG-1 maps to the most significant bit to the least significant bit, respectively.
2. The DCI is transmitted by types 1, 2A, 2B and 2C, and when the resource allocation header bit value is 1: in resource allocation type 1, the resource block allocation information indicates allocated RBs for a scheduled UE within a subset of the RBG set. The scheme groups PRBs according to Table 1, each RBG contains P PRBs, and the PRBs are numbered from 0 to P-1. Selecting PRBs numbered as P (P is more than or equal to 0 and less than or equal to P-1) in a section of continuous RBGs to form an RBG subset. The eNB allocates resources to the UE within the subset.
In type 1, the resource block allocation information is divided into 3 fields:
first field usageBits mark the position of the selected RB in the RBG;
the second field uses 1 bit to mark whether to use offset;
the third field contains a bitmap, each bit of which is used to represent one PRB in the selected RBG subset.
The RB is mapped to the bitmap starting from the most significant bit according to the increase in frequency. The size of the bitmap is defined as:
since the size of the bitmap in this method is smaller thanTherefore, the bitmap cannot cover all RBGs, and an offset is required when the RBGs are numbered. In this type of resource block allocation information, the second field indicates whether an offset is used, and when the field is 0, ΔshiftNo offset is used when (p) — 0. At this time, the number of the RB is sequentially increased from zero starting from the lowest frequency; when the field is 1, an offset is introduced into the RB number, and the offset takes the value ofWhereinIndicates the number of RBs in the RBG subset consisting of the RBs numbered p (designated as p RBG subset).Can be obtained by the following formula:
at the UE end, through PDCCH decoding, the UE obtains the value of the ith bit in the bitmap, and according to the RBG subset mark p, the RB relocation is completed through the following formula:
3. DCI is transmitted in types 1A, 1B, 1C, and 1D, and when a resource allocation type 2 is adopted: resource allocation type 0, 1 indicates resources using PRBs, and resource allocation type 2 indicates allocated resources using VRBs. The advantage of using the VRB is that continuous allocation can be used in resource scheduling, and then the VRB is allocated to the PRB in a local or distributed manner, and meanwhile, the overhead of signaling bits is also saved.
As can be seen from table 1, the size of the carrier bandwidth determines the size of the RBG, and further determines the number of resource allocation bits in the DCI and the overall bit length of the DCI.
The Carrier Segment (Carrier Segment) is an incompatible Carrier, and the Carrier Segment cannot be used independently, but can be used only as a part of the bandwidth of a certain backward compatible Carrier, so as to increase the transmission capability of the backward compatible Carrier. The sum of the bandwidth of the fragmented Carrier and the paired backward compatible Carrier does not exceed 110RBs (Carrier segments, If specific, area defined as the bandwidth extensions of a backward compatible Carrier (no large than 110RBs in total) and the bandwidth of the contract a mechanism to optimize the resource in the case of new transmission bandwidth in the backward compatible Carrier aggregation).
When a sliced carrier is configured, its characteristics are considered: after the slicing carrier is added, one PDCCH is still used for indicating the resources of the backward compatible carrier and the whole slicing carrier. The addition of the fragmented carrier brings the increase of the total number of PRBs (also called RBs), so that in the case of allocating the fragmented carrier to the UE, in the face of the increased PRBs, how the size of the RBGs is determined, and how the RBG numbering after the fragmented carrier is introduced is performed, the flexibility of the base station can be improved, the normal work of the original UE which is backward compatible with the carrier and an old version is not influenced, and the problem to be solved urgently is solved.
Disclosure of Invention
In view of the above, the present invention provides a method and an apparatus for determining a size and a number of an RBG after a fragmentation carrier is configured, so as to solve a problem of resource allocation confusion caused by non-uniform sizes of RBGs of UEs of different versions after the fragmentation carrier is configured.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the invention provides a method for determining the size and the number of an RBG (radial basis group) after a fragmentation carrier is configured, which comprises the following steps:
after an enhanced base station (eNB) configures a fragmentation carrier for a terminal (UE), the eNB and the UE determine that the size of a Resource Block Group (RBG) is equal to the size of the RBG corresponding to the sum of the fragmentation carrier and the bandwidth of a backward compatible carrier used by matching with the fragmentation carrier;
and according to the determined RBG size, dividing the RBs of the backward compatible carrier and the RBs of the slicing carrier into a whole or two parts, and numbering the divided RBGs of the backward compatible carrier and the divided RBGs of the slicing carrier.
The RBG size corresponding to the sum of the bandwidth of the slicing carrier and the bandwidth of the backward compatible carrier used by being paired with the slicing carrier is as follows:
when the sum of the bandwidths is less than or equal to 10, the corresponding RBG size is 1;
when the sum of the bandwidths is more than or equal to 11 and less than or equal to 26, the corresponding RBG size is 2;
when the sum of the bandwidths is greater than or equal to 27 and less than or equal to 63, the corresponding RBG size is 3;
and when the sum of the bandwidths is greater than or equal to 64 and less than or equal to 110, the corresponding RBG size is 4.
Taking the RBs of the backward compatible carrier and the RBs of the slicing carrier as a whole to divide RBGs, and the RBGs are as follows:
and regarding the RBs of the backward compatible carrier and the RBs of the slicing carrier as a whole, dividing the RBGs according to the determined RBG size, wherein each divided RBG only comprises the RBs of the backward compatible carrier, only comprises the RBs of the slicing carrier, or simultaneously comprises the RBs of the backward compatible carrier and the RBs of the slicing carrier.
When dividing the RBG, the method also comprises the following steps:
when the total number of RBs of the backward compatible carrier and the RBs of the slicing carrier is not an integer multiple of the determined RBG size, the number of RBs contained in one of the RBGs is allowed to be smaller than the determined RBG size.
Dividing RBG by regarding the RB of the backward compatible carrier and the RB of the slicing carrier as two parts:
and regarding the RBs of the backward compatible carrier and the RBs of the slicing carrier as two parts, and dividing the RBGs according to the determined RBG size respectively, wherein each divided RBG only comprises the RBs of the backward compatible carrier or only comprises the RBs of the slicing carrier.
When dividing the RBG, the method also comprises the following steps:
when the number of RBs of the backward compatible carrier and/or the number of RBs of the sliced carrier is not an integer multiple of the determined RBG size, allowing the number of RBs contained within one of the RBGs of the backward compatible carrier and/or one of the RBGs of the sliced carrier to be less than the RBG size.
Numbering the divided RBGs of the backward compatible carrier and the RBGs of the slicing carrier as follows:
numbering the RBGs of the backward compatible carrier from 0, and numbering the RBGs of the sliced carrier in sequence from low frequency to high frequency or from high frequency to low frequency from the maximum value of the RBG number of the backward compatible carrier according to the sequence of the frequency band of the sliced carrier from low frequency to high frequency or from high frequency to low frequency.
Numbering the divided RBGs of the backward compatible carrier and the RBGs of the slicing carrier as follows:
numbering the RBGs of the backward compatible carrier from 0, and numbering the RBGs of the sliced carrier sequentially from 0 according to the sequence of the frequency band of the sliced carrier from low frequency to high frequency or from high frequency to low frequency.
The invention also provides a device for determining the size and the number of the RBG after the configuration of the fragmentation carrier, which comprises the following steps: the RBG identification unit comprises an RBG determination unit, an RBG division unit and an RBG numbering unit; wherein:
the RBG determining unit is used for determining that the RBG size is equal to the RBG size corresponding to the sum of the bandwidth of the fragmentation carrier and the bandwidth of a backward compatible carrier used by being paired with the fragmentation carrier after the fragmentation carrier is configured;
the RBG dividing unit is used for dividing the RBG by regarding the RB of the backward compatible carrier and the RB of the slicing carrier as a whole or two parts according to the determined RBG size;
and the RBG numbering unit is used for numbering the divided RBGs of the backward compatible carrier and the RBGs of the slicing carrier.
The RBG determining unit is further configured to determine that the corresponding RBG size is 1 when the sum of the bandwidths is less than or equal to 10; when the sum of the bandwidths is more than or equal to 11 and less than or equal to 26, determining that the corresponding RBG size is 2; when the sum of the bandwidths is greater than or equal to 27 and less than or equal to 63, determining that the corresponding RBG size is 3; and when the sum of the bandwidths is greater than or equal to 64 and less than or equal to 110, determining that the corresponding RBG size is 4.
The RBG dividing unit is further configured to regard the RB of the backward compatible carrier and the RB of the sliced carrier as a whole, and divide the RBGs according to a determined RBG size, where each divided RBG includes only the RB of the backward compatible carrier, only the RB of the sliced carrier, or both the RB of the backward compatible carrier and the RB of the sliced carrier.
The RBG dividing unit is further configured to regard the RB of the backward compatible carrier and the RB of the sliced carrier as two parts, and divide the RBGs according to the determined sizes of the RBGs, where each divided RBG only includes the RB of the backward compatible carrier or only includes the RB of the sliced carrier.
The RBG numbering unit is further configured to number the RBGs of the backward compatible carrier starting from 0, and number the RBGs of the sliced carrier sequentially from a maximum value of the RBG numbers of the backward compatible carrier according to an order of a frequency band of the sliced carrier from a low frequency to a high frequency or from a high frequency to a low frequency.
The RBG numbering unit is further configured to number the RBGs of the backward compatible carrier starting from 0, and number the RBGs of the sliced carrier sequentially from 0 according to a sequence of a frequency band of the sliced carrier from a low frequency to a high frequency or from a high frequency to a low frequency.
According to the method and the device for determining the size and the number of the RBG after the fragmentation carrier is configured, after the eNB configures the fragmentation carrier for the new version UE, the size of the RBG is corresponding to the sum of the bandwidth of the RBG size fragmentation carrier and the bandwidth of a backward compatible carrier used by matching with the RBG size fragmentation carrier; and according to the determined RBG size, dividing the RBs of the backward compatible carrier and the RBs of the slicing carrier into a whole or two parts, and numbering the divided RBGs of the backward compatible carrier and the divided RBGs of the slicing carrier. The scheme of the invention realizes that the RBG size is flexibly determined by the bandwidth used by the UE for the UE (including the UE of an old version and the UE of a new version) which is not allocated with the use of the fragmented carrier, and ensures that the work of the backward compatible carrier and the scheduling rule of the base station are not influenced; for the UE which is allocated to use the fragmented carrier, the RBG size suitable for the UE can be flexibly determined according to the bandwidth size of the fragmented carrier, so that the base station can flexibly determine the RBG size and the number of the UE scheduled at this time according to the bandwidth condition used by the UE, and the scheduling flexibility of the base station is improved.
Drawings
FIG. 1 is a schematic flow chart illustrating a method for determining RBG size and serial number after a fragmentation carrier is configured according to the present invention;
fig. 2 is a schematic diagram illustrating determination of the RBG size and the number after a fragmentation carrier is configured according to an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating determination of the RBG size and the number after a second configuration of a fragmentation carrier according to a second embodiment of the present invention;
fig. 4 is a schematic diagram illustrating determination of the size and number of an RBG after a third configuration of a fragmented carrier according to an embodiment of the present invention;
fig. 5 is a first schematic diagram illustrating determination of the RBG size and the number after a fourth configuration of a fragmentation carrier according to a first embodiment of the present invention;
fig. 6 is a schematic diagram illustrating determination of the RBG size and the number after a fourth configuration of a fragmentation carrier according to a second embodiment of the present invention;
fig. 7 is a schematic structural diagram of a device for determining the size and number of an RBG after a slice carrier is configured according to the present invention.
Detailed Description
The method for determining the size and the number of the RBG after the configuration of the fragmented carrier, as shown in FIG. 1, includes the following steps:
step 101, after the eNB configures the fragmentation carrier for the UE, the eNB and the UE determine that the RBG size is equal to the RBG size corresponding to the sum of the fragmentation carrier and the bandwidth of the backward compatible carrier used in pairing with the fragmentation carrier.
The RBG size corresponding to the sum of the bandwidths is mainly determined according to table 1, namely:
when the sum of the bandwidths is less than or equal to 10, the corresponding RBG size is 1;
when the sum of the bandwidths is more than or equal to 11 and less than or equal to 26, the corresponding RBG size is 2;
when the sum of the bandwidths is greater than or equal to 27 and less than or equal to 63, the corresponding RBG size is 3;
when the sum of the bandwidths is greater than or equal to 64 and less than or equal to 110, the corresponding RBG size is 4.
And 102, dividing RBGs of the backward compatible carrier and RBs of the slicing carriers into a whole or two parts according to the determined RBG size, and numbering the divided RBGs of the backward compatible carrier and the divided RBGs of the slicing carriers.
When RBG division is performed on RBs of backward compatible carriers and RBs of slicing carriers included in a carrier bandwidth, the RBGs are divided into two conditions:
the first step is to regard the RB of the backward compatible carrier and the RB of the sliced carrier as a whole to perform RBG division, specifically:
and regarding the RBs of the backward compatible carrier and the RBs of the slicing carrier as a whole, dividing the RBGs according to the determined RBG size, wherein each divided RBG only comprises the RBs of the backward compatible carrier, only comprises the RBs of the slicing carrier, or simultaneously comprises the RBs of the backward compatible carrier and the RBs of the slicing carrier.
For such a division, there are cases as follows: when the total number of RBs of the backward compatible carrier and the RBs of the sliced carrier is not an integer multiple of the determined RBG size, the number of RBs contained in one of the RBGs is allowed to be smaller than the determined RBG size.
And secondly, dividing RBGs by regarding RBs of backward compatible carriers and RBs of slicing carriers as two parts, specifically:
and regarding the RBs of the backward compatible carrier and the RBs of the slicing carrier as two parts, respectively dividing the RBGs according to the determined RBG size, wherein each divided RBG only comprises the RBs of the backward compatible carrier or only comprises the RBs of the slicing carrier.
For such a division, there are cases as follows: when the number of RBs of the backward compatible carrier and/or the number of RBs of the sliced carrier is not an integer multiple of the determined RBG size, allowing the number of RBs contained within one of the RBGs of the backward compatible carrier and/or one of the RBGs of the sliced carrier to be less than the RBG size.
When the RBG numbering is carried out,
the first and second dividing manners may both adopt the following RBG numbering manners: the RBGs of the backward compatible carrier are numbered from 0, and from the maximum value of the RBG numbers of the backward compatible carrier, the RBGs of the sliced carrier are numbered in sequence from low frequency to high frequency or from high frequency to low frequency of the frequency band of the sliced carrier (as in the first, second, and fourth embodiments).
For the second division, the following RBG numbering scheme may also be adopted: the RBGs of the backward compatible carrier are numbered from 0, and the RBGs of the sliced carrier are numbered sequentially from 0 in the order from low frequency to high frequency or from high frequency to low frequency (as in the third embodiment).
The technical solution of the present invention will be described below by way of specific examples.
In the specific embodiment of the invention, the scenario of aggregation use of backward compatible carriers and fragmented carriers in the LTE-a system is mainly considered. Assuming that two component carriers are configured in the LTE-a system, the usage can be aggregated. The UE may be a new-version UE or an old-version UE.
Example one
In this embodiment, the new release UE aggregates and uses one backward compatible carrier of 5MHz (containing 25 RBs) and one fragmented carrier of 1.4MHz (containing 6 RBs).
Firstly, determining the RBG size:
as shown in fig. 2, UE1 only uses 5MHz backward compatible carrier, and determines the RBG size corresponding to UE1 as: the eNB configures a new carrier bandwidth of 25 (i.e., the number of RBs is 25) for the UE1 after using a backward compatible carrier of 5MHz, and as can be seen from table 1, the corresponding RBG size is 2;
UE2 uses a backward compatible carrier of 5MHz and a slicing carrier of 1.4MHz in an aggregation way, and the RBG size corresponding to UE2 is determined as follows: the eNB configures UE2 with a carrier bandwidth sum of 31 (i.e., number of RBs: 6+ 25: 31) after using 1.4MHz segment carrier and 5MHz backward compatible carrier, and as can be seen from table 1, the corresponding RBG size is 3.
The RBG size determining mode has no influence on the UE of the old version, and for the UE of the new version, if the fragmented carrier is used, signaling does not need to be added, so that the scheduling flexibility of the eNB is improved.
Numbering RBGs: and numbering according to the determined RBG size.
In this embodiment, the RBs included in the backward compatible carrier and the sliced carrier are taken as a whole, RBG division is performed according to the determined RBG size P (i.e., one RBG includes P RBs), and RBG numbering is performed. For example:
for UE1, the carrier bandwidth is 25, and the corresponding RBG size is 2, then RBs included in the carrier bandwidth can be divided into 13 RBGs, and the 13 RBGs are numbered sequentially, preferably, numbering can be started from 0 (0 to 12). It should be noted that the number of RBs included in the backward compatible carrier in this embodiment is not an integer multiple of the size of the RBG, so that the last RBG is allowed to include a smaller number of RBs than the size of the RBG, for example, as can be seen from fig. 2, the RBG numbered 12 of UE1 includes only 1 RB.
For the UE2, all RBs included in the backward compatible carrier and the segment carrier used by the UE are divided into RBGs and numbered. If the carrier bandwidth of UE2 is 31 and the corresponding RBG size is 3, the carrier bandwidth may be divided into 11 RBGs, and the 11 RBGs are numbered sequentially, preferably starting from 0. Wherein, the RBG number of the backward compatible carrier is from 0 to 8, and the RBGs of the sliced carrier are numbered from 8 to 10 from the maximum value of the RBG number of the backward compatible carrier, as can be seen from fig. 2, since UE2 uses both the backward compatible carrier and the sliced carrier, and the number of RBs included in the backward compatible carrier is not a multiple of the RBG size (3), the 8 th RBG corresponding to the adjacent position of the backward compatible carrier and the sliced carrier includes both RBs of the backward compatible carrier and RBs of the sliced carrier. It should be noted that, for an RBG of a sliced carrier, RBG numbering may be performed in the order from low frequency to high frequency, as shown in fig. 2; the RBG numbering may also be performed in order of high frequency to low frequency.
As shown in fig. 2, eNB schedules UE1 and UE2, and when RBG allocation is indicated, the working method of resource allocation type 0, 1, 2 in 3gpp release-10 is followed, with the difference that: since the number of RBGs of UE1 and UE2 is different, the number of resource allocation bits used is different. That is, for UE1 and UE2, although the same backward compatible carrier is used, the RBG numbers in the backward compatible carrier are different because UE2 configures and uses the fragmented carrier, so that eNB can flexibly determine the RBG size and number scheduled by the UE for the bandwidth situation used by the UE in the same subframe, thereby increasing the flexibility of base station scheduling.
Example two
The main difference between this embodiment and the first embodiment is that the UE aggregation uses the RBG partition when the backward compatible carrier and the fragmented carrier are used.
Specifically, in the first embodiment, all RBs included in a compatible carrier and a sliced carrier are taken as a whole to perform RBG division; in the embodiment, the RBs included in the backward compatible carrier and the slicing carrier are regarded as two parts to be respectively subjected to RBG division.
As shown in fig. 3, for UE2, RBs of the backward compatible carrier and RBs of the sliced carrier are respectively RBG-divided according to the determined RBG size (3). The numbering rules are as follows: the RBGs of the backward compatible carrier are numbered starting from 0, and the RBGs of the sliced carrier continue to be numbered from the maximum value of the RBG numbers of the backward compatible carrier.
It should be noted that, in the case of dividing the RBs included in the carrier bandwidth into two parts, i.e., a backward compatible carrier and a sliced carrier, if the number of RBs included in a certain part is not an integer multiple of the RBG size, the number of RBs included in the last RBG of the part is allowed to be smaller than the RBG size. In addition, for the RBGs of one sliced carrier, RBG numbering can be performed in the order from low frequency to high frequency, as shown in fig. 3; the RBG numbering may also be performed in order of high frequency to low frequency.
As shown in fig. 3, the RBs of the backward compatible carrier and the sliced carrier are respectively divided to obtain 11 RBGs, wherein the RBGs of the backward compatible carrier are numbered from 0 to 8, and the RBGs of the sliced carrier are numbered from the maximum value 8 of the RBG number of the backward compatible carrier to 9 to 10 in the order from low frequency to high frequency. Where the number of RBs of the backward compatible carrier part is not a multiple of 3, so the last RBG (numbered 8) of the backward compatible carrier contains only one RB.
The RBG size determination method and the RBG numbering method of this embodiment may maximize system benefits in some scenarios, for example, when an RBG size determined according to a carrier bandwidth obtained after using a backward compatible carrier and a sliced carrier is the same as an RBG size determined according to a carrier bandwidth of only the backward compatible carrier, it may be ensured that the RBG size and the RBG numbering in the backward compatible carrier of UE1 and UE2 are completely the same, in this case, the eNB may schedule only transmission data of UE2 in the backward compatible carrier, and use a DCI format that is the same as UE1, mainly the same number of bits for indicating resource allocation, avoid using a new DCI format or newly increasing the number of bits for indicating resource allocation, and save system resources.
EXAMPLE III
The manner of determining the size of the RBG in this embodiment is the same as that in the first embodiment, and the main difference is the manner of numbering the RBGs.
Wherein, the RBG coding method when UE1 only uses the backward compatible carrier is the same as the first embodiment, and is not described herein again. For the case that UE2 uses the backward compatible carrier and the slicing carrier, in this embodiment, RBs included in the backward compatible carrier and the slicing carrier are respectively RBG divided and numbered from 0.
As shown in fig. 4, for UE2, RBs (31) included in the carrier bandwidth are divided into two parts, namely, a backward compatible carrier and a slicing carrier, and the RBs in the two parts are respectively subjected to RBG division according to the determined RBG size (3), where the numbering rule is as follows: the RBGs of the backward compatible carrier are numbered starting from 0 and the RBGs of the sliced carrier are also numbered starting from 0.
It should be noted that, in the case of dividing the RBs included in the carrier bandwidth into two parts, i.e., a backward compatible carrier and a sliced carrier, if the number of RBs included in a certain part is not an integer multiple of the RBG size, the number of RBs included in the last RBG of the part is allowed to be smaller than the RBG size.
As shown in fig. 4, RBs of the backward compatible carrier and the sliced carrier are divided into 11 RBGs, wherein the RBGs of the backward compatible carrier are numbered 0 to 8 from 0, and the sliced carrier is numbered 0 to 1 from 0 in the order from low frequency to high frequency (or from high frequency to low frequency). The advantage of such numbering is that the eNB can schedule a certain UE independently within a fragmented carrier, which can reduce the number of bits indicating resource allocation. Where the number of RBs of the backward compatible carrier part is not a multiple of 3, so the last RBG (numbered 8) of the backward compatible carrier contains only one RB.
Or,
the RBGs of the backward compatible carrier are numbered starting from 0, and the RBGs of the sliced carrier are numbered starting from 0 in the order of low frequency to high frequency or high frequency to low frequency (as in the third embodiment).
The above-mentioned dividing manner and numbering manner are both examples of configuring one fragmented carrier, and when a plurality of fragmented carriers are configured and the plurality of fragmented carriers are discontinuous, the dividing manner adopts the second type, and particularly, the encoding rule is as follows:
the RBGs of the backward compatible carrier are numbered from 0, one or more slicing carriers of the high-frequency part are numbered continuously according to the sequence from low frequency to high frequency or from high frequency to low frequency from the maximum value of the RBG number of the backward compatible carrier, and then one or more slicing carriers of the low-frequency part are numbered continuously according to the sequence from low frequency to high frequency or from high frequency to low frequency; or, continue numbering one or more sliced carriers of the low-frequency part according to the sequence from low frequency to high frequency or from high frequency to low frequency, and continue numbering one or more sliced carriers of the high-frequency part according to the sequence from low frequency to high frequency or from high frequency to low frequency (as in the fourth embodiment);
or,
numbering RBGs of backward compatible carriers from 0, numbering one or more sliced carriers of a high-frequency part from 0 according to a sequence from low frequency to high frequency or from high frequency to low frequency, and then continuously numbering one or more sliced carriers of a low-frequency part according to a sequence from low frequency to high frequency or from high frequency to low frequency; or, one or more slicing carriers of the low frequency part are numbered from 0 in the order from low frequency to high frequency or from high frequency to low frequency, and then one or more slicing carriers of the high frequency part are numbered continuously in the order from low frequency to high frequency or from high frequency to low frequency (as in the fourth embodiment).
Example four
In this embodiment, the new version UE aggregates and uses one backward compatible carrier of 10MHz (including 50 RBs) and two slicing carriers of 1.4 MHz; wherein the two sliced carriers are located at two sides of the backward compatible carrier, respectively, as shown in fig. 5. In this embodiment, the RBG size determination method is the same as that in the first embodiment, and the main difference is how the RBG number is performed when there are multiple fragmented carriers in the system.
Wherein, the RBG coding method when UE1 only uses the backward compatible carrier is the same as the first embodiment, and is not described herein again.
When a plurality of fragmented carriers exist in the system, the RBG numbering can be carried out in the following way: the RBGs of the backward compatible carrier are numbered from 0; from the maximum RBG number of the backward compatible carrier, continuously numbering the sliced carrier of the low-frequency part according to the sequence from low frequency to high frequency or from high frequency to low frequency, and then continuously numbering the sliced carrier of the high-frequency part according to the sequence from low frequency to high frequency or from high frequency to low frequency; or, the slicing carriers of the high frequency part are numbered continuously according to the sequence from low frequency to high frequency or from high frequency to low frequency, and then the slicing carriers of the low frequency part are numbered continuously according to the sequence from low frequency to high frequency or from high frequency to low frequency.
As shown in fig. 5, for UE2, RBs (62) included in the carrier bandwidth are divided into two parts, i.e., a backward compatible carrier and a sliced carrier, and the RBs in the two parts are respectively RBG-divided according to the determined RBG size (3).
The numbering rules are as follows: the RBGs of the backward compatible carrier are numbered from 0 to 16, the RBGs of the backward compatible carrier are numbered from 16 to 16, the RBGs of the low frequency part are numbered from 17 to 18 according to the sequence from low frequency to high frequency (or from high frequency to low frequency) first, and the RBGs of the high frequency part are numbered from 19 to 20 according to the sequence from low frequency to high frequency (or from high frequency to low frequency) second, as shown in FIG. 5.
Certainly, the number of the segment carrier 2 of the high frequency part can be continuously numbered first, and then the number of the segment carrier 1 of the low frequency part can be continuously numbered;
the following numbering rules may also be employed: the RBGs of the backward compatible carrier are numbered from 0; firstly, numbering the sliced carrier waves of the low-frequency part from 0 according to the sequence from low frequency to high frequency or from high frequency to low frequency, and then continuously numbering the sliced carrier waves of the high-frequency part according to the sequence from low frequency to high frequency or from high frequency to low frequency; or, numbering one or more slicing carriers of the high-frequency part from 0 according to the sequence from low frequency to high frequency or from high frequency to low frequency, and then numbering one or more slicing carriers of the low-frequency part continuously according to the sequence from low frequency to high frequency or from high frequency to low frequency.
As shown in fig. 6, the RBGs of backward compatible carriers are numbered 0 to 16 from 0, the chip carriers 1 of the low frequency part are numbered 0 to 1 from 0 in the order from low frequency to high frequency (or from high frequency to low frequency), and the chip carriers 2 of the high frequency part are numbered 2 to 3 from low frequency to high frequency (or from high frequency to low frequency).
Of course, the number of the segment carrier 2 in the high frequency part may be started from 0, and then the number of the segment carrier 1 in the low frequency part may be continued.
In order to implement the method, as shown in fig. 7, the present invention provides an apparatus for determining a size and a number of an RBG after configuring a sliced carrier, including: the RBG identification unit comprises an RBG determination unit, an RBG division unit and an RBG numbering unit; wherein:
the RBG determining unit is used for determining that the size of the RBG is equal to the size of the RBG corresponding to the sum of the bandwidth of the fragmentation carrier and the bandwidth of a backward compatible carrier used by being paired with the fragmentation carrier after the fragmentation carrier is configured;
the RBG dividing unit is used for dividing RBGs by regarding RBs of backward compatible carriers and RBs of slicing carriers as a whole or two parts according to the determined RBGs;
and the RBG numbering unit is used for numbering the divided RBGs of the backward compatible carrier and the RBGs of the slicing carrier.
The RBG determining unit is further used for determining that the corresponding RBG size is 1 when the sum of the bandwidths is less than or equal to 10; when the sum of the bandwidths is more than or equal to 11 and less than or equal to 26, determining the corresponding RBG size to be 2; when the sum of the bandwidths is greater than or equal to 27 and less than or equal to 63, determining that the corresponding RBG size is 3; when the sum of the bandwidths is greater than or equal to 64 and less than or equal to 110, the corresponding RBG size is determined to be 4.
And the RBG dividing unit is further used for regarding the RBs of the backward compatible carrier and the RBs of the slicing carrier as a whole, dividing the RBGs according to the determined RBG size, wherein each divided RBG only comprises the RBs of the backward compatible carrier, only comprises the RBs of the slicing carrier, or simultaneously comprises the RBs of the backward compatible carrier and the RBs of the slicing carrier.
And the RBG dividing unit is further used for regarding the RBs of the backward compatible carrier and the RBs of the slicing carrier as two parts, dividing the RBGs according to the determined RBG size respectively, wherein each divided RBG only comprises the RBs of the backward compatible carrier or only comprises the RBs of the slicing carrier.
And the RBG numbering unit is further used for numbering the RBGs of the backward compatible carrier from 0, and numbering the RBGs of the slicing carrier sequentially from the maximum value of the RBG numbers of the backward compatible carrier according to the sequence of the frequency band of the slicing carrier from low frequency to high frequency or from high frequency to low frequency.
And the RBG numbering unit is further used for numbering the RBGs of the backward compatible carrier from 0, and numbering the RBGs of the sliced carrier sequentially from 0 to low frequency or from high frequency to low frequency according to the sequence of the frequency band of the sliced carrier from low frequency to high frequency.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims (9)

1. A method for determining RBG size and number after configuration of a sliced carrier, the method comprising:
after an enhanced base station (eNB) configures a fragmentation carrier for a terminal (UE), the eNB and the UE determine that the size of a Resource Block Group (RBG) is equal to the size of the RBG corresponding to the sum of the fragmentation carrier and the bandwidth of a backward compatible carrier used by matching with the fragmentation carrier;
according to the determined RBG size, the RB of the backward compatible carrier and the RB of the slicing carrier are regarded as a whole to be divided into RBGs, and the divided RBGs of the backward compatible carrier and the divided RBGs of the slicing carrier are numbered;
wherein the dividing of the RBs of the backward compatible carrier and the RBs of the sliced carrier from the RBs to the RBGs is performed as a whole by:
regarding the RBs of the backward compatible carrier and the RBs of the slicing carrier as a whole, and dividing the RBs into RBGs according to the determined RBG size, wherein the divided RBGs comprise: an RBG that contains both RBs of the backward compatible carrier and RBs of the sliced carrier;
and the bandwidth corresponding to the backward compatible carrier and the bandwidth corresponding to the slicing carrier belong to the same carrier.
2. The method of claim 1, wherein the RBG size corresponding to the sum of bandwidths of the sliced carrier and a backward compatible carrier used in pair with the sliced carrier is:
when the sum of the bandwidths is less than or equal to 10, the corresponding RBG size is 1;
when the sum of the bandwidths is more than or equal to 11 and less than or equal to 26, the corresponding RBG size is 2;
when the sum of the bandwidths is greater than or equal to 27 and less than or equal to 63, the corresponding RBG size is 3;
and when the sum of the bandwidths is greater than or equal to 64 and less than or equal to 110, the corresponding RBG size is 4.
3. The method of claim 1, wherein the RBs of the backward compatible carrier and the RBs of the sliced carrier are considered as a whole, and the RBs-to-RBGs are divided according to the determined RBG size, and the divided RBGs further include: RBGs that contain only RBs of backward compatible carriers and/or RBGs that contain only RBs of tiled carriers.
4. The method for determining the size and number of an RBG after configuring a sliced carrier as claimed in claim 1, wherein the method further comprises, when performing RBG partitioning:
when the total number of RBs of the backward compatible carrier and the RBs of the slicing carrier is not an integer multiple of the determined RBG size, the number of RBs contained in one of the RBGs is allowed to be smaller than the determined RBG size.
5. The method for determining the size and number of the RBGs after configuring the sliced carrier according to claim 1 or 4, wherein numbering the RBGs of the backward compatible carrier and the RBGs of the sliced carrier after partitioning is as follows:
numbering the RBGs of the backward compatible carrier from 0, and numbering the RBGs of the sliced carrier in sequence from low frequency to high frequency or from high frequency to low frequency from the maximum value of the RBG number of the backward compatible carrier according to the sequence of the frequency band of the sliced carrier from low frequency to high frequency or from high frequency to low frequency.
6. An apparatus for determining RBG size and number after configuration of a sliced carrier, comprising: the RBG identification unit comprises an RBG determination unit, an RBG division unit and an RBG numbering unit; wherein:
the RBG determining unit is used for determining that the RBG size is equal to the RBG size corresponding to the sum of the bandwidth of the fragmentation carrier and the bandwidth of a backward compatible carrier used by being paired with the fragmentation carrier after the fragmentation carrier is configured;
the RBG dividing unit is used for dividing the RB of the backward compatible carrier and the RB of the slicing carrier into a whole according to the determined RBG size;
the RBG numbering unit is used for numbering the divided RBGs of the backward compatible carrier and the RBGs of the slicing carrier;
the RBG dividing unit is further configured to regard the RB of the backward compatible carrier and the RB of the sliced carrier as a whole, and divide the RB into RBGs according to a determined RBG size, where the divided RBGs include: an RBG that contains both RBs of the backward compatible carrier and RBs of the sliced carrier;
and the bandwidth corresponding to the backward compatible carrier and the bandwidth corresponding to the slicing carrier belong to the same carrier.
7. The apparatus of claim 6, wherein the RBG determining unit is further configured to determine that the corresponding RBG size is 1 when the sum of the bandwidths is less than or equal to 10; when the sum of the bandwidths is more than or equal to 11 and less than or equal to 26, determining that the corresponding RBG size is 2; when the sum of the bandwidths is greater than or equal to 27 and less than or equal to 63, determining that the corresponding RBG size is 3; and when the sum of the bandwidths is greater than or equal to 64 and less than or equal to 110, determining that the corresponding RBG size is 4.
8. The apparatus as claimed in claim 6, wherein the RBG partitioning unit is further configured to consider the RB of the backward compatible carrier and the RB of the sliced carrier as a whole, and partition the RB into RBGs according to the determined RBG size, and the partitioned RBGs further include: RBGs that contain only RBs of backward compatible carriers and/or RBGs that contain only RBs of tiled carriers.
9. The apparatus as claimed in claim 6, wherein the RBG numbering unit is further configured to number RBGs of the backward compatible carrier starting from 0, and number the RBGs of the sliced carrier sequentially from a low frequency to a high frequency or from a high frequency to a low frequency of a frequency band of the sliced carrier from a maximum value of the RBG number of the backward compatible carrier.
CN201110258014.XA 2011-09-01 2011-09-01 It is a kind of configuration fragment carrier wave after RBG sizes and number determination method and apparatus Active CN102970709B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201110258014.XA CN102970709B (en) 2011-09-01 2011-09-01 It is a kind of configuration fragment carrier wave after RBG sizes and number determination method and apparatus
PCT/CN2012/077919 WO2013029419A1 (en) 2011-09-01 2012-06-29 Determination method and device for size and number of rbg allocated with fragment carrier

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201110258014.XA CN102970709B (en) 2011-09-01 2011-09-01 It is a kind of configuration fragment carrier wave after RBG sizes and number determination method and apparatus

Publications (2)

Publication Number Publication Date
CN102970709A CN102970709A (en) 2013-03-13
CN102970709B true CN102970709B (en) 2018-08-03

Family

ID=47755286

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201110258014.XA Active CN102970709B (en) 2011-09-01 2011-09-01 It is a kind of configuration fragment carrier wave after RBG sizes and number determination method and apparatus

Country Status (2)

Country Link
CN (1) CN102970709B (en)
WO (1) WO2013029419A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105992351B (en) * 2015-01-30 2021-05-11 中兴通讯股份有限公司 Resource allocation method and device and information feedback method and device
ES2906677T3 (en) * 2016-08-11 2022-04-19 Samsung Electronics Co Ltd Method and apparatus for data transmission in next generation cellular networks
US10863505B2 (en) 2016-08-26 2020-12-08 Qualcomm Incorporated Data channel resource allocation
CN109548149B (en) 2017-09-21 2020-11-10 电信科学技术研究院 RBG (role-based group) dividing method and user terminal
CN109714137B (en) * 2017-10-25 2021-08-06 普天信息技术有限公司 Resource allocation processing method and device

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036387A (en) * 2009-09-30 2011-04-27 中兴通讯股份有限公司 Method for indicating wireless channel resource allocation, base station, decoding method and terminal
WO2011084822A1 (en) * 2009-12-21 2011-07-14 Qualcomm Incorporated Method and apparatus for resource allocation with carrier extension

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2359518A1 (en) * 2008-09-25 2011-08-24 Nokia Corporation Advanced resource allocation signaling
JP5422211B2 (en) * 2009-01-21 2014-02-19 株式会社日立製作所 Wireless communication system, terminal and base station
WO2011016252A1 (en) * 2009-08-07 2011-02-10 パナソニック株式会社 Radio base station and radio communication method
JP5404462B2 (en) * 2010-02-12 2014-01-29 シャープ株式会社 Base station apparatus, mobile station apparatus and integrated circuit

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102036387A (en) * 2009-09-30 2011-04-27 中兴通讯股份有限公司 Method for indicating wireless channel resource allocation, base station, decoding method and terminal
WO2011084822A1 (en) * 2009-12-21 2011-07-14 Qualcomm Incorporated Method and apparatus for resource allocation with carrier extension

Also Published As

Publication number Publication date
WO2013029419A1 (en) 2013-03-07
CN102970709A (en) 2013-03-13

Similar Documents

Publication Publication Date Title
CN109565861B (en) Method and apparatus for data transmission in next generation cellular networks
CN110771083B (en) Method, apparatus and system for transmitting or receiving control channel and data channel in wireless communication system
CN105979597B (en) Communication resource allocation method, allocation device, base station and terminal
CN110999194B (en) Communication system
CN106455081B (en) Resource allocation method and resource allocation device
CN106851744B (en) Method and apparatus for wireless communication
EP2517516B1 (en) Method and apparatus for resource allocation with carrier extension
CN107925999B (en) Resource allocation method and device
CN107210892B (en) Radio node, wireless device and method for configuring wireless device in radio node
CN107294897B (en) Downlink information sending and receiving method and device
WO2016161917A1 (en) Method and device for implementing resource allocation
EP2485549A1 (en) Method and apparatus for configuring downlink scheduling information
CN101883434B (en) A kind of channel resource allocation method and base station
CN110769508B (en) Signal transmission method, device, terminal equipment, network equipment and system
CN108401292B (en) Control information transmission method, control information receiving device, base station and terminal
WO2019052455A1 (en) Data channel parameter configuration method and device
WO2011095069A1 (en) Method, device and system for indicating resource allocation mode
WO2017132967A1 (en) Data sending method, data receiving method, user equipment and base station
CN108076518B (en) Uplink data transmission method and device
CN109906654B (en) Wireless resource allocation system and method
CN102970709B (en) It is a kind of configuration fragment carrier wave after RBG sizes and number determination method and apparatus
WO2013082784A1 (en) Resource allocation by component carrier sub-bands
KR20120080983A (en) Methods for transmitting or processing control information in telecommunication system and apparatus using the methods
KR20170107019A (en) Resource allocation method, base station and user equipment
CN108029117B9 (en) Method and apparatus for resource allocation

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant