CN102469486B - A kind of method and system improving reliability of wireless network controller - Google Patents

A kind of method and system improving reliability of wireless network controller Download PDF

Info

Publication number
CN102469486B
CN102469486B CN201010551272.2A CN201010551272A CN102469486B CN 102469486 B CN102469486 B CN 102469486B CN 201010551272 A CN201010551272 A CN 201010551272A CN 102469486 B CN102469486 B CN 102469486B
Authority
CN
China
Prior art keywords
nodeb
rnc
rnc1
omc
rnc2
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201010551272.2A
Other languages
Chinese (zh)
Other versions
CN102469486A (en
Inventor
冯超
续斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN201010551272.2A priority Critical patent/CN102469486B/en
Priority to PCT/CN2011/075575 priority patent/WO2012065433A1/en
Publication of CN102469486A publication Critical patent/CN102469486A/en
Application granted granted Critical
Publication of CN102469486B publication Critical patent/CN102469486B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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

Landscapes

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

Abstract

The invention discloses a kind of method improving reliability of wireless network controller, the method comprises: be the backup RNC that the configuration of base station (NodeB) current affiliated radio network controller (RNC) is corresponding, when ruling out NodeB according to switchover policy and needing to switch, the RNC of NodeB belonging to it is switched to backup RNC, configuration data relevant with Node B on the RNC belonging to NodeB is synchronized to and backs up RNC.The invention also discloses a kind of system improving reliability of wireless network controller, the handover decisions unit in this system is used for notice configuration and switch control unit when ruling out NodeB and needing to switch and carries out switching controls.Adopt method and system of the present invention, can improve the reliability of RNC, when one of them RNC can not provide service for NodeB, all NodeB had under its command are switched on another one RNC.

Description

Method and system for improving reliability of wireless network controller
Technical Field
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.
Background
Network reliability is one of the concerns of operators. Besides relying on high-reliability network element equipment and network infrastructure, the reliability of the network also contributes to the improvement of the network reliability due to a new networking mode and a new network topology. The network element equipment comprises a Core Network (CN)/RNC/base station (NodeB) and the like; the network infrastructure includes transmission network equipment and communication cables/cables, etc.
Fig. 1 is a diagram of the architecture of the UMTS radio access network of the existing 3GPP, and it can be seen from fig. 1 that the Iu-flex networking technology that has been standardized at present is that one RNC can be connected to multiple CNs, and multiple CNs form a resource Pool (Resources Pool), and when one of the CNs fails, or when one of the CNs is overloaded, the traffic of a user can be shared by other CNs. One of the purposes of using Iu flex is to improve the reliability of the CN.
Similar backup and redundancy mechanisms have not been implemented by 3GPP in radio access networks at present. Since the number of nodebs accessing each RNC in the radio access network is huge (tens, hundreds or even thousands), the probability of occurrence of link failure at the Iub port is much higher than that at the Iu port. This can lead to adverse conditions, such as: (1) although the effect of a Iub port failure is lower than that of the Iu port, it will still interrupt the service of one or more sites (in case of NodeB concatenation), causing regional user complaints; (2) if disaster conditions are met to cause the failure of the whole RNC, all NodeBs under the jurisdiction of the RNC cannot work, and a very large communication blind area is formed. It can be seen that: it is necessary to establish a mechanism for improving reliability of the RNC, and in order to improve reliability of the RNC, it may be considered that when one RNC cannot provide a service for a NodeB, all nodebs under its jurisdiction are switched to another RNC, which may also be understood as: and providing a backup RNC for the NodeB and establishing a backup mechanism. However, no such implementation is currently available.
Disclosure of Invention
In view of the above, the main objective of the present invention is to provide a method and a system for improving reliability of RNCs, which can improve reliability of RNCs, and switch all nodebs under its jurisdiction to another RNC when one RNC cannot provide services for the nodebs.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a method of improving reliability of a radio network controller, the method comprising: configuring a corresponding backup RNC for a Radio Network Controller (RNC) to which a base station (NodeB) belongs currently, switching the NodeB from the RNC to the backup RNC when the NodeB needs to be switched according to a switching strategy, and synchronizing configuration data related to the NodeB on the RNC to which the NodeB belongs to the backup RNC.
Wherein, the method also comprises: and the backup RNC updates local data related to the NodeB according to the synchronized configuration data, and deletes the configuration data related to the NodeB on the RNC to which the NodeB belongs after the switching is finished.
Wherein, when the RNC to which the NodeB belongs is specifically the first radio network controller (RNC1), and the backup RNC is specifically the second radio network controller (RNC2), the method further includes: before handover, the NodeB establishes transport connections with the RNC1 and the RNC2, respectively, and establishes cells on the RNC1 to serve the NodeB, and the RNC2 does not involve the traffic of the NodeB.
Wherein the information referred to for performing the decision comprises: at least one of external operation and maintenance commands, operation states of the RNC1 and the RNC2, link states of the Iub port and the Iu port of the RNC1 and the RNC2, loads of the RNC1 and the RNC2, geographical location information of the NodeB, and sub-geographical distribution information.
Wherein the data related to the NodeB specifically includes: a neighbor relation; and/or the identity information of the NodeB and the cells governed by the NodeB is presented for fault management and performance management.
A system for improving reliability of a radio network controller, the system comprising: a configuration and switching control unit and a switching decision unit; wherein,
the configuration and switching control unit is used for configuring a corresponding backup RNC for the RNC to which the NodeB currently belongs, controlling the NodeB to be switched to the backup RNC from the RNC to which the NodeB belongs under the condition that the NodeB is informed of the need of switching, and synchronizing configuration data related to the NodeB on the RNC to which the NodeB belongs to the backup RNC;
and the switching decision unit is used for judging whether the NodeB needs to be switched or not according to the switching strategy, and informing the configuration and switching control unit to carry out switching control when the NodeB needs to be switched.
Wherein, when the RNC to which the NodeB belongs is specifically the RNC1, and the backup RNC is specifically the RNC2, the configuration and switching control unit further includes: RNC operation maintenance center 1(OMC-RNC1), RNC operation maintenance center 2(OMC-RNC 2); the switching decision unit is further a NodeB switching decision subsystem;
the NodeB switching decision subsystem is separately deployed at the NodeB side or is respectively integrated with the OMC-RNC1 and the OMC-RNC2 for deployment,
the information referred to for performing the decision includes: at least one of an external operation maintenance command, an operation state of the OMC-RNC1 and the OMC-RNC2, a link state of the Iub port and the Iu port of the OMC-RNC1 and the OMC-RNC2, a load of the OMC-RNC1 and the OMC-RNC2, geographical location information of the NodeB, and sub-geographical distribution information.
Wherein the OMC-RNC1 is further configured to synchronize Node B related configuration data on RNC1 to OMC-RNC2 if the NodeB handover decision subsystem determines that the NodeB needs to be handed over from RNC1 to RNC 2; after the switching is completed, deleting configuration data related to Node B on RNC 1;
the OMC-RNC2 is further configured to update local data related to the NodeB according to the synchronized configuration data, and notify the RNC2 to establish cell radio resources to provide services for the NodeB after the update.
The NodeB switching decision subsystem is further configured to receive a command sent by an external operation and maintenance center, or receive an information instruction sent by the RNC1, the RNC2, and the NodeB during operation.
The OMC-RNC1 is further configured to interact with the OMC-RNC2 directly for data synchronization or interact with the OMC-RNC2 under the control of a higher-level telecommunications management network.
The invention configures a corresponding backup RNC for the RNC to which the NodeB currently belongs, when the NodeB is judged to need switching according to a switching strategy, the NodeB is switched to the backup RNC from the RNC to which the NodeB belongs, and the configuration data related to the NodeB on the RNC to which the NodeB belongs is synchronized to the backup RNC.
By adopting the invention, the backup RNC is configured for the NodeB, when one RNC can not work normally, the NodeB is switched to the other RNC, thereby ensuring the continuity of the NodeB service and improving the reliability of the network.
Drawings
FIG. 1 is a diagram of a prior art 3GPP UMTS radio access network architecture;
FIG. 2 is a schematic diagram of an example process flow of the method of the present invention;
FIG. 3 is a schematic diagram of an example of the composition of the system of the present invention;
FIG. 4 is a schematic diagram of a first embodiment of the present invention;
FIG. 5 is a flow chart illustrating a first implementation of the first embodiment of the present invention;
FIG. 6 is a flow chart illustrating an implementation of a second application example of the present invention;
FIG. 7 is a flow chart illustrating a third implementation of the present invention;
FIG. 8 is a flow chart illustrating an implementation of example four of the present invention;
FIG. 9 is a schematic diagram showing the constitution of a fifth example of the application of the present invention;
fig. 10 is a schematic flow chart of an implementation example five of the present invention.
Detailed Description
The basic idea of the invention is: and configuring a corresponding backup RNC for the RNC to which the NodeB currently belongs, switching the NodeB from the RNC to which the NodeB belongs to the backup RNC when the NodeB needs to be switched according to a switching strategy, and synchronizing configuration data related to the NodeB on the RNC to which the NodeB belongs to the backup RNC so as to ensure the continuity of the NodeB service.
The invention is further described with reference to the following examples with reference to the accompanying drawings.
A method for improving reliability of RNC includes:
and configuring a corresponding backup RNC for the RNC to which the NodeB currently belongs, and switching the NodeB from the RNC to the backup RNC when the NodeB is judged to be required to be switched to the backup RNC according to the switching strategy. Here, the decision may be made by a newly added NodeB handover decision subsystem, as described in detail with respect to the system of the present invention. And will not be described in detail herein.
The following description will be made by taking the first radio network controller (RNC1) as the current RNC of the NodeB and the second radio network controller (RNC2) as the backup RNC.
Firstly, the NodeB establishes transport connections with the RNC1 and the RNC2, and maintains a substantial radio resource assignment relationship with the RNC1, that is: cells are established on the RNC1 to serve the NodeB, and the RNC2 does not involve any traffic relationship with the NodeB.
Further, the relevant radio network layer data of the NodeB has only one piece of valid data between both RNC1 and RNC2, and exists only at the RNC having the radio resource attribution relationship with the NodeB. The initial configuration is determined by network planning.
Further, the neighboring cells related to the NodeB, including the neighboring cells of the cell under the NodeB, or the cell under the NodeB is a neighboring cell of another cell, only need to configure data under initial configuration.
Further, the valid data refers to data that can interact with the NodeB, and is not limited to a specific representation, for example, a set of NodeB data may be stored in the RNC1 and the RNC2, respectively, but the data in the RNC1 is valid data, and the NodeB can be operated under the RNC 1; while the data on RNC2 is only a collection and does not allow the NodeB to operate under RNC 2.
And secondly, the NodeB switching decision subsystem can judge that the NodeB needs to be switched from the RNC1 to the RNC2 according to the switching strategy.
Further, the NodeB switching decision subsystem is responsible for making the final NodeB switching decision, and the NodeB switching decision subsystem may receive an instruction from an external operation maintenance center, or may receive an information instruction sent by the RNC and the NodeB during the operation.
Further, the NodeB handover decision subsystem may transfer information between the operation and maintenance center, the RNC, and the NodeB. Such as information transfer between RNC1 and RNC operation and maintenance center 1(OMC-RNC1), information transfer between RNC2 and RNC operation and maintenance center 2(OMC-RNC2), information transfer between NodeB operation and maintenance center (OMC-NodeB) and NodeB, etc.
Further, the information that can be referred to when the NodeB switching decision subsystem makes a decision includes: external operation and maintenance commands, the operation states of the RNC1 and the RNC2, and the link states of the Iub port and the Iu port of the RNC 1/the RNC 2. Further, reference may also be made to the load of RNC1 and RNC 2. Furthermore, the decision may also refer to the geographical location information of the NodeB and the sub-geographical distribution information. Wherein the external operation and maintenance command comprises a manual operation and the like. The operation states of the RNC1 and the RNC2 include a physical device state, a software operation state, a traffic service state, and the like. The link state includes whether the link works normally, and the like, and the load includes occupation of physical resources, occupation of wireless resources, and the like.
Further, the NodeB switching decision subsystem is a logical concept, and its physical representation may be various, for example, the NodeB switching decision subsystem is deployed and distributed on each node device, or may be deployed on one node device in a centralized manner, and so on. The key point is its logical function, the NodeB handover decision subsystem can decide when to perform the NodeB handover. Specifically, the method comprises the following steps:
further, the handover policy includes: the current RNC fault of NodeB or the current RNC link fault between NodeB and NodeB must be switched to backup RNC; or, the RNC to which the NodeB currently belongs is overloaded, and a handover to the backup RNC may be selected in order to provide better service to the user. Specifically, the NodeB handover decision subsystem may make handover decisions based on the following handover strategies, but not limited to these, the emphasis is to make decisions based on rules based on inputs:
the operation maintenance personnel initiates a NodeB switching command in the operation center, and the NodeB switching decision subsystem decides to initiate the switching command.
The RNC1 has a failure in the whole device, and the NodeB handover decision subsystem decides to initiate a handover command.
The RNC1 cannot serve the NodeB because of a software failure, etc., whereupon the NodeB handover decision subsystem decides to initiate a handover command.
The Iub interface links of NodeB and RNC1 are broken, and the NodeB switching decision subsystem decides to initiate the switching command.
The Iu interface link between the RNC1 and the CN is broken, and the NodeB switching decision subsystem decides to initiate a switching command.
The RNC1 is overloaded and the NodeB handover decision subsystem decides to initiate a handover command.
Thirdly, the configuration data of the NodeB to be handed over can be synchronized by the OMC-RNC1 to the OMC-RNC2 of the RNC 2.
Further, there is an inherent consistency between the OMC-RNC1 and the OMC-RNC2 for the data of the same NodeB, and the data consistency can be achieved by an automatic synchronization process, which may be in a real-time, periodic or event-triggered manner. Data consistency can also be achieved manually, with the emphasis on data having inherent consistency.
Further, the automatic synchronization process of data between the OMC-RNC1 and the OMC-RNC2 may be directly interactive or may be synchronized through a higher level telecommunication maintenance network.
Further, the data of the OMC-NodeB to the NodeB is also consistent before and after the NodeB is handed over, and if the OMC-NodeB is attached to the OMC-RNC, the OMC-NodeB may be synchronized to maintain consistency.
Further, for the scenario that the OMC-NodeB is attached to the OMC-RNC, the NodeB can accept the operation and maintenance commands of the OMC-NodeB on different OMC-RNCs.
And fourthly, after data synchronization is carried out between the OMC-RNC1 and the OMC-RNC2, the OMC-RNC2 updates data related to the NodeB, wherein the data comprises the neighboring area relation, and identity information of the NodeB and cells governed by the NodeB, which is presented for fault management and performance management.
Further, for the NodeB switched from RNC1 to RNC2, OMC-RNC2 needs to change the data of the neighboring cell relation between the RNC and the switched NodeB once, so as to ensure that the mobility of the NodeB is still not affected after the NodeB is switched.
Further, the updating of the data may be automatic or may be manually intervened.
Further, after the NodeB is switched to the RNC2, the operation, maintenance, and management center may merge the identity of the NodeB on the RNC2 with the province of the NodeB on the RNC1, and present a consistent identity to the functions of external fault management, performance management, and the like, or may not merge the identities, and maintain independent identities.
And fifthly, the RNC2 establishes radio resources such as cells and the like together with the NodeB according to the self situation and the process specified by the 3GPP, and the RNC2 formally serves the NodeB.
And sixthly, the NodeB is switched to the RNC2, and after the RNC2 formally serves the NodeB, the OMC-RNC1 deletes the service cell data of the NodeB and updates the adjacent cell data related to the NodeB under the RNC 1.
Further, for the NodeB switched from RNC1 to RNC2 and the cell governed by the NodeB, OMC-RNC1 needs to change the data of the neighboring cell relationship between the RNC and the switched NodeB at one time, so as to ensure that the mobility is still not affected after the NodeB is switched.
And seventhly, the NodeB finishes the switching, the NodeB switching decision subsystem continues working, and if the NodeB needs to initiate the switching again, the switching operation is continuously executed from the two steps.
A system for improving reliability of a radio network controller, the system comprising: a configuration and switching control unit and a switching decision unit. The configuration and switching control unit is used for configuring a corresponding backup RNC for the RNC to which the NodeB belongs currently, controlling the NodeB to be switched to the backup RNC from the RNC to which the NodeB belongs under the condition that the NodeB needs to be switched, and synchronizing configuration data related to the NodeB on the RNC to which the NodeB belongs to the backup RNC. The switching decision unit is used for judging whether the NodeB needs to be switched according to the switching strategy, and informing the configuration and switching control unit to carry out switching control when the NodeB needs to be switched.
Further, when the RNC to which the NodeB belongs is specifically the RNC1, and the backup RNC is specifically the RNC2, the configuration and handover control unit further includes: OMC-RNC1, OMC-RNC 2; and the switching decision unit is further a NodeB switching decision subsystem. The NodeB switching decision subsystem may be deployed on the NodeB side alone, or may be deployed integrally with the OMC-RNC1 and the OMC-RNC2, respectively.
Further, the OMC-RNC1 is further configured to synchronize Node B related configuration data on the RNC1 to the OMC-RNC2 in case the NodeB handover decision subsystem decides that the NodeB needs to be handed over from the RNC1 to the RNC 2; after the handover is completed, the configuration data on the RNC1 relating to the Node B is deleted. The OMC-RNC2 is further adapted to update local NodeB-related data according to the synchronized configuration data, and to inform the RNC2 to establish cell radio resources to serve the NodeB.
Further, the NodeB switching decision subsystem can accept commands from an external operation and maintenance center, or can accept information commands from the RNC1, the RNC2, and the NodeB during operation.
Further, the OMC-RNC1 is further adapted to enable data synchronization directly with the OMC-RNC2 or with the OMC-RNC2 under control of a higher level telecommunications management network.
In summary, compared with the prior art, the reliability of the RNC can be integrally improved, and the possibility of single point failure of the RNC is reduced; the workload of operation and maintenance can be greatly simplified, and the participation of the operation, maintenance and management center ensures that the invention has great benefits in the aspects of data configuration, fault management, performance management and the like, and the modes of enhancing the reliability of RNC/NodeB, such as RNC disaster recovery, NodeB double backup and the like, can really realize operable maintenance and management; the switching of the NodeB can realize automatic judgment and can also realize a manual intervention mode, the switching can also be carried out in batch according to a NodeB group, or can also be carried out according to a single NodeB, under the batch switching, the NodeB switching decision subsystem can collect the NodeB to be switched, and after a certain quantity of NodeB is collected, the NodeB is intensively carried out the switching process, and the switching of the single NodeB means that when the NodeB switching decision subsystem detects that one NodeB needs to be switched, the NodeB is immediately initiated to the NodeB for switching; the fault alarm, the performance counter and the like can be combined into the same fixed identity NodeB/cell data, and can also be processed separately, thereby being more beneficial to the requirement of operation and maintenance.
The invention is illustrated below.
FIG. 2 is a schematic diagram of an exemplary process flow of the method of the present invention, including the following steps:
step 101, the NodeB and the RNC1 establish a radio resource attribution relationship.
Step 102, the NodeB switching decision subsystem carries out switching decision, if the NodeB is decided to need to carry out switching, step 103 is executed; otherwise, judging that the NodeB does not need to switch, and ending the current switching process.
Step 103, the OMC-RNC1 synchronizes the NodeB related data to the OMC-RNC 2.
Step 104, OMC-RNC2 updates the local data.
Step 105, RNC2 and NodeB establish radio resource attribution relation.
Step 106, the RNC1 deletes the serving cell data of the NodeB and updates the neighbor cell related data.
Fig. 3 is a schematic diagram of an example of the composition structure of the system of the present invention, which includes: RNC1 and RNC2 governed by the core network, and RNC1 and RNC2 are respectively used as the belonged RNC and the backup RNC of the NodeB; a NodeB switching decision subsystem for starting switching decision; the OMC-RNC1 and the OMC-RNC2 are respectively used as operation and maintenance centers of the RNC1 and the RNC2 for data synchronization between the two; the OMC-NodeB serves as an operation maintenance center of the NodeB and also comprises a Telecommunication Management Network (TMN).
Application example one:
in this example, referring to the schematic diagram of the composition structure shown in fig. 4, a NodeB handover decision subsystem may be separately deployed for handover decision; the OMC-RNC and the RNC are deployed together, for example, the OMC-RNC1 and the RNC1 are deployed together, and the OMC-RNC2 and the RNC2 are deployed together; the OMC-NodeB and the OMC-RNC are deployed together, for example, the OMC-NodeB can be deployed together with the OMC-RNC1 or can be deployed together with the OMC-RNC 2; the configuration data may be stored on either of the OMC-RNC1 and the OMC-RNC 2.
The handover implementation flow of this example is shown in fig. 5, and includes the following steps:
step 201: the RNC1 is a master RNC of a NodeB, which is currently a current RNC of the NodeB, and establishes radio resources such as cells between the NodeB and the RNC 1.
Step 202: the NodeB detects that no periodic audit message from the RNC1 exists for a long time, but the Iub link still works normally, and the NodeB reports the detection result to the NodeB switching decision subsystem.
Step 203: the NodeB handover decision subsystem decides that a handover is required and accordingly issues an instruction to the RNC2 instructing the RNC2 to take over the NodeB.
Step 204: the NodeB handover decision subsystem sends instructions to the OMC-RNC1 to synchronize NodeB related data to the RNC 2.
Step 205: and after receiving the data, the OMC-RNC2 updates the configuration of the relevant neighbor cell data. In the cell in the RNC, if the cell switched over before is used as the neighboring cell, the neighboring cell data of the cell is updated.
Step 206: radio resources such as cells are established between the NodeB and the RNC 2.
Step 207: and the OMC-RNC1 deletes the switched NodeB data and updates the neighbor cell data under the RNC.
Application example two:
the handover implementation flow of this example is shown in fig. 6, and includes the following steps:
step 301: the RNC1 is a master RNC of a NodeB, which is currently a current RNC of the NodeB, and establishes radio resources such as cells between the NodeB and the RNC 1.
Step 302: during operation, the data relating to the NodeB, if there is a change, is synchronized to the OMC-RNC2 corresponding to RNC 2.
Step 303: the RNC1 equipment is failed integrally, and the NodeB switching decision subsystem detects that the RNC1 has no response information for a long time.
Step 304: the NodeB handover decision subsystem decides that a handover is required and accordingly issues an instruction to the OMC-RNC2 instructing the RNC2 to take over the NodeB.
Step 305: and after receiving the command, the OMC-RNC2 updates the relevant neighbor cell data configuration. In the cell in the RNC, if the cell switched over before is used as the neighboring cell, the neighboring cell data of the cell is updated.
Step 306: radio resources such as cells are established between the NodeB and the RNC 2.
Application example three:
the handover implementation flow of this example is shown in fig. 7, and includes the following steps:
step 401: the RNC1 is a master RNC of a NodeB, which is currently a current RNC of the NodeB, and establishes radio resources such as cells between the NodeB and the RNC 1.
Step 402: and an operation maintenance worker initiates a manual switching operation command on the OMC-NodeB, and the OMC-NodeB reports the command to the NodeB switching decision subsystem.
Step 403: the NodeB handover decision subsystem decides that a handover is required and accordingly issues an instruction to the RNC2 instructing the RNC2 to take over the NodeB.
Step 404: the NodeB handover decision subsystem sends instructions to the OMC-RNC1 to synchronize NodeB related data to the RNC 2.
Step 405: and after receiving the data, the OMC-RNC2 updates the configuration of the relevant neighbor cell data. In the cell in the RNC, if the cell switched over before is used as the neighboring cell, the neighboring cell data of the cell is updated.
Step 406: radio resources such as cells are established between the NodeB and the RNC 2.
Step 407: and the OMC-RNC1 deletes the switched NodeB data and updates the neighbor cell data under the RNC.
Application example four:
the handover implementation flow of this example is shown in fig. 8, and includes the following steps:
step 501: the RNC1 is a master RNC of a NodeB, which is currently a current RNC of the NodeB, and establishes radio resources such as cells between the NodeB and the RNC 1.
Step 502: during operation, if there is a change in the data related to the NodeB, synchronization is performed to the OMC-RNC2 corresponding to the RNC2, and a periodic data synchronization procedure also exists.
Step 503: and when the load of the RNC1 is too high, the information is reported to the NodeB switching decision subsystem.
Step 504: the NodeB handover decision subsystem decides that a handover is required and accordingly issues an instruction to the OMC-RNC2 instructing the RNC2 to take over the NodeB.
Step 505: and after receiving the command, the OMC-RNC2 updates the relevant neighbor cell data configuration. In the cell in the RNC, if the cell switched over before is used as the neighboring cell, the neighboring cell data of the cell is updated.
Step 506: radio resources such as cells are established between the NodeB and the RNC 2.
Application example five:
in this example, referring to the schematic structural diagram shown in fig. 9, the NodeB switching decision subsystem is deployed on the RNC1 and the RNC 2; the OMC-RNC and the RNC are deployed together, for example, the OMC-RNC1 and the RNC1 are deployed together, and the OMC-RNC2 and the RNC2 are deployed together; the OMC-NodeB and the OMC-RNC are deployed together, for example, the OMC-NodeB can be deployed together with the OMC-RNC1 or can be deployed together with the OMC-RNC 2; the configuration data may be stored on either of the OMC-RNC1 and the OMC-RNC 2.
The handover implementation procedure of this example, as shown in fig. 10, includes the following steps:
step 601: the RNC1 is a master RNC of a NodeB, which is currently a current RNC of the NodeB, and establishes radio resources such as cells between the NodeB and the RNC 1. When the data related to the NodeB on the RNC1 is changed, a backup is made on the RNC2 in real time.
Step 602: and a NodeB switching decision subsystem deployed on the RNC2 finds that the RNC1 has overall failure, decides that switching is needed, and initiates a command for taking over the NodeB to the RNC2 where the NodeB is located.
Step 603: the RNC2 commits the previous backup data of the NodeB to effect as the official data.
Step 604: the RNC2 updates the relevant neighbor data configuration.
Step 605: radio resources such as cells are established between the NodeB and the RNC 2.
Step 606: after the failure of the RNC1 is recovered, the NodeB switching decision subsystem deployed on the RNC1 finds that the NodeB has been switched to the RNC2, deletes the NodeB-related valid data on the RNC1 where it is located, and updates the neighboring cell-related configuration.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims (7)

1. A method for improving reliability of a radio network controller, the method comprising: configuring a corresponding backup RNC for a Radio Network Controller (RNC) to which a base station (NodeB) belongs currently, switching the NodeB from the RNC to the backup RNC when the NodeB needs to be switched according to a switching strategy, and synchronizing configuration data related to the NodeB on the RNC to which the NodeB belongs to the backup RNC;
wherein, after the NodeB is switched to the backup RNC, the identity of the NodeB on the backup RNC is allowed to be merged with the identity of the NodeB on the RNC to which the NodeB belongs,
when the RNC to which the NodeB belongs is specifically the first radio network controller (RNC1), and the backup RNC is specifically the second radio network controller (RNC2), the method further includes: before handover, the NodeB establishes transport connections with the RNC1 and the RNC2, respectively, and establishes cells on the RNC1 to serve the NodeB, the RNC2 is not involved in the traffic of the NodeB,
the information referred to for performing the decision includes: at least one of external operation and maintenance commands, operation states of the RNC1 and the RNC2, link states of the Iub port and the Iu port of the RNC1 and the RNC2, loads of the RNC1 and the RNC2, geographical location information of the NodeB, and sub-geographical distribution information.
2. The method of claim 1, further comprising: and the backup RNC updates local data related to the NodeB according to the synchronized configuration data, and deletes the configuration data related to the NodeB on the RNC to which the NodeB belongs after the switching is finished.
3. The method according to claim 2, wherein the NodeB-related data specifically includes: a neighbor relation; and/or the identity information of the NodeB and the cells governed by the NodeB is presented for fault management and performance management.
4. A system for improving reliability of a radio network controller, the system comprising: a configuration and switching control unit and a switching decision unit; wherein,
the configuration and switching control unit is used for configuring a corresponding backup RNC for the RNC to which the NodeB currently belongs, controlling the NodeB to be switched to the backup RNC from the RNC to which the NodeB belongs under the condition that the NodeB is informed of the need of switching, and synchronizing configuration data related to the NodeB on the RNC to which the NodeB belongs to the backup RNC;
the switching decision unit is used for judging whether the NodeB needs to be switched according to the switching strategy, and informing the configuration and switching control unit to carry out switching control when the NodeB needs to be switched is judged;
wherein, after the NodeB is switched to the backup RNC, the identity of the NodeB on the backup RNC is allowed to be merged with the identity of the NodeB on the RNC to which the NodeB belongs,
the RNC to which the NodeB belongs is specifically the RNC1, and when the backup RNC is specifically the RNC2, the configuration and handover control unit further includes: RNC operation maintenance center 1(OMC-RNC1), RNC operation maintenance center 2(OMC-RNC 2); the switching decision unit is further a NodeB switching decision subsystem;
the NodeB switching decision subsystem is separately deployed at the NodeB side or is respectively integrated with the OMC-RNC1 and the OMC-RNC2 for deployment,
the information referred to for performing the decision includes: at least one of an external operation maintenance command, an operation state of the OMC-RNC1 and the OMC-RNC2, a link state of the Iub port and the Iu port of the OMC-RNC1 and the OMC-RNC2, a load of the OMC-RNC1 and the OMC-RNC2, geographical location information of the NodeB, and sub-geographical distribution information.
5. The system of claim 4 wherein the OMC-RNC1 is further configured to synchronize Node B related configuration data on RNC1 to OMC-RNC2 if the NodeB handover decision subsystem determines that a NodeB needs to be handed over from RNC1 to RNC 2; after the switching is completed, deleting configuration data related to Node B on RNC 1;
the OMC-RNC2 is further configured to update local data related to the NodeB according to the synchronized configuration data, and notify the RNC2 to establish cell radio resources to provide services for the NodeB after the update.
6. The system of claim 4 wherein the NodeB handover decision subsystem is further configured to accept commands from an external operation and maintenance center or information commands from the RNC1, the RNC2 and the NodeB during operation.
7. The system of claim 6, wherein the OMC-RNC1 is further configured to enable data synchronization directly with the OMC-RNC2 interaction or with the OMC-RNC2 interaction under control of a higher level telecommunications management network.
CN201010551272.2A 2010-11-18 2010-11-18 A kind of method and system improving reliability of wireless network controller Active CN102469486B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201010551272.2A CN102469486B (en) 2010-11-18 2010-11-18 A kind of method and system improving reliability of wireless network controller
PCT/CN2011/075575 WO2012065433A1 (en) 2010-11-18 2011-06-10 Method and system for enhanceing reliability of radio network controller

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201010551272.2A CN102469486B (en) 2010-11-18 2010-11-18 A kind of method and system improving reliability of wireless network controller

Publications (2)

Publication Number Publication Date
CN102469486A CN102469486A (en) 2012-05-23
CN102469486B true CN102469486B (en) 2015-09-16

Family

ID=46072508

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201010551272.2A Active CN102469486B (en) 2010-11-18 2010-11-18 A kind of method and system improving reliability of wireless network controller

Country Status (2)

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

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 updating radio network controller

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2012398320B2 (en) * 2012-12-27 2016-12-01 Huawei Technologies Co., Ltd. Method, device and wireless communication system for dual-network backup

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1418023A (en) * 2001-11-06 2003-05-14 华为技术有限公司 Back-up method and device for base station controller in radio access network
CN1678124A (en) * 2004-03-31 2005-10-05 日本电气株式会社 Executing handover and relocation involving plural RNCs
CN1859697A (en) * 2006-02-10 2006-11-08 华为技术有限公司 Disaster tolerance method and system for radio network controller node
CN101127588A (en) * 2007-10-11 2008-02-20 华为技术有限公司 A failure processing method, system and device for wireless network controller
CN101217824A (en) * 2008-01-07 2008-07-09 华为技术有限公司 Wireless network switching system and its switching method
CN101867941A (en) * 2010-06-10 2010-10-20 华为技术有限公司 Data processing method and network management equipment

Family Cites Families (3)

* 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
CN101547084B (en) * 2008-03-24 2011-04-20 大唐移动通信设备有限公司 System and method for transferring multimedia broadcasting service
CN101621820A (en) * 2009-07-29 2010-01-06 普天信息技术研究院有限公司 Method and device for switching host link and reserve links of Iub port

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1418023A (en) * 2001-11-06 2003-05-14 华为技术有限公司 Back-up method and device for base station controller in radio access network
CN1678124A (en) * 2004-03-31 2005-10-05 日本电气株式会社 Executing handover and relocation involving plural RNCs
CN1859697A (en) * 2006-02-10 2006-11-08 华为技术有限公司 Disaster tolerance method and system for radio network controller node
CN101127588A (en) * 2007-10-11 2008-02-20 华为技术有限公司 A failure processing method, system and device for wireless network controller
CN101217824A (en) * 2008-01-07 2008-07-09 华为技术有限公司 Wireless network switching system and its switching method
CN101867941A (en) * 2010-06-10 2010-10-20 华为技术有限公司 Data processing method and network management equipment

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 updating radio network controller

Also Published As

Publication number Publication date
CN102469486A (en) 2012-05-23
WO2012065433A1 (en) 2012-05-24

Similar Documents

Publication Publication Date Title
CN105704769B (en) The method and system of handover between cells in base station
CN101815298B (en) Tracking area optimizing and updating method, device and system
EP3596969B1 (en) Slice-compliant handover control
CN102209338B (en) Switching self-optimizing method for mobile communication network
EP2601804B1 (en) Method for self-optimized interworking between radio access networks
EP2346215B1 (en) Equipment pool management method, node equipment and communication system
JP5563524B2 (en) Radio communication system and method for changing accommodation of radio communication system component device
CN101877871B (en) Network self-organization method and evolution base station
CN108207010B (en) Method, device and system for managing wireless link
EP1983777A1 (en) Method,system and control device for disaster recovery of rnc nodes
WO2001086988A1 (en) Rehoming and resource sharing in cellular communications networks
CN108282796B (en) Method, device and system for managing wireless link
CA2249912C (en) Cellular networks with spare base and satellite stations
CN101124845B (en) Control unit and method for controlling load in mobile telecom network
CN102547764A (en) Method, system and device for improving mobile robustness
CN101094502B (en) Network architecture, and switching method based on the network architecture
CN102469486B (en) A kind of method and system improving reliability of wireless network controller
CN102647737B (en) Method and system for self optimization of wireless parameters
EP1971164A1 (en) Handover method for a mobile communication device and controller for handover of a mobile communication device
WO2006063519A1 (en) Method for networking base station of wireless access network and the wireless access network
CN104519506A (en) Method and device for self-optimization
EP1303943B1 (en) Base station control in telecommunications system
CN102395148A (en) Method for improving mobility robustness, system and equipment thereof
CN102281523A (en) Radio network controller and neighbouring cell information updating method thereof
CN117837266A (en) System and method for implementing interworking in an ad hoc network

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant