CN101141398A

CN101141398A - RNC load sharing disaster recovery method, system and device

Info

Publication number: CN101141398A
Application number: CNA2007101638857A
Authority: CN
Inventors: 秦圣奕; 吕玖有; 秦中玉; 赵永祥
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-10-11
Filing date: 2007-10-11
Publication date: 2008-03-12
Also published as: WO2009049552A1

Abstract

The present invention discloses a method for sharing the disaster tolerance of the RNC load. A base station NodeB is at least connected with a first radio network controller RNC and a second radio network controller RNC, an imputation relation is established between the first RNC and the second RNC. The method comprises the following steps: the NodeB respectively establishes communication connection with the first RNC and the second RNC; and the NodeB initiates registration; the NodeB selects one from the first RNC and the second RNC for access according to the returned registration response. Through the embodiment of the present invention, when the current RNC accessed by the NodeB or the IUB transmission link connected with the RNC has a fault, the current RNC can be switched to the other RNC in time, therefore, the detection rate of the transmission fault is increased, and the reliability of the RNC and the IUB transmission link can be improved.

Description

A kind of mthods, systems and devices of RNC load sharing disaster recovery

Technical field

The present invention relates to the mobile communication technology field, particularly relate to a kind of mthods, systems and devices of RNC load sharing disaster recovery.

Background technology

Existing UMTS (Universal Mobile Telecommunications System, universal mobile telecommunications system) system adopts WCDMA (Wideband Code Division Multiple Access, the Wideband Code Division Multiple Access (WCDMA) access) therefore the 3-G (Generation Three mobile communication system) of air interface technologies also calls the WCDMA communication system to the UMTS system usually.The UMTS system has adopted and the similar structure of second generation mobile communication system, comprises RAN (Radio Access Network, Radio Access Network) and CN (CoreNetwork, core network).Wherein Radio Access Network is used to handle all and wireless function associated, and CN handles that all voice calls are connected with data in the UMTS system, and the exchange of realization and external network and routing function.CN is from being divided into CS territory (Circuit Switched Domain, circuit commutative field) and PS territory (Packet Switched Domain, packet-switched domain) in logic.UTRAN, CN and UE (User Equipment, subscriber equipment) have constituted whole UMTS system together.

As shown in Figure 1, be the structure chart of UTRAN in the prior art, UTRAN is a land radio access web, and it comprises one or several RNS (Radio Network Subsystem, RNS).A RNS is made up of a RNC (Radio Network Controller, radio network controller) and one or more NodeB (base station).RNC is that the Iu interface is connected with interface between the CN, and NodeB is connected by Iub interface with RNC.In UTRAN inside, interconnected by Iur between the RNC, Iur can connect or connect by transmission network by the direct physical between the RNC.RNC is used for distributing and is attached thereto with control or the Radio Resource of relevant NodeB.NodeB then finishes the conversion of the data flow between Iub interface and the Uu interface, also participates in a part of RRM simultaneously.

RNC is used to control the Radio Resource of UTRAN, mainly finishes functions such as RRC (Radio ResourceControl, Radio Resource control) connection foundation and disconnection, switching, the merging of grand diversity, RRM, and is specific as follows:

(1) executive system information broadcast and system's access control function;

(2) switching and SRNC (Radio Network Controller, service wireless network controller) migration wait the mobile management function;

(3) RRM and controlled function such as grand diversity merging, power control, radio bearer distribution;

NodeB is the base station (being radio receiving-transmitting unit) of WCDMA system, comprises radio receiving-transmitting unit and Base-Band Processing parts.By the Iub interface and the RNC interconnection of standard, mainly finish the processing of Uu interface physical layer protocol.Its major function is spread spectrum, modulation, chnnel coding and despreading, demodulation, channel-decoding, also comprises the functions such as mutual conversion of baseband signal and radiofrequency signal.As shown in table 1 below, be the Iub interface protocol stack:

The Iub interface protocol stack is divided into wireless network control face, transmission network chain of command, user's face, bearing bed has ATM (Asynchronous Transfer Mode, asynchronous transfer mode) and two kinds of transmission meanss of IP: during the ATM mode, the transport layer of wireless network control face is used SSCF-UNI/SSCOP/AAL5/ATM, the transmission network chain of command uses ALCAP/SSCF-UNI/SSCOP/AAL5/ATM, and user's face transport layer is used AAL2/ATM; During the IP mode, the transport layer of wireless network control face is used SCTP/IP/Data LinkLayer, and user's face transport layer is used UDP/IP/Data Link Layer, does not have the transmission network chain of command.The different channel of user's face uses different FP, comprises common signal channel RACH FP/PCH FP/FACH FP, dedicated channel DCH FP, and HSDPA channel HS-DSCH FP, other channels are as DSCH FP or the like

The voice-and-data of UE is encapsulated in the various FP frames, uses transport layer (ATM or IP) function, transmits at Iub interface.RNC and NODEB form wireless access network (RAN), and wherein RNC bears administrator role, and control NODEB provide wireless access function, a large amount of NODEB of RNC management, and a NODEB only belongs to a RNC.

In realizing embodiment of the invention process, the inventor finds that there are the following problems at least in the prior art: along with progressively popularizing of HSPA business, data throughput is more and more higher, capacity requirement to RNC is also more and more higher, particularly following HSPA+ introduces, the RNC capacity requirement is higher, and the capacity of RNC is also done bigger and bigger.The influence of RNC fault is increasing, and operator is to the also constantly aggravation of worry of network security.Except that improving the RNC equipment dependability, adopt the mode of cold standby that RNC is backed up, but the mode of this cold standby is in case after RNC breaks down, need the manual lot of data configuration of on backup RNC, carrying out, transmit adjustment simultaneously, not only above-mentioned manual back-up job amount is big, and recovery time is longer, can not satisfy the requirement of fast quick-recovery.

Summary of the invention

The problem that the embodiment of the invention will solve provides a kind of mthods, systems and devices of RNC load sharing disaster recovery, and manual back-up job amount is big in the solution prior art, recovers untimely technological deficiency.

For achieving the above object, the embodiment of the invention proposes a kind of method of RNC load sharing disaster recovery on the one hand, base station node B links to each other with the 2nd RNC with first radio network controller (RNC) at least, a described RNC and described the 2nd RNC set up attaching relation, may further comprise the steps: described NodeB sets up respectively and the communicating to connect of a described RNC and described the 2nd RNC; Described NodeB initiates registration; Described NodeB selects a RNC to insert from a described RNC and described the 2nd RNC according to the registration response of returning.

On the other hand, the embodiment of the invention also provides a kind of system of RNC load sharing disaster recovery, comprise the RNC that concerns under NodeB and at least two foundation that link to each other with described NodeB, described NodeB, be used for setting up respectively and the communicating to connect of described RNC, initiate registration for one in described RNC, and, from described RNC, select a RNC to insert according to the registration response of returning; Described RNC is used for after the registration that receives described NodeB, returns corresponding registration response to described NodeB.

Again on the one hand, the embodiment of the invention also provides a kind of NodeB, the RNC that concerns under described NodeB and at least two foundation links to each other, comprise and communicate to connect module, registration initiation module, registration response receiver module and access module, the described module that communicates to connect, be used for setting up respectively with described foundation under the communicating to connect of two RNC concerning; Described registration initiation module is used for initiating registration; Described registration response receiver module is used to receive the registration response of returning; Described access module is used for responding according to the registration that described registration response receiver module receives, and selects a RNC to insert two RNC that concern under described foundation.

The embodiment of the invention also provides a kind of RNC, comprises that register requirement receiver module, registration judge module and registration response return module, and described register requirement receiver module is used to receive the registration that NodeB initiates; Described registration judge module is used to judge whether to accept the registration of described NodeB; Module is returned in described registration response, is used for returning the registration response according to the judged result of described registration judge module to described NodeB.

The technical scheme of the embodiment of the invention has the following advantages; because adopt to the dual-homed protection of the RNC of NodeB; when RNC or the IUB transmission link that is connected with RNC break down; can in time switch on other RNC; therefore improve the transmission fault verification and measurement ratio, improved the reliability of RNC and IUB transmission link.

Description of drawings

Fig. 1 is the structure chart of UTRAN in the prior art;

Fig. 2 be under the embodiment of the invention ATM pattern NodeB with set up under concern the connection diagram of RNC;

Fig. 3 be under the embodiment of the invention IP pattern NodeB with set up under concern the connection diagram of RNC;

Fig. 4 is the system construction drawing of embodiment of the invention RNC load sharing disaster recovery;

Fig. 5 is the structure chart of embodiment of the invention NodeB;

Fig. 6 is the structure chart of embodiment of the invention RNC;

Fig. 7 is the method flow diagram of the RNC load sharing disaster recovery of the embodiment of the invention one;

Fig. 8 is the method flow diagram of RNC load sharing disaster recovery under principal and subordinate's attributable system of the embodiment of the invention two;

Fig. 9 is the method flow diagram of RNC load sharing disaster recovery under the symmetrical attributable system of the embodiment of the invention three;

Figure 10 is that the embodiment of the invention one is eliminated the flow chart that influence method of RNC switching to peripheral network element;

Figure 11 is that the embodiment of the invention two is eliminated the flow chart that influence method of RNC switching to peripheral network element.

Embodiment

Below in conjunction with drawings and Examples, the specific embodiment of the present invention is described in further detail:

The embodiment of the invention guarantees that by for NodeB is provided with the resource pool of being made up of the RNC that concerns under a plurality of foundation this NodeB can in time switch to other RNC access networks when RNC breaks down.For convenience of explanation; the following description of the embodiment of the invention will be that example is described with dual-homed RNC; therefore yet can not think that the embodiment of the invention only can realize two RNC protections, therefore any quantitative variation all should be embodiment of the invention protection range and contains about RNC.

At first the IUB coffret to NodeB expands, and expands the IUB coffret of NodeB according to the quantity to RNC in the RNC resource pool of this NodeB protection.NodeB is dual-homed, then this NodeB is expanded to make it provide two cover IUB coffrets to insert the RNC that concerns under two foundation respectively.Wherein, two cover IUB coffrets can be physical layer all separate with link layer or physical layer shared+link-layer separation, when transmitting, use different PVC (permanent virtualcircuit, permanent virtual circuit) as ATM.Because bearing bed has ATM and two kinds of transmission meanss of IP, therefore the embodiment of the invention has also proposed to concern the connection diagram of RNC under NodeB under two kinds of patterns and foundation, respectively as shown in Figures 2 and 3, NodeB links to each other respectively with RNC by the IUB coffret that expands.When the ATM mode transfer, each NodeB configuration 2 cover IUB link, 2 cover IUB links insert 2 RNC by ATM switch, every cover IUB link comprises 1 NCP (Network CoreProtocol, Network Core Protocol), M bar CCP, K bar AAL2 PATH and 1 IPOA, wherein M and K represent that CCP and AAL2 PATH can be configured as required by the user, for example can be CCP of a cell configuration, or the shared CCP in a plurality of sub-district; Equally for AAL2PATH, also can many AAL2 PATH be set according to the transport service difference, for example for the higher speech business of real-time with concerning the less demanding data service of real-time, if with data service and the shared AAL2 PATH of speech business, so data service may will influence the real-time of speech business, so just can be respectively speech business and an AAL2 PATH is respectively disposed in data service by user's selection.The IUB link uses different PVC separately, if operator transmission is nervous, these PVC can be multiplexing on same physical transfer circuit, exchanges to 2 RNC by ATM switch then, if transmit abundantly, 2 cover IUB links use different transmission line carryings.Which kind of is selected by operator in concrete use.Equally when the IP mode transfer, each NodeB configuration 2 cover IUB link, 2 cover IUB links insert 2 RNC by network equipments such as switch, router or MSTP, wherein 2 RNC use different IP addresses, 2 each self-configuring SCTP of cover IUB link (StreamControl Transmission Protocol, SCTP) link and IP PATH, and corresponding different IP addresses use the IP route implementing message of standard to be routed to 2 RNC.

Yet need to prove among above-mentioned Fig. 2 and Fig. 3; NodeB and RNC only are the optimal ways of the embodiment of the invention by being similar to that the network equipments such as switch, router link to each other; transmit under the abundant situation in operator; also can between NodeB is directly linked to each other with RNC by the IUB link, the RNC that concerns under realizing setting up is to the protection of NodeB.

As shown in Figure 4, be the system construction drawing of embodiment of the invention RNC load sharing disaster recovery, this embodiment is that example is described with 2 RNC.This system comprises the RNC that concerns under NodeB1 and at least two foundation that link to each other with NodeB1, a RNC2 and the 2nd RNC3, and a RNC2 and the 2nd RNC3 are in running order, separately the NodeB under the management.The wireless data (NodeB, sub-district, neighboring BS relationship and algorithm parameter) of the NodeB of management and IUB transmission data under the RNC configuration, and IU data (signalling point and signaling link, link set).To a dual-homed NodeB, the different transport layer data (NodeB uses 2 cover IUB transmission links) of configuration on 2 RNC, concerning radio layer, cell data when all disposing this base station ownership cell data, this NodeB on this RNC the time on 2 RNC and belonging on another RNC, normalization (logic district ID, comprise ownership and 2 kinds of states of non-attribution) neighboring BS relationship, by the RNC home state current according to the base station, corresponding cell data and adjacent area data accordingly.Therefore in the time of can breaking down (comprising IUB interface link fault) at a RNC, can realize quick switching to RNC.

NodeB1 is used for setting up respectively and the communicating to connect an of RNC2 and the 2nd RNC3, and a RNC in a RNC2 and the 2nd RNC3 initiates registration, and according to the registration response of returning, selects a RNC to insert from a RNC2 and the 2nd RNC3; The one RNC2 or the 2nd RNC3 are used for after the registration that receives NodeB1, return corresponding registration response to NodeB1.For example, accept the registration of this NodeB1, then return success the registration response to this NodeB1; Otherwise return the failed registration response to this NodeB1.

Wherein, also comprise the network equipment 4, NodeB1 by the network equipment 4 respectively with two foundation under the RNC2 or the 2nd RNC3 that concern link to each other.

Wherein, a RNC2 or the 2nd RNC3 also are used for consulting mutually the attaching relation of NodeB1, and return corresponding registration response according to the attaching relation of consulting to NodeB1.Initiate registration as NodeB1 to a RNC2, after then a RNC2 receives register requirement, hold consultation with the 2nd RNC3.If consult in described RNC2 registration, then a RNC2 returns success the registration response to described NodeB1; If consult the registration at the 2nd RNC3, then a RNC3 returns the failed registration response to NodeB1; NodeB1 inserts the 2nd RNC3 after receiving the failed registration response that a RNC2 returns.

Wherein, a RNC2 or the 2nd RNC3 also are used for according to self load condition, return corresponding registration response to NodeB1.Initiate registration as NodeB1 to a RNC2, then a RNC2 judges self load condition, if a RNC2 load height then return to have ready conditions to NodeB1 and allow registration response or failed registration response; Otherwise return success the registration response to NodeB1.

The embodiment of the invention has proposed two kinds of affiliated modes that concern of RNC foundation according to the tendentiousness that NodeB inserts RNC, a kind of is principal and subordinate's attributable system, one of them RNC provides main service to be called main ownership RNC, and the IUB transmission link that this master's ownership RNC is connected with NodeB is called main ownership IUB transmission link; Another RNC provides the disaster tolerance service, is called from ownership RNC, and the IUB transmission link that it is connected with NodeB is called the transmission link from ownership IUB.Another kind is symmetrical ownership pattern, and NodeB does not contain any tendentiousness, by consulting to determine which RNC NodeB inserts between the RNC mutually.Below just be that example is described respectively above-mentioned dual mode with Fig. 4:

Mode one: principal and subordinate's attributable system is main ownership RNC as a RNC2, and the 2nd RNC3 is from ownership RNC, and NodeB1 selects the RNC access procedure as follows:

At first NodeB1 transmits communicating to connect of foundation respectively and a RNC2 and the 2nd RNC3 by the 2 cover IUB that expand; Communicating to connect of NodeB1 and a RNC2 and the 2nd RNC3 set up finish after, NodeB1 preferentially registers to the main RNC (RNC2) that belongs to by main ownership IUB transmission link; Main ownership RNC judges whether to allow its access according to the load state of self, if disposing, this master's ownership RNC do not force to forbid registration, or enabled the NodeB re-host of load triggers and led the current load of ownership RNC not high, then main ownership RNC judges that permission NodeB1 inserts, and return success registration response to it, after NodeB1 receives successfully registration response, flow process according to the IUB interface standard inserts main ownership RNC, just can under main ownership RNC control, provide the wireless access service then, only be used for NodeB1 and from ownership RNC keep communicating to connect from ownership IUB transmission link this moment, be used for fault detect, but do not control this NodeB1 from ownership RNC.If main ownership RNC load height then returns the success registration response of having ready conditions to NodeB1, NodeB1 receives the described success registration response of having ready conditions, by from ownership IUB transmission link to registering from ownership RNC.Equally from belonging to RNC after receiving the register requirement of NodeB1, also can judge whether to allow its access according to the load condition of self, and return corresponding registration response to it, if return success the registration response to NodeB1 from ownership RNC, then NodeB1 selects to insert from ownership RNC, is providing the wireless access service under the control of ownership RNC; If also return the success registration response of having ready conditions to NodeB1 from ownership RNC, then NodeB1 is still preferential selects main ownership RNC to insert.If same main ownership RNC returns the failed registration response to NodeB1, then NodeB1 just uses from ownership IUB transmission link to initiating register flow path from ownership RNC.The embodiment of the invention belongs to pattern at this principal and subordinate and has also proposed a kind of recovery pattern, NodeB1 be linked into from the ownership RNC on after, to continue to attempt on main ownership RNC, to register, if main ownership RNC returns success the registration response, then NodeB1 will select suitable opportunity (business will be lower than the thresholding of configuration, avoid the influence professional) carry out re-host (returning genus), re-register under the main ownership RNC, and and carry out de-host (go ownership) from ownership RNC, remain preferential selection of NodeB1 like this and insert to main ownership RNC.

Mode two: symmetrical attributable system equally also needs NodeB1 to transmit communicating to connect of foundation respectively and a RNC2 and the 2nd RNC3 by the 2 cover IUB that expand; Illustrate that this NodeB1 can't register to it if NodeB1 can't establish a communications link with RNC, therefore can only register to another one RNC.Communicating to connect of NodeB1 and a RNC2 and the 2nd RNC3 set up finish after, NodeB1 can select a normal transmission link to initiate registration to RNC, for example initiate registration to a RNC2, the one RNC2 can hold consultation with the 2nd RNC3 after receiving the register requirement of NodeB1, consult the attaching relation of NodeB1, can be by IUR interface RNSAP (the Radio Network Subsystem Application Part between expansion the one RNC2 and the 2nd RNC3, Radio Network Subsystem Application Part), increase corresponding negotiation message and flow process.If a RNC2 and the 2nd RNC3 determine to register on a RNC2 after consulting, then a RNC2 returns success the registration response to NodeB1; If consult to determine to register on the 2nd RNC3, then a RNC2 returns the failed registration response to NodeB1, and NodeB1 can if the 2nd RNC3 returns success the registration response, then insert the 2nd RNC3 from trend the 2nd RNC3 registration after receiving this failed registration response.Equally in this embodiment, the embodiment of the invention has also proposed the recovery pattern, after inserting a RNC2 at NodeB1, the one RNC2 present load height, and disposed the re-host (returning genus) of load triggers, therefore a RNC2 can initiatively send the re-host request to the NodeB1 of registration, require this NodeB1 heavily to register, can whether can NodeB1 judges carry out re-host to the 2nd RNC3, for example normally judge and carry out re-host to the 2nd RNC3 by judging with the communication link of the 2nd RNC3.Can carry out re-host to the 2nd RNC3 if NodeB1 judges, then to attempt registering, if succeed in registration then return the re-host success response to a RNC2 to the 2nd RNC3; Otherwise return the re-host failure response, this moment, this NodeB1 still belonged on a RNC2.

By above-mentioned two kinds of RNC ownership pattern, if the RNC of the current access of NodeB breaks down or when breaking down with the IUB link of this RNC, NodeB just can initiatively initiate to register to another RNC, and provides the wireless access service by other RNC to it.And the embodiment of the invention can also initiatively trigger NodeB and return genus when the RNC of current access load be high, by adjusting the attaching relation of NodeB and RNC, is implemented in the Load Reshuffling of RNC when busy, therefore realizes meeting sharing of RNC in the control aspect.

Yet because third party's controller (as adjacent area RNC) is the measurement (UMTS measures cell scrambling) that utilizes UE, and, initiate relevant access process to the RNC at this place, sub-district according to pre-configured neighboring BS relationship.If therefore the host at NodeB is carrying out can't notifying third party's controller when RNC switches, and exist this moment NodeB to switch the situation that identical scrambler is used in the sub-district, front and back, can not insert the switching of RNC because know NodeB at third party's controller so, still find former RNC, therefore will initiate relevant access process to the RNC of mistake, and then cause service fail.Even, before and after NodeB switches, use different scramblers, so still need in third party's controller 2 sub-districts of each physical cell configuration (before 1 corresponding switching, the corresponding back of switching) in order to prevent that above-mentioned situation from taking place.Because the adjacent area specification is subjected to protocols limit, maximum has 32 homogeneous-frequency adjacent-domains, 32 alien frequencies adjacent areas, 32 different system adjacent areas, and at dense city, adjacent area quantity is original just relatively more nervous, so this scheme also can't well solve the influence problem of RNC switching to peripheral network element.

Therefore in order to solve the influence problem of above-mentioned RNC switching to peripheral network element, the described RNC of the embodiment of the invention also is used for, behind the signaling message of receiving third party's controller (as peripheral RNC or BSC), judge the sub-district ownership according to the signaling message that receives, if this sub-district ownership is then directly handled on this RNC; If this sub-district belongs to another RNC, then described signaling message is transmitted to another RNC, for example adopt SCCP (Signalling Connection Control Part, signaling connection control protocol) trunking scheme to carry out.Even therefore third party's controller has sent signaling message to the RNC of mistake, receive that the RNC of this signaling message also can be forwarded to this signaling message on the correct RNC automatically, thereby eliminate the influence of RNC switching peripheral network element.If this RNC breaks down, disposed the signalling point of the RNC of this fault that can superpose automatically after another RNC that signalling point helps each other detects so.This moment is because former RNC fault, message will send by alternate route, message will be by normal RNC interposition like this, if this sub-district belongs under this RNC, then directly handle, if do not belong at this RNC, the RNC that then forwards current ownership to handles, if there is the RNC of a plurality of load sharings, then can transmit according to the forwards tabulation of configured in advance.This embodiment disaster tolerance RNC bunch of inner circulation, has solved ownership and has switched influence to third party's controller by signaling message, thereby realizes that RNC bunch of disaster tolerance and periphery have the seamless connection of network element.

