WO2012065433A1 - 一种提高无线网络控制器可靠性的方法及系统 - Google Patents

一种提高无线网络控制器可靠性的方法及系统 Download PDF

Info

Publication number
WO2012065433A1
WO2012065433A1 PCT/CN2011/075575 CN2011075575W WO2012065433A1 WO 2012065433 A1 WO2012065433 A1 WO 2012065433A1 CN 2011075575 W CN2011075575 W CN 2011075575W WO 2012065433 A1 WO2012065433 A1 WO 2012065433A1
Authority
WO
WIPO (PCT)
Prior art keywords
nodeb
rnc
rnc2
rnc1
handover
Prior art date
Application number
PCT/CN2011/075575
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 中兴通讯股份有限公司
Publication of WO2012065433A1 publication Critical patent/WO2012065433A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/12—Access point controller devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method and system for improving reliability of a Radio Network Controller (RNC) in a Code Division Multiple Access (CDMA) system.
  • RNC Radio Network Controller
  • CDMA Code Division Multiple Access
  • Network reliability is one of the concerns of operators. Network reliability In addition to relying on highly reliable network element equipment and network infrastructure, new networking methods and network topologies can also help improve network reliability.
  • the network element device includes a core network (CN)/RNC/base station (NodeB) and the like; and the network infrastructure includes a transmission network device and a communication cable/optical cable.
  • FIG. 1 is a schematic diagram of a UMTS radio access network architecture of the existing 3GPP.
  • the Iu-flex networking technology that has been standardized at present is that one RNC can be connected to multiple CNs, and multiple CNs constitute a resource pool ( Resources Pool ), when one of the CNs fails, or when one of the CNs is overloaded, the user's services can be shared by other CNs.
  • One of the purposes of using Iu flex is to improve the reliability of the CN.
  • the main purpose of the present invention is to provide a method and system for improving the reliability of an RNC, which can improve the reliability of the RNC.
  • an RNC which can improve the reliability of the RNC.
  • a method for improving the reliability of a radio network controller comprising: configuring a corresponding backup RNC for a radio network controller (RNC) to which a base station (NodeB) belongs, and determining, when the NodeB needs to be switched according to the handover policy, the NodeB The RNC to which it belongs is switched to the backup RNC, and the configuration data related to the Node B on the RNC to which the NodeB belongs is synchronized to the backup RNC.
  • RNC radio network controller
  • NodeB base station
  • the method further includes: the backup RNC updates the local and NodeB related data according to the synchronized configuration data, and after the handover is completed, deletes the configuration data related to the Node B on the RNC to which the NodeB belongs.
  • the method further includes: before the handover, the NodeB and the The RNC1 and the RNC2 establish a transmission connection, and establish a cell on the RNC1 to provide a service for the NodeB, and the RNC2 does not involve the service of the NodeB.
  • the information referenced by the execution of the decision includes: an external operation and maintenance command, an operation state of the RNC1 and the RNC2, a link state of the Iub interface and the Iu interface of the RNC1 and the RNC2, a load of the RNC1 and the RNC2, and a geographical location information of the NodeB. And at least one of geographically distributed information.
  • the data related to the NodeB includes: a neighbor relationship; and/or identity information of a cell managed by the NodeB and the NodeB presented for fault management and performance management.
  • a system for improving reliability of a wireless network controller comprising: a configuration and switching control unit, and a handover decision unit; wherein
  • the configuration and handover control unit is configured to configure a corresponding backup RNC for the RNC to which the NodeB belongs.
  • the control NodeB is handed over to the backup RNC by the RNC to which the NodeB belongs, and the RNC to which the NodeB belongs.
  • the configuration data related to the Node B is synchronized to the backup RNC;
  • the handover decision unit is configured to determine, according to the handover policy, whether the NodeB needs to be handed over, and notify the configuration and handover control unit to perform handover control when it is determined that the NodeB needs to be handed over.
  • the configuration and handover control unit further includes: RNC operation and maintenance center 1 ( OMC-RNC1 ), RNC operation and maintenance center 2 ( OMC-RNC2), when the RNC belongs to the RNC, and the backup RNC is the RNC 2
  • the handover decision unit further switches the decision subsystem to the NodeB;
  • the NodeB handover decision subsystem is separately deployed on the NodeB side or integrated with the OMC-RNC1 and the OMC-RNC2, respectively.
  • the OMC-RNC1 is further configured to: when the NodeB handover decision subsystem determines that the NodeB needs to be handed over from the RNC1 to the RNC2, synchronize configuration data related to the Node B on the RNC1 to the OMC-RNC2; After deleting the configuration data related to the Node B on the RNC1;
  • the OMC-RNC2 is further configured to update local and NodeB related data according to the synchronized configuration data, and notify the RNC2 to establish a cell radio resource to provide services for the NodeB after the update.
  • the NodeB handover decision subsystem is further configured to accept commands issued by an external operation maintenance center or to receive information commands issued by RNC1, RNC2, and NodeB during operation.
  • the OMC-RNC1 is further configured to directly interact with the OMC-RNC2 Perform data synchronization, or perform data synchronization with the OMC-RNC2 under the control of the superior telecommunication management network.
  • the present invention is configured to configure a backup RNC corresponding to the RNC to which the NodeB belongs.
  • the NodeB needs to perform handover according to the handover policy, the NodeB is switched from the RNC to which the NodeB belongs to the backup RNC, and the configuration data related to the Node B on the RNC to which the NodeB belongs is configured. Synchronize to the backup RNC.
  • the NodeB by configuring a backup RNC for the NodeB, when one of the RNCs fails to work normally, the NodeB is switched to another RNC to ensure the continuity of the NodeB service and improve the reliability of the network.
  • FIG. 1 is a schematic diagram of an existing 3GPP UMTS radio access network architecture
  • FIG. 2 is a schematic diagram of an example of a process flow of the method of the present invention.
  • Figure 3 is a schematic view showing an example of the structure of a system of the present invention.
  • FIG. 4 is a schematic structural view of a first application example of the present invention.
  • FIG. 5 is a schematic diagram of an implementation flow of an application example 1 of the present invention.
  • FIG. 6 is a schematic diagram of an implementation flow of an application example 2 of the present invention.
  • FIG. 7 is a schematic diagram showing an implementation flow of an application example 3 of the present invention.
  • FIG. 8 is a schematic diagram of an implementation flow of an application example 4 of the present invention.
  • FIG. 9 is a schematic structural diagram of a fifth application example of the present invention.
  • FIG. 10 is a schematic diagram showing an implementation flow of an application example 5 of the present invention. detailed description
  • the basic idea of the present invention is to: configure a corresponding backup RNC for the RNC to which the NodeB belongs.
  • the NodeB needs to be handed over according to the handover policy, the NodeB is switched from the RNC to which the NodeB belongs to the backup RNC, and the RNC to which the NodeB belongs is associated with the Node.
  • the configuration data of B is synchronized to the backup RNC to ensure the continuity of the NodeB service.
  • a method for improving the reliability of RNC the main contents of which include:
  • the NodeB When the NodeB needs to switch to the backup RNC according to the switching policy, the NodeB is switched to the backup RNC by the RNC to which it belongs.
  • the decision may be made by a new NodeB handover decision subsystem, as described in detail with respect to the system description of the present invention. I won't go into details here.
  • the first radio network controller (RNC1) is used as the RNC to which the NodeB belongs
  • the second radio network controller (RNC2) is taken as a backup RNC as an example.
  • the NodeB establishes a transmission connection with RNC1 and RNC2, and maintains a substantial radio resource affiliation relationship with RNC1, namely: establishing a cell on RNC1 to provide services for the NodeB, and RNC2 does not involve any NodeB service relationship.
  • the associated wireless network layer data of the NodeB has only one valid data between RNC1 and RNC2, and exists only on the RNC having the radio resource belonging relationship with the NodeB.
  • the initial configuration is determined by the network plan.
  • the neighboring area associated with the NodeB includes the neighboring cell of the cell under the NodeB, or the cell in the NodeB is a neighboring cell of another cell, and only needs to configure the data in the initial configuration.
  • the valid data refers to data that can interact with the NodeB, and is not limited to a specific expression.
  • RNC1 and RNC2 can respectively save a set of NodeB data, but the data on RNC1 is valid data. It is possible to let the NodeB work under RNC1; the data on RNC2 is just a collection, and the NodeB will not work under RNC2.
  • the NodeB handover decision subsystem can determine that the NodeB needs to switch from RNC1 to RNC2 according to the handover policy.
  • the NodeB handover decision-making subsystem is responsible for the final decision of the NodeB handover, and the NodeB handover decision-making subsystem can accept the commands of the external operation and maintenance center, and can also accept the information commands sent by the RNC and the NodeB during the operation. Further, the NodeB handover decision subsystem can pass information between the operation and maintenance center, the RNC, and the NodeB. For example, information is transferred between RNC1 and RNC Operation and Maintenance Center 1 (OCC-RNC1), information is transmitted between RNC2 and RNC Operation and Maintenance Center 2 (OCC-RNC2), and information is transmitted between NodeB Operation and Maintenance Center (OCC-NodeB) and NodeB. Wait.
  • OCC-RNC1 RNC Operation and Maintenance Center 1
  • OC-RNC2 RNC Operation and Maintenance Center 2
  • OCC-NodeB NodeB Operation and Maintenance Center
  • the information that can be referred to when the NodeB handover decision-making subsystem performs the judgment includes: an external operation and maintenance command, an operation state of the RNC1 and the RNC2, an Iub interface of the RNC1/RNC2, and a link state of the Iu interface. Further, reference can also be made to the loads of RNC1 and RNC2. Further, the decision can also refer to the geographical location information of the NodeB and the geographical distribution information.
  • the external operation and maintenance command includes a manual operation or the like.
  • the operating states of the RNC1 and RNC2 include physical device status, software working status, business service status, and the like.
  • the link status includes whether the link works normally, and the load includes occupation of physical resources, occupation of radio resources, and the like.
  • the NodeB handover decision subsystem is a logical concept, and its physical representation can be various, such as deployment distributed on each node device, or a single node device can be deployed in a centralized manner. The focus is on its logic, and the NodeB switch decision subsystem can decide when to switch NodeB. in particular:
  • the foregoing switching policy includes: the RNC that the NodeB currently belongs to is faulty, or the link failure between the NodeB and the RNC to which the NodeB belongs must be switched to the backup RNC; or the current RNC load of the NodeB is too high, in order to provide a better user.
  • the service can choose to switch to the backup RNC.
  • the NodeB handover decision subsystem can make handover decisions based on the following handover strategies, but not only limit these handover strategies, but focus on making decisions based on the rules and according to the rules:
  • the operation and maintenance personnel initiates a NodeB handover command at the operation center, according to which the NodeB handover decision subsystem decides to initiate a handover command.
  • the entire device of RNC1 is faulty. According to this, the NodeB switching decision-making subsystem decides to initiate the switching. Order.
  • the NodeB handover decision subsystem decides to initiate the handover command.
  • the Iub interface link between NodeB and RNC1 is interrupted, and the NodeB handover decision subsystem decides to initiate the handover command.
  • the Iu interface link between RNC 1 and CN is interrupted, and the NodeB handover decision subsystem decides to switch commands.
  • the load of RNC1 is too high, and according to this, the NodeB handover decision subsystem decides to initiate a handover command. 3.
  • the configuration data of the NodeB that needs to be switched can be synchronized by the OMC-RNC1 to the OMC-RNC2 of the RNC2.
  • the data of the same NodeB is inherently consistent between the OMC-RNC 1 and the OMC-RNC2, and the data consistency can be implemented by an automatic synchronization process, and the synchronization can be a real-time, periodic or event-triggered manner. . Data consistency can also be achieved manually, with an emphasis on the inherent consistency of the data.
  • the automatic synchronization process of data between the OMC-RNC1 and the OMC-RNC2 can be directly performed, or can be synchronized through the upper-level telecommunication maintenance network.
  • the OMC-NodeB is consistent before and after the NodeB data is switched on the NodeB. If the OMC-NodeB is attached to the OMC-RNC, the OMC-NodeB can synchronize to maintain consistency.
  • the NodeB can receive operation and maintenance commands of the OMC-NodeB on different OMC-RNCs.
  • OMC-RNC2 After data synchronization between OMC-RNC 1 and OMC-RNC2, OMC-RNC2 updates the data related to the NodeB, including the neighbor relationship, the NodeB and NodeB for fault management and performance management. The identity information of the community.
  • the RNC has a one-time change of the data in the neighbor relationship with the switched NodeB, ensuring that the mobility of the NodeB remains unaffected after the handover occurs.
  • the update of the data can be automatic or manual intervention.
  • the operation and maintenance management center can set the NodeB in
  • RNC2 The identity of RNC2 is merged with the provinces of NodeB on RNC1 to provide consistent identity for external fault management, performance management, etc., and it is also possible to combine identity and maintain independent identity.
  • RNC2 establishes radio resources such as cells according to the procedures specified by 3GPP according to its own situation, and RNC2 officially serves as NodeB.
  • NodeB switches to RNC2. After RNC2 is officially served by NodeB, OMC-RNC1 deletes the serving cell data of NodeB and updates the neighboring cell data related to NodeB under RNC1.
  • the OMC-RNC1 needs to change the data in the neighbor relationship between the RNC and the switched NodeB in one time, ensuring that the mobility of the NodeB remains after the handover occurs. Not affected.
  • the NodeB handover is completed this time, and the NodeB handover decision subsystem continues to work. If it is determined that the NodeB needs to initiate the handover again, then another handover operation is continued from the above two.
  • a system for improving the reliability of a wireless network controller comprising: a configuration and switching control unit, and a switching decision unit.
  • the configuration and handover control unit is configured to configure a corresponding backup RNC for the RNC to which the NodeB belongs.
  • the control NodeB is switched from the RNC to which the NodeB belongs to the backup RNC, and the RNC to which the NodeB belongs is associated with the Node.
  • the configuration data related to B is synchronized to the backup RNC.
  • the handover decision unit is configured to determine whether the NodeB needs to be handed over according to the handover policy, and notify the configuration and handover control unit to perform handover control when it is determined that the NodeB needs to be handed over.
  • the configuration and handover control unit further includes: 0MC-RNC1, OMC-RNC2; handover decision unit, further switching the decision subsystem for the NodeB.
  • the NodeB handover decision subsystem may be deployed separately on the NodeB side or integrated with the OMC-RNC1 and OMC-RNC2 respectively.
  • the 0MC-RNC1 is further configured to: when the NodeB handover decision subsystem determines that the NodeB needs to be handed over from the RNC1 to the RNC2, synchronize configuration data related to the Node B on the RNC1 to the 0MC-RNC2; after the handover is completed, delete the RNC1.
  • the 0MC-RNC2 is further configured to update local and NodeB related data according to the synchronized configuration data, and notify the RNC2 to establish a cell radio resource to provide a service for the NodeB after the update.
  • the NodeB handover decision subsystem can accept commands issued by an external operation and maintenance center, or can accept information commands issued by RNC1, RNC2, and NodeB during operation.
  • the 0MC-RNC1 is further configured to perform data synchronization directly with the 0MC-RNC2, or to perform data synchronization with the 0MC-RNC2 under the control of the superior telecommunication management network.
  • the present invention can improve the reliability of the RNC as a whole and reduce the possibility of a single point of failure of the RNC as compared with the prior art; the workload of the operation and maintenance can be greatly simplified, due to the operation and maintenance management center. Participation, the invention has great advantages in data configuration, fault management, performance management, etc., and enables RNC disaster recovery, NodeB dual backup and the like to enhance the reliability of the RNC/NodeB, and realize the operation and maintenance. Manageable; NodeB switching can implement automatic judgment or manual intervention. Switching can also be performed in batches according to NodeB group, or can be switched according to a single NodeB. Under batch switching, the NodeB switching decision subsystem can collect and switch.
  • the NodeB after collecting a certain number, performs a handover process on the NodeBs in a centralized manner, and the handover of the single NodeB refers to that the NodeB handover decision-making subsystem immediately initiates a handover process to the NodeB when it detects that a NodeB needs to be handed over; Fault alarms, performance counters, etc. can be combined into the same fixed identity NodeB/cell data, or they can be processed separately, which is more conducive to the needs of operation and maintenance.
  • the invention is illustrated by way of example below.
  • FIG. 2 is a schematic diagram of a process flow of a method according to the present invention, including the following steps: Step 101: A NodeB establishes a radio resource affiliation relationship with RNC1.
  • Step 102 The NodeB handover decision subsystem performs a handover decision. If it is determined that the NodeB needs to perform handover, step 103 is performed; otherwise, it is determined that the NodeB does not need to perform handover, and the current handover procedure is ended.
  • Step 103 The OMC-RNC1 synchronizes the data related to the NodeB to the OMC-RNC2.
  • Step 104 The OMC-RNC2 updates the local data.
  • Step 105 The RNC2 and the NodeB establish a radio resource affiliation relationship.
  • Step 106 The RNC1 deletes the serving cell data of the NodeB, and updates the neighboring area related data.
  • FIG. 3 is a schematic diagram showing an example of a component structure of the system according to the present invention, including: RNC1 and RNC2 under the control of the core network, RNC1 and RNC2 respectively serving as the RNC and backup RNC of the NodeB; and a NodeB handover decision-making subsystem serving as a handover decision; OMC-RNC1 and OMC-RNC2 are used as operation and maintenance centers of RNC1 and RNC2 respectively for data synchronization between the two; OMC-NodeB serves as the operation and maintenance center of the NodeB, and also includes the Telecommunication Management Network (TMN).
  • Telecommunication Management Network Telecommunication Management Network
  • a NodeB handover decision subsystem may be separately deployed for handover decision; OMC-RNC and RNC are deployed together, such as OMC-RNC1 and RNC1 are deployed together, OMC - RNC2 and RNC2 are deployed together; OMC-NodeB and OMC-RNC are deployed together, such as OMC-NodeB can be deployed with OMC-RNC 1 or with OMC-RNC2; configuration data can be saved in OMC- Any of the RNC 1 and OMC-RNC2 on the OMC-RNC.
  • RNC1 is the primary RNC of the NodeB, which is the RNC to which the NodeB belongs, and establishes radio resources such as cells between the NodeB and the RNC1.
  • Step 202 The NodeB detects that there is no periodic audit message from the RNC1 for a long time, but the lub link still works normally, and the NodeB reports the detection result to the NodeB handover decision subsystem.
  • Step 203 The NodeB handover decision subsystem determines that a handover is required, and accordingly issues an instruction to the RNC2 to instruct the RNC2 to take over the NodeB.
  • Step 204 The NodeB handover decision subsystem issues an instruction to the OMC-RNC1 to synchronize the NodeB related data to the RNC2.
  • Step 205 After receiving the data, the OMC-RNC2 updates the related neighbor data configuration.
  • the cell in the RNC updates the neighboring cell data of the cell if it has previously been the neighboring cell.
  • Step 206 Establish a radio resource such as a cell between the NodeB and the RNC2.
  • Step 207 The OMC - RNC1 deletes the switched NodeB data and updates the neighbor data under the RNC.
  • the handover implementation process of this example is shown in Figure 6, and includes the following steps:
  • Step 301 RNC1 is used as the primary RNC of the NodeB, and is the RNC to which the NodeB belongs, and establishes a radio resource such as a cell between the NodeB and the RNC1.
  • Step 302 During the running, the data related to the NodeB, if there is a change, is synchronized to the OMC-RNC2 corresponding to the RNC2.
  • Step 303 The RNC1 device fails overall, and the NodeB handover decision subsystem detects that the RNC1 has no response information for a long time.
  • Step 304 The NodeB handover decision subsystem determines that a handover is required, and sends an instruction to the OMC-RNC2 to instruct the RNC2 to take over the NodeB.
  • Step 305 After receiving the command, the OMC-RNC2 updates the related neighbor data configuration.
  • the OMC-RNC2 updates the related neighbor data configuration.
  • the cell in the cell if there is a cell with a handover as a neighboring cell, the neighboring cell data of the cell is updated.
  • Step 306 Establish a radio resource such as a cell between the NodeB and the RNC2.
  • the handover implementation process of this example is shown in Figure 7, and includes the following steps:
  • Step 401 The RNC1 is used as the primary RNC of the NodeB, and is the RNC to which the NodeB belongs, and establishes a radio resource such as a cell between the NodeB and the RNC1.
  • Step 402 The operation and maintenance personnel initiate a manual handover operation command on the OMC-NodeB, and the OMC-NodeB reports the command to the NodeB handover decision subsystem.
  • Step 403 The NodeB handover decision subsystem determines that a handover is required, and accordingly issues an instruction to the RNC2 to instruct the RNC2 to take over the NodeB.
  • Step 404 The NodeB handover decision subsystem issues an instruction to the OMC-RNC1 to synchronize the NodeB related data to the RNC2.
  • Step 405 After receiving the data, the OMC-RNC2 updates the related neighbor data configuration.
  • the cell in the RNC updates the neighboring cell data of the cell if it has previously been the neighboring cell.
  • Step 406 Establish a radio resource such as a cell between the NodeB and the RNC2.
  • Step 407 The OMC-RNC1 deletes the switched NodeB data and updates the neighbor data under the RNC.
  • the handover implementation process of this example is shown in Figure 8, and includes the following steps:
  • Step 501 RNC1 is used as the primary RNC of the NodeB, and is the RNC to which the NodeB belongs.
  • a radio resource such as a cell is established between the NodeB and the RNC1.
  • Step 502 During the running, the data related to the NodeB is synchronized to the OMC-RNC2 corresponding to the RNC2, and the periodic data synchronization process also exists.
  • Step 503 The RNC1 load is too high, and the information is sent to the NodeB handover decision subsystem.
  • Step 505 After receiving the command, the OMC-RNC2 updates the related neighbor data configuration.
  • the cell in the RNC updates the neighboring cell data of the cell if it has previously been the neighboring cell.
  • Step 506 Establish a radio resource such as a cell between the NodeB and the RNC2.
  • the NodeB handover decision-making subsystem is deployed on RNC1 and RNC2; the OMC-RNC and the RNC are deployed together, such as OMC-RNC1 and RNC1 are deployed together, OMC-RNC2 and RNC2 Deployed together; OMC-NodeB and OMC-RNC are deployed together, such as OMC-NodeB can be deployed with OMC-RNC1, or with OMC-RNC2; configuration data can be saved in OMC-RNC1 and OMC-RNC2 Any one of the OMC-RNC.
  • the handover implementation process of this example includes the following steps as shown in FIG. 10:
  • Step 601 RNC1 is used as the primary RNC of the NodeB, and is the RNC to which the NodeB belongs.
  • a radio resource such as a cell is established between the NodeB and the RNC1.
  • a backup is performed in real time on RNC2.
  • Step 602 The NodeB handover decision subsystem deployed on the RNC2 finds that the RNC1 has failed overall, and determines that the handover needs to be performed, and initiates a command to take over the NodeB to the RNC2 where it is located.
  • Step 603 The RNC2 takes the backup data of the previous NodeB as the official data, and the submission takes effect.
  • Step 605 Establish a radio resource such as a cell between the NodeB and the RNC2.
  • Step 606 After the RNC1 is recovered, the NodeB handover decision sub-system deployed on the RNC1 finds that the NodeB has been switched to the RNC2, deletes the relevant effective data of the NodeB on the RNC1 where the RNC1 is located, and updates the neighbor-related configuration.
  • the NodeB by configuring a backup RNC for the NodeB, when one of the RNCs fails to work normally, the NodeB is switched to another RNC to ensure the continuity of the NodeB service and improve the reliability of the network.

Abstract

本发明公开了一种提高无线网络控制器可靠性的方法，该方法包括：为基站（NodeB）当前所属的无线网络控制器（RNC）配置对应的备份RNC，当根据切换策略判决出NodeB需要切换时，将NodeB由其所属的RNC切换到备份RNC，将NodeB所属的RNC上与NodeB有关的配置数据同步到备份RNC。本发明还公开了一种提高无线网络控制器可靠性的系统，该系统中的切换决策单元用于当判决出NodeB需要切换时通知配置及切换控制单元进行切换控制。采用本发明的方法及系统，能提高RNC的可靠性，当其中一个RNC不能为NodeB提供服务时，将其下辖的所有的NodeB切换到另外一个RNC上。

Description

一种提高无线网络控制器可靠性的方法及系统 技术领域
本发明涉及移动通讯领域， 尤其涉及一种码分多址 （CDMA, Code Division Multiple Access )系统中提高无线网络控制器（ RNC , Radio Network Controller )可靠性的方法及系统。 背景技术
网络可靠性是运营商关注的问题之一。 网络的可靠性除依赖于高可靠 性的网元设备和网络基础设施外， 新的组网方式和网络拓朴也有助于提高 网络可靠性。 其中， 所述网元设备包括核心网 （ CN ) /RNC/基站（ NodeB ) 等； 所述网络基础设施包括传输网设备和通信电缆 /光缆等。
图 1是现有 3GPP的 UMTS无线接入网络架构图， 由图 1可以看出， 目前已经完成标准化的 Iu-flex组网技术是一个 RNC可以连接到多个 CN, 多个 CN构成资源池（Resources Pool ), 当其中一个 CN发生故障时， 或者 当其中一个 CN的负荷过重时，用户的业务可以被其他 CN分担。釆用 Iu flex 的目的之一就是提高 CN的可靠性。
目前无线接入网中 3GPP尚未实现类似的备份和冗余机制。由于无线接 入网中接入每个 RNC的 NodeB数量庞大（几十、 几百甚至上千）， 因此 lub 口链路故障的发生概率要远高于 Iu 口。 这样就会导致一些不利的情况， 例 如： （1 ) 虽然一个 lub口故障带来的影响要低于 Iu口， 但仍将使一个或多 个站点 （NodeB 级连情况下） 的业务中断， 引发区域性用户投诉； （2 )如 果遇到灾难情况导致整个 RNC故障，那么其下辖的所有的 NodeB都将无法 工作， 形成非常大的通信盲区。 可见： 建立提高 RNC可靠性的机制是十分 必要的， 为了提高 RNC可靠性， 可以考虑当其中一个 RNC不能为 NodeB 提供服务时，将其下辖的所有的 NodeB切换到另外一个 RNC上，也可以理 解为： 为 NodeB提供备份 RNC, 建立备份机制。 然而目前并未有这样的实 现方案。 发明内容
有鉴于此， 本发明的主要目的在于提供了一种提高 RNC可靠性的方法 及系统， 能提高 RNC的可靠性， 当其中一个 RNC不能为 NodeB提供服务 时， 将其下辖的所有的 NodeB切换到另外一个 RNC上。
为达到上述目的， 本发明的技术方案是这样实现的：
一种提高无线网络控制器可靠性的方法，该方法包括：为基站（NodeB ) 当前所属的无线网络控制器（RNC ) 配置对应的备份 RNC, 当根据切换策 略判决出 NodeB需要切换时， 将 NodeB由其所属的 RNC切换到所述备份 RNC,将 NodeB所属的 RNC 上与 Node B有关的配置数据同步到所述备份 RNC。
其中， 该方法还包括： 所述备份 RNC根据所同步的配置数据对本地与 NodeB相关的数据进行更新， 切换完成后， 删除 NodeB所属的 RNC上与 Node B有关的配置数据。
其中， 所述 NodeB所属的 RNC为第一无线网络控制器 （RNC1 ), 所 述备份 RNC为第二无线网络控制器（RNC2 ) 时， 该方法还包括： 切换之 前， 所述 NodeB分别与所述 RNC1和所述 RNC2建立传输连接， 并在所述 RNC1上建立小区，为 NodeB提供服务，所述 RNC2不涉及 NodeB的业务。
其中， 执行所述判决所参考的信息包括： 外部的操作维护命令、 RNC1 和 RNC2的运行 态、 RNC1和 RNC2的 Iub口和 Iu口的链路 态、 RNC1 和 RNC2的负荷、 NodeB的地理位置信息及分地理分布信息中的至少一种。
其中， 所述与 NodeB相关的数据包括： 邻区关系； 和 /或为故障管理、 性能管理呈现的 NodeB和 NodeB所管辖的小区的身份信息。 一种提高无线网络控制器可靠性的系统， 该系统包括： 配置及切换控 制单元、 切换决策单元； 其中，
所述配置及切换控制单元， 用于为 NodeB当前所属的 RNC配置对应 的备份 RNC, 在获知 NodeB需要切换的情况下， 控制 NodeB由其所属的 RNC切换到所述备份 RNC, 将 NodeB所属的 RNC 上与 Node B有关的配 置数据同步到所述备份 RNC;
所述切换决策单元， 用于根据切换策略判决 NodeB是否需要切换， 当 判决出 NodeB需要切换时通知所述配置及切换控制单元进行切换控制。
其中， 所述 NodeB所属的 RNC为 RNC1 , 所述备份 RNC为 RNC2时， 所述配置及切换控制单元， 进一步包括： RNC 操作维护中心 1 ( OMC-RNC1 )、 RNC操作维护中心 2 ( OMC-RNC2 ); 所述切换决策单元， 进一步为 NodeB切换决策子系统；
所述 NodeB切换决策子系统单独部署在 NodeB侧、 或者分别与所述 OMC-RNC1和所述 OMC-RNC2集成部署在一起。
其中， 所述 OMC-RNC1 , 进一步用于在所述 NodeB切换决策子系统判 决出 NodeB需要从 RNC1切换到 RNC2的情况下， 将 RNC1上与 Node B 有关的配置数据同步到 OMC - RNC2; 切换完成后， 删除 RNC1上与 Node B有关的配置数据；
所述 OMC-RNC2,进一步用于根据所同步的配置数据对本地与 NodeB 相关的数据进行更新， 更新后通知 RNC2建立小区无线资源为 NodeB提供 服务。
其中， 所述 NodeB切换决策子系统， 进一步用于能接受外部的操作维 护中心发出的命令、 或者能接受由 RNC1、 RNC2及 NodeB运行过程中发 出的信息指令。
其中， 所述 OMC-RNC1 , 进一步用于能直接与所述 OMC-RNC2交互 进行数据同步、 或者能在上级的电信管理网络的控制下与所述 OMC-RNC2 交互进行数据同步。
本发明为 NodeB当前所属的 RNC配置对应的备份 RNC, 当根据切换 策略判决出 NodeB需要切换时， 将 NodeB 由其所属的 RNC切换到备份 RNC,将 NodeB所属的 RNC 上与 Node B有关的配置数据同步到备份 RNC。
釆用本发明， 通过为 NodeB配置备份 RNC,当其中一个 RNC无法正常 工作时， 将 NodeB切换到另一个 RNC上， 保证 NodeB业务的连续性， 提 高网络的可靠性。 附图说明
图 1是现有 3GPP的 UMTS无线接入网络架构图；
图 2是本发明方法的一处理流程实例的示意图；
图 3是本发明系统的一组成结构实例的示意图；
图 4是本发明应用实例一的组成结构示意图；
图 5是本发明的应用实例一的实现流程示意图；
图 6是本发明的应用实例二的实现流程示意图；
图 7是本发明的应用实例三的实现流程示意图；
图 8是本发明的应用实例四的实现流程示意图；
图 9是本发明的应用实例五的组成结构示意图；
图 10是本发明的应用实例五的实现流程示意图。 具体实施方式
本发明的基本思想是： 为 NodeB 当前所属的 RNC 配置对应的备份 RNC, 当根据切换策略判决出 NodeB需要切换时， 将 NodeB 由其所属的 RNC切换到备份 RNC, 将 NodeB所属的 RNC 上与 Node B有关的配置数 据同步到备份 RNC, 以保证 NodeB业务的连续性。 下面参照附图结合实施例对本发明做进一步的描述。
一种提高 RNC可靠性的方法， 其主要内容包括：
为 NodeB当前所属的 RNC配置对应的备份 RNC, 当根据切换策略判 决出 NodeB需要切换到该备份 RNC时，将 NodeB由其所属的 RNC切换到 该备份 RNC。 这里， 所述判决可以由新增的 NodeB切换决策子系统作出， 具体见针对本发明的系统描述。 这里不作赘述。
以下以第一无线网络控制器（RNC1 )作为 NodeB当前所属的 RNC, 第二无线网络控制器（RNC2 )作为备份 RNC为例进行具体阐述。
一、 NodeB与 RNC1和 RNC2建立传输连接， 并且与 RNC1上保持了 实质上无线资源归属关系， 即为： 在 RNC1上建立小区， 为 NodeB提供服 务， RNC2不涉及任何 NodeB的业务关系。
进一步， NodeB的相关无线网络层数据在 RNC1和 RNC2二者之间只 有一份有效的数据， 并且只存在于与 NodeB 有所述无线资源归属关系的 RNC上。 初始配置由网络规划决定。
进一步， NodeB 相关的邻区， 包括本 NodeB 下小区的邻区， 或者本 NodeB下小区是其他小区的邻区， 只需要在初始配置下配置好数据即可。
进一步， 所述有效的数据是指可以和 NodeB进行交互的数据， 而不限 于于具体的表现形式， 比如， RNC1和 RNC2上可以分别保存一套 NodeB 数据，但 RNC1上的数据是有效的数据，是可以让 NodeB工作在 RNC1下； 而 RNC2上的数据仅仅是一个集合， 不会让 NodeB工作在 RNC2下。
二、可以由 NodeB切换决策子系统根据切换策略判决出 NodeB需要从 RNC1切换到 RNC2上。
进一步， NodeB 切换决策子系统负责进行 NodeB 切换最终决策， 该 NodeB 切换决策子系统可以接受外部的操作维护中心的命令， 也可以接受 由 RNC、 NodeB运行过程中发出的信息指令。 进一步， NodeB 切换决策子系统可以在操作维护中心、 RNC、 NodeB 之间传递信息。 比如 RNC1和 RNC操作维护中心 1 ( OMC-RNC1 )之间传 递信息、 RNC2和 RNC操作维护中心 2( OMC-RNC2 )之间传递信息、 NodeB 操作维护中心 （ OMC-NodeB )和 NodeB之间传递信息等。
进一步， NodeB 切换决策子系统进行判决时可参考的信息包括： 外部 的操作维护命令、 RNC1和 RNC2的运行状态、 RNC1/RNC2的 Iub口和 Iu 口的链路状态。 进一步的， 还可以参考 RNC1和 RNC2的负荷。 更进一步 的， 决策还可以参考 NodeB的地理位置信息以及分地理分布信息。 其中， 所述外部的操作维护命令包括人工操作等。 所述 RNC1和 RNC2的运行状 态包括物理设备状态、 软件工作状态、 业务服务状态等等。 所述链路状态 包括链路是否正常工作等， 负荷包括物理资源的占用， 无线资源的占用等 等。
进一步， NodeB 切换决策子系统是一个逻辑概念， 其物理表现形式可 以是多样的， 比如部署分布在各个节点设备， 也可以集中单独部署一个节 点设备上等等。 重点在于其逻辑功能， NodeB 切换决策子系统能决策出何 时进行 NodeB的切换。 具体而言：
进一步，上述切换策略包括： NodeB当前所属的 RNC故障，或者 NodeB 与 NodeB当前所属的 RNC间链路故障必须切换到备份 RNC;或者， NodeB 当前所属的 RNC负荷过高， 为了给用户提供更好的业务可以选择切换到备 份 RNC 。具体来说， NodeB切换决策子系统可以依据下列切换策略作出切 换决策， 但不仅仅局限这些切换策略， 重点在于依据输入， 根据规则， 作 出决策：
操作维护人员在操作中心发起 NodeB切换命令，据此 NodeB切换决策 子系统决策出发起切换命令。
RNC1整个设备故障， 据此 NodeB切换决策子系统决策出发起切换命 令。
因为软件故障等导致 RNC1无法为 NodeB提供服务，据此 NodeB切换 决策子系统决策出发起切换命令。
NodeB和 RNC1的 Iub口链路中断， 据此 NodeB切换决策子系统决策 出发起切换命令。
RNC 1和 CN的 Iu口链路中断， 据此 NodeB切换决策子系统决策出发 起切换命令。
RNC1的负荷过高，据此 NodeB切换决策子系统决策出发起切换命令。 三、可以由 OMC-RNC1将需要切换的 NodeB的配置数据同步到 RNC2 的 OMC - RNC2上。
进一步 , OMC-RNC 1和 OMC-RNC2之间对同一个 NodeB的数据具有 内在的一致性， 其数据一致性可以通过自动的同步过程来实现， 同步可以 是实时的、 周期的或者事件触发的方式。 数据一致性也可以通过人工来实 现， 重点在于数据具有内在的一致性。
进一步， OMC-RNC1和 OMC-RNC2之间的数据的自动同步过程可以 直接进行交互， 也可以通过上级的电信维护网络来进行同步。
进一步， OMC-NodeB对于 NodeB的数据在 NodeB发生切换的前后也 是一致的， 如果 OMC-NodeB附属在 OMC-RNC上， 则 OMC-NodeB则可 以进行同步来保持一致性。
进一步， 对于 OMC-NodeB附属在 OMC-RNC上场景， NodeB可以接 受不同 OMC-RNC上的 OMC-NodeB的操作维护命令。
四、 在 OMC-RNC 1和 OMC-RNC2之间进行数据同步后 , OMC-RNC2 会更新与 NodeB相关的数据， 这些数据包括邻区关系、 为故障管理、 性能 管理呈现的 NodeB和 NodeB所管辖的小区的身份信息。
进一步， 对从 RNC1切换到 RNC2的 NodeB, OMC-RNC2需要把在本 RNC与切换的 NodeB有邻区关系的数据进行一次性更改， 确保 NodeB在 发生切换后， 移动性仍然不受影响。
进一步， 数据的更新可以是自动的， 也可以人工干预的。
进一步， NodeB切换到 RNC2后， 操作维护管理中心可以将 NodeB在
RNC2上身份与 NodeB在 RNC1上的省份进行合并， 对外部故障管理、 性 能管理等功能呈现一致的身份， 也可以不对身份进行合并， 保持独立的身 份。
五、 RNC2根据自身情况， 同 NodeB—起按照 3GPP规定的过程建立 小区等无线资源， RNC2正式为 NodeB服务。
六、 NodeB切换到 RNC2, RNC2正式为 NodeB服务后， OMC-RNC1 删除 NodeB的服务小区数据， 更新 RNC1下同 NodeB相关的邻区数据。
进一步， 对从 RNC1 切换到 RNC2 的 NodeB 及其所管辖的小区， OMC-RNC1需要把在本 RNC与切换的 NodeB有邻区关系的数据进行一次 性更改， 确保 NodeB在发生切换后， 移动性仍然不受影响。
七、 NodeB本次切换完成， NodeB切换决策子系统继续工作， 如果判 决出 NodeB需要再次发起切换， 则从上述二开始继续执行再一次的切换操 作。
一种提高无线网络控制器可靠性的系统， 该系统包括： 配置及切换控 制单元、 切换决策单元。 其中， 配置及切换控制单元用于为 NodeB当前所 属的 RNC配置对应的备份 RNC, 在获知 NodeB需要切换的情况下， 控制 NodeB由其所属的 RNC切换到备份 RNC ,将 NodeB所属的 RNC 上与 Node B有关的配置数据同步到备份 RNC。 切换决策单元用于根据切换策略判决 NodeB是否需要切换， 当判决出 NodeB需要切换时通知配置及切换控制单 元进行切换控制。
进一步的， NodeB所属的 RNC具体为 RNC1 ,备份 RNC具体为 RNC2 时， 配置及切换控制单元进一步包括： 0MC-RNC1、 OMC-RNC2; 切换决 策单元， 进一步为 NodeB切换决策子系统。 其中， NodeB切换决策子系统 可以单独部署在 NodeB侧、或者分别与 OMC-RNC1和 OMC-RNC2集成部 署在一起。
进一步的， 0MC-RNC1 进一步用于在 NodeB切换决策子系统判决出 NodeB需要从 RNC1切换到 RNC2的情况下， 将 RNC1上与 Node B有关 的配置数据同步到 0MC - RNC2; 切换完成后， 删除 RNC1上与 Node B有 关的配置数据。 0MC-RNC2 进一步用于根据所同步的配置数据对本地与 NodeB相关的数据进行更新，更新后通知 RNC2建立小区无线资源为 NodeB 提供服务。
进一步的， NodeB切换决策子系统能接受外部的操作维护中心发出的 命令、 或者能接受由 RNC1、 RNC2及 NodeB运行过程中发出的信息指令。
进一步的， 0MC-RNC1进一步用于能直接与 0MC-RNC2交互进行数 据同步、或者能在上级的电信管理网络的控制下与 0MC-RNC2交互进行数 据同步。
综上所述， 釆用本发明， 与现有技术相比， 可以整体提高 RNC的可靠 性， 减少 RNC发生单点故障的可能性； 可以大大简化运维的工作量， 由于 操作维护管理中心的参与， 使得本发明在数据配置、 故障管理、 性能管理 等等可运维方面具有非常大的好处， 让 RNC 容灾、 NodeB 双备份等增强 RNC/NodeB可靠性的方式真正的实现可运行维护、 可管理； NodeB的切换 可以实现自动判断、 也可以实现人工干预的方式， 切换也可以按照 NodeB 组进行批量切换、 也可以按照单个 NodeB进行切换， 批量切换下， NodeB 切换决策子系统可以收集需要切换的 NodeB, 等收集到一定的数量后， 对 这些 NodeB集中执行切换过程， 单个 NodeB的切换则是指 NodeB切换决 策子系统检测到一个 NodeB需要切换时， 立即对该 NodeB发起切换过程； 故障告警、性能计数器等可以在合并成同一个固定的身份 NodeB/小区数据， 也可以分开处理， 更加有利于运营维护的需要。
以下对本发明进行举例阐述。
如图 2所示为本发明方法的一处理流程实例示意图， 包括以下步骤： 步骤 101、 NodeB同 RNC1建立无线资源归属关系。
步骤 102、 NodeB切换决策子系统进行切换判决， 如果判决出 NodeB 需要进行切换， 则执行步骤 103; 否则， 判决出 NodeB不需要进行切换， 结束当前切换流程。
步骤 103、 OMC-RNC1将与 NodeB相关的数据同步到 OMC-RNC2。 步骤 104、 OMC-RNC2更新本地的数据。
步骤 105、 RNC2和 NodeB建立无线资源归属关系。
步骤 106、 RNC1删除 NodeB的服务小区数据， 更新邻区相关数据。 如图 3 所示为本发明系统的一组成结构实例示意图， 包括： 核心网所 管辖的 RNC1和 RNC2, RNC1和 RNC2分别作为 NodeB的所属 RNC和备 份 RNC;起切换判决的 NodeB切换决策子系统； OMC-RNC1和 OMC-RNC2 分别作为 RNC1 和 RNC2 的操作维护中心， 用于二者之间的数据同步； OMC-NodeB作为 NodeB的操作维护中心， 还包括电信管理网络（ TMN )。
应用实例一：
本实例中，参考图 4所示的组成结构示意图，可以单独部署一个 NodeB 切换决策子系统， 用于切换的判决； OMC-RNC 和 RNC 部署在一起， 如 OMC-RNC1 和 RNC1 部署在一起， OMC-RNC2 和 RNC2部署在一起； OMC-NodeB和 OMC-RNC部署在一起，如 OMC-NodeB可以和 OMC-RNC 1 部署在一起， 也可以和 OMC-RNC2 部署在一起； 配置数据可以保存在 OMC-RNC 1和 OMC-RNC2中任一个 OMC-RNC上。
本实例的切换实现流程如图 5所示， 包括以下步骤： 步骤 201: RNC1作为 NodeB的主用 RNC,是 NodeB当前所属的 RNC, 在 NodeB和 RNC1之间建立小区等无线资源。
步骤 202: NodeB检测到长时间没有来自 RNC1的周期性审计消息，但 是 lub链路仍然工作正常， NodeB将检测结果上报给 NodeB切换决策子系 统。
步骤 203: NodeB 切换决策子系统判决出需要切换， 并据此向 RNC2 发出指令， 指示 RNC2接管 NodeB。
步骤 204: NodeB切换决策子系统向 OMC-RNC1发出指令， 将 NodeB 相关的数据同步给 RNC2。
步骤 205: OMC-RNC2收到数据后，更新相关邻区数据配置。在本 RNC 内的小区， 如果以前有以切换的小区为邻区， 则更新这小区的邻区数据。
步骤 206: 在 NodeB和 RNC2之间建立小区等无线资源。
步骤 207: OMC - RNC1删除切换的 NodeB数据， 更新本 RNC下的邻 区数据。
应用实例二：
本实例的切换实现流程如图 6所示， 包括以下步骤：
步骤 301: RNC1作为 NodeB的主用 RNC,是 NodeB当前所属的 RNC, 在 NodeB和 RNC1之间建立小区等无线资源。
步骤 302: 在运行过程中， 同 NodeB相关的数据， 如果有变化， 则实 施同步到 RNC2对应的 OMC-RNC2上。
步骤 303: RNC1设备整体故障， NodeB切换决策子系统检测到 RNC1 长时间没有应答信息。
步骤 304 : NodeB 切换决策子系统判决出需要切换， 并据此向 OMC-RNC2发出指令， 指示 RNC2接管 NodeB。
步骤 305: OMC-RNC2收到命令后，更新相关邻区数据配置。在本 RNC 内的小区， 如果以前有以切换的小区为邻区， 则更新这小区的邻区数据。 步骤 306: 在 NodeB和 RNC2之间建立小区等无线资源。
应用实例三：
本实例的切换实现流程如图 7所示， 包括以下步骤：
步骤 401: RNC1作为 NodeB的主用 RNC,是 NodeB当前所属的 RNC, 在 NodeB和 RNC1之间建立小区等无线资源。
步骤 402:操作维护人员在 OMC-NodeB上发起一个人工切换操作命令， OMC-NodeB将该命令上报给 NodeB切换决策子系统。
步骤 403: NodeB 切换决策子系统判决出需要切换， 并据此向 RNC2 发出指令， 指示 RNC2接管 NodeB。
步骤 404: NodeB切换决策子系统向 OMC-RNC1发出指令， 将 NodeB 相关的数据同步给 RNC2。
步骤 405: OMC-RNC2收到数据后，更新相关邻区数据配置。在本 RNC 内的小区， 如果以前有以切换的小区为邻区， 则更新这小区的邻区数据。
步骤 406: 在 NodeB和 RNC2之间建立小区等无线资源。
步骤 407: OMC-RNC1删除切换的 NodeB数据， 更新本 RNC下的邻 区数据。
应用实例四：
本实例的切换实现流程如图 8所示， 包括以下步骤：
步骤 501: RNC1作为 NodeB的主用 RNC,是 NodeB当前所属的 RNC, 在 NodeB和 RNC1之间建立小区等无线资源。
步骤 502: 在运行过程中， 同 NodeB相关的数据， 如果有变化， 则实 施同步到 RNC2对应的 OMC-RNC2上， 同时， 周期性的数据同步过程也是 存在的。
步骤 503: RNC1负荷过高， 将信息上才艮给 NodeB切换决策子系统。 步骤 504 : NodeB 切换决策子系统判决出需要切换， 并据此向 OMC-RNC2发出指令， 指示 RNC2接管 NodeB。
步骤 505: OMC-RNC2收到命令后，更新相关邻区数据配置。在本 RNC 内的小区， 如果以前有以切换的小区为邻区， 则更新这小区的邻区数据。
步骤 506: 在 NodeB和 RNC2之间建立小区等无线资源。
应用实例五：
本实例中， 参考图 9所示的组成结构示意图， NodeB切换决策子系统 部署在 RNC1和 RNC2上； OMC-RNC和 RNC部署在一起，如 OMC-RNC1 和 RNC1部署在一起， OMC-RNC2和 RNC2部署在一起； OMC-NodeB和 OMC-RNC部署在一起， 如 OMC-NodeB可以和 OMC-RNC1部署在一起， 也可以和 OMC-RNC2部署在一起； 配置数据可以保存在 OMC-RNC1 和 OMC-RNC2中任一个 OMC-RNC上。
本实例的切换实现流程， 如图 10所示包括以下步骤：
步骤 601: RNC1作为 NodeB的主用 RNC,是 NodeB当前所属的 RNC, 在 NodeB和 RNC1之间建立小区等无线资源。当 RNC1上 NodeB相关的数 据发起变更， 均在 RNC2上实时做一次备份。
步骤 602: 部署在 RNC2上的 NodeB切换决策子系统发现 RNC1 已经 整体故障，判决出需要切换，向自身所在的 RNC2发起接管 NodeB的命令。
步骤 603: RNC2将之前 NodeB的备份数据作为正式数据， 提交生效。 步骤 604: RNC2更新相关邻区数据配置。
步骤 605: 在 NodeB和 RNC2之间建立小区等无线资源。
步骤 606: RNC1故障恢复后， 部署在 RNC1上的 NodeB切换决策子 系统发现 NodeB已经切换到 RNC2上， 删除自身所在的 RNC1上的 NodeB 相关生效数据， 更新邻区相关配置。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。 工业实用性
采用本发明， 通过为 NodeB配置备份 RNC,当其中一个 RNC无法正常 工作时， 将 NodeB切换到另一个 RNC上， 保证 NodeB业务的连续性， 提 高网络的可靠性。

Claims

权利要求书
1、一种提高无线网络控制器可靠性的方法，其特征在于，该方法包括： 为基站（ NodeB )当前所属的无线网络控制器（ RNC )配置对应的备份 RNC, 当根据切换策略判决出所述 NodeB需要切换时，将所述 NodeB由其所属的 RNC切换到所述备份 RNC, 将所述 NodeB所属的 RNC 上与 Node B有关 的配置数据同步到所述备份 RNC。
2、 根据权利要求 1所述的方法， 其特征在于， 该方法还包括： 所述备 份 RNC根据所同步的配置数据对本地与 NodeB相关的数据进行更新，切换 完成后， 删除所述 NodeB所属的 RNC上与 Node B有关的配置数据。
3、根据权利要求 1或 2所述的方法， 其特征在于， 所述 NodeB所属的 RNC为第一无线网络控制器（RNC1 ), 所述备份 RNC为第二无线网络控 制器（ RNC2 )时，该方法还包括：切换之前，所述 NodeB分别与所述 RNC1 和所述 RNC2建立传输连接， 并在所述 RNC1上建立小区， 为 NodeB提供 服务， 所述 RNC2不涉及 NodeB的业务。
4、 根据权利要求 3所述的方法， 其特征在于， 执行所述判决所参考的 信息包括： 外部的操作维护命令、 RNC1 和 RNC2的运行状态、 RNC1 和 RNC2的 Iub口和 Iu口的链路状态、 RNC1和 RNC2的负荷、 NodeB的地 理位置信息及分地理分布信息中的至少一种。
5、 根据权利要求 2所述的方法， 其特征在于， 所述与 NodeB相关的 数据包括： 邻区关系； 和 /或为故障管理、 性能管理呈现的 NodeB和 NodeB 所管辖的小区的身份信息。
6、一种提高无线网络控制器可靠性的系统，其特征在于，该系统包括： 配置及切换控制单元、 切换决策单元； 其中，
所述配置及切换控制单元， 用于为 NodeB当前所属的 RNC配置对应 的备份 RNC, 在获知 NodeB需要切换的情况下， 控制 NodeB由其所属的 RNC切换到所述备份 RNC, 将 NodeB所属的 RNC 上与 Node B有关的配 置数据同步到所述备份 RNC;
所述切换决策单元， 用于根据切换策略判决 NodeB是否需要切换， 当 判决出 NodeB需要切换时通知所述配置及切换控制单元进行切换控制。
7、根据权利要求 6所述的系统，其特征在于，所述 NodeB所属的 RNC 为 RNC1 , 所述备份 RNC为 RNC2时， 所述配置及切换控制单元， 进一步 包括： RNC 操作维护中心 1 ( 0MC-RNC1 )、 RNC 操作维护中心 2
( OMC-RNC2 ); 所述切换决策单元， 进一步为 NodeB切换决策子系统； 所述 NodeB切换决策子系统单独部署在 NodeB侧、 或者分别与所述 OMC-RNC1和所述 OMC-RNC2集成部署在一起。
8、 根据权利要求 7所述的系统， 其特征在于， 所述 OMC-RNC1 , 进 一步用于在所述 NodeB切换决策子系统判决出 NodeB需要从 RNC1切换到 RNC2的情况下， 将 RNC1 上与 Node B有关的配置数据同步到 OMC - RNC2; 切换完成后， 删除 RNC1上与 Node B有关的配置数据；
所述 OMC-RNC2,进一步用于根据所同步的配置数据对本地与 NodeB 相关的数据进行更新， 更新后通知 RNC2建立小区无线资源为 NodeB提供 服务。
9、 根据权利要求 7所述的系统， 其特征在于， 所述 NodeB切换决策 子系统， 进一步用于能接受外部的操作维护中心发出的命令、 或者能接受 由 RNC1、 RNC2及 NodeB运行过程中发出的信息指令。
10、 根据权利要求 8所述的系统， 其特征在于， 所述 OMC-RNC1 , 进 一步用于能直接与所述 OMC-RNC2交互进行数据同步、或者能在上级的电 信管理网络的控制下与所述 OMC-RNC2交互进行数据同步。
PCT/CN2011/075575 2010-11-18 2011-06-10 一种提高无线网络控制器可靠性的方法及系统 WO2012065433A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010551272.2A CN102469486B (zh) 2010-11-18 2010-11-18 一种提高无线网络控制器可靠性的方法及系统
CN201010551272.2 2010-11-18

Publications (1)

Publication Number Publication Date
WO2012065433A1 true WO2012065433A1 (zh) 2012-05-24

Family

ID=46072508

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/075575 WO2012065433A1 (zh) 2010-11-18 2011-06-10 一种提高无线网络控制器可靠性的方法及系统

Country Status (2)

Country Link
CN (1) CN102469486B (zh)
WO (1) WO2012065433A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3002906A4 (en) * 2013-06-09 2016-06-08 Huawei Tech Co Ltd METHOD AND DEVICE FOR UPGRADING A RADIO NET CONTROL

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103229536B (zh) * 2012-12-27 2017-04-19 华为技术有限公司 双网备份的方法、设备和无线通信系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127588A (zh) * 2007-10-11 2008-02-20 华为技术有限公司 一种无线网络控制器的故障处理方法、系统及装置
CN101547084A (zh) * 2008-03-24 2009-09-30 大唐移动通信设备有限公司 一种多媒体广播业务传输系统及方法
CN101621820A (zh) * 2009-07-29 2010-01-06 普天信息技术研究院有限公司 一种Iub口主备用链路切换方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8195187B2 (en) * 2001-06-25 2012-06-05 Airvana Network Solutions, Inc. Radio network control
CN1232131C (zh) * 2001-11-06 2005-12-14 华为技术有限公司 无线接入网中基站控制器的备份实现方法及装置
JP4400733B2 (ja) * 2004-03-31 2010-01-20 日本電気株式会社 移動体通信システムの制御方法
CN100389628C (zh) * 2006-02-10 2008-05-21 华为技术有限公司 一种无线网络控制器节点容灾方法及系统
CN101217824B (zh) * 2008-01-07 2010-12-22 华为技术有限公司 无线网络切换系统及其切换方法
CN101867941B (zh) * 2010-06-10 2012-08-08 华为技术有限公司 数据处理方法及网管设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127588A (zh) * 2007-10-11 2008-02-20 华为技术有限公司 一种无线网络控制器的故障处理方法、系统及装置
CN101547084A (zh) * 2008-03-24 2009-09-30 大唐移动通信设备有限公司 一种多媒体广播业务传输系统及方法
CN101621820A (zh) * 2009-07-29 2010-01-06 普天信息技术研究院有限公司 一种Iub口主备用链路切换方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3002906A4 (en) * 2013-06-09 2016-06-08 Huawei Tech Co Ltd METHOD AND DEVICE FOR UPGRADING A RADIO NET CONTROL

