CN102469486A - Method and system for improving reliability of wireless network controller - Google Patents
Method and system for improving reliability of wireless network controller Download PDFInfo
- Publication number
- CN102469486A CN102469486A CN2010105512722A CN201010551272A CN102469486A CN 102469486 A CN102469486 A CN 102469486A CN 2010105512722 A CN2010105512722 A CN 2010105512722A CN 201010551272 A CN201010551272 A CN 201010551272A CN 102469486 A CN102469486 A CN 102469486A
- Authority
- CN
- China
- Prior art keywords
- nodeb
- rnc
- rnc2
- rnc1
- omc
- 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.)
- Granted
Links
Images
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
Abstract
The invention discloses a method for improving the reliability of a wireless network controller. The method comprises the steps of configuring a wireless network controller (RNC) to which a base station (NodeB) belongs currently with a corresponding backup RNC; switching the NodeB from the RNC to which the NodeB belongs to the backup RNC when the demand for switching the NodeB is judged according to a switch strategy; and synchronously backing up configured data which is related to the NodeB and located on the RNC to which the NodeB belongs to the backup RNC. The invention also discloses a system for improving the reliability of a wireless network controller, a switching decision-making unit in the system is used for informing a configure and switching control unit of performing switching control when the NodeB is judged needing switch. By adopting the method and the system, provided by the invention, the RNC reliability is improved; and when one of the RNCs can not provide service for the NodeB, all NodeBs belonging thereto are switched into the other RNC.
Description
Technical field
The present invention relates to field of mobile communication, relate in particular to the method and system that improve radio network controller (RNC, Radio Network Controller) reliability in a kind of code division multiple access (CDMA, Code Division Multiple Access) system.
Background technology
Network reliability is one of problem of operator's concern.The reliability of network is except that network element device that depends on high reliability and network infrastructure, and new networking mode and network topology also help to improve network reliability.Wherein, said network element device comprises core net (CN)/RNC/ base station (NodeB) etc.; Said network infrastructure comprises transmission network equipment and telecommunication cable/optical cable etc.
Fig. 1 is the UMTS Radio Access Network Organization Chart of existing 3GPP; Can find out by Fig. 1; Having accomplished standardized Iu-flex networking technology at present is that a RNC can be connected to a plurality of CN, and a plurality of CN constitute resource pool (Resources Pool), when one of them CN breaks down; Perhaps when the overload of one of them CN, user's business can be shared by other CN.One of purpose that adopts Iu flex is exactly the reliability that improves CN.
3GPP still is unrealized and is similarly backed up and redundancy scheme in the present wireless access network.Owing to insert the NodeB quantity of each RNC huge (tens, hundreds of even thousands of) in the wireless access network, so the probability of happening of Iub mouth link failure will be far above the Iu mouth.Will cause some disadvantageous situation like this, for example: (1) will make the service disconnection of one or more websites (under the NodeB cascade situation), the customer complaint of initiation area property though the influence that Iub mouth fault is brought will be lower than the Iu mouth; (2) cause whole RNC fault if run into disaster scenario, its all NodeB that have under its command can't work so, form very large communication blind district.It is thus clear that: it is very necessary setting up the mechanism that improves the RNC reliability; In order to improve the RNC reliability; One of them RNC can consider when can not provide service for NodeB; Its all NodeB that have under its command is switched on the another one RNC, also be appreciated that for: for NodeB provide the backup RNC, set up back mechanism.Yet such implementation is not arranged at present.
Summary of the invention
In view of this; Main purpose of the present invention has been to provide a kind of method and system of the RNC of raising reliability; Can improve the reliability of RNC, when one of them RNC can not provide service for NodeB, its all NodeB that have under its command switched on the another one RNC.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind of method that improves the radio network controller reliability; This method comprises: be base station (NodeB) the current affiliated corresponding backup RNC of radio network controller (RNC) configuration; When ruling out the switching of NodeB needs according to switchover policy; NodeB is switched to said backup RNC by the RNC under it, the RNC under the NodeB is gone up the configuration data relevant with Node B be synchronized to said backup RNC.
Wherein, this method also comprises: said backup RNC according to synchronous configuration data the local data relevant with NodeB are upgraded, switch accomplish after, the affiliated RNC of deletion NodeB is the configuration data relevant with NodeB upward.
Wherein, RNC under the said NodeB is specially first radio network controller (RNC1), and when said backup RNC was specially second radio network controller (RNC2), this method also comprised: before the switching; Said NodeB sets up transmission with said RNC1 and said RNC2 respectively and is connected; And on said RNC1, set up the sub-district, for NodeB provides service, said RNC2 does not relate to the business of NodeB.
Wherein, the information of carrying out the reference of said judgement institute comprises: the load of the Iub mouth of running status, RNC1 and the RNC2 of outside operational maintenance command, RNC1 and RNC2 and Link State, RNC1 and the RNC2 of Iu mouth, the geographical location information of NodeB and divide at least a in the geographical distribution information.
Wherein, the said data relevant with NodeB specifically comprise: neighboring BS relationship; And/or the identity information of the sub-district that NodeB and NodeB administered that appears for fault management, performance management.
A kind of system that improves the radio network controller reliability, this system comprises: configuration and switch control unit, handover decisions unit; Wherein,
Said configuration and switch control unit; Be used to the current affiliated corresponding backup RNC of RNC configuration of NodeB; Knowing under the situation that NodeB need switch; Control NodeB switches to said backup RNC by the RNC under it, the RNC under the NodeB is gone up the configuration data relevant with Node B be synchronized to said backup RNC;
Said handover decisions unit is used for whether needs switch according to switchover policy judgement NodeB, notifies said configuration and switch control unit to carry out switching controls when NodeB need switch when ruling out.
Wherein, the RNC under the said NodeB is specially RNC1, and when said backup RNC was specially RNC2, said configuration and switch control unit further comprised: RNC operation maintenance center 1 (OMC-RNC1), RNC operation maintenance center 2 (OMC-RNC2); Said handover decisions unit further is a NodeB handover decisions subsystem;
Said NodeB handover decisions subsystem is deployed in the NodeB side separately, or respectively with said OMC-RNC1 with said OMC-RNC2 is integrated is deployed in.
Wherein, said OMC-RNC1, being further used for ruling out NodeB at said NodeB handover decisions subsystem need switch to from RNC1 under the situation of RNC2, RNC1 is gone up the configuration data relevant with Node B be synchronized to OMC-RNC2; After switching completion, deletion RNC1 goes up the configuration data relevant with Node B;
Said OMC-RNC2, be further used for according to synchronous configuration data the local data relevant with NodeB are upgraded, upgrade that afterwards to notify RNC2 to set up cell radio resource be that NodeB provides service.
Wherein, said NodeB handover decisions subsystem is further used for accepting order that outside operation maintenance center sends, or can accepts the information command sent by in RNC1, RNC2 and the NodeB running.
Wherein, said OMC-RNC1, be further used for can be directly with said OMC-RNC2 carry out alternately data sync, or can the control of higher level's telecommunication management network down and said OMC-RNC2 carry out data sync alternately.
The present invention is the current affiliated corresponding backup RNC of RNC configuration of NodeB; When ruling out the switching of NodeB needs according to switchover policy; NodeB is switched to backup RNC by the RNC under it, the RNC under the NodeB is gone up the configuration data relevant with Node B be synchronized to backup RNC.
Adopt the present invention, through be NodeB configuration backup RNC, when one of them RNC can't operate as normal, NodeB is switched on another RNC, guarantee the continuity that NodeB is professional, the reliability of raising network.
Description of drawings
Fig. 1 is the UMTS Radio Access Network Organization Chart of existing 3GPP;
Fig. 2 is the sketch map of a handling process instance of the inventive method;
Fig. 3 is the sketch map that one of system of the present invention forms structure example;
Fig. 4 is the composition structural representation of application example one of the present invention;
Fig. 5 is the realization flow sketch map of application example one of the present invention;
Fig. 6 is the realization flow sketch map of application example two of the present invention;
Fig. 7 is the realization flow sketch map of application example three of the present invention;
Fig. 8 is the realization flow sketch map of application example four of the present invention;
Fig. 9 is the composition structural representation of application example five of the present invention;
Figure 10 is the realization flow sketch map of application example five of the present invention.
Embodiment
Basic thought of the present invention is: be the current affiliated corresponding backup RNC of RNC configuration of NodeB; When ruling out the switching of NodeB needs according to switchover policy; NodeB is switched to backup RNC by the RNC under it; RNC under the NodeB is gone up the configuration data relevant with Node B be synchronized to backup RNC, with the continuity that guarantees that NodeB is professional.
Combine embodiment that the present invention is done further description with reference to the accompanying drawings.
A kind of method that improves the RNC reliability, its main contents comprise:
Be the RNC configuration corresponding backup RNC of NodeB under current,, NodeB switched to this backup RNC by the RNC under it when ruling out the NodeB needs according to switchover policy when switching to this backup RNC.Here, said judgement can be made by newly-increased NodeB handover decisions subsystem, specifically sees to system description of the present invention.Here do not give unnecessary details.
Below with first radio network controller (RNC1) as the RNC of NodeB under current, second radio network controller (RNC2) is that example is specifically set forth as backup RNC.
One, NodeB and RNC1 and RNC2 set up transmission and are connected, and with RNC1 on kept Radio Resource attaching relation in fact, be: on RNC1, set up the sub-district, for NodeB provides service, RNC2 does not relate to the business relations of any NodeB.
Further, the related radio network layer data of NodeB has only a active data at RNC1 and RNC2 between the two, and only is present in NodeB and has on the RNC of said Radio Resource attaching relation.Initial configuration is determined by the network planning.
Further, the adjacent area that NodeB is relevant comprises the adjacent area of sub-district under this NodeB, and perhaps the sub-district is the adjacent area of other sub-districts under this NodeB, only need under initial configuration, configure data and get final product.
Further, said active data is meant and can carries out mutual data with NodeB, and is not limited in the concrete form of expression; Such as; Can preserve cover NodeB data on RNC1 and the RNC2 respectively, but the data on the RNC1 are active datas, are to let NodeB be operated under the RNC1; And the data on the RNC2 only are set, can not let NodeB be operated under the RNC2.
Two, can rule out the NodeB needs according to switchover policy by NodeB handover decisions subsystem switches on the RNC2 from RNC1.
Further, NodeB handover decisions subsystem responsible is carried out NodeB and is switched final decision, and this NodeB handover decisions subsystem can be accepted the order of outside operation maintenance center, also can accept the information command of sending by in RNC, the NodeB running.
Further, NodeB handover decisions subsystem can be between operation maintenance center, RNC, NodeB transmission information.Such as transmission information etc. between transmission information, NodeB operation maintenance center (OMC-NodeB) and the NodeB between transmission information, RNC2 and the RNC operation maintenance center 2 (OMC-RNC2) between RNC1 and the RNC operation maintenance center 1 (OMC-RNC1).
Information that can reference when further, NodeB handover decisions subsystem is adjudicated comprises: running status, the Iub mouth of RNC1/RNC2 and the Link State of Iu mouth of outside operational maintenance command, RNC1 and RNC2.Further, can also be with reference to the load of RNC1 and RNC2.Further, decision-making can also be with reference to geographical location information and the branch geographical distribution information of NodeB.Wherein, the operational maintenance command of said outside comprises manual operation etc.The running status of said RNC1 and RNC2 comprises physical equipment state, software work state, business service state or the like.Said Link State comprises whether operate as normal etc. of link, and load comprises taking of physical resource, the taking or the like of Radio Resource.
Further, NodeB handover decisions subsystem is a logical concept, and its physics form of expression can be various, is distributed in each node device such as deployment, also can concentrate on node device of independent deployment or the like.Focusing on its logic function, when NodeB handover decisions subsystem carries out the switching of NodeB if being made a strategic decision out.Particularly:
Further, above-mentioned switchover policy comprises: the RNC fault under NodeB is current, and perhaps link failure must switch to backup RNC between the current affiliated RNC of NodeB and NodeB; Perhaps, the RNC load under NodeB is current is too high, can select to switch to backup RNC for better business is provided to the user.Specifically, NodeB handover decisions subsystem can be made handover decisions according to following switchover policy, but not only limits to these switchover policy, focuses on, making decisions according to rule according to input:
The Operation and Maintenance personnel heart in operation is initiated the NodeB switching command, in view of the above the NodeB handover decisions subsystem initiation switching command of making a strategic decision out.
RNC1 entire equipment fault, the NodeB handover decisions subsystem initiation switching command of making a strategic decision out in view of the above.
Because software faults etc. cause RNC1 service to be provided for NodeB, the NodeB handover decisions subsystem initiation switching command of making a strategic decision out in view of the above.
The Iub mouth link down of NodeB and RNC1, the NodeB handover decisions subsystem initiation switching command of making a strategic decision out in view of the above.
The Iu mouth link down of RNC1 and CN, the NodeB handover decisions subsystem initiation switching command of making a strategic decision out in view of the above.
The load of RNC1 is too high, in view of the above the NodeB handover decisions subsystem initiation switching command of making a strategic decision out.
The configuration data of the NodeB that three, can will be switched by OMC-RNC1 is synchronized on the OMC-RNC2 of RNC2.
Further, the data to same NodeB between OMC-RNC1 and the OMC-RNC2 have inherent consistency, and its data consistency can realize through automatic synchronizing process, can be mode real-time, the cycle or Event triggered synchronously.Data consistency also can realize through manual work, focuses on data and has inherent consistency.
Further, the automatic synchronizing process of the data between OMC-RNC1 and the OMC-RNC2 can directly carry out also can carrying out synchronously through higher level's telecommunications maintaining network alternately.
Further, OMC-NodeB also is consistent for the data of NodeB in the front and back that NodeB switches, if OMC-NodeB is attached on the OMC-RNC, then OMC-NodeB then can keep consistency synchronously.
Further, be attached to OMC-RNC for OMC-NodeB and go up scene, NodeB can accept the operational maintenance command of the OMC-NodeB on the different OMC-RNC.
Four, after carrying out data sync between OMC-RNC1 and the OMC-RNC2, OMC-RNC2 can upgrade the data relevant with NodeB, the identity information of the sub-district that NodeB and NodeB administered that these data comprise neighboring BS relationship, appear for fault management, performance management.
Further, to switch to the NodeB of RNC2 from RNC1, OMC-RNC2 need have the NodeB in this RNC and switching the data of neighboring BS relationship to carry out disposable change, guarantees NodeB after switching, and mobility is still unaffected.
Further, updating data can be automatically, also can manual intervention.
Further; After NodeB switched to RNC2, the oam center can merge NodeB in identity on the RNC2 and the province of NodeB on RNC1, and functions such as outside fault management, performance management are presented consistent identity; Can identity not merged yet, keep independently identity.
Five, RNC2 sets up Radio Resources such as sub-district according to the process of 3GPP regulation according to s own situation with NodeB together, and RNC2 formally is the NodeB service.
Six, NodeB switches to RNC2, and RNC2 is formally for after the NodeB service, and the Serving cell data of OMC-RNC1 deletion NodeB are upgraded under the RNC1 with the relevant adjacent area data of NodeB.
Further, to switch to the NodeB of RNC2 and the sub-district of being administered thereof from RNC1, OMC-RNC1 need have the NodeB in this RNC and switching the data of neighboring BS relationship to carry out disposable change, guarantees NodeB after switching, and mobility is still unaffected.
Seven, this switching of NodeB is accomplished, and NodeB handover decisions subsystem works on, and needs to initiate once more to switch if rule out NodeB, then begins to continue to carry out handover operation again from above-mentioned two.
A kind of system that improves the radio network controller reliability, this system comprises: configuration and switch control unit, handover decisions unit.Wherein, Configuration and switch control unit are used to the current affiliated corresponding backup RNC of RNC configuration of NodeB; Knowing under the situation that NodeB need switch; Control NodeB switches to backup RNC by the RNC under it, the RNC under the NodeB is gone up the configuration data relevant with Node B be synchronized to backup RNC.The handover decisions unit is used for whether needs switch according to switchover policy judgement NodeB, notifies configuration and switch control unit to carry out switching controls when ruling out when NodeB need switch.
Further, the RNC under the NodeB is specially RNC1, and when backup RNC was specially RNC2, configuration and switch control unit further comprised: OMC-RNC1, OMC-RNC2; The handover decisions unit further is a NodeB handover decisions subsystem.Wherein, NodeB handover decisions subsystem can be deployed in the NodeB side separately, or respectively with OMC-RNC1 with OMC-RNC2 is integrated is deployed in.
Further, OMC-RNC1 is further used for ruling out NodeB at NodeB handover decisions subsystem and need switches to from RNC1 under the situation of RNC2, RNC1 is gone up the configuration data relevant with Node B be synchronized to OMC-RNC2; After switching completion, deletion RNC1 goes up the configuration data relevant with Node B.OMC-RNC2 be further used for according to synchronous configuration data the local data relevant with NodeB are upgraded, upgrade that afterwards to notify RNC2 to set up cell radio resource be that NodeB provides service.
Further, NodeB handover decisions subsystem can be accepted order that outside operation maintenance center sends, or can accept the information command sent by in RNC1, RNC2 and the NodeB running.
Further, OMC-RNC1 be further used for can be directly with OMC-RNC2 carry out alternately data sync, or can be under the control of higher level's telecommunication management network and OMC-RNC2 carry out data sync alternately.
In sum, adopt the present invention, compared with prior art, can the whole reliability that improves RNC, reduce the possibility that Single Point of Faliure takes place RNC; Can simplify the workload of O&M greatly; Because the participation at oam center; But make the present invention have very large benefit aspect data configuration, fault management, performance management or the like the O&M, but let the real realization operation maintenance of the mode of enhancing RNC/NodeB reliabilities such as RNC disaster tolerance, NodeB double copies, can manage; The switching of NodeB can realize automatic judgement, also can realize the mode of manual intervention; Switch also and can carry out the batch switching, also can switch according to the NodeB group according to single NodeB; Switch in batches down; NodeB handover decisions subsystem can be collected the NodeB that need to switch, wait collect certain quantity after, to these NodeB concentrative implementation handoff procedures; The switching of single NodeB then is meant initiates handoff procedure to this NodeB when NodeB handover decisions subsystem detects a NodeB and need switch immediately; Fault warning, performance counter etc. can be merged into same fixing identity NodeB/ cell data, also can separate processes, help the needs of operation maintenance more.
Below to the present invention's elaboration of giving an example.
Be illustrated in figure 2 as a handling process example schematic of the inventive method, may further comprise the steps:
Step 101, NodeB set up the Radio Resource attaching relation with RNC1.
Step 102, NodeB handover decisions subsystem carry out switch decision, need switch if rule out NodeB, and then execution in step 103; Otherwise, rule out NodeB and need not switch, finish current switching flow.
Step 103, OMC-RNC1 will be relevant with NodeB data sync to OMC-RNC2.
Step 104, OMC-RNC2 upgrade local data.
Step 105, RNC2 and NodeB set up the Radio Resource attaching relation.
The Serving cell data of step 106, RNC1 deletion NodeB are upgraded the adjacent area related data.
Be illustrated in figure 3 as one of system of the present invention and form the structure example sketch map, comprising: RNC1 that core net is administered and RNC2, RNC1 and RNC2 respectively as the affiliated RNC of NodeB with back up RNC; Play the NodeB handover decisions subsystem of switch decision; OMC-RNC1 and OMC-RNC2 are used for the data sync between the two respectively as the operation maintenance center of RNC1 and RNC2; OMC-NodeB also comprises telecommunications management network (tmn) as the operation maintenance center of NodeB.
Application example one:
In this instance,, can dispose a NodeB handover decisions subsystem separately, the judgement that is used to switch with reference to composition structural representation shown in Figure 4; OMC-RNC and RNC are deployed in together, are deployed in together like OMC-RNC1 and RNC1, and OMC-RNC2 and RNC2 are deployed in together; OMC-NodeB and OMC-RNC are deployed in together, can be deployed in together with OMC-RNC1 like OMC-NodeB, also can be deployed in together with OMC-RNC2; Configuration data can be kept among OMC-RNC1 and the OMC-RNC2 on any OMC-RNC.
The switching realization flow of this instance is as shown in Figure 5, may further comprise the steps:
Step 201:RNC1 uses RNC as the main of NodeB, is the current affiliated RNC of NodeB, between NodeB and RNC1, sets up Radio Resources such as sub-district.
Step 202:NodeB detects the long-time periodicity audit message that does not have from RNC1, but the Iub link is still in proper working order, and NodeB reports NodeB handover decisions subsystem with testing result.
Step 203:NodeB handover decisions subsystem rules out to be needed to switch, and sends instruction to RNC2 in view of the above, and indication RNC2 takes over NodeB.
Step 204:NodeB handover decisions subsystem sends instruction to OMC-RNC1, and the data sync that NodeB is relevant is given RNC2.
After step 205:OMC-RNC2 receives data, upgrade relevant adjacent area data configuration.Sub-district in this RNC is the adjacent area if the sub-district to switch was arranged in the past, then upgrades the adjacent area data of this sub-district.
Step 206: between NodeB and RNC2, set up Radio Resources such as sub-district.
The NodeB data that step 207:OMC-RNC1 deletion is switched are upgraded the adjacent area data under this RNC.
Application example two:
The switching realization flow of this instance is as shown in Figure 6, may further comprise the steps:
Step 301:RNC1 uses RNC as the main of NodeB, is the current affiliated RNC of NodeB, between NodeB and RNC1, sets up Radio Resources such as sub-district.
Step 302: in running,,, then implement to be synchronized on the corresponding OMC-RNC2 of RNC2 if change with the relevant data of NodeB.
Step 303:RNC1 equipment integral fault, NodeB handover decisions subsystem detects RNC1 does not have response message for a long time.
Step 304:NodeB handover decisions subsystem rules out to be needed to switch, and sends instruction to OMC-RNC2 in view of the above, and indication RNC2 takes over NodeB.
After step 305:OMC-RNC2 receives orders, upgrade relevant adjacent area data configuration.Sub-district in this RNC is the adjacent area if the sub-district to switch was arranged in the past, then upgrades the adjacent area data of this sub-district.
Step 306: between NodeB and RNC2, set up Radio Resources such as sub-district.
Application example three:
The switching realization flow of this instance is as shown in Figure 7, may further comprise the steps:
Step 401:RNC1 uses RNC as the main of NodeB, is the current affiliated RNC of NodeB, between NodeB and RNC1, sets up Radio Resources such as sub-district.
Step 402: the Operation and Maintenance personnel initiate an artificial handover operation order on OMC-NodeB, OMC-NodeB gives NodeB handover decisions subsystem with this command report.
Step 403:NodeB handover decisions subsystem rules out to be needed to switch, and sends instruction to RNC2 in view of the above, and indication RNC2 takes over NodeB.
Step 404:NodeB handover decisions subsystem sends instruction to OMC-RNC1, and the data sync that NodeB is relevant is given RNC2.
After step 405:OMC-RNC2 receives data, upgrade relevant adjacent area data configuration.Sub-district in this RNC is the adjacent area if the sub-district to switch was arranged in the past, then upgrades the adjacent area data of this sub-district.
Step 406: between NodeB and RNC2, set up Radio Resources such as sub-district.
The NodeB data that step 407:OMC-RNC1 deletion is switched are upgraded the adjacent area data under this RNC.
Application example four:
The switching realization flow of this instance is as shown in Figure 8, may further comprise the steps:
Step 501:RNC1 uses RNC as the main of NodeB, is the current affiliated RNC of NodeB, between NodeB and RNC1, sets up Radio Resources such as sub-district.
Step 502: in running, with the relevant data of NodeB, if change, then implement to be synchronized on the corresponding OMC-RNC2 of RNC2, simultaneously, periodic data synchronization process also exists.
Step 503:RNC1 load is too high, gives NodeB handover decisions subsystem with information reporting.
Step 504:NodeB handover decisions subsystem rules out to be needed to switch, and sends instruction to OMC-RNC2 in view of the above, and indication RNC2 takes over NodeB.
After step 505:OMC-RNC2 receives orders, upgrade relevant adjacent area data configuration.Sub-district in this RNC is the adjacent area if the sub-district to switch was arranged in the past, then upgrades the adjacent area data of this sub-district.
Step 506: between NodeB and RNC2, set up Radio Resources such as sub-district.
Application example five:
In this instance, with reference to composition structural representation shown in Figure 9, NodeB handover decisions subsystem is deployed on RNC1 and the RNC2; OMC-RNC and RNC are deployed in together, are deployed in together like OMC-RNC1 and RNC1, and OMC-RNC2 and RNC2 are deployed in together; OMC-NodeB and OMC-RNC are deployed in together, can be deployed in together with OMC-RNC1 like OMC-NodeB, also can be deployed in together with OMC-RNC2; Configuration data can be kept among OMC-RNC1 and the OMC-RNC2 on any OMC-RNC.
The switching realization flow of this instance, shown in figure 10 may further comprise the steps:
Step 601:RNC1 uses RNC as the main of NodeB, is the current affiliated RNC of NodeB, between NodeB and RNC1, sets up Radio Resources such as sub-district.Initiate change when RNC1 goes up the relevant data of NodeB, all on RNC2, do once backup in real time.
Step 602: the NodeB handover decisions subsystem that is deployed on the RNC2 is found RNC1 total failure, and ruling out needs to switch, and initiates to take over the order of NodeB to the RNC2 that self belongs to.
Step 603:RNC2 is the formal data of Backup Data conduct of NodeB before, and submission comes into force.
Step 604:RNC2 upgrades relevant adjacent area data configuration.
Step 605: between NodeB and RNC2, set up Radio Resources such as sub-district.
After the step 606:RNC1 fault recovery, the NodeB handover decisions subsystem that is deployed on the RNC1 finds that NodeB has switched on the RNC2, deletes the relevant data that come into force of NodeB on the RNC1 that self belongs to, and upgrades the adjacent area relevant configuration.
The above is merely preferred embodiment of the present invention, is not to be used to limit protection scope of the present invention.
Claims (10)
1. method that improves the radio network controller reliability; It is characterized in that; This method comprises: be base station (NodeB) the current affiliated corresponding backup RNC of radio network controller (RNC) configuration; When ruling out the switching of NodeB needs according to switchover policy, NodeB is switched to said backup RNC by the RNC under it, the RNC under the NodeB is gone up the configuration data relevant with Node B be synchronized to said backup RNC.
2. method according to claim 1; It is characterized in that; This method also comprises: said backup RNC according to synchronous configuration data the local data relevant with NodeB are upgraded, switch accomplish after, the affiliated RNC of deletion NodeB is the configuration data relevant with Node B upward.
3. method according to claim 1 and 2 is characterized in that, the RNC under the said NodeB is specially first radio network controller (RNC1); When said backup RNC is specially second radio network controller (RNC2); This method also comprises: before the switching, said NodeB sets up transmission with said RNC1 and said RNC2 respectively and is connected, and on said RNC1, sets up the sub-district; For NodeB provides service, said RNC2 does not relate to the business of NodeB.
4. method according to claim 3; It is characterized in that the information of carrying out the reference of said judgement institute comprises: the load of the Iub mouth of running status, RNC1 and the RNC2 of outside operational maintenance command, RNC1 and RNC2 and Link State, RNC1 and the RNC2 of Iu mouth, the geographical location information of NodeB and divide at least a in the geographical distribution information.
5. method according to claim 2 is characterized in that, the said data relevant with NodeB specifically comprise: neighboring BS relationship; And/or the identity information of the sub-district that NodeB and NodeB administered that appears for fault management, performance management.
6. a system that improves the radio network controller reliability is characterized in that, this system comprises: configuration and switch control unit, handover decisions unit; Wherein,
Said configuration and switch control unit; Be used to the current affiliated corresponding backup RNC of RNC configuration of NodeB; Knowing under the situation that NodeB need switch; Control NodeB switches to said backup RNC by the RNC under it, the RNC under the NodeB is gone up the configuration data relevant with Node B be synchronized to said backup RNC;
Said handover decisions unit is used for whether needs switch according to switchover policy judgement NodeB, notifies said configuration and switch control unit to carry out switching controls when NodeB need switch when ruling out.
7. system according to claim 6; It is characterized in that; RNC under the said NodeB is specially RNC1; When said backup RNC was specially RNC2, said configuration and switch control unit further comprised: RNC operation maintenance center 1 (OMC-RNC1), RNC operation maintenance center 2 (OMC-RNC2); Said handover decisions unit further is a NodeB handover decisions subsystem;
Said NodeB handover decisions subsystem is deployed in the NodeB side separately, or respectively with said OMC-RNC1 with said OMC-RNC2 is integrated is deployed in.
8. system according to claim 7; It is characterized in that; Said OMC-RNC1, being further used for ruling out NodeB at said NodeB handover decisions subsystem need switch to from RNC1 under the situation of RNC2, RNC1 is gone up the configuration data relevant with Node B be synchronized to OMC-RNC2; After switching completion, deletion RNC1 goes up the configuration data relevant with Node B;
Said OMC-RNC2, be further used for according to synchronous configuration data the local data relevant with NodeB are upgraded, upgrade that afterwards to notify RNC2 to set up cell radio resource be that NodeB provides service.
9. system according to claim 7; It is characterized in that; Said NodeB handover decisions subsystem is further used for accepting order that outside operation maintenance center sends, or can accepts the information command sent by in RNC1, RNC2 and the NodeB running.
10. system according to claim 8; It is characterized in that; Said OMC-RNC1, be further used for can be directly with said OMC-RNC2 carry out alternately data sync, or can the control of higher level's telecommunication management network down and said OMC-RNC2 carry out data sync alternately.
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 true CN102469486A (en) | 2012-05-23 |
| CN102469486B 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 (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103229536A (en) * | 2012-12-27 | 2013-07-31 | 华为技术有限公司 | Dual-network backup method and device and wireless communication system |
| CN104969513A (en) * | 2013-06-09 | 2015-10-07 | 华为技术有限公司 | Method and device for updating radio network controller |
Citations (7)
| 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 |
| US20050213555A1 (en) * | 2001-06-25 | 2005-09-29 | Vedat Eyuboglu | Radio network control |
| 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 (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
-
2010
- 2010-11-18 CN CN201010551272.2A patent/CN102469486B/en active Active
-
2011
- 2011-06-10 WO PCT/CN2011/075575 patent/WO2012065433A1/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050213555A1 (en) * | 2001-06-25 | 2005-09-29 | Vedat Eyuboglu | Radio network control |
| 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 (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103229536A (en) * | 2012-12-27 | 2013-07-31 | 华为技术有限公司 | Dual-network backup method and device and wireless communication system |
| CN103229536B (en) * | 2012-12-27 | 2017-04-19 | 华为技术有限公司 | Dual-network backup method and device and wireless communication system |
| CN104969513A (en) * | 2013-06-09 | 2015-10-07 | 华为技术有限公司 | Method and device for updating radio network controller |
| CN104969513B (en) * | 2013-06-09 | 2018-08-21 | 华为技术有限公司 | Wireless controller upgrade method and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102469486B (en) | 2015-09-16 |
| WO2012065433A1 (en) | 2012-05-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101815298B (en) | Tracking area optimizing and updating method, device and system | |
| EP3582550A1 (en) | Active set update (asu) with high speed downlink shared channel (hs-dsch) information | |
| EP2811776A1 (en) | Self organizing network coordination method, device and system | |
| CN102726098B (en) | Operator public land mobile network identification delivery method, base station and subscriber equipment | |
| CN109474465A (en) | A kind of method and system of the high availability that can dynamically circulate based on server cluster | |
| US10070350B2 (en) | Network coordination apparatus | |
| CN101426304B (en) | Adjacent cell configuring method, communication device and communication system | |
| CN102685811A (en) | Method and system for transmitting community resource status information under network sharing scene | |
| CN102547764B (en) | Method, system and device for improving mobile robustness | |
| CN101094502B (en) | Network architecture, and switching method based on the network architecture | |
| CN101217824B (en) | Wireless network switching system and its switching method | |
| CN102469486A (en) | Method and system for improving reliability of wireless network controller | |
| WO2009115055A1 (en) | Method and device for networking of base station control node | |
| CN102647737B (en) | Method and system for self optimization of wireless parameters | |
| JP2010010904A (en) | Method for optimizing station data in mobile communication network, device, and computer program | |
| CN102281523A (en) | Radio network controller and neighbouring cell information updating method thereof | |
| CN102378233A (en) | Method and system for improving reliability of wireless communication network system | |
| CN102595457B (en) | A kind of method and system of maintenance customer's terminal coordinated multipoint transmission | |
| WO2002003615A1 (en) | Base station control in telecommunications system | |
| CN110880988B (en) | Network management system upgrading method and device | |
| CN105959172B (en) | A kind of the redundant network management method and platform of group system | |
| WO2021093898A1 (en) | Method and apparatus for upgrading network management system | |
| CN215956660U (en) | Baseband processing unit, base station and wireless communication system | |
| CN102958077B (en) | Maintaining method for neighbor relation table of same system | |
| CN212696009U (en) | Network management system |
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 |