The embodiment of the invention also proposes to measure by strengthening UE, make third party's controller can obtain the RNC ID at place, sub-district, thereby third party's controller can be initiated operation flow to correct RNC, thereby solves the influence problem of above-mentioned RNC switching to peripheral network element.Therefore RNC also is used for after the access of accepting NodeB Cell ID being handed down to described NodeB; NodeB broadcasts the Cell ID that described RNC issues in cell system message; UE is when measuring the adjacent area, Cell ID in the meeting reading cell system message, thereby obtain the ID of the RNC of sub-district correspondence according to this Cell ID, and be carried at and send to third party's controller in the measurement report, the ID of third party's controller RNC that just can report according to UE initiates operation flow to correct RNC like this.After NodeB switched RNC, the new RNC that switches also can be handed down to NodeB with the Cell ID corresponding with self equally, and by in cell system message, the broadcasting of NodeB, thereby make the RNC after third party's controller can be selected to switch initiate operation flow.This embodiment can solve the influence of ownership switching to third party's controller, and can reduce the parameter configuration workload simultaneously, realizes the network self-adapting adjustment, has reduced maintenance workload, and meets the needs of following wireless network flattening development.

Therefore corresponding to foregoing description, the NodeB of the embodiment of the invention and the structure of RNC are as follows:

As shown in Figure 5, be the structure chart of embodiment of the invention NodeB, this NodeB1 comprises two cover IUB transmission links 10 at least, and by described IUB transmission link respectively with at least two foundation under the RNC that concerns link to each other.This NodeB1 comprises and communicates to connect module 11, registration initiation module 12, registration response receiver module 13 and access module 14, communicate to connect module 11 be used for setting up respectively and setting up under the communicating to connect of two RNC of relation; Registration initiation module 12 is used for initiating registration; Registration response receiver module 13 is used to receive the registration response of returning; Access module 14 is used for responding according to the registration that registration response receiver module 13 receives, and selects a RNC to insert under setting up two RNC of relation.

Wherein, NodeB1 links to each other by the RNC that concerns under the network equipment 4 and at least two foundation.

Wherein, comprise that also registration response judge module 15 is used for judging according to the registration response that registration response receiver module 13 receives whether the RNC that initiates registration allows to insert, if described RNC does not allow to insert, then notify described registration initiation module 12 other RNC of relation under setting up to initiate registration; If described RNC allows to insert, then notify access module 14 to insert described RNC.

Wherein, also comprise Cell ID receiver module 16 and cell system message broadcast module 17, Cell ID receiver module 16 is used for receiving Cell ID from the RNC that inserts, and described Cell ID is corresponding with the RNC ID of described access; The Cell ID that cell system message broadcast module 17 is used for receiving broadcasts at cell system message.

As shown in Figure 6, be the structure chart of embodiment of the invention RNC, this RNC2 comprises register requirement receiver module 21, registration judge module 22 and registers response and return module 23 that register requirement receiver module 21 is used to receive the registration that NodeB1 initiates; Registration judge module 22 is used to judge whether to accept the registration of NodeB1; The registration response is returned module 23 and is used for returning the registration response according to the judged result of registration judge module 22 to NodeB1.

Wherein, registration judge module 22 comprises load judgment submodule 221, is used for judging whether to accept according to RNC self loading condition the registration of described NodeB.

Wherein, register judge module 22 and also comprise negotiation judgement submodule 222, be used for holding consultation, judge whether to accept the registration of NodeB1 according to negotiation result with setting up the affiliated RNC that concerns.

Wherein, this RNC comprises that also Cell ID preserves module 24 and Cell ID issues module 25, and Cell ID issues Cell ID that module 24 is used for preserving and is handed down to and allows the NodeB that inserts.

Wherein, this RNC also comprises signaling message receiver module 26, sub-district ownership judge module 27 and signaling message forwarding module 28, and signaling message receiver module 26 is used to receive the signaling message of third party's controller; The signaling message that sub-district ownership judge module 28 is used for receiving according to described signaling message receiver module is judged the sub-district ownership; Signaling message forwarding module 28 is used for described signaling message being transmitted to the RNC that sets up affiliated relation when sub-district ownership judge module 27 is judged not on described RNC according to signaling message.

Wherein, this RNC also comprises the signalling point module 29 of helping each other, and is used for when the RNC that sets up attaching relation with this RNC breaks down, and the signalling point of this fault RNC that superposes is taken over this fault RNC.When breaking down as a RNC, the superpose signalling point of a RNC of the 2nd RNC is taken over a RNC.

System and corresponding NodeB and RNC by above-mentioned RNC load sharing disaster recovery, in the time of can breaking down at the RNC of the current access of NodeB or break down with the IUB link of this RNC, the RNC that in time switches to backup provides the wireless access service for this NodeB, thereby improves the reliability of RNC.And the embodiment of the invention can also realize the Load Reshuffling of RNC by adjusting the attaching relation of NodeB and RNC, realizes load sharing in the controller aspect.And the embodiment of the invention can also be eliminated the influence of ownership switching to third party's controller.

As shown in Figure 7, be the method flow diagram of the RNC load sharing disaster recovery of the embodiment of the invention one, NodeB links to each other with the 2nd RNC with first radio network controller (RNC) at least, and relation under setting up between a RNC and the 2nd RNC may further comprise the steps:

Step S701, NodeB sets up respectively and the communicating to connect of a described RNC and described the 2nd RNC by the IUB transmission link that expands.

Step S702, NodeB initiate registration.

Step S703, NodeB select a RNC to insert from a RNC and the 2nd RNC according to the registration response of returning.

When this embodiment can break down at the RNC of the current access of NodeB or break down with the IUB link of this RNC, the RNC that in time switches to backup provided the wireless access service for this NodeB, thereby improves the reliability of RNC.

The embodiment of the invention has proposed two kinds of affiliated modes that concern of RNC foundation according to the tendentiousness that NodeB inserts RNC, a kind of is principal and subordinate's attributable system, one of them RNC provides main service to be called main ownership RNC, and the IUB transmission link that this master's ownership RNC is connected with NodeB is called main ownership IUB transmission link; Another RNC provides the disaster tolerance service, is called from ownership RNC, and the IUB transmission link that it is connected with NodeB is called the transmission link from ownership IUB.Another kind is symmetrical ownership pattern, and NodeB does not contain any tendentiousness, by consulting to determine which RNC NodeB inserts between the RNC mutually.

As shown in Figure 8, the method flow diagram for RNC load sharing disaster recovery under principal and subordinate's attributable system of the embodiment of the invention two may further comprise the steps:

Step S801, NodeB sets up respectively and the communicating to connect of the RNC of principal and subordinate's ownership by the 2 cover IUB transmission of expanding.

Step S802, communicating to connect of NodeB and a RNC and the 2nd RNC set up finish after, NodeB1 preferentially registers to main ownership RNC by main ownership IUB transmission link.

Step S803, main ownership RNC judges whether to allow NodeB to insert according to the load state of self.

Step S804, if disposing, this master's ownership RNC do not force to forbid registration, or enabled the NodeB re-host of load triggers and led the current load of ownership RNC not high, then main ownership RNC judges that permission NodeB inserts, and return success registration response to it, after NodeB receives successfully registration response, flow process according to the IUB interface standard inserts main ownership RNC, just can under main ownership RNC control, provide the wireless access service then, only be used for NodeB and from ownership RNC keep communicating to connect from ownership IUB transmission link this moment, be used for fault detect, but do not control this NodeB from ownership RNC.

Step S805 is if main ownership RNC load height then returns the success registration response of having ready conditions to NodeB1.

Step S806, NodeB receive the described success registration response of having ready conditions, by from ownership IUB transmission link to registering from ownership RNC.

Step S807 after receiving the register requirement of NodeB, also can judge whether to allow its access from ownership RNC according to the load condition of self, and returns corresponding registration response to it.

Step S808, NodeB belong to access of selection the RNC according to the registration response of returning from ownership RNC from the principal and subordinate.If return success the registration response from ownership RNC to NodeB, then NodeB selects to insert from ownership RNC, is providing the wireless access service under the control of ownership RNC; If also return the success registration response of having ready conditions to NodeB from ownership RNC, then NodeB is still preferential selects main ownership RNC to insert.If main certainly ownership RNC returns the failed registration response to NodeB, then NodeB just uses from ownership IUB transmission link to initiating register flow path from ownership RNC.

The embodiment of the invention belongs to pattern at this principal and subordinate and has also proposed a kind of recovery pattern, NodeB be linked into from the ownership RNC on after, to continue to attempt on main ownership RNC, to register, if main ownership RNC returns success the registration response, then NodeB will select suitable opportunity (business will be lower than the thresholding of configuration, avoid the influence professional) carry out re-host (returning genus), re-register under the main ownership RNC, and and carry out de-host (go ownership) from ownership RNC, remain preferential selection of NodeB like this and insert to main ownership RNC.

As shown in Figure 9, the method flow diagram for RNC load sharing disaster recovery under the symmetrical attributable system of the embodiment of the invention three may further comprise the steps:

Step S901, NodeB transmits communicating to connect of foundation respectively and a RNC and the 2nd RNC by the 2 cover IUB that expand.Illustrate that this NodeB can't register to it if NodeB can't establish a communications link with RNC, therefore can only register to another one RNC.

Step S902, communicating to connect of NodeB and a RNC and the 2nd RNC set up finish after, NodeB can select a normal transmission link to initiate registration to RNC, as initiating registration to a RNC.

Step S903, a RNC can hold consultation with the 2nd RNC after receiving the register requirement of NodeB, consult the attaching relation of NodeB, can increase corresponding negotiation message and flow process by the IUR interface RNSAP between expansion the one RNC and the 2nd RNC.

Step S904, NodeB selects an access according to the registration response of returning from a RNC and the 2nd RNC.If a RNC and the 2nd RNC determine to register on a RNC after consulting, then a RNC returns success the registration response to NodeB; If consult to determine to register on the 2nd RNC, then a RNC returns the failed registration response to NodeB, and NodeB can if the 2nd RNC returns success the registration response, then insert the 2nd RNC3 from trend the 2nd RNC registration after receiving this failed registration response.

Equally in this embodiment, the embodiment of the invention has also proposed the recovery pattern, after inserting a RNC at NodeB, the one RNC present load height, and disposed the re-host (returning genus) of load triggers, therefore a RNC can initiatively send the re-host request to the NodeB of registration, requires this NodeB heavily to register, can whether can NodeB judges carry out re-host to the 2nd RNC, for example normally judge and carry out re-host to the 2nd RNC by judging with the communication link of the 2nd RNC3.Can carry out re-host to the 2nd RNC if NodeB judges, then to attempt registering, if succeed in registration then return the re-host success response to a RNC to the 2nd RNC; Otherwise return the re-host failure response, this moment, this NodeB still belonged on a RNC.

By above-mentioned two kinds of RNC ownership pattern, make that NodeB just can initiatively initiate to register to another RNC, and provides the wireless access service by other RNC to it when the RNC of the current access of NodeB breaks down or breaks down with the IUB link of this RNC.And the embodiment of the invention can also initiatively trigger NodeB and return genus when the RNC of current access load be high, by adjusting the attaching relation of NodeB and RNC, is implemented in the Load Reshuffling of RNC when busy, therefore realizes meeting sharing of RNC in the control aspect.

The present invention solves the influence problem of RNC switching to peripheral network element by following two kinds of embodiment.

As shown in figure 10, eliminate the flow chart that influence method of RNC switching, may further comprise the steps peripheral network element for the embodiment of the invention one:

Step S1001, a RNC receives the signaling message of third party's controller (as peripheral RNC or BSC).

Step S1002, a RNC judges the sub-district ownership according to the signaling message that receives.

Step S1003, is then directly handled by a RNC on a RNC if judge this sub-district ownership.

Step S1004, if judge this sub-district ownership on the 2nd RNC, then a RNC is transmitted to the 2nd RNC with described signaling message, for example adopts SCCP (Signalling Connection ControlPart, signaling connection control protocol) trunking scheme to carry out.

