WO2012048655A1 - 载波聚合场景下中继节点的资源分配方法和设备 - Google Patents
载波聚合场景下中继节点的资源分配方法和设备 Download PDFInfo
- Publication number
- WO2012048655A1 WO2012048655A1 PCT/CN2011/080772 CN2011080772W WO2012048655A1 WO 2012048655 A1 WO2012048655 A1 WO 2012048655A1 CN 2011080772 W CN2011080772 W CN 2011080772W WO 2012048655 A1 WO2012048655 A1 WO 2012048655A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- relay node
- interface
- information
- cell
- available
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/155—Ground-based stations
- H04B7/15507—Relay station based processing for cell extension or control of coverage area
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/047—Public Land Mobile systems, e.g. cellular systems using dedicated repeater stations
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a resource allocation method and device for a relay node in a carrier aggregation scenario.
- LTE Long Term Evolution
- UE User Equipment, User Equipment
- FIG. 1 is a schematic diagram of carrier bandwidth in an existing LTE system
- a carrier has a maximum bandwidth of 20 MHz.
- LTE-A Long Term Evolution Advanced
- LTE-A Long Term Evolution Advanced
- the LTE-A system requires good compatibility with the LTE system.
- CA carrier aggregation
- each carrier is set to a maximum of 20 MHz.
- Each component carrier in the LTE-A system is an LTE Rel-8 compatible carrier.
- FIG. 2 it is a schematic diagram of a CA technology in an existing LTE-A system.
- the number of carriers that can be aggregated by the UE is four, and the network side can perform data transmission with the UE on four carriers at the same time.
- FIG. 3 it is a schematic diagram of a network structure of an existing RN (Relay Node) system, where an eNB (evolved NodeB, an evolved node, ie, a base station) is connected through a wired interface.
- the core network Core Network, CN
- the RN is connected to the DeNB (Door eNB, which is the home eNB of the RN) through the radio interface (Un interface), and the R-UE (the UE of the RN's monthly service) passes the radio interface (Uu interface).
- the RN Relay Node
- the RN type (RN Type) can be classified into the following types:
- L2 RN Layer 2 Relay Node, Layer 2 Relay
- L3 RN Layer 3 Relay Node, Layer 3 Relay
- the L3 RN can be classified into the following two types according to whether it is necessary to divide the carrier resources in the time domain:
- the RN Type mentioned is the foregoing RN that needs resource division or the RN that does not need resource division.
- the RN cannot send and receive at the same time on the Uu interface and the Un interface. Otherwise, self-interference will occur.
- one solution is to perform downlink access (access) transmission on the Uu interface R-UE.
- the 'gaps' time slot
- the gap can be used for the DL BH Link (downlink backhaul link), that is, the downlink BH subframe.
- the 'gaps' configuration can be implemented by MBSFN (Multicast Broadcast Single Frequency Network) subframe.
- FIG. 4 it is a schematic diagram of performing downlink transmission of a relay link by using an MBSFN subframe in the Un interface in the prior art.
- the DeNB will perform downlink transmission with the RN, and the RN and R-UE will not perform downlink transmission.
- the RN startup process in the existing RN-introduced network is divided into the following two Stages:
- the first P-segment acts as a UE to access the network.
- the specific processing flow is:
- the RN attaches to the network according to the manner of the UE, and downloads initial configuration information from the RN OAM, where the list of Donor cells that are allowed to be connected is included, and then the RN attaches.
- the second phase As the RN access network, the specific processing flow is:
- the RN selects Donor cell: Select a Donor Cell from the Donor Cell list provided in Phase I.
- the MME is selected for the RN:
- the RN informs the DeNB of its RN identity through RRC signaling, and based on this information, the DeNB selects an RN supporting the RN for the RN;
- Selecting GW for the RN After the CN notifies the MME that the access node is the RN, the MME selects the DeNB as the P/S-GW of the RN;
- the corresponding S1 and X2 interfaces are proposed between the RN and the DeNB:
- the RN initiates the S1 and X2 establishment procedures on the bearers established by the DeNB.
- the L3 RN type is determined as follows:
- the RN type determination depends on the RN implementation.
- One possible way is as follows:
- the RN obtains the cell supported by the RN Uu interface from the RN OAM;
- the RN determines the cell used by its Un interface according to the donor cell it accesses;
- the RN determines the RN type (whether or not resource division is required) based on the cell supported by the Uu and Un interfaces and the RN's own hardware and software capabilities;
- the RN indicates the type of the RN to the DeNB through an lbit indication.
- the RN type indication can be in the following two ways, and there is no conclusion as to which one is used.
- Alt2 Define a separate RN type indication message
- the DeNB learns the RN type, it determines whether it needs to be configured after the BH subframe is configured according to the RN type.
- the RN performs the RACH access to the DeNB 1 on the cell A in the second P-segment initiated by the RN, and the cell that can be used by the RN under the DeNB1 is the cell a and the cell according to the cell list downloaded from the RN OAM by the first P-segment. b.
- the cell list of the Uu interface that the RN downloads from the RN OAM is cell a, cell b, and cell c. In this way, if the RN type reported by the RN to the DeNB is "no resource division", the DeNB does not work normally.
- the main reasons are as follows: (1) The DeNB does not know whether the RN supports other cells except cell a, and therefore cannot The RN implements the CA operation;
- the DeNB does not know whether the cells on the RN Uu interface and the cell combination of the cell and the Un interface need resource division.
- the embodiments of the present invention provide a resource allocation method and a device for a relay node in a carrier aggregation scenario, and report the resource resources of the Un interface to the base station through RRC signaling, which solves the problem that the CA and the RN fusion system cannot be configured according to the existing mechanism. The problem of working properly.
- an embodiment of the present invention provides a resource allocation method for a relay node in a carrier aggregation scenario, including:
- the relay node acquires information about available cells of the Un interface
- the relay node determines its own relay node type according to the information of the available cells of the Un interface
- the embodiment of the present invention further provides a relay node, including: an ear module, configured to acquire information about an available cell of the Un interface;
- a type determining module configured to determine, according to information about an available cell of the Un interface acquired by the acquiring module, a relay node type of the relay node;
- An information determining module configured to determine, according to the information about the available cell of the Un interface acquired by the acquiring module, and the type of the relay node determined by the type determining module, that the Un interface of the relay node is currently available for allocation Cell information;
- the embodiment of the present invention further provides a resource allocation method for a relay node in a carrier aggregation scenario, including:
- the base station receives the information of the currently available cell of the Un interface sent by the relay node; the base station allocates the resource of the Un interface to the relay node according to the information of the currently available cell of the Un interface.
- a base station including:
- a receiving module configured to receive information about a currently available area of the Un interface sent by the relay node
- an allocating module configured to allocate resources of the Un interface to the relay node according to information about a cell currently available to be allocated by the Un interface received by the receiving module.
- the embodiment of the invention has the following advantages:
- the relay node may determine the cell information that can be allocated by the Un interface, and report the information to the base station, so that the base station can allocate the corresponding Un interface resource to the relay node, thereby
- the base station side can accurately obtain the cell resource information of the Un interface that is currently allocated by the relay node, and solves the carrier caused by the mismatch between the Un interface resource directly allocated by the base station and the relay node in the prior art.
- the problem that the relay node in the aggregation scenario cannot work normally.
- FIG. 1 is a schematic diagram of a carrier distribution of an LTE cell in the prior art
- FIG. 2 is a schematic diagram of a CA technology in the prior art
- FIG. 3 is a schematic structural diagram of an LTE-A network in the prior art
- FIG. 4 is a schematic diagram of an Un interface in the prior art for performing downlink transmission on a relay link by using an MBSFN subframe;
- FIG. 5 is a schematic flowchart of a method for allocating resources of a relay node in a carrier aggregation scenario according to an embodiment of the present disclosure
- FIG. 6 is a schematic flowchart of a resource allocation method of a relay node in a specific application scenario on a base station side according to an embodiment of the present invention
- FIG. 7 is a schematic structural diagram of a relay node according to an embodiment of the present invention
- FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present invention.
- the RN is introduced to improve the system throughput and the network coverage is increased, and the CA is introduced to improve the peak rate.
- the embodiment of the present invention provides a system in which the CA and the RN are integrated. A method for determining a medium Uu interface and a Un interface carrier/cell resource.
- FIG. 5 is a schematic flowchart of a method for allocating resources of a relay node in a carrier aggregation scenario according to an embodiment of the present disclosure, which specifically includes the following steps:
- Step S501 The relay node acquires information about an available cell of the Un interface.
- the relay node determines, according to the cell list information downloaded from the 0 AM of the relay node, the attribution relationship between each cell and the base station to which the relay node belongs;
- the relay node determines that the cell is an available cell of its Un interface.
- the implementation process of the step further includes the process of the relay node acquiring the information of the available cell of the Uu interface, and the specific processing procedure is as follows:
- the relay node acquires information about the available cells of its Uu interface according to the cell list information of the Uu interface downloaded from the 0 AM of the relay node.
- Step S502 The relay node determines its own relay node type according to the information of the available cells of the Un interface.
- step S501 when the information about the available cells of the Uu interface is also obtained in step S501, the processing procedure in this step is specifically:
- the relay node determines its own relay node type according to the information of the available cells of the Un interface, the information of the available cells of the Uu interface, and its own software/hardware capability information.
- Case 1 When the relay node's own software/hardware capability information only supports resource partitioning, the relay node determines that its own relay node type requires resource partitioning.
- Case 3 When the relay node's own software/hardware capability information supports both resource partitioning and resource partitioning, the information about the available cells of the Un interface and the information of the available cells of the Uu interface can be further classified into the following three cases:
- the relay node determines that its own relay node type requires resource division.
- the relay node determines its own relay node type according to its own requirements. Resource allocation or resource division is not required;
- the relay node determines that its own relay node type does not require resource division.
- Step S503 The relay node determines, according to information about the available cells of the Un interface, and the type of the relay node, information about the currently available cell of the Un interface.
- the relay node may further determine, according to the relay node type, the information of the current available channel of the Uu interface, so as to avoid the step S501.
- the information of the available cells of the obtained Uu interface has resources that cannot be allocated, and the information of the currently available cells of the Uu interface is mainly determined by the type of the relay node.
- Step S504 The relay node sends the information of the currently available cell of the Un interface to the base station to which the UE is allocated, so that the base station allocates the resource of the Un interface to the relay node according to the information of the currently available cell of the Un interface. .
- the relay node reports the information of the currently available cell of the Un interface to the base station to which the eNB belongs by using the RRC message;
- the base station allocates resources of the Un interface to the relay node according to the information of the currently available cell of the Un interface and the current service requirement.
- the relay node may report the information of the currently available cell of the Un interface to the base station to which the eNB belongs, and the RRC message may also carry the relay of the relay node. Node type.
- the relay node type can also be sent to the base station through other messages.
- the above description is directed to the implementation process of the technical solution proposed by the embodiment of the present invention on the relay node side.
- the base station On the base station side, the base station directly allocates the resource of the Un interface to the relay node according to the information reported by the relay node. The description will not be repeated here.
- the embodiment of the invention has the following advantages:
- the relay node may determine the cell information that can be allocated by the Un interface, and report the information to the base station, so that the base station can allocate the corresponding Un interface resource to the relay node, thereby
- the base station side can accurately obtain the cell resource information of the Un interface that is currently allocated by the relay node, and solves the carrier caused by the mismatch between the Un interface resource directly allocated by the base station and the relay node in the prior art.
- the problem that the relay node in the aggregation scenario cannot work normally.
- the embodiment of the present invention provides a method for determining a U/interface and a Un-interface compatible carrier/cell resource allocation by a RN in a system in which a CA and an RN are fused, that is, the RN is determined by the RN according to the RN type.
- the available resource of the RN Uu/Un interface is allocated, and then the Un-configured cell resource is reported to the DeNB through RRC signaling.
- the un-interface is available to the cell of the same DeNB.
- the RN that the RN downloads in the first P-segment of the RN can access the cells in the cell list that are selected by the Phase II P-RAN to belong to the same DeNB.
- the Un interface can be configured with the cell: that is, in the currently determined RN type, the cell that the RN can work on the Un interface is the complete set or subset of the available cells of the Un interface.
- Uu interface available cell The cell that the RN can use from the RN UAM to download from the RN OAM;
- the Uu interface can be configured with the cell: that is, the cell that the RN can work on the Uu interface under the currently determined RN type, which is the complete set or subset of the available cell of the Uu interface.
- the technical solution proposed by the embodiment of the present invention can be embodied as follows:
- the RN can determine the affiliation relationship between the cell and the DeNB according to the first 20 bits of the cell ID in the cell list information downloaded from the RN OAM. If the cell and the cell accessed by the current RN belong to one DeNB, the RN can determine that the cell is The RN Un interface can use cdl.
- the RN can also determine the available cells of the RN Uu interface, that is, all the cells in the Uu interface cell list configured by the RN OAM.
- the RN type is determined by the RN implementation.
- the main basis for determining the RN type includes: RN Un interface available cell, RN Uu interface available cell, and RN's own software/hardware capabilities.
- the manner of determining the RN type includes but is not limited to the following:
- the RN type can be determined as "required resource partitioning"
- the RN type can be determined as "no resource partitioning"; C. If the RN software/hardware capability supports resource partitioning and supports resource partitioning, then:
- the RN type can only select "requires resource division”; b. If the cell and Un interface supported by the Uu interface support Only some cells between the cells can meet the requirements of not dividing resources. Then the RN type can select "requires resource division” or "no resource division", and the specific choice depends on the RN implementation;
- the RN type can be selected as "no resource division".
- RN Uu/Un interface can be determined by the cell RN Uu / Un interface can be equipped with cell.
- the Uu interface with the RN Un interface cannot meet the requirements.
- the available cell cannot be configured as the RN Uu available cdl.
- the basis for determining the configurable cell of the Uu interface is mainly RN type.
- the RN reports to the DeNB that the Un interface can be configured with the cell.
- the RN reports the Un-interface to the RN through the RRC signaling.
- the DeNB configures the cell that the Un-interface actually works according to the cell and service requirements reported by the RN.
- the RN reports to the DeNB that the Un-interface can be configured with the RN type, and the RN reports that the Un-interface can be configured with the same RRC signaling or different RRC signaling.
- the RN is allowed to modify the RN type and the Uu/Un configurable carrier resources in the subsequent process, for example, the Un interface UL is congested, and the Uu interface resource is sufficient. Such a change does not affect the protection scope of the present invention. .
- the following embodiments are further provided in the embodiment of the present invention. As shown in FIG. 6, the following steps are included:
- Step S601 The RN acquires RN OAM configuration information.
- the RN attaches to the network according to the manner of the UE, downloads initial configuration information from the OAM of the RN, and then detaches.
- the RN OAM information includes at least a Uu interface aggregateable cell set between the RN and the R-UE, and a list of donor cells allowed by the RN;
- Step S602 The RN determines the donor cdl to be accessed.
- the RN selects a cell from the donor cell list configured in the RN OAM or selects a cell as a donor cell.
- Step S603 The RN determines that the Un interface is available for the cell set Gun_pre.
- the RN first determines which DeNB the donor cell selected in step S602 belongs to, and then
- the RN selects all cells belonging to the same DeNB from the list of donor cells configured by the RN and the M. These cells serve as the Unselectable cell candidate set Gun_pre.
- Step S604 The RN determines that the Uu interface uses the cell set Guu_pre.
- the Uu interface directly configured by the RN Q&M can aggregate the cell set as the RN can use the cell collection Guu_pre on the Uu interface.
- Step S605 The RN determines its own RN type.
- the RN determines the RN type according to the Uu interface determined by the above steps, the cell set Guu_pre, the Un available cell candidate set Gun_pre, and the RN's own software/hardware capabilities. The principle is determined as follows:
- the RN type can be determined as "required resource partitioning"
- the RN type can be determined as "no resource partitioning"
- the RN type can only select "require resource partitioning"
- the RN type can select "require resource division” or "no resource division", and the specific selection depends on the RN. achieve; If the cell included in Guu_pre and the cell included in Gun_pre satisfy the requirement of not dividing the resource, the RN type may select "no resource division"; step S606, the RN determines that the RN Uu interface can be configured with the cell set Guu. .
- the RN determines the RN Uu interface according to the RN type and the Uu interfaces Guu_pre and Gun_pre.
- the UA Uu interface can be configured with the cell set Guu.
- the RN can use Guu_pre as Guu or part of Guu.
- Step S607 The RN determines that the RN Un interface can be configured with the cell set Gun.
- the Gun is determined by the RN through some implementation.
- the RN can determine the Gun by:
- the RN type is "no resource division", then the RN selects from the Gun_pre and all the cells in the Guu satisfy the cell that does not require the resource division requirement as the Gun.
- the RN type is "requires resource division", then the RN selects from Gun_pre and any cell in Guu that does not satisfy the isolation requirement as the Gun.
- Step S608 The RN notifies the DeNB of the RN type and the Gun by using RRC signaling.
- the Gun is a set of configurable cells between the DeNB and the RN.
- Step S609 The DeNB allocates an Un interface resource to the RN according to the Gun.
- the embodiment of the invention has the following advantages:
- the relay node may determine the cell information that can be allocated by the Un interface, and report the information to the base station, so that the base station can allocate the corresponding Un interface resource to the relay node, thereby
- the base station side can accurately obtain the cell resource information of the Un interface that is currently allocated by the relay node, and solves the carrier caused by the mismatch between the Un interface resource directly allocated by the base station and the relay node in the prior art.
- the problem that the relay node in the aggregation scenario cannot work normally.
- the embodiment of the present invention further provides a relay node, and a schematic structural diagram thereof is shown in FIG. 7, which specifically includes:
- the type determining module 72 is configured to determine, according to information about an available cell of the Un interface acquired by the obtaining module 71, a relay node type of the relay node;
- the information determining module 73 is configured to determine information about a currently available cell of the Un interface of the relay node according to the information about the available cell of the Un interface acquired by the obtaining module 71 and the type of the relay node determined by the type determining module 72. ;
- the sending module 74 is configured to send the information about the currently available cell of the Un interface determined by the information determining module 73 to the base station to which the relay node belongs, so that the base station is based on the information of the currently available cell of the Un interface.
- the node allocates resources of the Un interface.
- the obtaining module 71 is specifically configured to:
- the relay node When a cell and a cell accessed by the relay node belong to the same base station, it is determined that the cell is an available cell of the Un interface of the relay node.
- the obtained module 71 is further configured to acquire information of the available cells 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.
- the type determining module 72 is specifically configured to determine the relay node type of the relay node according to the information of the available cells of the Un interface, the information of the available cells of the Uu interface, and the software/hardware capability information of the relay node. .
- the type determining module 72 is specifically configured to:
- the relay node's own software/hardware capability information only supports resource partitioning, it is determined that the relay node type of the relay node needs resource division;
- the relay node's own software/hardware capability information only supports the unnecessary resource division, it is determined that the relay node's relay node type does not require resource division;
- the relay node's own software/hardware capability information supports both resource partitioning and resource partitioning, and the information of the available cell of the Un interface and the cell corresponding to the information of the available cell of the Uu interface do not satisfy the requirement of not dividing the resource. Determining the relay node type of the relay node as requiring resource division;
- the soft/hardware capability information of the relay node supports the resource division and the resource division, the part of the cell corresponding to the information of the available cell of the Un interface and the information of the available cell of the Uu interface meets the requirement of not dividing the resource.
- Relay section Point requirements determine the relay node type of the relay node to require resource division or no resource division;
- the soft/hardware capability information of the relay node supports the resource division and the resource division, and the information of the available cell of the Un interface and the cell corresponding to the information of the available cell of the Uu interface satisfy the requirement of not dividing the resource, It is determined that the relay node type of the relay node does not require resource division.
- the information determining module 73 is further configured to determine information about a currently available cell of the Uu interface of the relay node according to the type of the relay node determined by the type determining module 72.
- sending module 74 is specifically used to:
- the information about the currently available cell of the Un interface is reported by the RRC message to the base station to which the eNB belongs, and the station allocates the resource of the Un interface to the relay node according to the information of the currently available cell of the Un interface and the current service requirement.
- the sending module 74 is further configured to report, by using an RRC message, the relay node type of the relay node to the base station to which the RRC message belongs, and the RRC message may be the same RRC message as the information of the currently available cell of the Un interface. It can also be other RRC messages.
- an embodiment of the present invention further provides a base station, and a schematic structural diagram thereof is shown in FIG. 8 , including:
- the receiving module 81 is configured to receive information about a cell currently available for allocation by the Un interface sent by the relay node;
- the allocating module 82 is configured to allocate resources of the Un interface to the relay node according to the information of the currently available AP of the Un interface received by the receiving module 81.
- the receiving module 81 is specifically configured to receive information about a cell currently available for allocation by the Un interface sent by the relay node through the RRC message.
- the embodiment of the invention has the following advantages:
- the relay node may determine the cell information that can be allocated by the Un interface, and report the information to the base station, so that the base station can allocate the corresponding Un interface resource to the relay node, thereby , enabling the base station side to accurately obtain
- the cell resource information of the Un interface that is currently allocated by the relay node is obtained, and the relay node in the carrier aggregation scenario caused by the mismatch between the Un interface resource and the relay node directly allocated by the base station in the prior art is solved. The problem is not working properly.
- modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the description of the embodiments, or may be correspondingly changed in one or more apparatuses different from the embodiment.
- the modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Description
载波聚合场景下中继节点的资源分配方法和设备 本申请要求于 2010年 10月 15 日提交中国专利局, 申请号为 201010515839.0, 发明名称为 "载波聚合场景下中继节点的资源分配 方法和设备"的中国专利申请的优先权, 其全部内容通过引用结合在 本申请中。 技术领域
本发明涉及通信技术领域,特别涉及一种载波聚合场景下中继节 点的资源分配方法和设备。 背景技术
LTE ( Long Term Evolution, 长期演进 ) 及以前的无线通信*** 中, 通常每个小区中只有一个(或一对 )载波, UE ( User Equipment, 用户设备) 同一时刻只能在一个小区中 (载波上)进行数据收发。
如图 1所示, 为现有的 LTE***中载波带宽的示意图, 在 LTE ***中, 载波的最大带宽为 20MHz。
随着通信技术的发展, LTE-A ( Long Term Evolution Advanced, 高级长期演进) ***的峰值速率较 LTE有很大的提高, 要求达到下 行 lGbps, 上行 500Mbps, 显然, 20MHz的传输带宽已经无法满足 这种需求。 而在更高的传输速率的需求的同时, LTE-A ***要求和 LTE***有很好的兼容性。 基于提高峰值速率、 与 LTE***兼容以 及充分利用频谱资源的需要, LTE-A ***引入了 CA ( Carrier Aggregation, 载波聚合 )技术, 即 UE能够同时聚合多个成员载波并 在这些载波上同时进行数据传输, 从而提高数据传输速率。
为了保证 LTE***的 UE能在每一个聚合的载波下工作,设定每 一个载波最大不超过 20MHz。 LTE-A***中每个成员载波都是 LTE Rel-8兼容的载波。
如图 2所示, 为现有的 LTE-A***中的 CA技术的示意图。
在图 2所示的 LTE-A***中, UE可聚合的载波个数为 4个, 网 络侧可以同时在 4个载波上和 UE进行数据传输。
进一步的, 如图 3所示, 为现有的引入 RN ( Relay Node, 中继 节点 )的***的网络结构示意图, 其中, eNB ( evolved NodeB , 演进 的 Β节点, 即基站 )通过有线接口连到核心网( Core Network, CN ) , RN通过无线接口 (Un接口)连接到 DeNB ( Donor eNB, 即 RN的 归属 eNB ) , R-UE ( RN所月良务的 UE )通过无线接口 ( Uu接口)连 接到 RN。
在现有技术中, 按照中继数据包的类型, RN的类型 (RN Type ) 可以分为以下几种:
LI RN ( Layer 1 Relay Node, 层 1中继) ;
L2 RN ( Layer 2 Relay Node, 层 2中继) ;
L3 RN ( Layer 3 Relay Node, 层 3中继) 。
其中, 对于 L3 RN, 根据是否需要对载波资源在时域上进行划分 又可以分为以下两种:
需要资源划分的 RN;
不需要资源划分的 RN;
需要说明的是, 在本发明实施例的后续说明中, 所提及的 RN Type即为上述的需要资源划分的 RN或不需要资源划分的 RN。
对于需要资源划分的 RN, RN不能在 Uu接口和 Un接口同时收 发, 否则会产生自干扰, 为了避免自干扰的产生, 一种解决方法就是 在 Uu接口 R-UE的下行 access (接入 )传输时间内创造 'gaps' (时 隙) , 该 gap可以用于 DL BH Link ( Downlink Backhaul Link, 下行 回程链路 ) ,即下行 BH子帧。 'gaps'配置可以通过 MBSFN( Multicast Broadcast Single Frequency Network , 多播 /组播单频网络)子帧实现。
如图 4所示, 为现有技术中 Un接口利用 MBSFN子帧进行中继 链路下行传输的示意图。 在这些 'gaps' 内, DeNB将和 RN之间进 行下行传输, RN与 R-UE不进行下行传输。
进一步的, 现有的引入 RN的网络中的 RN启动过程分为如下两
个阶段:
第一 P介段: RN作为 UE接入网络, 具体的处理流程为:
RN按照 UE的方式附着到网络,从 RN OAM下载初始配置信息, 其中, 包括允许连接的 Donor Cell列表, 然后, RN去附着。
第二阶段: 作为 RN接入网络, 具体的处理流程为:
首先, RN选择 Donor cell: 从 Phase I中提供的 Donor Cell列表 中选择一个 Donor Cell。
然后, 为 RN选择 MME: 在附着过程中, RN通过 RRC信令告 知 DeNB其 RN身份,基于这个信息, DeNB给 RN选择一个支持 RN 的 MME;
为 RN选择 GW: 在 CN通知 MME接入节点为 RN后, MME选 择 DeNB作为 RN的 P/S-GW;
在 RN和 DeNB之间建议相应的 S1和 X2接口: RN在 DeNB为 其建立的承载上发起 S1和 X2建立过程。
在现有的技术方案中, L3 RN类型的确定方法如下:
在 3GPP LTE-A规范 R10版本中,如果不考虑 Un接口使用 CA, 那么 RN类型确定取决于 RN实现, 一种可能的方式如下:
RN从 RN OAM获取 RN Uu接口支持的 cell;
RN根据其接入的 donor cell确定其 Un接口使用的 cell;
RN根据 Uu和 Un接口支持的 cell以及 RN自身软硬件能力确定 RN类型 (是否需要资源划分) ;
RN通过 lbit指示向 DeNB指示该 RN的类型。
在现有的技术方案中, RN类型指示可以有如下两种方式, 具体 使用哪种目前还没有结论。
Altl: 携带在 RRC connection complete消息中;
Alt2: 定义单独的 RN type指示消息;
在实现本发明实施例的过程中,申请人发现现有技术至少存在以 下问题:
如果不考虑 CA, Uu接口和 Un接口都只支持一个 cell, 那么就
不存在 Un和 Uu接口 CC/cell分配的问题。 DeNB获知 RN type后, 按照 RN type确定是否需要配置 BH子帧后即可正常工作。
如果考虑 CA, 问题就会变得比较复杂, 在 Un接口, 某些 RN 原本可以接入的 cell由于 RN type的限制可能变得不能接入。 举例说 明如下:
RN在 RN启动的第二 P介段在 cell a上进行 RACH接入了 DeNB 1 , 根据其第一 P介段从 RN OAM下载的 cell list,在 DeNBl下 RN可以使 用的 cell为 cell a和 cell b, 同时 RN从 RN OAM下载到的 Uu接口 cell list为 cell a、 cell b和 cell c。这样如果 RN向 DeNB上报的 RN type 为 "不需要资源划分",那么 DeNB并不能正常工作,主要原因如下: ( 1 ) DeNB不知道除了 cell a外, RN是否还支持其它 cell, 因 此无法对该 RN实施 CA操作;
( 2 )DeNB不知道 RN Uu接口可能会使用哪些 cell以及这些 cell 和 Un接口的 cell组合时是否需要资源划分;
综上所述, 为了保证 CA和 RN融合的******能够正常工作, 需要考虑如何解决上述问题, 而现有技术中并没有这样的技术方案。 发明内容
本发明实施例提供一种载波聚合场景下中继节点的资源分配方 法和设备, 通过 RRC信令将 Un接口可配小区资源上报给基站, 解决 了 CA和 RN融合***中按照现有机制***无法正常工作的问题。
为达到上述目的,本发明实施例一方面提供了一种载波聚合场景 下中继节点的资源分配方法, 包括:
中继节点获取 Un接口的可用小区的信息;
所述中继节点根据所述 Un接口的可用小区的信息, 确定自身的 中继节点类型;
所述中继节点根据 Un接口的可用小区的信息, 以及所述中继节 点类型, 确定自身的 Un接口当前可供分配的小区的信息;
所述中继节点将确定的所述 Un接口当前可供分配的小区的信息 发送给自身所归属的基站, 以使所述基站根据所述 Un接口当前可供 分配的小区的信息为所述中继节点分配 Un接口的资源。 另一方面, 本发明实施例还提供了一种中继节点, 包括: 获耳^莫块, 用于获取 Un接口的可用小区的信息;
类型确定模块, 用于根据所述获取模块所获取的 Un接口的可用 小区的信息, 确定所述中继节点的中继节点类型;
信息确定模块, 用于根据所述获取模块所获取的 Un接口的可用 小区的信息, 以及所述类型确定模块所确定的中继节点类型, 确定所 述中继节点的 Un接口当前可供分配的小区的信息;
发送模块, 用于将所述信息确定模块所确定的所述 Un接口当前 可供分配的小区的信息发送给所述中继节点所归属的基站,以使所述 基站根据所述 Un接口当前可供分配的小区的信息为所述中继节点分 配 Un接口的资源。 另一方面,本发明实施例还提供了一种载波聚合场景下中继节点 的资源分配方法, 包括:
基站接收中继节点发送的 Un接口当前可供分配的小区的信息; 所述基站根据所述 Un接口当前可供分配的小区的信息为所述中 继节点分配 Un接口的资源。 另一方面, 本发明实施例还提供了一种基站, 包括:
接收模块, 用于接收中继节点发送的 Un接口当前可供分配的小 区的信息;
分配模块, 用于根据所述接收模块所接收的 Un接口当前可供分 配的小区的信息为所述中继节点分配 Un接口的资源。
与现有技术相比, 本发明实施例具有以下优点:
通过应用本发明实施例的技术方案, 中继节点可以确定 Un接口 当前可供分配的小区信息, 并将该信息上报给基站, 使基站可以据此 为中继节点分配相应的 Un接口资源, 从而, 使基站侧能够准确的获 取到中继节点当前所对应的可供分配的 Un接口的小区资源信息, 解 决了现有技术中基站直接分配的 Un接口资源与中继节点不匹配而导 致的载波聚合场景下的中继节点无法正常工作的问题。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面 将对实施例或现有技术描述中所需要使用的附图作筒单地介绍,显而 易见地, 下面描述中的附图仅仅是本发明的一些实施例, 对于本领域 普通技术人员来讲, 在不付出创造性劳动性的前提下, 还可以根据这 些附图获得其他的附图。
图 1为现有技术中的 LTE小区的载波分布的示意图;
图 2为现有技术中的 CA技术的示意图;
图 3为现有技术中的 LTE-A网络的结构示意图;
图 4 为现有技术中的 Un接口利用 MBSFN子帧进行中继链路下 行传输的示意图;
图 5 为本发明实施例所提出的一种载波聚合场景下中继节点的 资源分配方法的流程示意图;
图 6 为本发明实施例提出的一种具体应用场景下中继节点的资 源分配方法在基站侧的流程示意图;
图 7为本发明实施例所提出的一种中继节点的结构示意图; 图 8为本发明实施例所提出的一种基站的结构示意图。 具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方 案进行清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部 分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普 通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
如背景技术所述, 在 LTE-A***中, 为了提高***吞吐量和增加 网络覆盖引入了 RN, 同时为了提高峰值速率引入了 CA, 本发明实施 例给出了一种 CA和 RN融合的***中 Uu接口和 Un接口载波 /小区资源 确定的方法。
如图 5所示, 为本发明实施例所提出的一种载波聚合场景下中继 节点的资源分配方法的流程示意图, 具体包括以下步骤:
步骤 S501、 中继节点获取 Un接口的可用小区的信息。
在实际应用中, 本步骤的实现过程具体为:
中继节点根据从中继节点的 0 AM下载的小区列表信息, 确定各 小区和中继节点所归属的基站之间的归属关系;
当一个小区与中继节点所接入的小区归属于同一个基站时, 中继 节点确定小区为自身的 Un接口的可用小区。
进一步的, 本步骤的实现过程还包括中继节点获取 Uu接口的可 用小区的信息的处理, 具体的处理过程如下:
中继节点根据从中继节点的 0 AM下载的 Uu接口的小区列表信 息, 获取自身的 Uu接口的可用小区的信息。
步骤 S502、 中继节点根据 Un接口的可用小区的信息, 确定自身 的中继节点类型。
基于步骤 S501中的说明, 当步骤 S501中还获取到了 Uu接口的可 用小区的信息时, 本步骤的处理过程具体为:
中继节点根据 Un接口的可用小区的信息, Uu接口的可用小区的 信息, 以及自身的软 /硬件能力信息, 确定自身的中继节点类型。
根据上述个条件, 在具体的应用场景中, 本步骤所确定的中继节 点类型分为以下几种情况:
情况一、 当中继节点自身的软 /硬件能力信息只支持资源划分时, 中继节点确定自身的中继节点类型为需要资源划分。
情况二、 当中继节点自身的软 /硬件能力信息只支持不需要资源 划分时, 中继节点确定自身的中继节点类型为不需要资源划分。
情况三、 当中继节点自身的软 /硬件能力信息同时支持资源划分 和不需要资源划分时, 根据 Un接口的可用小区的信息和 Uu接口的可 用小区的信息, 进一步可以分为以下三种情况:
( 1 ) Un接口的可用小区的信息和 Uu接口的可用小区的信息所对 应的小区都不满足不进行资源划分的要求时, 中继节点确定自身的中 继节点类型为需要资源划分。
( 2 ) Un接口的可用小区的信息和 Uu接口的可用小区的信息所对 应的小区中有一部分满足不进行资源划分的要求时, 中继节点根据自 身的需求,确定自身的中继节点类型为需要资源划分或不需要资源划 分;
( 3 ) Un接口的可用小区的信息和 Uu接口的可用小区的信息所对 应的小区都满足不进行资源划分的要求时,中继节点确定自身的中继 节点类型为不需要资源划分。
步骤 S503、 中继节点根据 Un接口的可用小区的信息, 以及中继 节点类型, 确定自身的 Un接口当前可供分配的小区的信息。
需要指出的是,在步骤 S502中确定了中继节点的中继节点类型之 后, 中继节点还可以根据中继节点类型确定自身的 Uu接口当前可供 分配的小区的信息, 以便避免步骤 S501中所获取的 Uu接口的可用小 区的信息中存在不能分配的资源, 而 Uu接口当前可供分配的小区的 信息的确定依据主要是中继节点类型。
另外, 需要指出的是, Uu接口当前可供分配的小区的信息和 Un 接口当前可供分配的小区的信息的确定顺序可以相互调整,优先进行 那种信息的确定并不会影响本发明的保护范围。
步骤 S504、 中继节点将确定的 Un接口当前可供分配的小区的信 息发送给自身所归属的基站, 以使基站根据 Un接口当前可供分配的 小区的信息为中继节点分配 Un接口的资源。
在实际应用中, 本步骤的处理过程具体为:
中继节点通过 RRC消息向自身所归属的基站上报 Un接口当前可 供分配的小区的信息;
基站根据 Un接口当前可供分配的小区的信息和当前的业务需求 为中继节点分配 Un接口的资源。
需要指出的是, 在实际应用中, 中继节点通过 RRC消息向自身所 归属的基站上报 Un接口当前可供分配的小区的信息的同时, 该 RRC 消息中还可以携带该中继节点的中继节点类型。
当然, 该中继节点类型也可以通过其他消息发送给基站。
以上说明为本发明实施例所提出的技术方案在中继节点侧的实 现流程, 在基站侧, 相对应的, 基站直接根据中继节点上报的信息对 该中继节点进行 Un接口的资源分配, 在此不再重复说明。
与现有技术相比, 本发明实施例具有以下优点:
通过应用本发明实施例的技术方案, 中继节点可以确定 Un接口 当前可供分配的小区信息, 并将该信息上报给基站, 使基站可以据此 为中继节点分配相应的 Un接口资源, 从而, 使基站侧能够准确的获 取到中继节点当前所对应的可供分配的 Un接口的小区资源信息, 解 决了现有技术中基站直接分配的 Un接口资源与中继节点不匹配而导 致的载波聚合场景下的中继节点无法正常工作的问题。
下面, 结合具体的应用场景, 对本发明实施例所提出的技术方案 进行说明。
本发明实施例给出了一种 CA和 RN融合的***中由 RN确定 Uu接 口和 Un接口可配载波 /小区资源分配的方法, 即由 RN根据 RN type确
定 RN Uu/Un接口的可配小区资源, 然后通过 RRC信令将 Un接口可配 小区资源上报给 DeNB。
为了便于后续描述, 首先, 说明一下如下名词在本发明后续的实 施例中的含义:
Un接口可用 cell: 即 RN在 RN启动过程的第一 P介段下载的 RN可接 入 cell list中那些与 Phase II P介段 RN选择接入的 cell归属于同一个 DeNB 的 cell。
Un接口可配 cell: 即在当前确定的 RN type下, RN在 Un接口可以 工作的 cell, 为 Un接口可用 cell的全集或者子集。
Uu接口可用 cell: RN从 RN OAM下载的 RN Uu接口可以使用的 cell;
Uu接口可配 cell: 即在当前确定的 RN type下, RN在 Uu接口可以 工作的 cell, 为 Uu接口可用 cell的全集或者子集。 本发明实施例所提出的技术方案可以具体化为如下几个方面:
1 )确定 RN Un接口可用 cell
RN根据从 RN OAM下载的 cell list信息中的 cell ID前 20 bit可以确 定 cell和 DeNB之间的归属关系, 这些 cell如果和当前 RN接入的 cell归 属于一个 DeNB, 那么就可以确定该 cell为 RN Un接口可用 cdl。
在此过程中, RN还可以确定 RN Uu接口可用 cell, 即 RN OAM配 置的 Uu接口 cell list中的所有 cell。
2 )确定 RN type, RN type的确定取决于 RN实现。
RN type确定的主要依据包括: RN Un接口可用 cell、 RN Uu接口 可用 cell , 以及 RN自身的软 /硬件能力。
RN type的确定方式包括但不限于如下方式:
A、 如果 RN软 /硬件能力只支持资源划分, RN类型就可以确定为 "需要资源划分" ;
B、 如果 RN软 /硬件能力只支持不需要资源划分, 那么 RN类型就 可以确定为 "不需要资源划分" ;
C、 如果 RN软 /硬件能力即支持资源划分又支持不进行资源划分, 那么:
a、 如果 Uu接口支持的 cell和 Un接口支持的 cell之间都不满足 不进行资源划分的要求, 那么 RN类型只能选择 "需要资源划分" ; b、 如果 Uu接口支持的 cell和 Un接口支持的 cell之间只有部分 cell可以满足不进行资源划分的要求, 那么 RN类型即可以选择 "需要 资源划分" , 也可以选择 "不需要资源划分" , 具体选择取决于 RN 实现;
c、 如果 Uu接口支持的 cell和 Un接口支持的 cell之间全部都满足不 进行资源划分的要求, 那么 RN类型即可以选择 "不需要资源划分" 。
3 )确定 RN Un/Uu接口可配 cell
如何确定取决于 RN实现,主要依据就是 RN type、 RN Uu/Un接口 可用 cell确定 RN Uu/Un接口可配 cell。
比如, 如果 RN type为 "需要资源划分" , 那么和 RN Un接口隔 离度不能满足要求的 Uu接口可用 cell则不能配置为 RN Uu可用 cdl。
其中, Uu接口的可配 cell的确定依据主要是 RN type。
4 ) 由 RN向 DeNB上报 Un接口可配 cell
RN通过 RRC信令向 RN上报 Un接口可配 cell, DeNB根据 RN上报 的 cell以及业务需求为 RN配置 Un接口实际工作的 cell。
此外, RN向 DeNB上报 Un接口可配 cell的同时还可以携带 RN type , RN上报 Un接口可配 cell可以和 RN type上报使用同一条 RRC信 令, 也可以使用不同的 RRC信令。
需要说明的是如果有需要, 在后续过程中允许 RN修改 RN type和 Uu/Un可配载波资源, 比如 Un接口 UL拥塞, Uu接口资源充裕的情况, 这样的变化并不影响本发明的保护范围。 在具体的应用场景中, 本发明实施例进一步给出以下实施例, 如 图 6所示, 包括以下步骤:
步骤 S601、 RN获取 RN OAM配置信息。
在 RN启动的第一 P介段, RN按照 UE的方式附着到网络, 从 RN的 OAM下载初始配置信息, 然后去附着。 其中 RN OAM信息至少包括 RN和 R-UE之间 Uu接口可聚合 cell集合, 以及 RN允许接入的 donor cell 列表;
步骤 S602、 RN确定要接入的 donor cdl。
RN从 RN OAM配置的 donor cell列表中随机或者按照某种规则选 择一个 cell , 作为 donor cell。
步骤 S603、 RN确定 Un接口可用 cell集合 Gun_pre。
RN首先确定步骤 S602中选择的 donor cell归属哪个 DeNB , 然后
RN从 RN 0&M配置的 donor cell列表中选择出归属同一个 DeNB的所 有 cell, 这些 cell作为 Un接口可用 cell备选集合 Gun_pre。
步骤 S604、 RN确定 Uu接口可用 cell集合 Guu_pre。
直接使用 RN Q&M配置的 Uu接口可聚合 cell集合作为 RN在 Uu接 口可用 cell集合 Guu_pre即可。
步骤 S605、 RN确定自身的 RN type。
RN根据上述步骤确定的 Uu接口可用 cell集合 Guu_pre、 Un可用 cell备选集合 Gun_pre以及 RN自身软 /硬件能力确定 RN类型,确定原则 如下:
( 1 )如果 RN软 /硬件能力只支持资源划分, RN type就可以确定 为 "需要资源划分" ;
( 2 )如果 RN软 /硬件能力只支持不需要资源划分, 那么 RN type 就可以确定为 "不需要资源划分" ;
( 3 )如果 RN软 /硬件能力即支持资源划分又支持不进行资源划 分, 那么:
如果 Guu_pre包含的 cell和 Gun_pre包含的 cell之间都不满足不进 行资源划分的要求, 那么 RN type只能选择 "需要资源划分" ;
如果 Guu_pre包含的 cell和 Gun_pre包含的 cell之间只有部分可以 满足不进行资源划分的要求, 那么 RN type即可以选择 "需要资源划 分" , 也可以选择 "不需要资源划分" , 具体选择取决于 RN实现;
如果 Guu_pre包含的 cell和 Gun—pre包含的 cell之间全部都满足不 进行资源划分的要求, 那么 RN type即可以选择 "不需要资源划分" ; 步骤 S606、 RN确定 RN Uu接口可配 cell集合 Guu。
RN根据 RN type以及 Uu接口 Guu_pre和 Gun_pre确定 RN Uu接口 可配 cell集合 Guu, 具体如何确定取决于 RN实现, RN可以将 Guu_pre 全部作为 Guu, 也可以选择一部分作为 Guu。
步骤 S607、 RN确定 RN Un接口可配 cell集合 Gun。
由 RN通过某种实现方式确定 Gun , 比如 RN可以通过如下方式确 定 Gun:
RN type为 "不需要资源划分" , 那么 RN从 Gun_pre中选择和 Guu 中所有 cell都满足不需要资源划分要求的 cell作为 Gun即可。
RN type为 "需要资源划分" , 那么 RN从 Gun_pre中选择和 Guu 中任何一个 cell不满足隔离度要求的 cell作为 Gun即可。
步骤 S608、 RN将 RN type和 Gun通过 RRC信令通知 DeNB。
Gun即 DeNB和 RN之间的可配置 cell集合。
步骤 S609、 DeNB根据 Gun为 RN分配 Un接口资源。
与现有技术相比, 本发明实施例具有以下优点:
通过应用本发明实施例的技术方案, 中继节点可以确定 Un接口 当前可供分配的小区信息, 并将该信息上报给基站, 使基站可以据此 为中继节点分配相应的 Un接口资源, 从而, 使基站侧能够准确的获 取到中继节点当前所对应的可供分配的 Un接口的小区资源信息, 解 决了现有技术中基站直接分配的 Un接口资源与中继节点不匹配而导 致的载波聚合场景下的中继节点无法正常工作的问题。 为了实现本发明实施例的技术方案,本发明实施例还提出了一种 中继节点, 其结构示意图如图 7所示, 具体包括:
获耳 ^莫块 71 , 用于获取 Un接口的可用小区的信息;
类型确定模块 72, 用于根据获取模块 71所获取的 Un接口的可用 小区的信息, 确定中继节点的中继节点类型;
信息确定模块 73, 用于根据获取模块 71所获取的 Un接口的可用 小区的信息, 以及类型确定模块 72所确定的中继节点类型, 确定中继 节点的 Un接口当前可供分配的小区的信息;
发送模块 74, 用于将信息确定模块 73所确定的 Un接口当前可供 分配的小区的信息发送给中继节点所归属的基站, 以使基站根据 Un 接口当前可供分配的小区的信息为中继节点分配 Un接口的资源。
在具体的应用场景中, 获取模块 71具体用于:
根据从中继节点的 OAM下载的小区列表信息, 确定各小区和中 继节点所归属的基站之间的归属关系;
当一个小区与中继节点所接入的小区归属于同一个基站时,确定 小区为中继节点的 Un接口的可用小区。
另一方面, 获耳 ^莫块 71 , 还用于根据从中继节点的 OAM下载的 Uu接口的小区列表信息,获取中继节点的 Uu接口的可用小区的信息。
在实际应用中, 类型确定模块 72, 具体用于根据 Un接口的可用 小区的信息, Uu接口的可用小区的信息, 以及中继节点的软 /硬件能 力信息, 确定中继节点的中继节点类型。
根据实际的应用场景, 类型确定模块 72, 具体用于:
当中继节点自身的软 /硬件能力信息只支持资源划分时, 确定中 继节点的中继节点类型为需要资源划分;
当中继节点自身的软 /硬件能力信息只支持不需要资源划分时, 确定中继节点的中继节点类型为不需要资源划分;
当中继节点自身的软 /硬件能力信息同时支持资源划分和不需要 资源划分, 且 Un接口的可用小区的信息和 Uu接口的可用小区的信息 所对应的小区都不满足不进行资源划分的要求时,确定中继节点的中 继节点类型为需要资源划分;
当中继节点自身的软 /硬件能力信息同时支持资源划分和不需要 资源划分, 且 Un接口的可用小区的信息和 Uu接口的可用小区的信息 所对应的小区中有一部分满足不进行资源划分的要求时,根据中继节
点的需求,确定中继节点的中继节点类型为需要资源划分或不需要资 源划分;
当中继节点自身的软 /硬件能力信息同时支持资源划分和不需要 资源划分, 且 Un接口的可用小区的信息和 Uu接口的可用小区的信息 所对应的小区都满足不进行资源划分的要求时,确定中继节点的中继 节点类型为不需要资源划分。
在实际应用中, 信息确定模块 73, 还用于用于根据类型确定模块 72所确定的中继节点类型, 确定中继节点的 Uu接口当前可供分配的 小区的信息。
需要进一步指出的是, 发送模块 74, 具体用于:
通过 RRC消息向自身所归属的基站上报 Un接口当前可供分配的 小区的信息, 以 站根据 Un接口当前可供分配的小区的信息和当 前的业务需求为中继节点分配 Un接口的资源。
其中, 发送模块 74, 还用于通过 RRC消息向自身所归属的基站上 报中继节点的中继节点类型, 该 RRC消息可以与上报 Un接口当前可 供分配的小区的信息是同一条 RRC消息, 也可以是其他 RRC消息。 另一方面, 本发明实施例还提供了一种基站, 其结构示意图如图 8所示, 包括:
接收模块 81 , 用于接收中继节点发送的 Un接口当前可供分配的 小区的信息;
分配模块 82, 用于根据接收模块 81所接收的 Un接口当前可供分 配的小区的信息为中继节点分配 Un接口的资源。
在具体的应用场景中,接收模块 81 , 具体用于接收中继节点通过 RRC消息发送的 Un接口当前可供分配的小区的信息。
与现有技术相比, 本发明实施例具有以下优点:
通过应用本发明实施例的技术方案, 中继节点可以确定 Un接口 当前可供分配的小区信息, 并将该信息上报给基站, 使基站可以据此 为中继节点分配相应的 Un接口资源, 从而, 使基站侧能够准确的获
取到中继节点当前所对应的可供分配的 Un接口的小区资源信息, 解 决了现有技术中基站直接分配的 Un接口资源与中继节点不匹配而导 致的载波聚合场景下的中继节点无法正常工作的问题。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解 到本发明可借助软件加必需的通用硬件平台的方式来实现, 当然也可 以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解, 软件产品的形式体现出来, 该计算机软件产品存储在一个存储介质 中, 包括若干指令用以使得一台计算机设备(可以是个人计算机, 服 务器, 或者网络设备等)执行本发明各个实施例所述的方法。
本领域技术人员可以理解附图只是一个优选实施例的示意图,附 图中的模块或流程并不一定是实施本发明所必须的。
本领域技术人员可以理解实施例中的装置中的模块可以按照实 施例描述进行分布于实施例的装置中,也可以进行相应变化位于不同 于本实施例的一个或多个装置中。上述实施例的模块可以合并为一个 模块, 也可以进一步拆分成多个子模块。
上述本发明实施例序号仅仅为了描述, 不代表实施例的优劣。 以上公开的仅为本发明的几个具体实施例, 但是, 本发明并非局 限于此,任何本领域的技术人员能思之的变化都应落入本发明的保护 范围。
Claims
1、 一种载波聚合场景下中继节点的资源分配方法, 其特征在于, 包括:
中继节点获取 Un接口的可用小区的信息;
所述中继节点根据所述 Un接口的可用小区的信息, 确定自身的 中继节点类型;
所述中继节点根据 Un接口的可用小区的信息, 以及所述中继节 点类型, 确定自身的 Un接口当前可供分配的小区的信息;
所述中继节点将确定的所述 Un接口当前可供分配的小区的信息 发送给自身所归属的基站, 以使所述基站根据所述 Un接口当前可供 分配的小区的信息为所述中继节点分配 Un接口的资源。
2、 如权利要求 1所述的方法, 其特征在于, 所述中继节点获取 Un接口的可用小区的信息, 具体为:
所述中继节点根据从中继节点的 OAM下载的小区列表信息, 确 定各小区和所述中继节点所归属的基站之间的归属关系;
当一个小区与所述中继节点所接入的小区归属于同一个基站时, 所述中继节点确定所述小区为自身的 Un接口的可用小区。
3、 如权利要求 1所述的方法, 其特征在于, 所述中继节点获取 Un接口的可用小区的信息, 还包括:
所述中继节点获取 Uu接口的可用小区的信息。
4、 如权利要求 3所述的方法, 其特征在于, 所述中继节点获取 Uu接口的可用小区的信息, 具体为:
所述中继节点根据从中继节点的 OAM下载的 Uu接口的小区列 表信息, 获取自身的 Uu接口的可用小区的信息。
5、 如权利要求 3所述的方法, 其特征在于, 所述中继节点根据 所述 Un接口的可用小区的信息,确定自身的中继节点类型,具体为: 所述中继节点根据所述 Un接口的可用小区的信息, 所述 Uu接 口的可用小区的信息, 以及自身的软 /硬件能力信息, 确定自身的中 继节点类型。
6、 如权利要求 5所述的方法, 其特征在于, 所述中继节点根据 所述 Un接口的可用小区的信息,确定自身的中继节点类型,具体为: 当所述中继节点自身的软 /硬件能力信息只支持资源划分时, 所 述中继节点确定自身的中继节点类型为需要资源划分;
当所述中继节点自身的软 /硬件能力信息只支持不需要资源划分 时, 所述中继节点确定自身的中继节点类型为不需要资源划分;
当所述中继节点自身的软 /硬件能力信息同时支持资源划分和不 需要资源划分, 且所述 Un接口的可用小区的信息和所述 Uu接口的 可用小区的信息所对应的小区都不满足不进行资源划分的要求时,所 述中继节点确定自身的中继节点类型为需要资源划分;
当所述中继节点自身的软 /硬件能力信息同时支持资源划分和不 需要资源划分, 且所述 Un接口的可用小区的信息和所述 Uu接口的 可用小区的信息所对应的小区中有一部分满足不进行资源划分的要 求时, 所述中继节点根据自身的需求, 确定自身的中继节点类型为需 要资源划分或不需要资源划分;
当所述中继节点自身的软 /硬件能力信息同时支持资源划分和不 需要资源划分, 且所述 Un接口的可用小区的信息和所述 Uu接口的 可用小区的信息所对应的小区都满足不进行资源划分的要求时,所述 中继节点确定自身的中继节点类型为不需要资源划分。
7、 如权利要求 1所述的方法, 其特征在于, 所述中继节点根据 所述 Un接口的可用小区的信息, 确定自身的中继节点类型之后, 还 包括:
所述中继节点根据所述中继节点类型, 确定自身的 Uu接口当前 可供分配的小区的信息。
8、 如权利要求 1所述的方法, 其特征在于, 所述中继节点将确 定的所述 Un接口当前可供分配的小区的信息发送给自身所归属的基 站, 以使所述基站根据所述 Un接口当前可供分配的小区的信息为所 述中继节点分配 Un接口的资源, 具体为: 所述中继节点通过 RRC 消息向自身所归属的基站上报所述 Un 接口当前可供分配的小区的信息;
所述基站根据所述 Un接口当前可供分配的小区的信息和当前的 业务需求为所述中继节点分配 Un接口的资源。
9、 如权利要求 8所述的方法, 其特征在于, 所述中继节点通过 RRC消息向自身所归属的基站上报所述 Un接口当前可供分配的小区 的信息的同时, 还包括:
所述中继节点通过 RRC消息向自身所归属的基站上报自身的中 继节点类型。
10、 一种中继节点, 其特征在于, 包括:
获耳^莫块, 用于获取 Un接口的可用小区的信息;
类型确定模块, 用于根据所述获取模块所获取的 Un接口的可用 小区的信息, 确定所述中继节点的中继节点类型;
信息确定模块, 用于根据所述获取模块所获取的 Un接口的可用 小区的信息, 以及所述类型确定模块所确定的中继节点类型, 确定所 述中继节点的 Un接口当前可供分配的小区的信息;
发送模块, 用于将所述信息确定模块所确定的所述 Un接口当前 可供分配的小区的信息发送给所述中继节点所归属的基站,以使所述 基站根据所述 Un接口当前可供分配的小区的信息为所述中继节点分 配 Un接口的资源。
11、 如权利要求 10所述的中继节点, 其特征在于, 所述获取模 块, 具体用于:
根据从中继节点的 OAM下载的小区列表信息, 确定各小区和所 述中继节点所归属的基站之间的归属关系;
当一个小区与所述中继节点所接入的小区归属于同一个基站时, 确定所述小区为所述中继节点的 Un接口的可用小区。
12、 如权利要求 10所述的中继节点, 其特征在于, 所述获取模 块,还用于根据从中继节点的 OAM下载的 Uu接口的小区列表信息, 获取所述中继节点的 Uu接口的可用小区的信息。
13、 如权利要求 12所述的中继节点, 其特征在于, 所述类型确 定模块, 具体用于:
根据所述 Un接口的可用小区的信息, 所述 Uu接口的可用小区 的信息, 以及所述中继节点的软 /硬件能力信息, 确定所述中继节点 的中继节点类型。
14、 如权利要求 13所述的中继节点, 其特征在于, 所述类型确 定模块, 具体用于:
当所述中继节点自身的软 /硬件能力信息只支持资源划分时, 确 定所述中继节点的中继节点类型为需要资源划分;
当所述中继节点自身的软 /硬件能力信息只支持不需要资源划分 时, 确定所述中继节点的中继节点类型为不需要资源划分;
当所述中继节点自身的软 /硬件能力信息同时支持资源划分和不 需要资源划分, 且所述 Un接口的可用小区的信息和所述 Uu接口的 可用小区的信息所对应的小区都不满足不进行资源划分的要求时,确 定所述中继节点的中继节点类型为需要资源划分;
当所述中继节点自身的软 /硬件能力信息同时支持资源划分和不 需要资源划分, 且所述 Un接口的可用小区的信息和所述 Uu接口的 可用小区的信息所对应的小区中有一部分满足不进行资源划分的要 求时, 根据所述中继节点的需求, 确定所述中继节点的中继节点类型 为需要资源划分或不需要资源划分;
当所述中继节点自身的软 /硬件能力信息同时支持资源划分和不 需要资源划分, 且所述 Un接口的可用小区的信息和所述 Uu接口的 可用小区的信息所对应的小区都满足不进行资源划分的要求时,确定 所述中继节点的中继节点类型为不需要资源划分。
15、 如权利要求 10所述的中继节点, 其特征在于, 所述信息确 定模块, 还用于用于根据所述类型确定模块所确定的中继节点类型, 确定所述中继节点的 Uu接口当前可供分配的小区的信息。
16、 如权利要求 10所述的中继节点, 其特征在于, 所述发送模 块, 具体用于:
通过 RRC消息向自身所归属的基站上报所述 Un接口当前可供分 配的小区的信息, 以使所述基站根据所述 Un接口当前可供分配的小 区的信息和当前的业务需求为所述中继节点分配 Un接口的资源。
17、 如权利要求 16所述的中继节点, 其特征在于, 所述发送模 块, 还用于:
通过 RRC消息向自身所归属的基站上报所述中继节点的中继节 点类型。
18、一种载波聚合场景下中继节点的资源分配方法,其特征在于, 包括:
基站接收中继节点发送的 Un接口当前可供分配的小区的信息; 所述基站根据所述 Un接口当前可供分配的小区的信息为所述中 继节点分配 Un接口的资源。
19、 如权利要求 18所述的方法, 其特征在于, 所述基站接收中 继节点发送的 Un接口当前可供分配的小区的信息, 具体为:
所述基站接收所述中继节点通过 RRC消息发送的 Un接口当前可 供分配的小区的信息。
20、 一种基站, 其特征在于, 包括:
接收模块, 用于接收中继节点发送的 Un接口当前可供分配的小 区的信息;
分配模块, 用于根据所述接收模块所接收的 Un接口当前可供分 配的小区的信息为所述中继节点分配 Un接口的资源。
21、 如权利要求 20所述的基站, 其特征在于, 所述接收模块, 具体用于:
接收所述中继节点通过 RRC消息发送的 Un接口当前可供分配的 小区的信息。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11832052.2A EP2629577B1 (en) | 2010-10-15 | 2011-10-14 | Resource allocation method and apparatus for relay node under the condition of carrier aggregation |
US13/691,744 US9807745B2 (en) | 2010-10-15 | 2012-12-01 | Resource allocation method and apparatus for relay node under the condition of carrier aggregation |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201010515839.0A CN102457965B (zh) | 2010-10-15 | 2010-10-15 | 载波聚合场景下中继节点的资源分配方法和设备 |
CN201010515839.0 | 2010-10-15 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/691,744 Continuation US9807745B2 (en) | 2010-10-15 | 2012-12-01 | Resource allocation method and apparatus for relay node under the condition of carrier aggregation |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012048655A1 true WO2012048655A1 (zh) | 2012-04-19 |
Family
ID=45937906
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/080772 WO2012048655A1 (zh) | 2010-10-15 | 2011-10-14 | 载波聚合场景下中继节点的资源分配方法和设备 |
Country Status (4)
Country | Link |
---|---|
US (1) | US9807745B2 (zh) |
EP (1) | EP2629577B1 (zh) |
CN (1) | CN102457965B (zh) |
WO (1) | WO2012048655A1 (zh) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9025478B2 (en) | 2011-08-16 | 2015-05-05 | Google Technology Holdings LLC | Self-interference handling in a wireless communication terminal supporting carrier aggregation |
BR112016002006A2 (pt) | 2013-08-05 | 2017-08-01 | Fujitsu Ltd | método e aparelho e sistema de configuração de rede |
CN111107606B (zh) * | 2019-01-18 | 2021-07-20 | 维沃软件技术有限公司 | 接口可用性上报、指示方法和设备 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101043640A (zh) * | 2006-03-23 | 2007-09-26 | 华为技术有限公司 | 一种演进网络中无线资源管理信息获取方法及*** |
CN101784075A (zh) * | 2009-01-21 | 2010-07-21 | 大唐移动通信设备有限公司 | 一种配置测量间隙的方法、基站和终端 |
CN101860870A (zh) * | 2010-05-26 | 2010-10-13 | 北京邮电大学 | 用于固定中继的蜂窝通信***的频率规划方法及*** |
Family Cites Families (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100975698B1 (ko) * | 2005-06-13 | 2010-08-12 | 삼성전자주식회사 | 셀룰러 통신을 위한 중계통신 시스템 및 방법 |
KR100961743B1 (ko) * | 2005-12-09 | 2010-06-07 | 삼성전자주식회사 | 다중 홉 중계방식의 광대역 무선 접속통신시스템에서 중계서비스를 지원하기 위한 장치 및 방법 |
CN101170797B (zh) * | 2006-10-25 | 2012-03-14 | 诺基亚西门子网络两合公司 | 利用中继站协助处理用户终端的请求的方法及装置 |
KR101498057B1 (ko) * | 2008-08-22 | 2015-03-03 | 엘지전자 주식회사 | 릴레이 시스템을 지원하기 위한 프리엠블 전송방법 |
US9007992B2 (en) * | 2008-11-18 | 2015-04-14 | Nokia Corporation | Relaying in a communication system |
US8989007B2 (en) * | 2009-01-30 | 2015-03-24 | Nokia Siemens Networks Oy | Load balancing in relay-enhanced access networks |
US8532015B2 (en) * | 2009-02-20 | 2013-09-10 | Nokia Siemens Networks Oy | Methods and apparatuses for transmitting downlink control signaling on wireless relay link |
US8553575B2 (en) * | 2009-03-19 | 2013-10-08 | Qualcomm Incorporated | Resource partitioning for uplink in a wireless communication network |
US9084150B2 (en) * | 2009-03-20 | 2015-07-14 | Telefonaktiebolaget L M Ericsson (Publ) | Signaling mechanisms for network-relay interface with reduced overhead |
US9265053B2 (en) * | 2009-04-06 | 2016-02-16 | Futurewei Technologies, Inc. | System and method for assigning backhaul resources |
KR100968037B1 (ko) * | 2009-04-21 | 2010-07-07 | 엘지전자 주식회사 | 무선 통신 시스템에서 무선 베어러를 관리하는 방법 및 장치 |
US9154352B2 (en) * | 2009-04-21 | 2015-10-06 | Qualcomm Incorporated | Pre-communication for relay base stations in wireless communication |
EP2465313A4 (en) * | 2009-08-14 | 2016-10-19 | Nokia Technologies Oy | FLEXIBLE WAYS FOR DISPLAYING DOWNLINK UPLINK BACKHAUL SUB-FRAME CONFIGURATIONS IN A RELAY SYSTEM |
EP2476284B1 (en) * | 2009-09-09 | 2014-01-15 | Telefonaktiebolaget LM Ericsson (publ) | Methods and apparatuses for interference coordination in a telecommunications system |
CN103188681B (zh) * | 2009-09-28 | 2016-08-10 | 华为技术有限公司 | 数据传输方法、装置及*** |
US8737289B2 (en) * | 2009-10-28 | 2014-05-27 | Lg Electronics Inc. | Method for transmitting and receiving signal of relay in radio communication system supporting multiple carriers |
JP2013513988A (ja) * | 2009-12-10 | 2013-04-22 | 富士通株式会社 | 中継ハンドオーバ制御 |
EP2517519A1 (en) * | 2009-12-22 | 2012-10-31 | Fujitsu Limited | Quality of service control in a relay |
JP2013515421A (ja) * | 2009-12-22 | 2013-05-02 | 富士通株式会社 | リレーノードを使用した通信システムにおける伝送方法 |
WO2011110224A1 (en) * | 2010-03-11 | 2011-09-15 | Nokia Siemens Networks Oy | Optimized signaling in relay-enhanced access networks |
US8620302B2 (en) * | 2010-04-02 | 2013-12-31 | Telefonaktiebolaget Lm Ericsson (Publ) | Configuring relay cell identities in cellular networks |
JP2013524643A (ja) * | 2010-04-02 | 2013-06-17 | インターデイジタル パテント ホールディングス インコーポレイテッド | 中継ノードを介した通信をサポートするための方法および装置 |
WO2011159211A1 (en) * | 2010-06-18 | 2011-12-22 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and nodes for probing types of interfaces |
WO2012002854A1 (en) * | 2010-06-30 | 2012-01-05 | Telefonaktiebolaget L M Ericsson (Publ) | Reduction of interference in relay systems |
WO2012019651A1 (en) * | 2010-08-13 | 2012-02-16 | Nokia Siemens Networks Oy | Enhancements to support mobility load balancing for relay |
US8538325B2 (en) * | 2010-09-17 | 2013-09-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Monitoring cellular radio access node performance |
US8743772B2 (en) * | 2010-10-01 | 2014-06-03 | Qualcomm Incorporated | Mobility load balancing and resource status report for scenarios with relay nodes |
EP2652997A4 (en) * | 2010-12-17 | 2017-01-04 | Nokia Solutions and Networks Oy | Dynamic configuration of relay nodes in a cellular communication system |
US9066242B2 (en) * | 2011-01-14 | 2015-06-23 | Telefonaktiebolaget L M Ericsson (Publ) | Method and device for distinguishing between relay types |
-
2010
- 2010-10-15 CN CN201010515839.0A patent/CN102457965B/zh active Active
-
2011
- 2011-10-14 EP EP11832052.2A patent/EP2629577B1/en active Active
- 2011-10-14 WO PCT/CN2011/080772 patent/WO2012048655A1/zh active Application Filing
-
2012
- 2012-12-01 US US13/691,744 patent/US9807745B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101043640A (zh) * | 2006-03-23 | 2007-09-26 | 华为技术有限公司 | 一种演进网络中无线资源管理信息获取方法及*** |
CN101784075A (zh) * | 2009-01-21 | 2010-07-21 | 大唐移动通信设备有限公司 | 一种配置测量间隙的方法、基站和终端 |
CN101860870A (zh) * | 2010-05-26 | 2010-10-13 | 北京邮电大学 | 用于固定中继的蜂窝通信***的频率规划方法及*** |
Non-Patent Citations (1)
Title |
---|
See also references of EP2629577A4 * |
Also Published As
Publication number | Publication date |
---|---|
US9807745B2 (en) | 2017-10-31 |
US20130182635A1 (en) | 2013-07-18 |
EP2629577A4 (en) | 2017-02-08 |
CN102457965A (zh) | 2012-05-16 |
EP2629577A1 (en) | 2013-08-21 |
CN102457965B (zh) | 2014-06-18 |
EP2629577B1 (en) | 2021-01-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR102175874B1 (ko) | Ue-ambr을 구성하는 방법 | |
US20220225264A1 (en) | Apparatus and method for service subscription through e2 interface in radio access network communication system | |
US9838935B2 (en) | Method and apparatus for assigning data to split bearers in dual connectivity | |
CN109150388B (zh) | 支持pdcp重复功能的***、数据传输方法及网络设备 | |
US10728882B2 (en) | Method for allocating aggregate maximum bit rate of UE, method for allocating aggregate bit rates of non-GBR services and base stations | |
US10206219B2 (en) | Base station apparatus and resource management method and data processing method in wireless communication system | |
WO2012094963A1 (zh) | 一种配置小区信息的方法和装置 | |
JP2022551602A (ja) | 無線アクセスネットワーク通信システムにおけるe2インタフェースを介するサービス加入のための装置及び方法 | |
KR102211470B1 (ko) | 듀얼 커넥티비티 하에서 무선 연결 재설정을 수행하는 방법 및 장치 | |
CN107079382B (zh) | 支持多无线电接入技术的方法和装置 | |
WO2014063542A1 (zh) | 一种载波聚合中管理辅小区的方法和装置 | |
WO2012100626A1 (zh) | 一种基于中继设备切换的资源处理方法和设备 | |
CN114946270A (zh) | 无线接入网络中包括小区信息的e2接口配置的装置和方法 | |
US11356985B2 (en) | Method for establishing evolved packet system bearer and base station | |
KR20220162695A (ko) | 무선 통신 시스템들에서의 동적 스펙트럼 공유 | |
CN107437985A (zh) | 一种建立演进分组***承载的方法及基站 | |
WO2014146261A1 (zh) | 接入控制方法、接入方法、装置、基站、用户设备和实体 | |
WO2012048655A1 (zh) | 载波聚合场景下中继节点的资源分配方法和设备 | |
WO2011153927A1 (zh) | 一种资源状态过程的映射方法和设备 | |
WO2018076887A1 (zh) | 多模式深度融合的方法、装置及基站 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11832052 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011832052 Country of ref document: EP |