Abstract:
A resource allocation method and apparatus for a relay node under the condition of carrier aggregation are disclosed in the embodiments of the present invention. By applying the technical solution of the embodiments of the present invention, a relay node can determine information of cells, which are currently available for allocation, of a Un interface, and report the information to an eNB, so that the eNB can allocate corresponding Un interface resources for the relay node according to the information. Thus the eNB side can accurately obtain the information of the cell resources, which are available for allocation and currently correspond to the relay node, of the Un interface. Thus the problem is solved that the relay node cannot properly work under the condition of the carrier aggregation caused by the mismatching between the Un interface resources directly allocated by the eNB and the relay node in the prior art.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application is a continuation of PCT/CN2011/080772 filed on Oct. 14, 2011, which claims priority to Chinese Patent Application No. 201010515839.0 entitled “Resource Allocation Method and Apparatus for Relay Node under the Condition of Carrier Aggregation” filed in the Patent Office of the People&#39;s Republic of China on Oct. 15, 2010, the disclosures of which are incorporated by reference in their entireties. 
     
    
     FIELD OF THE INVENTION 
       [0002]    The present invention relates to the field of communication technology, in particular to the resource allocation method and apparatus for relay node under the condition of carrier aggregation. 
       BACKGROUND OF THE PRESENT INVENTION 
       [0003]    In LTE (Long term Evolution) and previous wireless communication system, a cell only has a (or a pair of) carrier generally, and a UE (User Equipment) can only receive and send data in a cell (on carrier) at the same time. 
         [0004]      FIG. 1  shows the schematic diagram of carrier bandwidth in current LTE system. In LTE system, the maximum bandwidth of carrier is 20 MHz. 
         [0005]    With the development of communication technology, LTE-A (Long Term Evolution Advanced) system has witnessed great improvement of peak rate compared with LTE, and is required to reach 1 Gbps downlink and 500 Mbps uplink. Obviously, the transmission bandwidth of 20 MHz has been unable to meet such demand. Besides higher requirements on transmission rate, LTE-A system needs better compatibility with LTE system. In consideration of the improved peak rate, compatibility with LTE system and full use of spectrum resource, CA (Carrier Aggregation) technique is introduced in LTE-A system, viz. the UE can aggregate a plurality of component carriers at the same time and transmit data on the carrier at the same time so as to improve data transmission rate. 
         [0006]    To ensure that the UE of LTE system can work under each carrier aggregated, each carrier is set no more than 20 MHz. Each component carrier in LTE-A system is compatible with LTE Rel-8. 
         [0007]      FIG. 2  shows the schematic diagram of CA technique in current LTE-A system. 
         [0008]    In LTE-A system shown in  FIG. 2 , the UE can aggregate 4 carriers. Data can be transmitted to the UE on 4 carriers at network side at the same time. 
         [0009]    Furthermore,  FIG. 3  shows the schematic diagram for network structure of current system with RN (Relay Node) introduced; wherein, an eNB (evolved NodeB) is connected to a core network (CN) through a wire interface, the RN is connected to a DeNB (Donor eNB) through a wireless interface, a R-UE is connected to the RN through the wireless interface (Uu interface). 
         [0010]    In prior art, the RN can be divided into the following types according to type of a relay data package: 
         [0011]    L1 RN (Layer 1 Relay Node); 
         [0012]    L2 RN (Layer 2 Relay Node); 
         [0013]    L3 RN (Layer 3 Relay Node). 
         [0014]    Wherein, the L3 RN can be divided into the following two kinds according to that whether it is necessary to divide carrier resource on time domain: 
         [0015]    The RN requiring resource division; 
         [0016]    The RN not requiring resource division; 
         [0017]    It should be noted that the RN Type mentioned in follow-up description of embodiment of the present invention is namely the RN requiring or not requiring resource division. 
         [0018]    The RN requiring resource division cannot receive and send at Uu interface and Un interface at the same time, or self-interference will be caused. To avoid self-interference, a solution is to create ‘gaps’ in a downlink access transmission time of an R-UE of the Uu interface. The gap can be used for a DL BH Link (Downlink Backhaul Link), viz. downlink BH subframe. ‘Gaps’ configuration can be realized through a MBSFN (Multicast Broadcast Single Frequency Network) subframe. 
         [0019]      FIG. 4  shows the schematic diagram for relay link downlink transmission at Un interface by using MBSFN subframe in prior art. In these ‘gaps’, downlink transmission will be performed between the DeNB and the RN rather than between the RN and the R-UE. 
         [0020]    Furthermore, RN starting process of the current network with RN introduced is divided into the following two phase: 
         [0021]    Phase I: the RN is accessed to the network as a UE. The specific process flow is: 
         [0022]    The RN is attached to network in the same manner as UE. The RN downloads initial configuration information from RN OAM, including a Donor Cell list allowable for connection, and then is deattached. 
         [0023]    Phase II: accessed to network as the RN. The specific process flow is: 
         [0024]    First, the RN selects the Donor cell: select a Donor cell from the Donor cell list provided in Phase I. 
         [0025]    Then select a MME for the RN: the RN informs the DeNB the identity of the RN through a RRC signaling during attachment. The DeNB selects a MME supporting the RN for the RN based on the information; 
         [0026]    Select a GW for the RN: the MME selects the DeNB as a P/S-GW of the RN after a CN informs the MME that the access node is RN; 
         [0027]    Corresponding S1 and X2 interfaces are recommended between the RN and the DeNB: the RN launches the process of establishing S1 and X2 on a bear built by the DeNB. 
         [0028]    In the prior technical solution, L3 RN type is determined with the methods as below: 
         [0029]    If the application of CA for the Un interface is not taken into account in R10 edition of 3GPP LTE-A specification, RN type is determined by RN realization in a possible manner as below: 
         [0030]    The RN acquires the cell supported by a RN Uu interface from a RN OAM; 
         [0031]    The RN determines the cell used by the Un interface according to the donor cell accessed; 
         [0032]    The RN determines the RN type according to the cell supported by the Uu and Un interface and software and hardware capacity of the RN (whether resource division is required); 
         [0033]    The RN indicates type of the RN to the DeNB through a 1 bit indication. 
         [0034]    In the prior technical solution, RN type can be indicated in two manners as below. The specific manner has not been decided. 
         [0035]    Alt1: carried in a RRC connection complete message; 
         [0036]    Alt2: define independent RN type indication message; 
         [0037]    During implementation of the embodiments of the present invention, the applicant finds that the following problems at least exist in the available technology: 
         [0038]    If the CA is not taken into account and both Uu interface and Un interface only support a cell, CC/cell allocation of Un and Uu interface will not exist. The DeNB can work normally after determining whether it is necessary to configure the BH subframe according to the RN type after acquiring the RN type. 
         [0039]    If the CA is considered, the problem will be complex. The cell that can be accessed to some RNs in Un interface may be not accessed owing to limit of the RN type. For example: 
         [0040]    The RN accesses a DeNB1 for a RACH on cell a in Phase II for starting the RN. 
         [0041]    According to the cell list downloaded from the RN OAM in Phase I, the cell that can be used by the RN under the DeNB1 is cell a and cell b; meanwhile, the cell list of the Uu interface downloaded by the RN from the RN OAM comprises cell a, cell b and cell c. Thus, if the RN type reported by the RN to the DeNB is “Not requiring resource division”, the DeNB cannot work normally. The main reasons are as follows: 
         [0042]    (1) The DeNB does not know whether the RN supports other cells besides cell a, so the DeNB cannot realize CA operation for the RN; 
         [0043]    (2) The DeNB does not know which cells may be used by the RN Uu interface and whether resource division is required when these cells are combined with the cell of Un interface; 
         [0044]    In conclusion, to ensure that the system combining the CA and the RN can work normally, it is necessary to solve the problem; however, such technical solution has not been provided in prior art. 
       SUMMARY OF THE INVENTION 
       [0045]    The embodiments of the present invention provide a resource allocation method and apparatus for relay node under the condition of carrier aggregation. Resource of configurable cell of Un interface is reported to an eNB through a RRC signalling, which solves the problem that the CA and RN combining system cannot work normally according to the prior mechanism. 
         [0046]    To achieve the purpose, the embodiments of the present invention provide a resource allocation method for relay node under the condition of carrier aggregation on one hand, comprising: 
         [0047]    Relay node acquires information of available cell of Un interface; 
         [0048]    The relay node determines its relay node type according to information of available cell of the Un interface; 
         [0049]    The relay node determines information of the current cell available for allocation of Un interface according to the information of available cell of Un interface and relay node type; 
         [0050]    The relay node sends the determined information of the current cell available for allocation of Un interface to an eNB that the relay node is affiliated to, in order to make the eNB can allocate Un interface resource for the relay node according to information of the current cell available for allocation of Un interface. 
         [0051]    On the other hand, the embodiments of the present invention provide a relay node, which comprises: 
         [0052]    Acquisition module, is used for acquiring information of available cell of Un interface; 
         [0053]    Type determination module, is used for determining relay node type according to the information of the available cell of Un interface acquired by the acquisition module; 
         [0054]    Information determination module, is used for determining information of the cell available for allocation of Un interface of the relay node according to the information of the available cell of Un interface acquired by the acquisition module and relay node type determined by the type determination module; 
         [0055]    Sending module, is used for sending the information of the current cell available for allocation of the Un interface determined by the information determination module to the eNB that the relay node is affilicated to in order to make the eNB can allocate Un interface resource for the relay node according to information of the current cell available for allocation of Un interface. 
         [0056]    On the other hand, the embodiments of the present invention provide a resource allocation method for relay node under the condition of carrier aggregation, which comprises: 
         [0057]    The eNB receives information of the current cell available for allocation of the Un interface sent by the relay node; 
         [0058]    The eNB allocates resource of Un interface for the relay node according to the information of the current cell available for allocation of the Un interface. 
         [0059]    Besides, the embodiments of the present invention also provide an eNB, including: 
         [0060]    Receiving module, is used for receiving information of the current cell available for allocation of Un interface sent by the relay node; 
         [0061]    Allocation module, is used for allocating resource of Un interface for the delay node according to information of the current cell available for allocation of the Un interface received by the receiving module. 
         [0062]    Compared with available art, the embodiments of the present invention have the following advantages: 
         [0063]    Upon application of the technical solution for embodiments of the present invention, the relay node can determine information of the current cell available for allocation of the Un interface and report the information to the eNB so that the eNB can allocate corresponding Un interface resource for the relay node and further the eNB can accurately acquire resource information of the current cell available for allocation of the Un interface corresponding to the relay node, which solves the problem that the relay node cannot work normally under condition of carrier aggregation caused by mismatching between the Un interface resource directly allocated by the eNB and the relay node in prior art. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0064]    To further explain the technical solution of the embodiments of the present invention or available technology, the drawings required for description of the embodiments of the present invention or of available technology will be briefly introduced below. Obviously, the following described drawings only refer to some embodiments of the present invention. Technical personnel of the field can obtain other drawings according to these drawings without contributing creative work. 
           [0065]      FIG. 1  is a schematic diagram for carrier allocation of LTE cell in prior art; 
           [0066]      FIG. 2  is a schematic diagram for CA technology in prior art; 
           [0067]      FIG. 3  is a structural diagram for LTE-A network in prior art; 
           [0068]      FIG. 4  is a schematic diagram for relay link downlink transmission of Un interface by utilizing MBSFN subframe in prior art; 
           [0069]      FIG. 5  is a flow diagram for resource allocation method of relay node under the condition of carrier aggregation put forward in embodiments of the present invention; 
           [0070]      FIG. 6  is a flow diagram for resource allocation method of relay node under specific application scene at eNB side put forward by embodiments of the present invention; 
           [0071]      FIG. 7  is a structural diagram for relay node put forward by embodiments of the present invention; 
           [0072]      FIG. 8  is a structural diagram for eNB put forward by embodiments of the present invention. 
       
    
    
     DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS 
       [0073]    Then we will combine the attached drawings in the present invention to clearly and fully describe the technical proposals therein below. Obviously, the embodiments described are only a part of the embodiments of the present invention instead of the whole. Based on the embodiments of the present invention, all other embodiments acquired by ordinary technicians of this field on the premise of paying no creative work are within the protection of the present invention. 
         [0074]    As described in background technology, the RN is introduced into the LTE-A to improve the system throughput and increase network coverage and the CA is brought in for the purpose of improving peak rate. The embodiments of the present invention offer a method for determining carrier/cell source of Uu interface and Un interface in the system with combined CA and RN. 
         [0075]      FIG. 5  shows a flow diagram for resource allocation method for relay node under the condition of carrier aggregation put forward in embodiments of the present invention, which specifically comprises the following steps: 
         [0076]    Step S 501 , the relay node acquires information of available cell of the Un interface. 
         [0077]    In practical application, the step is realized through the following processes: 
         [0078]    The relay node determines which cells belonging to the eNB that the relay node is affiliated to according to the cell list information downloaded from OAM of the relay node. When a cell and the cell that the relay node is accessed to are affiliated to the same eNB, the relay node determines the cell as the available cell of its Un interface. 
         [0079]    Furthermore, realization of the step comprises the processing of the information that the relay node acquires from the available cell of the Uu interface. The specific processing is as below: 
         [0080]    The relay node acquires information of the available cell of its Uu interface according to the cell list information of Uu interface downloaded from the OAM of the relay node. 
         [0081]    Step S 502 , the relay node determines its relay node type according to the information of the available cell of the Un interface. 
         [0082]    Based on description in step S 501 , when information of the available cell of the Uu interface is acquired in step S 501 , the specific processing in this step is as below: 
         [0083]    The relay node determines its relay node type according to the information of the available cell of the Un interface, the information of the available cell of the Uu interface and its own software/hardware capacity information. 
         [0084]    According the conditions, the relay node determined in this step can be divided into the following types in specific application scene: 
         [0085]    Case I: when the software/hardware capacity information of the relay node only supports resource division, the relay node determines its relay node type as “Requiring resource division”. 
         [0086]    Case II: when the software/hardware capacity information of the relay node only supports not requiring resource division, the relay node determines its relay node type as “Not requiring resource division”. 
         [0087]    Case III: when the software/hardware capacity information of the relay node supports the both, the relay node type can be further divided into the following three conditions according to information of the available cell of the Un interface and information of the available cell of the Uu interface: 
         [0088]    (1) When both the cells corresponding to information of the available cell of the Un interface and information of the available cell of the Uu interface cannot meet the requirement of not requiring resource division, the relay node determines its relay node type as “Requiring resource division”. 
         [0089]    (2) When a part of the cells corresponding to information of the available cell of the Un interface and information of the available cell of the Uu interface meet the requirement of not requiring resource division, the relay node determines its relay node type as “Requiring resource division” or “Not requiring resource division” based on its demand. 
         [0090]    (3) When both the cells corresponding to information of the available cell of the Un interface and information of the available cell of the Uu interface meet the requirement of not requiring resource division, the relay node determines its relay node type as “Not requiring resource division”. 
         [0091]    Step S 503 , the relay node determines information of the current cell available for allocation of the Un interface according to information of the available cell of the Un interface and the relay node type. 
         [0092]    It should be noted that after determining the relay node type in step S 502 , the relay node can also determine information of the current cell available for allocation of its Uu interface according to the relay node type to avoid the existence of resource that cannot be allocated in information of the available cell of the Uu interface acquired in step S 501 . Information of the current cell available for allocation of the Uu interface is determined mainly based on the relay node type. 
         [0093]    In addition, it should be noted that the sequence for determining information of the current cell available for allocation of the Uu interface and information of the current cell available for allocation of the Un interface can be adjusted mutually and the preferential determination of information will not affect the protection scope of the present invention. 
         [0094]    In step S 504 , the relay node sends the determined information of the current cell available for allocation of the Un interface to the eNB that the relay node is affiliated to, in order to make the eNB can allocate Un interface resource for the relay node according to the information of the current cell available for allocation of the Un interface. 
         [0095]    In practical application, the specific processing in this step is as below: 
         [0096]    The relay node reports the information of the current cell available for allocation of the Un interface to the eNB that the relay node is affiliated to through RRC message; 
         [0097]    The eNB allocates Un interface resource for the relay node according to information of the current cell available for allocation of the Un interface and the current transmission demand. 
         [0098]    It should be noted that in practical application, when the relay node reports the information of the current cell available for allocation of the Un interface to the eNB that the relay node is affiliated to through RRC message, the RRC message can also carry the relay node relay node type. 
         [0099]    Certainly, the relay node type can be sent to the eNB through other messages. 
         [0100]    The description shows the realization flow of technical solution put forward in embodiments of the present invention at the relay node side. Correspondingly, the eNB allocates Un interface resource directly according to information reported by the relay node at eNB side. It will not be repeated hereby. 
         [0101]    Compared with available technology, the embodiments of the present invention have the following advantages: 
         [0102]    Upon application of the technical solution for embodiments of the present invention, the relay node can determine information of the current cell available for allocation of the Un interface and report the information to the eNB so that the eNB can allocate corresponding Un interface resource for the relay node, and the eNB can accurately acquire resource information of the current cell available for allocation of the Un interface corresponding to the relay node, which solves the problem that the relay node cannot work normally under condition of carrier aggregation caused by mismatching between the Un interface resource directly allocated by the eNB and the relay node in prior art. 
         [0103]    The technical solution put forward by the embodiments of the present invention will be explained in combination with actual implementation site. 
         [0104]    The embodiments of the present invention put forward a method for determining resource allocation of configurable carrier/cell of Uu interface and Un interface by RN in the system combining CA and RN, viz. the RN determines resource of configurable cell of RN Uu/Un interface according to RN type and then reports resource of configurable cell of the Un interface to DeNB through RRC signalling. 
         [0105]    To facilitate the follow-up description, meanings of the terms below in follow-up embodiments of the present invention are explained hereby: 
         [0106]    Available cell of Un interface: the cell downloaded by RN in Phase I for starting the RN and affiliated to the same DeNB as the cell which RN chose to access in Phase II in the cell list. 
         [0107]    Configurable cell of Un interface: the cell that the RN can work at Un interface under the current RN type determined. It is specifically the available cell list or cell sublist of Un interface. 
         [0108]    Available cell of Uu interface: the cell downloaded by the RN from RN OAM and can be used by RN Uu interface; 
         [0109]    Configurable cell of Uu interface: the cell that the RN can work in Uu interface under the current RN type determined. It is specifically the available cell assembly or cell sub-assembly of Uu interface. 
         [0110]    The technical solution put forward by the embodiments of the present invention can be specifically explained into the following aspects: 
       1) Determination of Cell Available for RN Un Interface 
       [0111]    The RN can determine the relation between cell and DeNB according to the former 20 bits of cell ID in cell list information downloaded from RN OAM. If the cell is affiliated to the same DeNB with the cell that the current RN is accessed to, the cell can be determined as the cell available for RN Un interface. 
         [0112]    In the process, the RN can also determine the cell available for RN Uu interface, viz. all cells in cell list of Uu interface configured by RN OAM. 
         [0000]    2) Determination of RN Type. RN Type is Determined by RN Realization. 
         [0113]    RN type is mainly determined based on: the cell available respectively for RN Un interface and RN Uu interface as well as software/hardware capacity of the RN. 
         [0114]    RN type is determined in, but not limited to the following manners: 
         [0115]    A. If RN software/hardware capacity only supports resource division, RN type can be determined as “Requiring resource division”; 
         [0116]    B. If RN software/hardware capacity only supports not requiring resource division, RN type can be determined as “Not requiring resource division”; 
         [0117]    C. If RN software/hardware capacity supports the both, then: 
         [0118]    a. If the both cells supported by Uu interface and Un interface cannot meet the requirements of not requiring resource division, RN type can only be selected as “Requiring resource division”; 
         [0119]    b. If a part of cell among cells supported by Uu interface and Un interface meet the requirements of not requiring resource division, RN type can be selected as “Requiring resource division” or “Not requiring resource division”. It is selected specifically depending on RN realization; 
         [0120]    c. If the both cells supported by Uu interface and Un interface meet the requirements of not requiring resource division, the RN type can be selected as “Not requiring resource division”. 
       3) Determination of Configurable Cell of the RN Un/Uu Interface 
       [0121]    The determination depends on RN realization. The configurable cell of the RN Uu/Un interface is determined based on the available cell of the RN type and the RN Uu/Un interface. 
         [0122]    For example, if the RN type is selected as “Requiring resource division”, the available cell of the Uu interface with the isolation to the RN Un interface not meeting the requirements cannot be configured as the available cell of the RN Uu interface. 
         [0123]    Wherein, the configurable cell of the Uu interface is determined mainly based on the RN type. 
       4) The RN Reports the Configurable Cell of the Un Interface to the DeNB 
       [0124]    The RN reports the configurable cell of the Un interface to the RN through the RRC signalling, and the DeNB configures the cell working at the Un interface for the RN according to the cell reported by the RN and traffic transmission demand. 
         [0125]    In addition, the RN can also carry RN type when reporting the configurable cell of the Un interface to the DeNB. RN is allowed to report the configurable cell of the Un interface and report the RN type with the same or different RRC signalling. 
         [0126]    It should be noted that it is allowed for the RN to modify the configurable carrier resource of the RN type and the Uu/Un in follow-up process if necessary (such as UL congestion of Un interface and sufficient resource of Uu interface). The change will not affect the protection scope of the present invention. 
         [0127]    In specific application scene, embodiments of the present invention further put forward the following embodiments, as shown in  FIG. 6 , which comprises the following steps: 
         [0128]    Step S 601 , the RN acquires RN OAM configuration information. 
         [0129]    In Phase I of starting RN, the RN is attached to network in the same manner of a UE. To be specific, the RN downloads initial configuration information from OAM of the RN and then is deattached. Wherein, the RN OAM information at least comprises the cell assembly that can be aggregated at Uu interface between the RN and R-UE, and the donor cell list allowed to be assessed by the RN; 
         [0130]    Step S 602 , the RN determines the donor cell to be assessed. 
         [0131]    The RN selects a cell from the donor cell list configured for the RN OAM at random or according to certain rules as the donor cell. 
         [0132]    Step S 603 , the RN determines the available cell assembly Gun_pre of the Un interface. 
         [0133]    The RN determines first which DeNB the donor cell selected in Step S 602  is affiliated to and then selects all cells afflicted to the same DeNB from the donor cell list configured for RN O&amp;M. The cells are alternative assembly Gun_pre of the available cell of the Un interface. 
         [0134]    Step S 604 , the RN determines the available cell assembly Guu_pre of the Uu interface. The cell assembly aggregated at Uu interface configured for the RN Q&amp;M is directly used as the available cell assembly Guu_pre of the RN on the Un interface. 
         [0135]    Step S 605 , the RN determines its relay node type. 
         [0136]    The RN determines the RN type according to the available cell assembly Guu_pre of the Uu interface, the available cell alternative assembly Gun_pre of Un and the software/hardware capacity of the RN determined in the aforesaid steps in the principles as below: 
         [0137]    (1) If RN software/hardware capacity only supports resource division, RN type can be determined as “Requiring resource division”; 
         [0138]    (2) If RN software/hardware capacity only supports not requiring resource division”, the RN type can be determined as “Not requiring resource division”; 
         [0139]    (3) If RN software/hardware capacity supports the both, then: 
         [0140]    If the both cells contained in the Guu_pre and the Gun_pre cannot meet the requirements of not requiring resource division, the RN type can only be selected as “Requiring resource division”; 
         [0141]    If partial cells contained in the Guu_pre and the Gun_pre can meet the requirements of not requiring resource division, the RN type can be selected as “Requiring resource division” or “Not requiring resource division”. It is selected specifically depending on RN realization; 
         [0142]    If the both cells contained in the Guu_pre and the Gun_pre meet the requirements of not requiring resource division, the RN type can be selected as “Not requiring resource division”. 
         [0143]    Step S 606 , the RN determines the configurable cell assembly Guu of the RN Uu interface. 
         [0144]    The RN determines the configurable cell assembly Guu according to the RN type and the Guu_pre and the Gun_pre of the Uu interface. The RN will determine depending on RN realization; the RN can determine all or a part of Guu_pre as the Guu. 
         [0145]    Step S 607 , the RN determines the configurable cell assembly Gun of the RN Un interface. 
         [0146]    The RN determines the Gun through certain realization manner. For example, the RN can determine the Gun in the manners as below: 
         [0147]    If the RN type is selected as “Not requiring resource division”, the RN selects the cell meeting the requirements of not requiring resource division together with all the cells in the Guu from the Gun_pre as the Gun. 
         [0148]    If the RN type is selected as “Requiring resource division”, the RN selects the cell that does not meet the requirements on isolation together with any cell in the Guu from the Gun_pre as the Gun. 
         [0149]    Step S 608 , the RN informs the RN type and Gun to the DeNB through the RRC signaling. 
         [0150]    Gun is namely the configurable cell assembly between the DeNB and the RN. 
         [0151]    Step S 609 , the DeNB allocates Un interface resource for the RN according to the Gun. 
         [0152]    Compared with available technology, the embodiments of the present invention have the following advantages: 
         [0153]    Upon application of the technical solution for embodiments of the present invention, the relay node can determine information of the current cell available for allocation of the Un interface and report the information to the eNB, so that the eNB can allocate corresponding Un interface resource for the relay node, and the eNB can accurately acquire resource information of the current cell available for allocation of the Un interface corresponding to the relay node, which solves the problem that the relay node cannot work normally under condition of carrier aggregation caused by mismatching between the Un interface resource directly allocated by the eNB and the relay node in prior art. 
         [0154]    To realize the technical solution for embodiments of the present invention, embodiments of the present invention also put forward a relay node. The structural diagram is shown in  FIG. 7 , which comprises: 
         [0155]    Acquisition module  71 , is used for acquiring information of available cell of Un interface; 
         [0156]    Type determination module  72 , is used for determining the relay node type according to the information of the available cell of the Un interface acquired by the acquisition module  71 ; 
         [0157]    Information determination module  73 , is used for determining information of the current cell available for allocation of the Un interface of the relay node according to the information of the available cell of the Un interface acquired by the acquisition module  71  and the relay node type determined by the type determination module  72 ; 
         [0158]    Sending module  74 , is used for sending the information of the current cell available for allocation of the Un interface determined by the information determination module  73  to the eNB that the relay node is affiliated to, in order to make the eNB allocates Un interface resource for the relay node according to information of the current cell available for allocation of the Un interface. 
         [0159]    In specific application scene, the acquisition module  71  is specifically used to: 
         [0160]    Determine which cells belonging to the eNB that the relay node is affiliated to, according to the cell list information downloaded from OAM of the relay node; 
         [0161]    When a cell and the cell that the relay node is accessed to are affiliated to the same eNB, the cell is determined as the available cell of its Un interface. 
         [0162]    On the other hand, the acquisition module  71  is also used to acquire information of the available cell of the Uu interface of the relay node according to the cell list information of the Uu interface downloaded from the OAM of the relay node. 
         [0163]    In practical application, the type determination module  72  is specifically used to determine the relay node type according to information of the available cell of the Un interface, information of the available cell of the Uu interface and the software/hardware capacity information of the relay node. 
         [0164]    According to the practical application scene, the type determination module  72  is specifically used to: 
         [0165]    Determine the relay node type as “Requiring resource division” when the software/hardware capacity information of the relay node only supports resource division; 
         [0166]    Determine the relay node type as “Not requiring resource division” when the software/hardware capacity information of the relay node only supports not requiring resource division; 
         [0167]    Determine the relay node type as “Requiring resource division” when the software/hardware capacity information of the relay node supports the both and both the cells corresponding to information of the available cell of the Un interface and information of the available cell of the Uu interface cannot meet the requirement of not requiring resource division; 
         [0168]    Determine the relay node type as “Requiring resource division” or “Not requiring resource division” according to the demand of relay node when the software/hardware capacity information of the relay node supports the both and a part of the cell corresponding to information of the available cell of the Un interface and information of the available cell of the Uu interface can meet the requirement of not requiring resource division; 
         [0169]    Determine the relay node type as “Not requiring resource division” when the software/hardware capacity information of the relay node supports the both and both the cells corresponding to information of the available cell of the Un interface and information of the available cell of the Uu interface meet the requirement of not requiring resource division; 
         [0170]    In practical application, the information determination module  73  is also used to determine information of the current cell available for allocation of the Uu interface of the relay node according to the relay node type determined by the type determination module  72 . 
         [0171]    It should be further noted that the sending module  74  is specifically used to: 
         [0172]    Report the information of the current cell available for allocation of the Un interface to the eNB that the relay node is affiliated to through the RRC message, so that the eNB can allocate Un interface resource for the relay node according to the information of the current cell available for allocation of the Un interface and the current transmission demand. 
         [0173]    Wherein, the sending module  74  is also used to report the relay node type to the eNB that the relay node is affiliated to through the RRC message. The RRC message can be as the same as or different from the RRC message for reporting information of the current cell available for allocation of the Un interface. 
         [0174]    On the other hand, embodiments of the present invention provide an eNB. The structural diagram is shown in  FIG. 8 , which comprises: 
         [0175]    Receiving module  81 , is used for receiving information of the current cell available for allocation of Un interface sent by the relay node; 
         [0176]    Allocation module  82 , is used for allocating Un interface resource for the relay node according to information of the current cell available for allocation of the Un interface received by the receiving module  81 . 
         [0177]    In specific application scene, the receiving module  81  is also used to receive information of the current cell available for allocation of the Un interface sent by the relay node through the RRC message. 
         [0178]    Compared with available art, the embodiments of the present invention have the following advantages: 
         [0179]    Upon application of the technical solution for embodiments of the present invention, the relay node can determine information of the current cell available for allocation of the Un interface and report the information to the eNB, so that the eNB can allocate corresponding Un interface resource for the relay node, and the eNB can accurately acquire resource information of the current cell available for allocation of the Un interface corresponding to the relay node, which solves the problem that the relay node cannot work normally under condition of carrier aggregation caused by mismatching between the Un interface resource directly allocated by the eNB and the relay node in prior art. With the description of the preferred embodiments hereinabove, those skilled in the art can clearly understand that the present invention can be realized with the aid of software and necessary commonly used hardware platforms, or the aid of hardware of course, but the former is a preferred embodiment in most cases. Based on this understanding, the technical proposal of the present invention or the part contributing to the current art can be reflected in the form of a software product, which is saved in a memory medium comprising instructions to enable a terminal equipment, which could be a personal computer, a server or a network device, to carry out the methods for each embodiment of the present invention. 
         [0180]    Technical personnel of the field can understand that the drawings only refer to the diagram of a preferred embodiment, and the module or procedure is not necessary for the implementation of the embodiments of the present invention. 
         [0181]    Technical personnel of the field can understand that the module in the unit of an embodiment can be allocated in such unit based on embodiment description, or located in one or more units of another embodiment through corresponding changes. Modules of the embodiments mentioned above can be merged into one module, or further divided into a plurality of submodules. 
         [0182]    The number of the aforementioned embodiments of the present invention is only used for description rather than for representing advantages or disadvantages. 
         [0183]    Only several specific embodiments of the present invention are released above. 
         [0184]    However, the present invention is not only comprised of those. Any change that technical personnel of the field can predict shall be protected by the present invention.