Also Published As

Publication number Publication date
CN102469486B (zh) 2015-09-16
CN102469486A (zh) 2012-05-23

Similar Documents

Publication Publication Date Title
EP3596969B1 (en) Slice-compliant handover control
CN105704769B (zh) 基站内小区间切换的方法及系统
EP2560454B1 (en) Method and system for implementing direct interface between access network nodes
EP2601804B1 (en) Method for self-optimized interworking between radio access networks
EP2346215B1 (en) Equipment pool management method, node equipment and communication system
US20110235505A1 (en) Efficient deployment of mobility management entity (MME) with stateful geo-redundancy
WO2018113410A1 (zh) 一种无线链路管理的方法及装置、系统、存储介质
EP1983777A1 (en) Method,system and control device for disaster recovery of rnc nodes
WO2001086988A1 (en) Rehoming and resource sharing in cellular communications networks
CN101536568B (zh) 用于在无线电通信系统中出现故障的情况下恢复连通性的方法及其控制节点
CN110267289A (zh) 一种检测无线链路失败或切换失败原因的方法
CN108282796B (zh) 一种无线链路管理的方法及装置、系统
WO2006063519A1 (fr) Procede de mise en reseau de station de base de reseau d'acces sans fil et reseau d'acces sans fil
CN101009940A (zh) 最小化分组呼叫重连延迟时间的切换方法及其多模终端
CN105580434A (zh) 交换主节点
JP2021519033A (ja) 第１のアクセスネットワークノードを管理する方法、装置、５Ｇネットワークの一般ノードＢ（ｇＮＢ）、非一時的コンピュータ可読媒体、コンピュータプログラム製品、及びデータセット
WO2012155595A1 (zh) 一种无线资源控制连接恢复方法、基站及终端
WO2012019553A1 (zh) 接口连通性信息的发送与接收方法、设备和系统
CN101932015A (zh) 切换参数调整方法及装置
CN101232402B (zh) 无线网络系统及其通讯方法
CN107770828B (zh) 一种基于本地移动性切换管理方法
CN101094502B (zh) 一种网络体系结构及基于该网络体系结构的切换方法
WO2014198018A1 (zh) 无线控制器升级方法和设备
CN102264084A (zh) 一种多基站联合进行覆盖优化的方法及装置
WO2012065433A1 (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: 11842365

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

Country of ref document: EP

Kind code of ref document: A1