WO2011150555A1 - 网络节点间负荷分担的方法、系统和网络设备 - Google Patents

网络节点间负荷分担的方法、系统和网络设备 Download PDF

Info

Publication number
WO2011150555A1
WO2011150555A1 PCT/CN2010/073448 CN2010073448W WO2011150555A1 WO 2011150555 A1 WO2011150555 A1 WO 2011150555A1 CN 2010073448 W CN2010073448 W CN 2010073448W WO 2011150555 A1 WO2011150555 A1 WO 2011150555A1
Authority
WO
WIPO (PCT)
Prior art keywords
load
sharing
node
network
neighboring
Prior art date
Application number
PCT/CN2010/073448
Other languages
English (en)
French (fr)
Inventor
刘霖
王继承
程翔
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to PCT/CN2010/073448 priority Critical patent/WO2011150555A1/zh
Publication of WO2011150555A1 publication Critical patent/WO2011150555A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/08Load balancing or load distribution
    • H04W28/086Load balancing or load distribution among access entities
    • H04W28/0861Load balancing or load distribution among access entities between base stations

Definitions

  • a UMTS (Universal Mobile Telecommunications System) system is a third-generation mobile communication system using WCDMA (Wideband Code Division Multiple Access) technology, and therefore UMTS is usually also adopted.
  • the system is called a WCDMA system.
  • the UMTS system uses a similar structure to the second generation mobile communication system, including RAN (Radio Access Network) and CN (Core Network).
  • the wireless access network handles all wireless-related functions.
  • the core network handles all voice calls and data connections in the UMTS system and implements switching and routing functions with external networks.
  • the CN is logically divided into a CS domain (circuit switched domain) and a PS domain (Packet Switched Domain) against UTRAN (Universal Terrestrial Radio Access Network), CN and UE ( User Equipment, User Equipment) constitutes the entire UMTS system.
  • Figure 1 is a structural diagram of UTRAN in the prior art, the UTRAN contains one or more RNS (Radio Network Subsystem); one RNS is controlled by one RNC (Radio Network Controller (Radio Network Controller) and one or more NodeBs (Nodes, ie, base stations).
  • the interface between the RNC and the CN is the Iu interface.
  • the NodeB and the RNC are connected through the Iub interface, and the RNCs are connected through the lur interface.
  • the lur interface can be connected through a direct physical connection between the RNCs or through a transport network.
  • the RNC allocates and controls the radio resources of the associated NodeB and the associated NodeB.
  • the NodeB performs data flow conversion between the Iub interface and the Uu interface, and also performs wireless Resource Management.
  • RNC is used to control the UTRAN radio resources, mainly to complete RRC (Radio Resource
  • Radio resource control Connection establishment and release, handover, macro-level merging, radio resource management, etc., as follows:
  • Radio resource management and control functions such as macro diversity combining, power control, and radio bearer allocation.
  • HSPA High Speed Packet Access
  • the data throughput rate is getting higher and higher, and the capacity demand for RNC is getting higher and higher, especially HSPA+ (Evolved High Speed Packet Access, evolved).
  • HSPA+ Evolved High Speed Packet Access, evolved.
  • the capacity of the RNC is higher, and the capacity of the RNC is also getting larger.
  • Due to the natural distribution and mobility of users, the RNC accessed by the UE has a large randomness, which may cause some RNCs to operate at a high load in a short period of time. This will inevitably affect the efficiency of the RNC and the data rate of the user, and dynamically consider the inter-RNC.
  • Load sharing is becoming more and more important.
  • load balancing and load sharing between RNCs are based on the premise that all RNCs can share resources.
  • the RNC defaults and its neighboring RNCs provide resource sharing unconditionally.
  • the RNC is overloaded, the user is migrated to other adjacent RNCs.
  • RNC does not provide resource sharing for some reason, so that RNC unknowingly migrating users to RNCs that do not support resource sharing will cause failure.
  • an effective solution has not been proposed yet.
  • a primary object of the present invention is to provide a method, system and network device for load sharing between network nodes to solve at least the above problems.
  • a method for load sharing between network nodes including: receiving, by a network node, load information of a neighboring node, where the load information includes whether neighboring nodes allow resource sharing; when the network node is overloaded According to the saved information, select adjacent nodes that support resource sharing for load sharing.
  • a network device including: a saving module, configured to receive and save load information of a neighboring node, where the load information includes whether a neighboring node allows resource sharing; and a load sharing module, configured to: When the load is overloaded, the neighboring nodes that support resource sharing are selected according to the saved information for load sharing.
  • a system for load sharing between network nodes including a network node and a plurality of neighboring nodes of a network node, the neighboring node is configured to send load information to the network node, where the load information includes adjacent Whether the node allows resource sharing; the network node includes: a saving module, configured to receive and save load information; and a load sharing module, when used for load overload, selects adjacent nodes that support resource sharing according to the saved information to perform load sharing.
  • FIG. 2 is a flowchart of a method for load sharing between network nodes according to Embodiment 1 of the present invention
  • FIG. 3 is an inter-RNC pass according to Embodiment 2 of the present invention
  • FIG. 4 is a flowchart of exchanging load information between load information messages between eNodeBs according to Embodiment 3 of the present invention
  • FIG. 5 is a core network exchange between RNCs according to Embodiment 4 of the present invention.
  • FIG. 6 is a flowchart of a method for load sharing between network nodes according to Embodiment 5 of the present invention
  • FIG. 7 is a structural block diagram of a network device according to Embodiment 6 of the present invention
  • FIG. 8 is an implementation of the present invention.
  • Example 7 is a system block diagram of load sharing between network nodes.
  • the radio access network includes a plurality of network nodes, for example: In a UMTS system, a plurality of radio network controllers RNC are included, and RNCs are connected through an Iu interface or an Iur interface; in an LTE system, a plurality of evolved Node Bs (eNodeBs) are included. ).
  • the connection relationship between the network nodes follows the relevant communication protocol.
  • FIG. 2 is a flowchart of a method for load sharing between network nodes according to an embodiment of the present invention.
  • the method includes: Step S202: A network node receives and stores load information of a neighboring node, where the load information includes neighboring Whether the node allows resource sharing; the neighboring node may send the load information by one of the following messages: a public measurement 4 report message, a load information message, a relocation request message, or a relocation request confirmation message.
  • the neighboring nodes that support resource sharing are selected according to the saved information to perform load sharing.
  • the load information sent by the neighboring nodes is usually in units of cells.
  • the load information provided by the neighboring nodes further includes: load information at the network element level, that is, Transmission resources, processor load conditions, etc. may be in units of RNC.
  • the neighboring node that supports resource sharing may be selected first; the load information according to the network element level (for example, the load information of the network element level and the load information of the cell level) is selected.
  • the neighboring nodes whose resources are shared are selected by the adjacent nodes whose load is less than the threshold to perform load sharing.
  • the foregoing load information may further include: load information of whether the adjacent node is allowed to be moved back; at this time, when the network node performs load sharing, the neighboring node that supports resource sharing may be selected first; Among the adjacent nodes sharing resources, the neighboring nodes that allow the fetching are selected for load sharing. In this case, when the load of the network node returns to normal, the network node and the adjacent node that performs load sharing can perform load fetching, and the user who migrates to the adjacent node is migrated back.
  • the foregoing load information may include: whether the neighboring node allows resource sharing, load information at the network element level, load information of whether the adjacent node is allowed to be moved back, and load information in the related art.
  • the network node can comprehensively consider this information for load sharing.
  • the network node in the related art cannot know whether the neighboring node allows resource sharing.
  • the network element or field
  • the neighboring nodes can provide the resources for sharing, and provide a reliable basis for the load sharing.
  • the network node in this embodiment performs load sharing, it is resolved whether the neighboring nodes provide resources by considering whether neighboring nodes allow resource sharing. The problem of load sharing failure is shared, and the effect of load balancing is reasonably achieved.
  • Embodiment 2 This embodiment describes the load information exchange between RNCs in the UMTS system as an example, where the RNC passes the public measurement.
  • the process of exchanging load information is as shown in FIG. 3: Step S302: The RNC1 initiates a public measurement report initiation request message to the RNC2, requesting the RNC2 to perform some common measurement. Step S304, after the RNC2 is ready to be completed, returning the public measurement to the RNC1.
  • step S306 After the RNC2 reaches the measurement reporting condition, the RNC1 sends a common measurement report message to the RNC1, where the corresponding measurement information is carried, for example, including RNC-level load information, and whether resource sharing is allowed and/or whether the migration load is allowed;
  • RNC1 After receiving the public measurement report of RNC2, RNC1 can obtain the load status of RNC2, and whether the RNC2 allows resource sharing and whether the load of the return load is allowed.
  • the RNC exchanges load information through a common measurement report, and the method is simple, and no new signaling is added, so that reliable data is provided for load sharing.
  • Embodiment 3 This embodiment uses the load information exchange between the eNodeBs in the LTE system as an example. The flow of the load information is exchanged between the eNodeBs through the load information message, as shown in FIG. 4: Step S402, the eNodeB2 sends the information to the eNodeB1.
  • Load information message where the load information of the eNodeB level, and whether resource sharing is allowed and/or whether the backhaul load is allowed;
  • the eNodeB1 can obtain the load status of the eNodeB2, and whether the eNodeB2 allows resource sharing and whether the backhaul load information is allowed.
  • the eNodeB exchanges load information through the load information message, and the method is simple, and no new signaling is added, so that reliable data is provided for load sharing.
  • Embodiment 4 This embodiment is described by taking the load information of the core network between the RNCs in the UMTS system as an example. The process of exchanging load information is as shown in FIG.
  • Step S501 The UE measures 4 reports on the RNC 1; Step S502, the RNC1 decides to initiate the inter-RNC handover according to the measurement of the UE, and initiates an SRNC relocation to the RNC2.
  • step S503 the RNC1 initiates a relocation request message to the CN, requesting to initiate relocation to the RNC2.
  • the message also carries the RNC-level load information of the RNC1, and whether the resource sharing and/or the relocation load is allowed, and the like.
  • step S504 the CN sends a relocation request message to the RNC2, where the load information of the RNC 1 is carried, including the RNC1.
  • step S505 the RNC2 returns a relocation request confirmation to the CN, where the load information of the RNC2 is included, including the RNC-level load information of the RNC2, and whether the permission is allowed.
  • Step S 506 the CN sends a relocation command message to the RNC 1 to notify the UE that the handover can be started, And the RNC 1 re-allocates the UE;
  • Step S509 the RNC2 returns the relocation completion to the CN;
  • S510 the CN sends an Iu release command to the RNC1; in step S511, after the RNC1 completes the release, the Iu release is completed to the CN;
  • Step S512 the UE continues the call normally through the RNC2.
  • step S513 the handover is completed, and the RNC1 and the RNC2 obtain the load information of the other party, including the RNC-level load information, and whether the resource sharing and/or the return load is allowed.
  • the RNC passes through the core network and exchanges load information in the relocation request message or the relocation request confirmation message.
  • the method is simple, and no new signaling is added, so that reliable data is provided for load sharing.
  • Embodiment 5 This embodiment provides a method for load sharing between network nodes. The method may be performed based on the foregoing Embodiment 2-4.
  • This implementation uses load balancing among RNCs in the UMTS system as an example. Referring to FIG. 6, the method is as follows.
  • the method for load sharing includes the following steps: Step S602: The RNC detects the overload of the load; in step S604, the RNC selects a lighter RNC for load sharing according to the stored load status of the neighboring RNC, for example, selecting a load smaller than the pre-load The RNC that sets the threshold performs load sharing; in step S606, the RNC determines whether the selected RNC supports resource sharing according to the stored load information of the neighboring RNC; if not, returns to step S604 to continue to reselect the RNC that can perform load sharing; Supporting, step S608 is performed; step S608, initiating a load sharing process to the selected RNC.
  • the RNC of the present embodiment When the RNC of the present embodiment performs load sharing, it considers whether the adjacent nodes allow resource sharing, and solves the problem that the load sharing fails due to the failure to know whether the adjacent nodes provide resource sharing, thereby achieving the effect of reasonably achieving load balancing.
  • Embodiment 6 This embodiment provides a network device. Referring to FIG. 7, the network device includes: a saving module 72, configured to receive and save load information of neighboring nodes, where the load information includes whether neighboring nodes allow resource sharing.
  • the above received load information can be carried in one of the following messages: Public measurement report message, A load information message, a relocation request message, or a relocation request confirmation message.
  • the load sharing module 74 is connected to the saving module 72.
  • the load information further includes: load information of the network element level; the load sharing module 74 includes: a first selecting unit, configured to select a neighboring node that supports resource sharing; and a first load sharing unit, configured to perform, according to the network element level
  • the load information is selected from the neighboring nodes that support the resource sharing selected by the first selection unit, and the adjacent nodes whose load is less than the threshold value are selected for load sharing.
  • the load information further includes: load information of whether the adjacent node is allowed to be moved back;
  • the load sharing module 74 includes: a second selecting unit, configured to select a neighboring node that supports resource sharing; and a second load sharing unit, connected to the second And a selecting unit, configured to select, from the neighboring nodes that support the resource sharing selected by the second selecting unit, load sharing according to whether the load information of the backing is allowed to be performed.
  • the network node in this embodiment may be the RNC in the foregoing embodiment, or may be the eNodeB in the foregoing embodiment.
  • Embodiment 7 This embodiment provides a system for load sharing between network nodes.
  • the system includes a plurality of adjacent nodes of the network node 82 and the network node 82.
  • multiple adjacent nodes are respectively The adjacent node 84, the adjacent node 86, and the adjacent node 88 are described as an example.
  • the neighboring node 84, the neighboring node 86, or the neighboring node 88 is configured to send load information to the network node 82, where the load information includes whether the neighboring node allows resource sharing; the network node 82 includes: a saving module, configured to: The load information is received and saved.
  • the load sharing module is configured to select a neighboring node that supports resource sharing according to the saved information to perform load sharing according to the saved information.
  • the load information sent by the neighboring nodes is usually in units of cells.
  • the load information provided by the neighboring nodes further includes: load information at the network element level, that is, Transmission resources, processor load conditions, etc. may be in units of RNC.
  • the neighboring nodes that support resource sharing may be selected first; the load information at the network element level (for example, considering the load information of the network element level and the load information of the cell level) from the selected supporting resources.
  • the neighboring nodes whose load is less than the threshold are selected among the shared neighboring nodes for load sharing.
  • the load information may further include: load information of whether the adjacent node is allowed to be moved back; at this time, when the load sharing module performs load sharing, the neighboring node that supports resource sharing may be selected first; The neighboring nodes that support resource sharing select the neighboring nodes that allow the backhaul to perform load sharing.
  • the foregoing load information may include: whether the neighboring node allows resource sharing, load information at the network element level, load information of whether the adjacent node is allowed to be moved back, and load information in the related art.
  • the network node can comprehensively consider this information for load sharing, so as to achieve better load balancing.
  • the network node 82 and the aforementioned neighboring nodes are both radio network controllers or evolved Node Bs.
  • the present invention achieves the following technical effects:
  • the network node in the above embodiment performs load sharing, it is resolved whether the neighboring node provides resource sharing by considering whether neighboring nodes allow resource sharing. Blindly initiates the problem of user migration causing failure, and thus achieves the effect of reasonable load balancing.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.

Landscapes

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

Description

网格节点间负荷分担的方法、 系统和网各设备 技术领域 本发明涉及无线通信领域, 具体而言, 涉及一种网络节点间负荷分担的 方法、 系统和网络设备。 背景技术 现有 UMTS ( Universal Mobile Telecommunications System, 通用移动通 信系统) 系统是釆用 WCDMA ( Wideband Code Division Multiple Access, 宽 带码分多址接入)技术的第三代移动通信系统, 因此通常也把 UMTS系统称 为 WCDMA 系统。 UMTS 系统釆用了与第二代移动通信系统类似的结构, 包括 RAN ( Radio Access Network, 无线接入网) 和 CN ( Core Network, 核 心网)。 其中无线接入网络处理所有与无线相关的功能, 核心网处理 UMTS 系统内所有的语音呼叫和数据连接, 并实现与外部网络的交换和路由功能。 CN从逻辑上分为 CS域 ( Circuit Switched Domain, 电路交换域 ) 和 PS域 ( Packet Switched Domain,分组交换域 )„ UTRAN( Universal Terrestrial Radio Access Network, 通用陆地无线接入网 ), CN与 UE ( User Equipment, 用户 设备) 构成了整个 UMTS系统。 图 1 为现有技术中 UTRAN 的结构图, UTRAN 包含一个或多个 RNS ( Radio Network Subsystem,无线网络子系统;)。一个 RNS由一个 RNC( Radio Network Controller, 无线网络控制器) 和一个或多个 NodeB (节点 B, 即基 站) 组成。 RNC与 CN之间的接口是 Iu接口, NodeB和 RNC通过 Iub接口 连接, RNC之间通过 lur接口相连, lur接口可以通过 RNC之间的直接物理 连接或者通过传输网连接。 RNC 分配和控制与之相连的以及相关的 NodeB 的无线资源。 NodeB完成 Iub接口和 Uu接口之间的数据流转换, 也进行无 线资源管理。 RNC 用于控制 UTRAN 的无线资源, 主要完成 RRC ( Radio Resource
Control, 无线资源控制) 连接建立和释放、 切换、 宏分级合并、 无线资源管 理等功能, 具体如下:
( 1 ) 执行系统信息广播和系统接入控制功能; ( 2 ) 切换和 SRNC ( Source Radio Network Controller, 月艮务无线网络控 制器) 重定位等移动性管理功能;
( 3 ) 宏分集合并、 功率控制、 无线承载分配等无线资源管理和控制功 能。 随着 HSPA ( High Speed Packet Access, 高速分组接入)业务的逐渐普及, 数据吞吐速率越来越高, 对 RNC 的容量需求也越来越高, 特别是 HSPA+ ( Evolved High Speed Packet Access, 演进的高速分组接入)的引入, 对 RNC 容量需求更高, RNC的容量也越故越大。 由于用户自然分布、 移动等原因, UE接入的 RNC存在很大的随机性, 短时间内可能造成某些 RNC高负荷运 行, 这样势必影响 RNC的效率和用户的数据速率, 动态考虑 RNC间的负荷 分担越来越重要。 目前 RNC间进行负荷均衡和负荷分担, 是基于所有 RNC都能进行资源 共享的前提的, RNC默认和其邻接的 RNC都无条件地提供资源共享, 在本 RNC过载时将用户迁移到邻接的其他 RNC, 以减轻本 RNC的负荷。 但在有 些情况下, RNC因为某些原因, 是不提供资源共享的, 这样 RNC在不知情 的情况下将用户迁移到不支持资源共享的 RNC就会造成失败。 针对相关技术中无法获知相邻 RNC 是否提供资源共享而导致负荷分担 失败的问题, 目前尚未提出有效的解决方案。 发明内容 本发明的主要目的在于提供一种网络节点间负荷分担的方法、 系统和网 络设备, 以至少解决上述问题。 根据本发明的一个方面,提供了一种网络节点间负荷分担的方法, 包括: 网络节点接收并保存相邻节点的负荷信息, 该负荷信息包括相邻节点是否允 许资源共享; 网络节点负荷过载时, 根据保存的信息选择支持资源共享的相 邻节点进行负荷分担。 根据本发明的另一方面, 提供了一种网络设备, 包括: 保存模块, 用于 接收并保存相邻节点的负荷信息, 该负荷信息包括相邻节点是否允许资源共 享; 负荷分担模块, 用于负荷过载时, 根据保存的信息选择支持资源共享的 相邻节点进行负荷分担。 根据本发明的又一方面, 提供了网络节点间负荷分担的系统, 包括网络 节点和网络节点的多个相邻节点,该相邻节点用于向网络节点发送负荷信息, 该负荷信息包括相邻节点是否允许资源共享; 该网络节点包括: 保存模块, 用于接收并保存负荷信息; 负荷分担模块, 用于负荷过载时, 根据保存的信 息选择支持资源共享的相邻节点进行负荷分担。 通过本发明, 釆用网络节点进行负荷分担时, 考虑相邻节点是否允许资 源共享, 解决了因无法获知相邻节点是否提供资源共享而盲目发起用户迁移 造成失败的问题, 进而达到了合理实现负载均衡的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是根据相关技术的 UTRAN的结构图; 图 2是 居本发明实施例 1的网络节点间负荷分担的方法流程图; 图 3是根据本发明实施例 2的 RNC间通过公共测量报告交换负荷信息 的流程图; 图 4是根据本发明实施例 3的 eNodeB间通过负荷信息消息交换负荷信 息的流程图; 图 5是才艮据本发明实施例 4的 RNC间核心网交换负荷信息的流程图; 图 6是 居本发明实施例 5的网络节点间负荷分担的方法流程图; 图 7是根据本发明实施例 6的网络设备的结构框图; 以及 图 8是 居本发明实施例 7的网络节点间负荷分担的系统结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。 无线接入网络包括多个网络节点, 例如: 在 UMTS系统中, 包括多个无 线网络控制器 RNC, RNC间通过 Iu接口或者 Iur接口相连; 在 LTE系统中, 包括多个演进的节点 B ( eNodeB )。 网络节点间的连接关系遵循相关通信协 议, 本发明的实施例以该无线接入网络为例进行说明。 实施例 1 图 2示出了 居本发明实施例的网络节点间负荷分担的方法流程图, 该 方法包括: 步骤 S202, 网络节点接收并保存相邻节点的负荷信息, 其中, 负荷信息 包括相邻节点是否允许资源共享; 上述相邻节点可以通过以下消息之一发送该负荷信息: 公共测量 4艮告消 息、 负荷信息消息、 重定位请求消息或重定位要求确认消息。 步骤 S204, 网络节点负荷过载时, 根据保存的信息选择支持资源共享的 相邻节点进行负荷分担。 相关技术相邻节点发送的负荷信息通常是以小区为单位的, 本实施例为 了使网络节点能够更好地进行负荷分担, 相邻节点提供的负荷信息还包括: 网元级别的负荷信息, 即传输资源、 处理器负荷状况等可以是以 RNC 为单 位的。 此时, 网络节点进行负荷分担时, 可以先选择支持资源共享的相邻节 点; 才艮据网元级别的负荷信息 (例如考虑网元级别的负荷信息和小区级别的 负荷信息) 从选择的支持资源共享的相邻节点中再选择负荷小于门限值的相 邻节点进行负荷分担。 优选地, 上述负荷信息还可以包括: 相邻节点是否允许回迁的负荷信息; 此时, 网络节点进行负荷分担时, 可以先选择支持资源共享的相邻节点; 根 据是否允许回迁的负荷信息从支持资源共享的相邻节点中选择允许回迁的相 邻节点进行负荷分担。 这种情况下, 该网络节点的负荷恢复正常时, 该网络 节点与进行负荷分担的相邻节点可以进行负荷回迁, 即将迁移到该相邻节点 的用户再迁移回来。 才艮据上述内容可知, 上述负荷信息可以包括: 相邻节点是否允许资源共 享、 网元级别的负荷信息、 相邻节点是否允许回迁的负荷信息以及相关技术 中的负荷信息等。 这样网络节点就可以综合考虑这些信息进行负荷分担, 达 到更好地实现负载均衡的目的。 相关技术中的网络节点不能获知相邻节点是否允许资源共享, 本实施例 通过在负荷信息中加入 "相邻节点是否允许资源共享,, 这一网元 (或字段) 后, 使网络节点能够得知相邻节点是否允许资源共享, 为进行负荷分担提供 可靠的依据。 本实施例的网络节点进行负荷分担时, 通过考虑相邻节点是否允许资源 共享, 解决了因无法获知相邻节点是否提供资源共享而导致负荷分担失败的 问题, 进而达到合理实现负载均衡的效果。 实施例 2 本实施例以在 UMTS 系统中 RNC间的负荷信息交换为例进行说明, 其 中, RNC间通过公共测量 4艮告交换负荷信息的流程, 如图 3所示: 步骤 S302, RNC1向 RNC2发起公共测量报告发起请求消息,请求 RNC2 进行一些公共测量; 步骤 S304, RNC2准备完成后, 向 RNC1返回公共测量 4艮告发起响应消 息, 报告公共测量初始化准备成功; 步骤 S306, RNC2达到测量上报条件后, 向 RNC1发送公共测量报告消 息, 其中携带相应的测量信息, 例如包括 RNC 级的负荷信息, 以及是否允 许资源共享和 /或是否允许回迁负荷;
RNC1收到 RNC2的公共测量 4艮告后, 可以获得 RNC2的负荷状况, 以 及 RNC2是否允许资源共享, 是否允许回迁负荷的信息。 本实施例 RNC 间通过公共测量报告交换负荷信息, 方法简单, 且没有 增加新的信令, 为进行负荷分担提供了可靠的数据。 实施例 3 本实施例以在 LTE系统中 eNodeB间的负荷信息交换为例进行说明, 其 中, eNodeB间通过负荷信息消息交换负荷信息的流程, 如图 4所示: 步骤 S402, eNodeB2向 eNodeB 1发送负荷信息消息, 其中 eNodeB级的 负荷信息, 以及是否允许资源共享和 /或是否允许回迁负荷; eNodeBl收到 eNodeB2的公共测量 4艮告后, 可以获得 eNodeB2的负荷 状况, 以及 eNodeB2是否允许资源共享, 是否允许回迁负荷的信息。 本实施例 eNodeB 间通过负荷信息消息交换负荷信息, 方法简单, 且没 有增加新的信令, 为进行负荷分担提供了可靠的数据。 实施例 4 本实施例以在 UMTS系统中 RNC间核心网交换负荷信息为例进行说明, 负荷信息的交换过程如图 5所示: 步骤 S 501 , UE向 RNC 1上 4艮测量 4艮告; 步骤 S502, RNC1才艮据 UE的测量 4艮告, 决定发起 RNC间切换, 发起 到 RNC2的 SRNC重定位 ¾ϊ程; 步骤 S503 , RNC1向 CN发起重定位请求消息, 要求发起到 RNC2的重 定位, 消息中还携带有 RNC1 的 RNC级负荷信息, 以及是否允许资源共享 和 /或是否允许回迁负荷等信息; 步骤 S504 , CN向 RNC2发起重定位要求消息, 其中携带 RNC 1的负荷 信息, 包括 RNC1的 RNC级负荷信息, 以及是否允许资源共享和 /或是否允 许回迁负荷等信息; 步骤 S505 , RNC2向 CN返回重定位要求确认, 其中携带 RNC2的负荷 信息, 包括 RNC2的 RNC级负荷信息, 以及是否允许资源共享和 /或是否允 许回迁负荷等信息; 步骤 S 506 , CN向 RNC 1发送重定位命令消息, 通知 UE可以开始切换, 消息中还携带 RNC2返回的负荷信息; 步骤 S 507 , RNC 1对 UE进行重配; 步骤 S508, UE重配完成后向 RNC2返回重配完成消息; 步骤 S509, RNC2向 CN返回重定位完成; 步骤 S510, CN向 RNC1发出 Iu释放命令; 步骤 S511 , RNC1完成释放后, 向 CN返回 Iu释放完成; 步骤 S512, UE通过 RNC2正常继续呼叫; 步骤 S513 , 切换完成, RNC1和 RNC2相互获得对方的负荷信息, 包括 RNC级负荷信息, 以及是否允许资源共享和 /或是否允许回迁负荷等信息。 本实施例 RNC 间通过核心网, 并在重定位请求消息或重定位要求确认 消息中交换负荷信息, 方法简单, 且没有增加新的信令, 为进行负荷分担提 供了可靠的数据。 实施例 5 本实施例提供了一种网络节点间负荷分担的方法, 该方法可以基于上述 实施例 2-4进行, 本实施以在 UMTS 系统中 RNC间实现负荷分担为例, 参 见图 6, 该负荷分担的方法包括以下步骤: 步骤 S602, RNC检测到自身负荷过载; 步骤 S604, RNC根据保存的相邻 RNC的负荷状况, 选择一个负荷较轻 的 RNC进行负荷分担, 例如, 选择一个负荷小于预先设定门限的 RNC进行 负荷分担; 步骤 S606, RNC根据保存的相邻 RNC的负荷信息判断选择的 RNC是 否支持资源共享; 如果不支持, 返回步骤 S604, 继续重新选择可以进行负荷 分担的 RNC; 如果支持, 执行步骤 S608; 步骤 S608, 发起到选择的 RNC的负荷分担流程。 本实施例的 RNC 进行负荷分担时, 通过考虑相邻节点是否允许资源共 享, 解决了因无法获知相邻节点是否提供资源共享而导致负荷分担失败的问 题, 进而达到合理实现负载均衡的效果。 实施例 6 本实施例提供了一种网络设备, 参见图 7, 该网络设备包括: 保存模块 72 , 用于接收并保存相邻节点的负荷信息, 其中, 负荷信息包 括相邻节点是否允许资源共享; 上述接收的负荷信息可以携带在以下消息之一中: 公共测量报告消息、 负荷信息消息、 重定位请求消息或重定位要求确认消息。 负荷分担模块 74 , 连接至保存模块 72 , 用于负荷过载时, 根据保存的 信息选择支持资源共享的相邻节点进行负荷分担。 优选地, 上述负荷信息还包括: 网元级别的负荷信息; 负荷分担模块 74 包括: 第一选择单元, 用于选择支持资源共享的相邻节点; 第一负荷分担单 元, 用于根据网元级别的负荷信息从第一选择单元选择的支持资源共享的相 邻节点中选择负荷小于门限值的相邻节点进行负荷分担。 或者, 上述负荷信息还包括: 相邻节点是否允许回迁的负荷信息; 负荷 分担模块 74 包括: 第二选择单元, 用于选择支持资源共享的相邻节点; 第 二负荷分担单元, 连接至第二选择单元, 用于根据是否允许回迁的负荷信息 从第二选择单元选择的支持资源共享的相邻节点中选择允许回迁的相邻节点 进行负荷分担。 本实施例的网络节点可以是上述实施例中的 RNC,也可以是上述实施例 中的 eNodeB。 本实施例的网络节点进行负荷分担时, 通过考虑相邻节点是否允许资源 共享, 解决了因无法获知相邻节点是否提供资源共享而导致负荷分担失败的 问题, 进而达到合理实现负载均衡的效果。 实施例 7 本实施例提供了一种网络节点间负荷分担的系统, 参见图 8, 该系统包 括网络节点 82和网络节点 82的多个相邻节点, 本实施例以多个相邻节点分 别为相邻节点 84、 相邻节点 86和相邻节点 88为例进行说明。 相邻节点 84、 相邻节点 86或相邻节点 88 , 用于向网络节点 82发送负 荷信息, 其中, 负荷信息包括所述相邻节点是否允许资源共享; 网络节点 82包括: 保存模块, 用于接收并保存上述负荷信息; 负荷分担模块, 用于负荷过载时, 根据保存的信息选择支持资源共享的 相邻节点进行负荷分担。 相关技术相邻节点发送的负荷信息通常是以小区为单位的, 本实施例为 了使网络节点能够更好地进行负荷分担, 相邻节点提供的负荷信息还包括: 网元级别的负荷信息, 即传输资源、 处理器负荷状况等可以是以 RNC 为单 位的。 此时, 负荷分担模块进行负荷分担时, 可以先选择支持资源共享的相 邻节点; 居网元级别的负荷信息 (例如考虑网元级别的负荷信息和小区级 别的负荷信息)从选择的支持资源共享的相邻节点中再选择负荷小于门限值 的相邻节点进行负荷分担。 优选地, 上述负荷信息还可以包括: 相邻节点是否允许回迁的负荷信息; 此时, 负荷分担模块进行负荷分担时,可以先选择支持资源共享的相邻节点; 根据是否允许回迁的负荷信息从支持资源共享的相邻节点中选择允许回迁的 相邻节点进行负荷分担。 这种情况下, 该网络节点的负荷恢复正常时, 该网 点的用户再迁移回来。 才艮据上述内容可知, 上述负荷信息可以包括: 相邻节点是否允许资源共 享、 网元级别的负荷信息、 相邻节点是否允许回迁的负荷信息以及相关技术 中的负荷信息等。 这样网络节点就可以综合考虑这些信息进行负荷分担, 达 到更好地实现负载均衡的目的。 网络节点 82和上述相邻节点均为无线网络控制器或演进的节点 B。 本实施例的网络节点进行负荷分担时, 通过考虑相邻节点是否允许资源 共享, 解决了因无法获知相邻节点是否提供资源共享而导致负荷分担失败的 问题, 进而达到合理实现负载均衡的效果。 从以上的描述中可以看出, 本发明实现了如下技术效果: 以上实施例的网络节点进行负荷分担时, 通过考虑相邻节点是否允许资 源共享, 解决了因无法获知相邻节点是否提供资源共享而盲目发起用户迁移 造成失败的问题, 进而达到合理实现负载均衡的效果。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 并 且在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步 H ^去 将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软件 结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的 ^"神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种网络节点间负荷分担的方法, 其特征在于, 包括:
网络节点接收并保存相邻节点的负荷信息, 所述负荷信息包括所述 相邻节点是否允许资源共享;
所述网络节点负荷过载时, 根据保存的信息选择支持资源共享的相 邻节点进行负荷分担。
2. 根据权利要求 1所述的方法, 其特征在于, 所述相邻节点通过以下消息 之一发送所述负荷信息: 公共测量报告消息、 负荷信息消息、 重定位请 求消息或重定位要求确认消息。
3. 根据权利要求 1所述的方法, 其特征在于, 所述负荷信息还包括: 网元 级别的负荷信息;
根据保存的信息选择支持资源共享的相邻节点进行负荷分担包括: 选择支持资源共享的相邻节点; 根据网元级别的负荷信息从所述支持资 源共享的相邻节点中选择负荷小于门限值的相邻节点进行负荷分担。
4. 根据权利要求 1所述的方法, 其特征在于, 所述负荷信息还包括: 所述 相邻节点是否允许回迁的负荷信息;
根据保存的信息选择支持资源共享的相邻节点进行负荷分担包括: 选择支持资源共享的相邻节点; 根据是否允许回迁的负荷信息从所述支 持资源共享的相邻节点中选择允许回迁的相邻节点进行负荷分担。
5. 根据权利要求 4所述的方法, 其特征在于, 所述方法还包括: 所述网络 节点的负荷恢复正常时, 所述网络节点与进行负荷分担的相邻节点进行 负荷回迁。
6. —种网络设备, 其特征在于, 包括:
保存模块, 用于接收并保存相邻节点的负荷信息, 所述负荷信息包 括所述相邻节点是否允许资源共享;
负荷分担模块, 用于负荷过载时, 根据保存的信息选择支持资源共 享的相邻节点进行负荷分担。
7. 根据权利要求 6所述的网络设备, 其特征在于, 所述保存模块接收并保 存的负荷信息还包括: 网元级别的负荷信息;
所述负荷分担模块包括:
第一选择单元, 用于选择支持资源共享的相邻节点;
第一负荷分担单元, 用于根据网元级别的负荷信息从所述第一选择 单元选择的支持资源共享的相邻节点中选择负荷小于门限值的相邻节点 进行负荷分担。
8. 根据权利要求 6所述的网络设备, 其特征在于, 所述保存模块接收并保 存的负荷信息还包括: 所述相邻节点是否允许回迁的负荷信息;
所述负荷分担模块包括:
第二选择单元, 用于选择支持资源共享的相邻节点;
第二负荷分担单元, 用于根据是否允许回迁的负荷信息从所述第二 选择单元选择的支持资源共享的相邻节点中选择允许回迁的相邻节点进 行负荷分担。
9. 一种网络节点间负荷分担的系统, 包括网络节点和所述网络节点的多个 相邻节点, 其特征在于,
所述相邻节点, 用于向所述网络节点发送负荷信息, 所述负荷信息 包括所述相邻节点是否允许资源共享;
网络节点包括:
保存模块, 用于接收并保存所述负荷信息;
负荷分担模块, 用于负荷过载时, 根据保存的信息选择支持资源共 享的相邻节点进行负荷分担。 才艮据权利要求 9所述的系统, 其特征在于, 所述网络节点和所述相邻节 点均为无线网络控制器或演进的节点 B。
PCT/CN2010/073448 2010-06-02 2010-06-02 网络节点间负荷分担的方法、系统和网络设备 WO2011150555A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/073448 WO2011150555A1 (zh) 2010-06-02 2010-06-02 网络节点间负荷分担的方法、系统和网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/073448 WO2011150555A1 (zh) 2010-06-02 2010-06-02 网络节点间负荷分担的方法、系统和网络设备

Publications (1)

Publication Number Publication Date
WO2011150555A1 true WO2011150555A1 (zh) 2011-12-08

Family

ID=45066115

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/073448 WO2011150555A1 (zh) 2010-06-02 2010-06-02 网络节点间负荷分担的方法、系统和网络设备

Country Status (1)

Country Link
WO (1) WO2011150555A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1856134A (zh) * 2005-04-18 2006-11-01 华为技术有限公司 一种实现核心网络节点负载分担的方法
CN101111078A (zh) * 2007-08-21 2008-01-23 华为技术有限公司 池区中实现负荷均衡的方法及核心网节点
CN101370162A (zh) * 2007-08-15 2009-02-18 华为技术有限公司 负载信息获得方法、装置及系统
CN101541041A (zh) * 2009-04-23 2009-09-23 华为技术有限公司 负载分担方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1856134A (zh) * 2005-04-18 2006-11-01 华为技术有限公司 一种实现核心网络节点负载分担的方法
CN101370162A (zh) * 2007-08-15 2009-02-18 华为技术有限公司 负载信息获得方法、装置及系统
CN101111078A (zh) * 2007-08-21 2008-01-23 华为技术有限公司 池区中实现负荷均衡的方法及核心网节点
CN101541041A (zh) * 2009-04-23 2009-09-23 华为技术有限公司 负载分担方法、装置及系统

Similar Documents

Publication Publication Date Title
RU2713442C1 (ru) Система и способ переключения сот
EP3979707B1 (en) Method for initiating user plane path modification in a communications system
US9906994B2 (en) Handover method, master base station and slave base station
EP2739082B1 (en) Load sharing method, device, and system
JP6283099B2 (ja) スモールセル切り替え方法、基地局およびコンピュータ記憶媒体
TW201737734A (zh) 與傳統無線電存取技術互動工作用於連接到下一代核心網路
EP3641483B1 (en) Wireless protocol layer entity processing method and corresponding user equipment
JP2020502928A5 (zh)
US20150312810A1 (en) Radio communication system and communication control method
US10320449B2 (en) Dynamic cell clustering for coordinated multipoint operation
WO2021012213A1 (en) Method and apparatus for connection reconfiguration
WO2011134348A1 (zh) 基站切换处理方法和基站设备
WO2012139400A1 (zh) 一种小区负荷控制方法及装置
WO2016202121A1 (zh) 一种负载均衡的方法及相关设备
WO2012126331A1 (zh) 数据传递方法及系统
WO2014177075A1 (zh) 连接建立方法与装置、系统、存储介质
JP5055599B2 (ja) 第1周波数でサービスを確立する方法およびデバイス
WO2016101586A1 (zh) 一种基站切换方法、系统及相关装置、存储介质
WO2014101469A1 (zh) 群组资源释放方法、装置及系统
WO2012155681A1 (zh) 一种csg信息的传输方法和设备
WO2015117325A1 (zh) 双连接拆建方法和装置
WO2011150555A1 (zh) 网络节点间负荷分担的方法、系统和网络设备
WO2014177107A1 (zh) 一种pdcp计数值的处理方法、装置和计算机存储介质
WO2011143982A1 (zh) 一种无线接入网络节点及节点间负荷分担的方法
JP2005252502A (ja) 移動通信システム及びそのリソース制御方法並びに無線回線制御装置

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: 10852354

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10852354

Country of ref document: EP

Kind code of ref document: A1