Even sent signaling message to the RNC of mistake, receive that the RNC of this signaling message also can be forwarded to this signaling message on the correct RNC automatically, thereby eliminate the influence of RNC switching peripheral network element by the foregoing description third party controller.If this RNC breaks down, disposed the signalling point of the RNC of this fault that can superpose automatically after another RNC that signalling point helps each other detects so.This moment is because former RNC fault, message will send by alternate route, message will be by normal RNC interposition like this, if this sub-district belongs under this RNC, then directly handle, if do not belong at this RNC, the RNC that then forwards current ownership to handles, if there is the RNC of a plurality of load sharings, then can transmit according to the forwards tabulation of configured in advance.

This embodiment disaster tolerance RNC bunch of inner circulation, has solved ownership and has switched influence to third party's controller by signaling message, thereby realizes that RNC bunch of disaster tolerance and periphery have the seamless connection of network element.

As shown in figure 11, for the embodiment of the invention two is eliminated the flow chart that influence method of RNC switching to peripheral network element, present embodiment is measured by strengthening UE, make third party's controller can obtain the RNC ID at place, sub-district, thereby third party's controller can be initiated operation flow to correct RNC, thereby solve the influence problem of above-mentioned RNC switching to peripheral network element, this embodiment may further comprise the steps:

Step S1101, RNC are handed down to described NodeB with the Cell ID of self correspondence after the access of accepting NodeB.

Step S1102, NodeB broadcasts the Cell ID that RNC issues in cell system message.

Step S1103, UE understand the Cell ID in the reading cell system message when measuring the adjacent area, thereby obtain the ID of the RNC of sub-district correspondence according to this Cell ID.

Step S1104, UE are carried at the ID of the RNC of the sub-district correspondence that obtains and send to third party's controller in the measurement report.

The ID of the RNC that step S1105, third party's controller just can report according to UE initiates operation flow to correct RNC.

After NodeB switched RNC, the new RNC that switches also can be handed down to NodeB with the Cell ID corresponding with self equally, and by in cell system message, the broadcasting of NodeB, thereby make the RNC after third party's controller can be selected to switch initiate operation flow.

This embodiment can solve the influence of ownership switching to third party's controller, and can reduce the parameter configuration workload simultaneously, realizes the network self-adapting adjustment, has reduced maintenance workload, and meets the needs of following wireless network flattening development.

The above only is a preferred implementation of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.

Claims

1. the method for a RNC load sharing disaster recovery is characterized in that, base station node B links to each other with the 2nd RNC with first radio network controller (RNC) at least, and described base station and a described RNC and described the 2nd RNC set up attaching relation, may further comprise the steps:

Described NodeB sets up respectively and the communicating to connect of a described RNC and described the 2nd RNC;

Described NodeB initiates registration;

Described NodeB selects a RNC to insert from a described RNC and described the 2nd RNC according to the registration response of returning.

2. the method for RNC load sharing disaster recovery according to claim 1 is characterized in that described NodeB links to each other with the 2nd RNC with a RNC and specifically comprises:

Described NodeB links to each other with described the 2nd RNC with a described RNC by the network equipment.

3. the method for RNC load sharing disaster recovery according to claim 1 is characterized in that, principal and subordinate's ownership each other between a described RNC and described the 2nd RNC,

Described NodeB initiates registration and specifically comprises:

Described NodeB preferentially registers to main ownership RNC by main ownership IUB transmission link.

4. as the method for RNC load sharing disaster recovery as described in the claim 3, it is characterized in that described NodeB selects a RNC to insert and specifically comprises according to the registration response of returning from a described RNC and described the 2nd RNC:

If described main ownership RNC allows registration, then return success the registration response to described NodeB;

After described NodeB receives described successfully registration response, insert described main ownership RNC.

5. the method for RNC load sharing disaster recovery according to claim 1 is characterized in that, described NodeB selects a RNC to insert from a described RNC and described the 2nd RNC and specifically comprises according to the registration response of returning:

If described main ownership RNC load height then returns the success registration response of having ready conditions to described NodeB;

Described NodeB receives the described success registration response of having ready conditions, by from ownership IUB transmission link to registering from ownership RNC;

Described NodeB is according to the described registration response of returning from ownership RNC, from described main ownership RNC with describedly select a RNC to insert from ownership RNC.

6. as the method for RNC load sharing disaster recovery as described in the claim 5, it is characterized in that described NodeB is according to the described registration response of returning from ownership RNC, from described main ownership RNC with describedly from ownership RNC, select a RNC to insert, specifically may further comprise the steps:

If describedly return the success registration response of having ready conditions from ownership RNC, then described NodeB selects main ownership RNC to insert;

If described returning success from ownership RNC registered response, then described NodeB selects to insert from ownership RNC.

7. as the method for RNC load sharing disaster recovery as described in the claim 5, it is characterized in that described NodeB is according to the described registration response of returning from ownership RNC, from described main ownership RNC with describedly from ownership RNC, select a RNC to insert, specifically may further comprise the steps:

If described main ownership RNC does not allow registration, then return the failed registration response to described NodeB;

After described NodeB receives described failed registration response, select to insert from ownership RNC.

8. as the method for RNC load sharing disaster recovery as described in claim 6 or 7, it is characterized in that, select after ownership RNC inserts at described NodeB, further comprising the steps of:

Described NodeB continues to attempt the registration to described main ownership RNC;

After receiving that described main ownership returns success the registration response, described NodeB selects described main ownership RNC to insert.

9. the method for RNC load sharing disaster recovery according to claim 1 is characterized in that, symmetry ownership each other between a described RNC and described the 2nd RNC;

Described NodeB initiates registration and specifically comprises:

Described NodeB registers to a described RNC by the IUB transmission link.

10. as the method for RNC load sharing disaster recovery as described in the claim 9, it is characterized in that described NodeB selects a RNC to insert and specifically comprises according to the registration response of returning from a described RNC and described the 2nd RNC:

A described RNC and described the 2nd RNC hold consultation;

If consult in described RNC registration, a then described RNC returns success the registration response to described NodeB;

If consult in described the 2nd RNC registration, a then described RNC returns the failed registration response to described NodeB;

Described NodeB inserts described the 2nd RNC after receiving the failed registration response that a described RNC returns.

11. the method as RNC load sharing disaster recovery as described in the claim 10 is characterized in that, and is after described NodeB inserts a described RNC or the 2nd RNC, further comprising the steps of:

If the RNC load height of the current access of described NodeB, then the RNC of described current access returns heavy register requirement to described NodeB, requires described NodeB to register to another RNC.

12. the method for RNC load sharing disaster recovery is characterized in that according to claim 1, and is further comprising the steps of:

After a described RNC receives the signaling message of third party's controller, judge the sub-district ownership according to described signaling message;

If described sub-district belongs to a described RNC, a then described RNC directly handles;

If described sub-district belongs to described the 2nd RNC, a then described RNC is transmitted to described the 2nd RNC with described signaling message.

13. the method for RNC load sharing disaster recovery is characterized in that according to claim 1,, selects from a described RNC and described the 2nd RNC after the RNC access according to the registration response of returning at described NodeB, and is further comprising the steps of:

The RNC that described NodeB inserts is handed down to described NodeB with Cell ID, and described Cell ID is corresponding with RNC ID;

Described NodeB broadcasts the Cell ID that described RNC issues in cell system message;

UE sends to third party's controller with described Cell ID after obtaining described Cell ID.

14. the system of a RNC load sharing disaster recovery is characterized in that, comprises the RNC that concerns under NodeB and at least two foundation that link to each other with described NodeB,

Described NodeB is used for setting up respectively and the communicating to connect of described RNC, and initiates registration for one in described RNC, and according to the registration response of returning, selects a RNC to insert from described RNC;

Described RNC is used for after the registration that receives described NodeB, returns corresponding registration response to described NodeB.

15. the system as RNC load sharing disaster recovery as described in the claim 14 is characterized in that, also comprises the network equipment, described NodeB links to each other by the RNC that concerns under the described network equipment and described two foundation.

16. the system as RNC load sharing disaster recovery as described in claim 14 or 15 is characterized in that, described RNC also is used for consulting mutually the attaching relation of described NodeB, and returns corresponding registration response according to the attaching relation of described negotiation to described NodeB.

17. the system as RNC load sharing disaster recovery as described in claim 14 or 15 is characterized in that described RNC also is used for according to self load condition, returns corresponding registration response to described NodeB.

18. system as RNC load sharing disaster recovery as described in claim 14 or 15, it is characterized in that, described RNC, also be used for behind the signaling message of receiving third party's controller, judge the sub-district ownership according to described signaling message, if described sub-district belongs to another RNC, then described signaling message is transmitted to another RNC.

19. the system as RNC load sharing disaster recovery as described in claim 14 or 15 is characterized in that, described RNC also is used for after the access of accepting described NodeB Cell ID being handed down to described NodeB;

The Cell ID that described NodeB also is used for described RNC is issued broadcasts at cell system message.

20. a NodeB is characterized in that, described NodeB links to each other with at least two RNC that set up attaching relation, comprise communicating to connect module, registration initiation module, registration response receiver module and access module,

The described module that communicates to connect is used for setting up respectively and the communicating to connect of described two RNC that set up attaching relation;

Described registration initiation module is used for initiating registration;

Described registration response receiver module is used to receive the registration response of returning;

Described access module is used for the registration response that receives according to described registration response receiver module, selects a RNC to insert from described two RNC that set up attaching relation.

21., it is characterized in that described NodeB links to each other with at least two RNC that set up attaching relation by the network equipment as NodeB as described in the claim 20.

22. as NodeB as described in claim 20 or 21, it is characterized in that, also comprise registration response judge module, be used for judging according to the registration response that described registration response receiver module receives whether the RNC that initiates registration allows to insert, if described RNC does not allow to insert, then notify described registration initiation module other RNC of relation under setting up to initiate registration; If described RNC allows to insert, then notify described access module to insert described RNC.

23., it is characterized in that as NodeB as described in the claim 22, also comprise Cell ID receiver module and cell system message broadcast module,

Described Cell ID receiver module is used for receiving Cell ID from the RNC that inserts, and described Cell ID is corresponding with the RNC ID of described access;

Described cell system message broadcast module, the Cell ID that is used for receiving broadcasts at cell system message.

24. a RNC is characterized in that, comprises that register requirement receiver module, registration judge module and registration response return module,

Described register requirement receiver module is used to receive the registration that NodeB initiates;

Described registration judge module is used to judge whether to accept the registration of described NodeB;

Module is returned in described registration response, is used for returning the registration response according to the judged result of described registration judge module to described NodeB.

25. RNC shown in claim 24 is characterized in that, described registration judge module comprises the load judgment submodule, is used for judging whether to accept according to described RNC self loading condition the registration of described NodeB.

26. RNC shown in claim 24 or 25 is characterized in that, described registration judge module also comprises to be consulted to judge submodule, is used for holding consultation with the RNC that sets up affiliated relation, judges whether to accept the registration of described NodeB according to negotiation result.

27. RNC shown in claim 26 is characterized in that, comprises that also Cell ID preserves module and Cell ID issues module,

Described Cell ID issues module, and the Cell ID that is used for preserving is handed down to the NodeB that allows access.

28. RNC shown in claim 26 is characterized in that, also comprises signaling message receiver module, sub-district ownership judge module and signaling message forwarding module,

Described signaling message receiver module is used to receive the signaling message of third party's controller;

Described sub-district ownership judge module, the signaling message that is used for receiving according to described signaling message receiver module is judged the sub-district ownership;

Described signaling message forwarding module is used for described signaling message being transmitted to the RNC that sets up affiliated relation when described sub-district ownership judge module is judged not on described RNC according to described signaling message.