CN101466089B - Method and system for processing disaster toleration, call processing method - Google Patents
Method and system for processing disaster toleration, call processing method Download PDFInfo
- Publication number
- CN101466089B CN101466089B CN2009100054119A CN200910005411A CN101466089B CN 101466089 B CN101466089 B CN 101466089B CN 2009100054119 A CN2009100054119 A CN 2009100054119A CN 200910005411 A CN200910005411 A CN 200910005411A CN 101466089 B CN101466089 B CN 101466089B
- Authority
- CN
- China
- Prior art keywords
- gateway
- controller
- sign
- location database
- corresponding relation
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The invention discloses a disaster-tolerance processing method, a system and a call processing method thereof; wherein, the disaster-tolerance processing comprises one or more controllers and a gateway position database; wherein, each controller includes one or more gateways; and the gateway position database is used for storing the corresponding relation between the identifier of the controllers and one or more gateway identifiers registered on the controllers. By means of the technical proposal and by the gateway position database, the corresponding relation between the gateways and the controllers is stored, only the registering record of the gateway is updated when the gateway changes the register, so as to simplify the disaster-tolerance processing method and realize the rapid register when the disaster-tolerance conversion; the controllers can rapidly find out the controller on which the current called gateway is positioned to execute the call and route selection after being correspondingly processed.
Description
Technical field
The present invention relates to the communications field, relate in particular to a kind of disaster tolerance processing method and system, call processing method.
Background technology
Next-generation communication network (Next Generation Network abbreviates NGN as) is a kind of network that control separates with access of calling out, and gateway device be responsible for accessing terminal user or terminal network, call controller are responsible for calling out control and Business Processing.
Call controller in the NGN core net (hereinafter to be referred as controller), soft switch (the Soft Switch in the flexible exchanging network for example, abbreviate SS as), IP multimedia subsystem, IMS (Multimedia Subsystem, abbreviate IMS as) gateway control entity (Gateway Control Function in the network, abbreviate GCF as), call conversation control entity (CallSession Control Function, abbreviate CSCF as), because controller is when realizing function, need have very high integrated level, and the very large customer volume of load, based on this, the disaster tolerance ability of controller is particularly important.
In implementation process, the function of the part disaster tolerance of NGN core net is meant: in the communication process of single gateway and former controller, when breaking down, this gateway can switch on the alternative core net switching equipment, communicate with this alternative core net switching equipment, and above-mentioned single gateway is switching to the process of alternative core net switching equipment from former controller, and other gateways except that this gateway are unaffected.
At present, the mechanism that realizes the core net disaster tolerance has Hot Spare, dual-homed etc., but these mechanism are when solving the quick routing function of part disaster tolerance function and part disaster tolerance, all have difficulties, quick routing function for how fast and effeciently realizing part disaster tolerance and part disaster tolerance does not propose effective solution as yet.
Summary of the invention
Consider a kind of technology of the needs that exist in the correlation technique to solve the problem of the quick routing function of how fast and effeciently realizing part disaster tolerance and part disaster tolerance and propose the present invention, for this reason, main purpose of the present invention is to provide a kind of disaster tolerance processing method and system, call processing method, to address the above problem.
According to an aspect of the present invention, provide a kind of disaster tolerance treatment system.
Disaster tolerance treatment system according to the present invention comprises: one or more controllers, and wherein, each controller includes one or more gateways; The gateway location database, corresponding relation between the one or more gateway identifications that are used to preserve the controller identifier of controller and be registered in this controller, wherein, the gateway location database root is determined the controller of the gateway registration of this gateway identification correspondence according to the query requests that carries gateway identification of coming self-controller.
Wherein, each controller all is used to preserve the corresponding relation between user's terminal iidentification and user's the gateway identification of home gateway.
Preferably, the gateway location database is positioned at one of following entity: attaching position register is that HLR, home subscriber server are that HSS, reorientation server are RS.
Wherein, the interface between gateway location database and the controller is realized by one of following agreement: session initiation protocol is that SIP, MAP are MAP, Diameter.
Preferably, gateway identification or controller identifier comprise one of following: device number, domain name.
According to another aspect of the present invention, provide a kind of disaster tolerance processing method.
Disaster tolerance processing method according to the present invention comprises: location registration process: first controller receives first register requirement from gateway, wherein, carries the sign of gateway in first register requirement; First controller sends second register requirement to the gateway location database, wherein, carries the sign of gateway and the sign of first controller in second register requirement; Corresponding relation set up to be handled: the gateway location database root is according to second register requirement, sets up the corresponding relation between the sign of the sign of gateway and first controller; The gateway location database root is determined the controller of the gateway registration of this gateway identification correspondence according to the query requests that carries gateway identification of coming self-controller.
Preferably, in above-mentioned location registration process, after the gateway location database was set up corresponding relation, this method also comprised: first controller is preserved the sign of gateway in this locality.
Further, after corresponding relation is set up processing, this method also comprises: the position is upgraded and is handled: under predetermined scene, corresponding relation between the sign of gateway location database cancellation gateway and the sign of first controller is set up the corresponding relation between the sign of the sign of gateway and second controller.
Preferably, upgrade in the processing in above-mentioned position, after the corresponding relation between the sign of gateway location database cancellation gateway and the sign of first controller, this method also comprises: gateway location database notification first controller, cancelled the corresponding relation between the sign of the sign of gateway and first controller; The sign of the local gateway of preserving of first controller deletion.
Wherein, it is one of following that predetermined scene comprises: first controller detects the interruption that is connected between gateway and first controller, send the primary importance update request to the gateway location database, carry the message that the indication gateway is not registered in the primary importance update request on first controller; Perhaps, second controller receives the 3rd register requirement from gateway, wherein, carries the sign of gateway in the 3rd register requirement; Second controller sends second place update request to the gateway location database, wherein, carries the sign of gateway and the sign of second controller in the second place update request.
Preferably, after the gateway location database was set up corresponding relation between the sign of the sign of gateway and second controller, this method also comprised:
Second controller is preserved the sign of gateway in this locality.
Wherein, sign comprises one of following: device number, domain name.
According to a further aspect of the invention, provide a kind of call processing method.
Call processing method according to the present invention comprises: controller sets in advance first corresponding relation between user ID and the gateway identification; Controller receives the call request from the calling subscriber, wherein, carries CSI called subscriber identification in the call request; Controller is determined the gateway identification corresponding with CSI called subscriber identification according to first corresponding relation; Controller is according to judging the gateway identification of whether preserving the CSI called subscriber identification correspondence in its registration gateway identification information; If preserve the gateway identification of CSI called subscriber identification correspondence in the registration gateway identification information, then controller makes a call by the called subscriber of gateway to the CSI called subscriber identification correspondence.
Further, said method also comprises: if do not preserve the gateway identification of CSI called subscriber identification correspondence in the controller, controller sends query requests to the gateway location database, carries the gateway identification of CSI called subscriber identification correspondence in the query requests; The gateway location database root be it is investigated to ask and is asked, determines the controller of gateway registration.
Preferably, this method also comprises: the gateway location database sets in advance second corresponding relation between gateway identification and the controller identifier, at this moment, the gateway location database determine gateway registration controller comprise: the gateway location database root is according to second corresponding relation, determine the current controller corresponding, and the sign of current controller is sent to controller with gateway identification.
Further, after the gateway location database sent to controller with the sign of current controller, said method also comprised: controller sends CSI called subscriber identification according to the sign of current controller to current controller; Current controller is by gateway, makes a call to the called subscriber of CSI called subscriber identification correspondence.
By above-mentioned at least one technical scheme of the present invention, by the corresponding relation between GL_DB preservation gateway and the controller, when changing registration, gateway only needs the more registration of new gateway, like this, simplified the disaster tolerance processing method, realized the fast registration when disaster tolerance switches, controller can find the current controller that is positioned at of called gateway to carry out call routing after handling accordingly fast.
Description of drawings
Accompanying drawing is used to provide further understanding of the present invention, and constitutes the part of specification, is used from explanation the present invention with embodiments of the invention one, is not construed as limiting the invention.In the accompanying drawings:
Fig. 1 is the flow chart according to the disaster tolerance processing method of the inventive method embodiment one;
Fig. 2 a is the flow chart according to the location registration process of the inventive method embodiment;
Fig. 2 b upgrades the flow chart of handling according to the position of the inventive method embodiment;
Fig. 3 is the flow chart according to the call processing method of the inventive method embodiment two;
Fig. 4 is the detailed process flow chart according to the call processing method of the inventive method embodiment;
Fig. 5 is a structured flowchart according to the GL_DB networking of the embodiment of the invention;
Fig. 6 is another structured flowchart according to the GL_DB networking of the embodiment of the invention;
Fig. 7 is the signaling process figure according to the registration handling method of the embodiment of the invention;
Fig. 8 is the signaling process figure according to the call processing method of the embodiment of the invention.
Embodiment
Functional overview
As mentioned above, problem at the quick routing function how fast and effeciently to realize part disaster tolerance and part disaster tolerance that exists in the prior art, the present invention proposes a kind of disaster tolerance processing scheme, by in this system, introducing gateway location database (Gateway LocationDatabase, abbreviate GL_DB as) realize the corresponding relation between one or more gateway identifications that part disaster tolerance, this GL_DB be used to preserve the controller identifier of controller and be registered in this controller.Like this, when gateway changes the controller of registration, only need to change the registration of gateway, do not relate to the change of complicated resource, can realize the fast registration when disaster tolerance switches, controller can find the current controller that is positioned at of called gateway to carry out call routing after improving accordingly fast.
System embodiment
According to the embodiment of the invention, provide a kind of disaster tolerance treatment system.
Disaster tolerance treatment system according to the embodiment of the invention comprises: gateway location database and one or more controller, and wherein, each controller includes one or more gateways; The gateway location database, the corresponding relation between the one or more gateway identifications that are used to preserve the controller identifier of controller and be registered in this controller; Each controller all is used to preserve the corresponding relation between user's terminal iidentification and this user's the gateway identification of home gateway; And it is one of following that gateway identification or controller identifier comprise: device number, domain name, that is and, gateway identification can comprise: the device number of gateway, the domain name of gateway; Controller identifier can comprise: the device number of controller, the domain name of controller.
Wherein, this database GL_DB can be positioned at attaching position register (HomeLocation Register, abbreviate HLR as), home subscriber server (Home SubscriberServer, abbreviate HSS as), reorientation server (Redirect Server abbreviates RS as) or other external equipments.That is, GL_DB can be positioned at outside the controller, for example, is positioned at RS, HLR, HSS, also can be independent equipment.
Controller (SS/GCF/CSCF) can be by corresponding protocol such as session initiation protocol (Session Initiation Protocol, abbreviate SIP as), MAP (MobileApplication Part, abbreviate MAP as) agreement, Diameter visit GL_DB equipment, that is, the interface of controller and GL_DB equipment can use existing SIP or MAP, Diameter.
Because GL_DB is used for the corresponding relation of storage gateway and the current controller that is registered in of this gateway, controller can inquire about GL_DB learn certain gateway on the controller of current registration, controller can also upgrade the registration scenarios of certain gateway by GL_DB.
The technical scheme that provides by the embodiment of the invention, by the corresponding relation between GL_DB preservation gateway and the controller, like this, when changing registration, gateway only needs the more registration of new gateway, do not relate to the change of complicated resource, realized the fast registration when disaster tolerance switches, controller can find the current controller that is positioned at of called gateway to carry out call routing after improving accordingly fast.
Method embodiment one
According to the embodiment of the invention, provide a kind of disaster tolerance processing method.
Fig. 1 is the flow chart according to the disaster tolerance processing method of the embodiment of the invention, need to prove, for convenience of description, in Fig. 1, illustrated and described the technical scheme of method embodiment of the present invention, can in computer system, carry out such as a set of computer-executable instructions in the step shown in Fig. 1 with the form of step.Though figure 1 illustrates logical order, in some cases, can carry out step shown or that describe with the order that is different from herein.As shown in Figure 1, this method may further comprise the steps (step S102 is to step S104).
Step S102, location registration process: first controller receives first register requirement from gateway, wherein, carries the sign of gateway in first register requirement; First controller sends second register requirement to the gateway location database, wherein, carry the sign of gateway and the sign of first controller in second register requirement, afterwards, first controller is preserved the sign of gateway in this locality, that is, represent that this gateway is current in upward registration of this controller (that is first controller).
Step S104, corresponding relation set up to handle: the gateway location database root is according to second register requirement, sets up the corresponding relation between the sign of the sign of gateway and first controller, and it is one of following that gateway identification comprises: the device number of gateway, the domain name of gateway.
In specific implementation process, also can upgrade processing in the location, mainly comprise following two kinds of situations.
Situation one, the first controller detects the interruption that is connected between gateway and first controller, sends the primary importance update request to the gateway location database, carries the message that the indication gateway is not registered on first controller in the primary importance update request; Corresponding relation between the sign of gateway location database cancellation gateway and the sign of first controller is set up the corresponding relation between the sign of the sign of gateway and second controller; Gateway location database notification first controller has been cancelled the corresponding relation between the sign of the sign of gateway and first controller; The sign of the local gateway of preserving of first controller deletion; And second controller is preserved the sign of gateway in this locality.
Situation two: gateway is initiated the 3rd register requirement to second controller, wherein, carry the sign of gateway in the 3rd register requirement, second controller sends second place update request according to this request to the gateway location database, wherein, carry the sign of gateway and the sign of second controller in the second place update request.Corresponding relation between the sign of gateway location database cancellation gateway and the sign of first controller is set up the corresponding relation between the sign of the sign of gateway and second controller; Gateway location database notification first controller has been cancelled the corresponding relation between the sign of the sign of gateway and first controller; The sign of the local gateway of preserving of first controller deletion; And second controller is preserved the sign of gateway in this locality.
By above-mentioned processing as can be seen, after introducing GL_DB, the gateway that is registered in same controller can be when former controller loses efficacy or interrupted with being connected of former controller, switch the work under other controllers that is registered to, and the registration handoff procedure of each gateway, and to select the controller of registration when switching be separate, realized the part disaster tolerance.
In actual mechanical process, the operation principle of part disaster tolerance can be described as two processes: registration updating process and BCP basic call process are elaborated below in conjunction with accompanying drawing 2 and 3 pairs of above-mentioned two processes of accompanying drawing.
Fig. 2 a is the process chart of registering on controller according to the gateway of the embodiment of the invention, is applied to the application scenarios of gateway to the controller registration, shown in Fig. 2 a, comprises following processing (step S201a is to step S205a).
Step S201a, gateway sends login request message to controller, wherein, carries the sign of this gateway in this login request message;
Step S202a, controller receive above-mentioned login request message, obtain the sign of gateway;
Step S203a, controller sends location update request message to GL_DB, and this gateway of notice GL_DB is registered thereon, wherein, carries the sign of gateway and the sign of controller in this location update request message;
Step S204a, GL_DB receiving position update inquiry information is obtained the sign of gateway wherein and the sign of controller, and sets up the corresponding relation of the sign of the sign of gateway and controller;
Step S205a, controller upgrade local registration, and this gateway of mark has been registered on this controller in the local record table.
Fig. 2 b is the process chart of nullifying on controller according to the gateway of the embodiment of the invention, is applied to the gateway application scenarios that registration or slave controller are not nullified on controller, shown in Fig. 2 b, comprises following processing (step S201b is to step S205b).
Step S201b, gateway registration on controller 1, but to can send register requirement 1 to controller 2 when this controller 1 is nullified, carry the gateway identification of this gateway in this register requirement 1;
Step S202b, controller 2 receives register requirement 1, and sends register requirement 2 to GL_DB, carries the sign of gateway and the sign of controller 2 in this register requirement 2;
Step S203b, GL_DB be according to register requirement 2, the corresponding relation between the sign of cancellation gateway and the sign of controller 1, and set up corresponding relation between the sign of the sign of gateway and controller 2;
Step S204b, the sign of the local gateway of preserving of controller 1 cancellation is represented that this gateway is current not register on this controller;
Step S205b, controller 2 preserve the sign of this gateway in this locality, represent that this gateway is current to register on this controller.
Method embodiment two
According to the embodiment of the invention, provide a kind of call processing method.
Fig. 3 is the flow chart according to call processing method of the present invention, as shown in Figure 3, comprises following processing (step S302 is to step S310).
Step S302, controller set in advance first corresponding relation between user ID and the gateway identification, and wherein, user ID can be user's termination number;
Step S304, controller receives the call request from the calling subscriber, wherein, carries CSI called subscriber identification in the call request;
Step S306, controller determine the gateway identification corresponding with CSI called subscriber identification according to first corresponding relation;
Step S308, controller is according to judging the gateway identification of whether preserving the CSI called subscriber identification correspondence in its registration gateway identification information;
Step S310, if preserve the gateway identification of CSI called subscriber identification correspondence in the registration gateway identification information of controller, then controller makes a call by the called subscriber of gateway to the CSI called subscriber identification correspondence, wherein, preserve the current gateway identification that is registered in a plurality of gateways on this controller in the registration gateway identification information of controller.
In above-mentioned steps S308, if do not preserve the gateway identification of CSI called subscriber identification correspondence in the registration gateway identification information of controller, controller sends query requests to the gateway location database, carries gateway identification in the query requests; The gateway location database root be it is investigated the request of asking, determine gateway registration controller.Particularly, the gateway location database can set in advance second corresponding relation between gateway identification and the controller identifier, the gateway location database root is determined the current controller corresponding with gateway identification according to second corresponding relation, and the sign of current controller is sent to controller; Controller sends CSI called subscriber identification according to the sign of current controller to current controller; Current controller is by gateway, makes a call to the called subscriber of CSI called subscriber identification correspondence.
Wherein, it is one of following that gateway identification or controller identifier can comprise: device number, domain name, that is and, gateway identification can comprise: the device number of gateway, the domain name of gateway; Controller identifier can comprise: the device number of controller, the domain name of controller.
Fig. 4 is the flow chart according to the calling procedure of the embodiment of the invention, as shown in Figure 4, comprises following processing (step S401 is to step S408).
Step S401, default corresponding relation: the corresponding relation of pre-configured all numbers of each controller and gateway, that is, each gateway can be corresponding to a plurality of termination numbers, each termination number all has the gateway of its ownership, is that example is described this calling procedure with controller 1 below.
Step S402, bid: the calling subscriber sends call request to controller 1, carry this called subscriber's termination number in this call request, preferably, the termination number that can comprise the calling subscriber, controller 1 can be according to the corresponding relation that pre-sets, search the gateway that has corresponding relation with called subscriber's termination number, promptly find called subscriber's the gateway that termination number belonged to, convenient for subsequent descriptions, the gateway that will have corresponding relation with this called subscriber's termination number is called gateway 1.
Step S403, controller 1 can be checked the registration scenarios of gateway 1 in the local record table.
Step S404, controller 1 judge that gateway 1 is current whether in upward registration of this controller (being controller 1), if judged result enters into step S407 for being, otherwise, enter into step S405.
Step S405, controller 1 judge gateway 1 current the registration on this controller, then need to the GL_DB inquiry gateway 1 current controller of registering, and controller 1 sends query requests to GL_DB, carries the sign of gateway 1 in this query requests.
Step S406, GL_DB obtains the sign of gateway 1, according to gateway of preserving and the corresponding relation between the controller, determine to have the controller of corresponding relation with gateway 1, and obtain the sign of the gateway 1 current controller that is registered in, for convenience, will become controller 2 in the controller of gateway 1 current registration;
GL_DB sends to controller 1 with the sign of controller 2; Controller 1 sends called subscribers' terminal iidentification according to the sign of controller 2 to controller 2, and controller 2 is called out by gateway 2.
Step S407, gateway 1 have been registered on the controller 1, and then controller 1 uses local routing call called.
Step S408, it is called to continue.
Because Session Initiation Protocol is very general in the NGN network application; the present invention will be described to be embodied as example with the interface between controller and the GL_DB equipment by Session Initiation Protocol below; but be not limited to this, realize that by the interface between other agreements realization controllers and the GL_DB equipment method of the present invention is still within protection scope of the present invention.
Before being specifically described, at first the applied environment to following example is described, and Fig. 5 is an example of GL_DB networking, as shown in Figure 5, gateway 1, gateway 2 are registered in controller 1, and gateway 3 is registered in controller 2, and gateway 4 is registered in controller 3, wherein, user A is arranged in gateway 1, and user B is arranged in gateway 2, and user C is positioned at gateway 3, user D is positioned at gateway 4, and gateway 2 can the disaster tolerance switching be registered to controller 2.
Based on GL_DB networking frame figure shown in Figure 5, when gateway 2 because with the interruption that is connected of controller 1, register and switch to controller 2, be updated to GL_DB networking frame figure shown in Figure 6, its corresponding handling process specifically comprises the steps (step S701 is to step S712) as shown in Figure 7.
Step S701, gateway 2 interrupted with being connected of controller 1;
Step S702, controller 1 detect the interruption that is connected with gateway 2;
Being connected of itself and gateway 2 takes place the message of interrupting by to GL_DB in step S703, controller 1.For example, the REGISTER message informing GL_DB by Session Initiation Protocol;
After step S704, GL_DB receive REGISTER message, upgrade relevant record, the corresponding relation of promptly remove controls device 1 sign and gateway 2 signs;
Step S705, the controller at gateway 2 current places are NULL (unregistered), and GL_DB returns 200OK message to controller 1;
Step S706, controller 1 upgrades its local record, that is and, gateway 2 is current not to be registered on this controller;
Step S706, gateway 2 switchings are registered on the controller 2;
Step S707, controller 2 is given the message informing that gateway 2 is registered on it, for example passes through the REGISTER message informing GL_DB of Session Initiation Protocol;
After step S708, GL_DB receive REGISTER message, upgrade relevant record, that is, set up the corresponding relation of gateway 2 signs and controller 2 signs;
Step S709, the gateway 2 current controllers that are registered in are controller 2;
Step S710, GL_DB returns 200OK message to controller 2;
Step S711, controller 2 upgrades its local records, that is and, gateway 2 is current to be registered on this controller;
Step S712, gateway 2 succeeds in registration at controller 2, and controller 2 returns the message that succeeds in registration to gateway 2.
Based on GL_DB networking frame figure shown in Figure 6, during user B on the user D called gateways 2 on the gateway 4, its corresponding flow process specifically comprises the steps (step S801 is to step S807) as shown in Figure 8.
Step S801, user D calling party B, the gateway 4 at user D place are to controller 4 Event Report BCSM, and particularly, user D sends call request to controller 4, carries the termination number of user D and the termination number of user B in this call request;
Step S802, controller 4 finds that according to the mapping table of its pre-configured termination number and gateway identification user B is positioned on the gateway 2, further, controller 4 finds that by the search local record gateway 2 is current in upward registration of this controller (being controller 4);
Step S803, controller 4 sends query requests to GL_DB, inquires about the gateway 2 current controllers that are registered in, and can carry the identification information of gateway 2 in this query requests, for example, controller 4 can send query requests to GL_DB by the INVITE in the Session Initiation Protocol;
Step S804, GL_DB inquires about the gateway of its preservation and the corresponding relation of controller, determining the controller that has a corresponding relation with gateway 2 is controller 2, promptly, the gateway 2 current controllers 2 that are registered in, and return Query Result to controller 4, carry the sign of controller 2 in this Query Result, for example, GL_DB can return Query Result to controller 2 by 302 message in the Session Initiation Protocol;
Step S805, controller 4 are according to Query Result, according to the sign of the controller 2 that carries in the Query Result, to controller 2 request of making a call, carry the termination number of user B in this call request, for example, can send call request to controller 2 by Session Initiation Protocol;
Step S806, controller 2 receives the call request of self-controller 4, according to the pre-configured termination number and the mapping table of gateway identification, finds that user B is positioned on the gateway 2;
Step S807, controller 2 search local records are found that gateway 2 is current to go up registration at this controller (being controller 2), in being to use this locality to be routed to gateway 2, and calling party B.
As mentioned above, by means of disaster tolerance processing method provided by the invention and/or system, call processing method, by the corresponding relation between GL_DB preservation gateway and the controller, like this, when gateway changes registration, only need change the registration of node, not relate to the change of complicated resource, realize the fast registration when disaster tolerance switches, controller can find the current controller that is positioned at of called gateway to carry out call routing after improving accordingly fast.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (15)
1. a disaster tolerance treatment system comprises one or more controllers, and wherein, each controller includes one or more gateways, it is characterized in that, described system also comprises:
The gateway location database, corresponding relation between the one or more gateway identifications that are used to preserve the controller identifier of controller and be registered in this controller, wherein, described gateway location database root is determined the controller of the gateway registration of described gateway identification correspondence according to the query requests that carries gateway identification of coming self-controller.
2. system according to claim 1 is characterized in that, each controller all is used to preserve the corresponding relation between user's terminal iidentification and described user's the gateway identification of home gateway.
3. system according to claim 1 is characterized in that, described gateway location database is positioned at one of following entity: attaching position register is that HLR, home subscriber server are that HSS, reorientation server are RS.
4. system according to claim 1 is characterized in that, the interface between described gateway location database and the controller is realized by one of following agreement: session initiation protocol is that SIP, MAP are MAP, Diameter.
5. according to each described system in the claim 1 to 4, it is characterized in that it is one of following that gateway identification or controller identifier comprise: device number, domain name.
6. a disaster tolerance processing method is characterized in that, comprising:
Location registration process: first controller receives first register requirement from gateway, wherein, carries the sign of described gateway in described first register requirement; Described first controller sends second register requirement to the gateway location database, wherein, carries the sign of described gateway and the sign of described first controller in described second register requirement;
Corresponding relation set up to be handled: described gateway location database root is according to described second register requirement, sets up the corresponding relation between the sign of the sign of described gateway and described first controller;
Described gateway location database root is determined the controller of the gateway registration of described gateway identification correspondence according to the query requests that carries gateway identification of coming self-controller.
7. method according to claim 6 is characterized in that, in the described location registration process, after described gateway location database was set up described corresponding relation, described method also comprised:
Described first controller is preserved the sign of described gateway in this locality.
8. method according to claim 6 is characterized in that, after described corresponding relation was set up processing, described method also comprised:
Upgrade to handle the position: under predetermined scene, described gateway location database is cancelled the corresponding relation between the sign of the sign of described gateway and described first controller, sets up the corresponding relation between the sign of the sign of described gateway and described second controller.
9. method according to claim 8 is characterized in that, during described position was upgraded and handled, described gateway location database was cancelled after the corresponding relation between the sign of the sign of described gateway and described first controller, and described method also comprises:
Described first controller of described gateway location database notification has been cancelled the corresponding relation between the sign of the sign of described gateway and described first controller;
The sign of the local described gateway of preserving of described first controller deletion.
10. method according to claim 8 is characterized in that, it is one of following that described predetermined scene comprises:
Described first controller detects the interruption that is connected between described gateway and described first controller, sends the primary importance update request to described gateway location database,
Carry the message that the described gateway of indication is not registered in the described primary importance update request on described first controller; Perhaps,
Second controller receives the 3rd register requirement from described gateway, wherein, carries the sign of described gateway in described the 3rd register requirement; Described second controller sends second place update request to described gateway location database, wherein, carries the sign of described gateway and the sign of described second controller in the described second place update request.
11. method according to claim 8 is characterized in that, described gateway location database is set up after the corresponding relation between the sign of the sign of described gateway and described second controller, and described method also comprises:
Described second controller is preserved the sign of described gateway in this locality.
12., it is characterized in that it is one of following that described sign comprises: device number, domain name according to each described method in the claim 6 to 11.
13. a call processing method is characterized in that, comprising:
Controller sets in advance first corresponding relation between user ID and the gateway identification;
Described controller receives the call request from the calling subscriber, wherein, carries CSI called subscriber identification in the described call request;
Described controller is determined the gateway identification corresponding with described CSI called subscriber identification according to described first corresponding relation;
Described controller is judged the gateway identification of whether preserving described CSI called subscriber identification correspondence in its registration gateway identification information;
If preserve the gateway identification of described CSI called subscriber identification correspondence in the described registration gateway identification information, then described controller makes a call by the called subscriber of described gateway to described CSI called subscriber identification correspondence;
If do not preserve the gateway identification of described CSI called subscriber identification correspondence in the described controller, described controller sends query requests to the gateway location database, carries the gateway identification of described CSI called subscriber identification correspondence in the described query requests;
Described gateway location database root is determined the controller of described gateway registration according to described query requests.
14. method according to claim 13 is characterized in that, described method also comprises: described gateway location database sets in advance second corresponding relation between gateway identification and the controller identifier,
Described gateway location database determine described gateway registration controller comprise:
Described gateway location database root is determined the current controller corresponding with described gateway identification according to described second corresponding relation, and the sign of described current controller is sent to described controller.
15. method according to claim 14 is characterized in that, after described gateway location database sent to described controller with the sign of described current controller, described method also comprised:
Described controller sends described CSI called subscriber identification according to the sign of described current controller to described current controller;
Described current controller is by described gateway, makes a call to the called subscriber of described CSI called subscriber identification correspondence.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100054119A CN101466089B (en) | 2009-01-15 | 2009-01-15 | Method and system for processing disaster toleration, call processing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100054119A CN101466089B (en) | 2009-01-15 | 2009-01-15 | Method and system for processing disaster toleration, call processing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101466089A CN101466089A (en) | 2009-06-24 |
| CN101466089B true CN101466089B (en) | 2011-05-11 |
Family
ID=40806392
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009100054119A Expired - Fee Related CN101466089B (en) | 2009-01-15 | 2009-01-15 | Method and system for processing disaster toleration, call processing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101466089B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107105070A (en) * | 2017-04-21 | 2017-08-29 | 上海寰创通信科技股份有限公司 | A kind of dynamically distributes gateway attribution method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1595887A (en) * | 2003-09-08 | 2005-03-16 | 华为技术有限公司 | A next generation network system and resource management method |
| CN1728649A (en) * | 2004-07-28 | 2006-02-01 | 华为技术有限公司 | Method and syste mfor granting NGN service in communication network |
| CN1881960A (en) * | 2005-06-14 | 2006-12-20 | 华为技术有限公司 | Edge or packet gateway control system in next generation network and its method |
-
2009
- 2009-01-15 CN CN2009100054119A patent/CN101466089B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1595887A (en) * | 2003-09-08 | 2005-03-16 | 华为技术有限公司 | A next generation network system and resource management method |
| CN1728649A (en) * | 2004-07-28 | 2006-02-01 | 华为技术有限公司 | Method and syste mfor granting NGN service in communication network |
| CN1881960A (en) * | 2005-06-14 | 2006-12-20 | 华为技术有限公司 | Edge or packet gateway control system in next generation network and its method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101466089A (en) | 2009-06-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9021014B2 (en) | Methods, systems, and computer readable media for providing home subscriber server (HSS) proxy | |
| KR100731321B1 (en) | System and method for handling sessions of specific type in communication networks | |
| CN101142833B (en) | Device for controlling a cs domain subscriber terminal access to an IMS communication network services | |
| CA2593569C (en) | A method and apparatus for handling emergency calls in a packet switched radio access network | |
| US7616953B2 (en) | System and a method of realizing subscriber's foreign roaming service through the router | |
| US8861508B2 (en) | Routing a call setup request to a destination serving node in an IMS network | |
| EP1843524A1 (en) | Locating devices | |
| US10136454B2 (en) | Application server for managing communications towards a set of user entities | |
| CN105873009B (en) | A kind of disaster recovery method, equipment and the system of IP short message intercommunication gateway | |
| CN100456847C (en) | Method, network and equipment for selecting called route | |
| US8467795B2 (en) | Location-based routing of IMS calls through femtocells | |
| CN1929678B (en) | Method and device for updating user terminal switch-in code | |
| CN103369159B (en) | A kind of call processing method and equipment | |
| US8855654B2 (en) | Methods, systems, and computer readable media for tracking and communicating long term evolution (LTE) handset communication capability | |
| CN102404708B (en) | Method and system for choosing domain of called user and HLR (Home Location Register) in system | |
| CN108882220B (en) | IMS terminal call service domain selection method, device, system and storage medium | |
| CN101267577A (en) | Method, system and device for call relay and intelligent service | |
| CN1929627B (en) | Method and system fro realizing public user identification carrying in IMS network | |
| CN101466089B (en) | Method and system for processing disaster toleration, call processing method | |
| KR100447412B1 (en) | The Apparatus and Method for the Mobility Management of IP Multimedia Service Subscriber | |
| US8948099B2 (en) | Geo-local routing in IMS | |
| CN101132603A (en) | Method and system for implementing user position locating in core network | |
| WO2005122617A1 (en) | Apparatuses and method to provide a network-requested pdp context activation procedure | |
| CN102739499B (en) | A kind of method for routing of signaling message, Apparatus and system | |
| CN109327870B (en) | Method, device and equipment for communicating with ATCF (advanced telecom computing framework) and computer storage medium |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110511 Termination date: 20180115 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |