CN102332991B - Backup method capable of keeping consistent state in soft switch and gateway device - Google Patents
Backup method capable of keeping consistent state in soft switch and gateway device Download PDFInfo
- Publication number
- CN102332991B CN102332991B CN 201110263757 CN201110263757A CN102332991B CN 102332991 B CN102332991 B CN 102332991B CN 201110263757 CN201110263757 CN 201110263757 CN 201110263757 A CN201110263757 A CN 201110263757A CN 102332991 B CN102332991 B CN 102332991B
- Authority
- CN
- China
- Prior art keywords
- softswitch
- limit
- terminal
- state
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a backup method capable of keeping consistent state in a soft switch and a gateway device, belonging to the data backup methods in the communication field. In the method, a primary side soft switch sends unsteady state terminal redundant data or steady state calling redundant data to a backup side soft switch according to the transition condition of the terminal state, and the backup side soft switch processes the data correspondingly and stores the state information of the terminal through a terminal state mapping table so as to ensure that the terminal state stored in the soft switch is consistent with the actual state of the gateway terminal device, and consequently ensure the communication to run smoothly; the method quickly and effectively solves the problem of inconsistency of the terminal state in the soft switch and the gateway caused by the unsteady calling in a primary-backup switching process, which cannot be solved by the conventional 1+1 hot backup method, so that the consistency of the terminal state in the soft switch and the terminal state of the gateway device is ensured, particularly, in the primary-backup switching process, the terminal can resume services as soon as possible.
Description
Technical field
The present invention relates to the method for data backup in a kind of communications field, particularly a kind of SoftSwitch backup method consistent with the gateway device SOT state of termination that keep.
Background technology
Next generation network take soft switch as core (NGN) is the inexorable trend of future communications development.Compare with legacy circuit-switched, flexible exchanging network adopts the technology that is separated with carrying of controlling of calling out, the disposal ability of the network equipment all improves a lot, the capacity of SoftSwitch and various gateways can be done very greatly, these are all the advantages of soft switch, but also allow it face more security threat simultaneously.SoftSwitch in case equipment goes wrong and fault, will cause large-scale communication failure as calling out in next generation network and the core of controlling, and cause very large impact for whole network.For realizing the high availability of SoftSwitch, adopt the framework of 1+1 hot backup more.1+1 hot backup is backed up in synchronization, and when main edge equipment went wrong, corresponding standby edge equipment can be taken over faulty equipment and resume work within the very short time.For reduce SoftSwitch active and standby between the data volume of redundancy, in design, only adopt called out the mode of carrying out redundancy to stable state more.
1+1 hot backup has been abandoned the redundancy to the unstable state call information, realized efficient backup, but also there is simultaneously following drawback: when calling is in the unstable state SoftSwitch and switches, due to unstable state call information redundancy not, cause SoftSwitch to think that this terminal is in idle condition, and gateway thinks that terminal is in seizure condition, thereby forms SoftSwitch and the inconsistent phenomenon of gateway preservation SOT state of termination.After this phenomenon produced, for SIP with H.323 wait terminal, when its on-hook, gateway can be placed in idle condition with terminal, was consistent with state in SoftSwitch.And for terminals such as MGCP and MEGACO, when its on-hook, because SoftSwitch fails terminal is deleted from the connection of having set up, terminal still is in seizure condition, can not proceed to call out, solution be SoftSwitch to gateway transmitting terminal initialization information (command terminal deletes from built vertical connection or command terminal reenters service), force terminal to enter idle condition.In the redundancy of SoftSwitch, how fast detecting SOT state of termination inconsistent and correcting, become a problem.
Summary of the invention
The technical problem to be solved in the present invention is to provide in the soft switch redundancy scheme, find fast with correct SoftSwitch and gateway in the inconsistent a kind of SoftSwitch backup method consistent with the gateway device SOT state of termination that keep of SOT state of termination.
For solving the problems of the technologies described above, the technical solution used in the present invention is: a kind of SoftSwitch backup method consistent with the gateway device SOT state of termination that keep comprises the steps:
A, will be for limit SoftSwitch and main limit SoftSwitch exact connect ion, start described standby limit SoftSwitch, and set up the SOT state of termination mapping table in the SoftSwitch of standby limit;
The data handling procedure of B, main limit SoftSwitch:
Main limit SoftSwitch receives the signaling message of self terminal, judges the terminal operate condition according to signaling message:
A, terminal transit to unstable state by idle stable state: described main limit SoftSwitch sends unstable state terminal redundant data to standby limit SoftSwitch;
B, terminal transit to idle stable state by unstable state: described main limit SoftSwitch sends unstable state terminal redundant data to standby limit SoftSwitch;
C, terminal transit to busy stable state by unstable state: described main limit SoftSwitch sends stable state call redundancy data to standby limit SoftSwitch;
D, terminal transit to idle stable state by busy stable state: described main limit SoftSwitch sends stable state call redundancy data to standby limit SoftSwitch;
Described unstable state terminal data comprises call reference, Termination ID sign and SOT state of termination transition sign, and described stable state call data comprise call reference, Termination ID sign;
Main limit SoftSwitch continues to carry out the above-mentioned B step, and described standby limit SoftSwitch is carried out the following C step;
The data handling procedure of C, described standby limit SoftSwitch:
1) described standby limit SoftSwitch is processed the data that receive from main limit SoftSwitch:
The data that a, described standby limit SoftSwitch are received are the unstable state terminal data, processing method by: judge according to the transition between states in the data that receive sign whether these data are to transit to unstable state by terminal from idle condition to be produced, if these data are to transit to unstable state by terminal by idle condition to be produced, the call reference of described standby limit SoftSwitch in these data identifies relevant mapping relations with call reference and Termination ID as the SOT state of termination mapping table foundation of key value in the SoftSwitch of described standby limit, carries out the following the 2nd) go on foot; Otherwise standby limit SoftSwitch carries out data according to following b described processing method of step to be processed;
The data that b, described standby limit SoftSwitch are received are the stable state call data, preserve this data, processing method is: described standby limit SoftSwitch compares the call reference in the call reference in the data that receive and described SOT state of termination mapping table, when having this call reference in described SOT state of termination mapping table, corresponding mapping relations of call reference are therewith deleted from described SOT state of termination mapping table, carry out the following the 2nd) step; Otherwise standby limit SoftSwitch directly carries out the following the 2nd) step;
2) judge whether described standby limit SoftSwitch is switched to main limit SoftSwitch:
When described standby limit SoftSwitch is switched to main limit SoftSwitch, the described SOT state of termination mapping table of new main limit SoftSwitch traversal after switching, detect the Termination ID sign in described SOT state of termination mapping table, make terminal initialization according to legal Termination ID identity validation terminal equipment place gateway and to described gateway transmission message, traversal is deleted described SOT state of termination mapping table after finishing; When described standby limit SoftSwitch was not switched to main limit SoftSwitch, standby limit SoftSwitch continued to carry out the above-mentioned C step.
adopt the technological progress that obtains after technique scheme to be: traditional 1+1 hot backup, only the stable state call information data is carried out redundancy backup, can't solve unstable state and call out the inconsistent problem of SOT state of termination in the SoftSwitch cause and gateway in active and standby handoff procedure, this scheme adopts the mode of redundancy unstable state end message between main limit SoftSwitch and standby limit SoftSwitch, guaranteed the consistency of SOT state of termination and gateway device SOT state of termination in the SoftSwitch, especially when standby limit SoftSwitch becomes main limit SoftSwitch, traversal queries to end message, by sending the initialization signaling to the unstable state terminal, fast and effeciently solved unstable state and called out the inconsistent problem of SOT state of termination that runs into when SoftSwitch switches, make terminal Resume service as early as possible.
Description of drawings
Fig. 1 is the flow chart of this method;
Fig. 2 is standby limit SoftSwitch to the process chart of the data that receive from main limit SoftSwitch;
Fig. 3 switches to main limit SoftSwitch flow chart of data processing figure afterwards for standby limit SoftSwitch;
Fig. 4 is the schematic network structure of embodiment.
Embodiment
The below arrives flow chart shown in Figure 3 according to Fig. 1, and in conjunction with the present invention is described in detail by embodiment shown in Figure 4.
Main limit SoftSwitch and standby limit SoftSwitch access IP network, and adopt the 1+1 hot backup redundancy scheme.Terminal 1 and terminal 2 are respectively by MEGACO comprehensive access gate 1 and SIP comprehensive access gate 2 access IP network.Terminal herein is to satisfy the terminal equipment of MGCP agreement or megaco protocol, is generally phone equipment, the terminal equipment that perhaps carries for Tandem Gateway.Tandem Gateway can be MGCP IAD or MEGACO Tandem Gateway, can also be the gateway of other types.The model of main limit SoftSwitch and standby limit SoftSwitch is AcroSwitch 6000.
After MEGACO comprehensive access gate 1 and SIP comprehensive access gate 2 succeeded in registration to main limit SoftSwitch, terminal 1 just can intercom mutually with terminal 2.
The present invention is described in detail as example take two kinds of different calling procedures between terminal 1 and terminal 2 for the below.
A kind of SoftSwitch backup method consistent with the gateway device SOT state of termination that keep comprises the steps:
S1, will be for limit SoftSwitch and main limit SoftSwitch exact connect ion, start described standby limit SoftSwitch, and set up the SOT state of termination mapping table in the SoftSwitch of standby limit;
Call out 1
Terminal 1 off-hook dialing, calling terminal 2, terminal 2 does not respond, and calls out not success, does not enter talking state, then, terminal 1 on-hook, end of calling.In this process, the state variation of terminal 1 is: idle stable state-〉 unstable state-〉 idle stable state, and main limit SoftSwitch with the standby concrete processing procedure of limit SoftSwitch is:
The data handling procedure of S2, main limit SoftSwitch:
Terminal 1 off-hook dialing, send signaling message to main limit SoftSwitch simultaneously, main limit SoftSwitch receives the signaling message of self terminal 1, learn that according to this signaling message terminal 1 enters unstable state by idle stable state, therefore, main limit SoftSwitch sends unstable state terminal redundant data to standby limit SoftSwitch; Described unstable state terminal redundant data comprises the ID sign of the call reference relevant to terminal 1, terminal 1 and the SOT state of termination transition sign that shows terminal 1 state variation;
Then, main limit SoftSwitch continues to receive the data of self terminal, and sends corresponding data to standby limit SoftSwitch, and described standby limit SoftSwitch is carried out the following S3 step;
The data handling procedure of S3, standby limit SoftSwitch:
1) described standby limit SoftSwitch is processed the data that receive from main limit SoftSwitch:
After described standby limit SoftSwitch receives that above-mentioned S2 comes the unstable state terminal redundant data of autonomous limit SoftSwitch in the step, judging terminal 1 according to the sign of the SOT state of termination transition in data is unstable state from idle stable state transition, therefore, standby limit SoftSwitch identifies relevant mapping relations in the foundation of SOT state of termination mapping table with call reference and Termination ID as key value with the call reference in this unstable state terminal redundant data, then carries out the following the 2nd) step;
2) judge whether described standby limit SoftSwitch is switched to main limit SoftSwitch:
when described standby limit SoftSwitch is switched to main limit SoftSwitch, new main limit SoftSwitch after switching travels through its inner SOT state of termination mapping table, detect one by one the Termination ID sign in described SOT state of termination mapping table, main limit SoftSwitch is connected with a lot of Tandem Gateways, also can receive the signaling message from different terminals, therefore can there be the information of a lot of terminals in the SOT state of termination mapping table, in ergodic process, at first judge whether the Termination ID sign is legal, for legal Termination ID sign, send message according to this identity validation terminal equipment place this described gateway of gateway and make terminal initialization, after traversal finishes, deletion SOT state of termination mapping table, when described standby limit SoftSwitch was not switched to main limit SoftSwitch, standby limit SoftSwitch continued to carry out the above-mentioned S3 step, namely continued receive the data of autonomous limit SoftSwitch and process, because terminal 1 back also has action, therefore main limit SoftSwitch continues to carry out following step,
The not calling of response terminal 1 of S4, terminal 2, terminal 1 on-hook end call, terminal 1 sends signaling message to main limit SoftSwitch, and like this, main limit SoftSwitch continues to carry out according to above-mentioned S2 step content, the data handling procedure that namely enters main limit SoftSwitch:
Main limit SoftSwitch receives the signaling message of self terminal 1, learns that according to signaling message terminal 1 enters idle stable state by unstable state, and main limit SoftSwitch sends unstable state terminal redundant data to standby limit SoftSwitch; The unstable state terminal redundant data of this moment is identical with the Termination ID sign content with call reference in unstable state terminal redundant data during above-mentioned S2 goes on foot, but SOT state of termination transition sign content is different; Then, main limit SoftSwitch continues to receive the data of self terminal, and sends data to standby limit SoftSwitch, and standby limit SoftSwitch is carried out following step;
The data handling procedure of S5, standby limit SoftSwitch:
1) described standby limit SoftSwitch is processed the data that receive from main limit SoftSwitch:
after standby limit SoftSwitch receives that above-mentioned S4 comes the above-mentioned unstable state terminal redundant data of autonomous limit SoftSwitch in the step, judging terminal 1 according to the sign of the SOT state of termination transition in data is idle stable state from the unstable state transition, therefore, standby limit SoftSwitch is compared the call reference in this unstable state terminal redundant data with the call reference in described SOT state of termination mapping table, because the above-mentioned S3 step the 1st) deposit this call reference in the SOT state of termination mapping table as key value in the step, so can find there has been this call reference in the SOT state of termination mapping table relatively, accordingly, standby limit SoftSwitch is with the corresponding mapping relations deletion of call reference therewith in the SOT state of termination mapping table, then carry out the 2nd in the step of above-mentioned S3) step, if there is no the identical call reference of call reference of data therewith in the SOT state of termination mapping table, so standby limit SoftSwitch is not done any operation, directly carries out the 2nd in the step of above-mentioned S3) step.
So far, calling out 1 finishes.If the firm off-hook of terminal 1, main limit SoftSwitch just breaks down and is replaced by standby limit SoftSwitch, in SOT state of termination mapping table in standby limit SoftSwitch this moment, the mapping of relevant terminal 1 shows that terminal also is in unstable state 1 this moment, so just can guarantee that SoftSwitch is inner consistent with the information of SOT state of termination in gateway device so.
Call out 2
Terminal 1 off-hook dialing, calling terminal 2, the calling of terminal 2 response terminals 1 enters talking state, after end of conversation, terminal 1 on-hook.In this process, the state variation of terminal 1 is: idle stable state-〉 unstable state-〉 stable state-〉 idle stable state, because of the transition between states for the first time of terminal 1 to call out similar in 1, therefore, the forward part of calling 2 processing procedures is identical with calling 1, and other processing procedure should be:
The calling of S4, terminal 2 response terminals 1, begin conversation between terminal 1 and terminal 2, terminal 1 sends signaling message to main limit SoftSwitch, like this, main limit SoftSwitch continues to carry out according to above-mentioned S2 step content, the data handling procedure that namely enters main limit SoftSwitch:
Main limit SoftSwitch receives the signaling message of self terminal 1, learns that according to signaling message terminal 1 enters busy stable state by unstable state, and so, main limit SoftSwitch sends stable state call redundancy data to standby limit SoftSwitch; Described stable state call data comprise the call reference relevant to terminal 1 and Termination ID sign, also comprise other call informations, as the hello protocol type, whether be that hair clip connects and calls out the information such as time started, call reference herein is identical with the Termination ID sign content with the call reference of calling out the unstable state terminal data in 1 with the Termination ID sign, because both relevant to terminal 1; Then, main limit SoftSwitch continues to receive the data of self terminal, and sends data to standby limit SoftSwitch, and standby limit SoftSwitch is carried out following step;
The data handling procedure of S5, standby limit SoftSwitch:
1) described standby limit SoftSwitch is processed the data that receive from main limit SoftSwitch:
after described standby limit SoftSwitch receives that above-mentioned S4 comes the stable state call redundancy data of autonomous limit SoftSwitch in the step, standby limit SoftSwitch is preserved the data that receive, and existing call reference in the call reference in these data and SOT state of termination mapping table is compared, because above-mentioned S2 deposits this call reference in the SOT state of termination mapping table in the step, so can find there has been this call reference in the SOT state of termination mapping table relatively, accordingly, with in the SOT state of termination mapping table therewith call reference to the deletion of the mapping relations of correspondence, standby limit SoftSwitch is carried out the 2nd in the step of above-mentioned S3) step, because terminal 1 back also has action, therefore main limit SoftSwitch continues to carry out following step,
S6, end of conversation, terminal 1 on-hook, and send signaling message to main limit SoftSwitch, main limit SoftSwitch learns that according to this signaling message terminal 1 enters idle stable state by busy stable state, so, main limit SoftSwitch sends stable state call redundancy data to standby limit SoftSwitch, and the call reference of stable state call redundancy data herein and Termination ID sign content are identical with the Termination ID sign content with the call reference of stable state call redundancy data during above-mentioned S4 goes on foot; Then, main limit SoftSwitch continues to receive the data of self terminal, and sends data to standby limit SoftSwitch, and standby limit SoftSwitch is carried out the following S7 step;
The data handling procedure of S7, standby limit SoftSwitch:
1) described standby limit SoftSwitch is processed the data that receive from main limit SoftSwitch:
after standby limit SoftSwitch receives that above-mentioned S6 comes the stable state call redundancy data of autonomous limit SoftSwitch in the step, standby limit SoftSwitch is preserved the data that receive, and existing call reference in the call reference in these data and SOT state of termination mapping table is compared, because above-mentioned S5 is the corresponding mapping deletion of call reference therewith in the step, therefore can't find identical call reference, so, standby limit SoftSwitch is not done any operation to the SOT state of termination mapping table, directly carry out the 2nd in the step of above-mentioned S3) step, namely whether the standby limit of judgement SoftSwitch is switched to main limit SoftSwitch.
So far, terminal 1 finishes with the whole communication process of terminal 2, whole process, the consistent signaling message of accepting self terminal of main limit SoftSwitch, and sending corresponding data according to this signaling message to standby limit SoftSwitch, standby limit SoftSwitch is processing the data of autonomous limit SoftSwitch always.Information about terminal 1 state in the SoftSwitch of standby limit is constantly corresponding with the state of terminal 1, only after terminal 1 off-hook, that is terminal is in and just can has the state of terminal 1 in the SOT state of termination mapping table astable the time, in addition, no matter which kind of state is terminal 1 be in, and in the SOT state of termination mapping table, the map information of relevant terminal 1 is all empty.Like this, when standby limit SoftSwitch was switched to main limit, in the SoftSwitch of standby limit, the information of the relevant SOT state of termination of storage was corresponding one by one with the state of terminal itself.
In the practical communication process, various situations are very complicated.When standby limit SoftSwitch does not receive unstable state terminal redundant data that main limit sends over or stable state call redundancy data, will consider whether main limit SoftSwitch is out of joint, at this moment, standby limit switch will be crossed the treatment step to the data of coming autonomous limit SoftSwitch, judge directly whether master/slave device switching has occured.Be sometimes that the standby limit of SoftSwitch notice, main limit SoftSwitch switches, like this, also need to cross standby limit switch to the treatment step of the data of next autonomous limit SoftSwitch, directly carry out according to the processing method after switching.Also have a lot of similarly situations, do not enumerate here, process in actual applications getting final product according to the core content of this method.
MEGACO comprehensive access gate 1 and SIP comprehensive access gate 2 in above-described embodiment, the present invention can also solve SoftSwitch and the consistent problem of gateway device SOT state of termination in terminal call process between two MEGACO comprehensive access gates or two MGCP comprehensive access gates or MEGACO comprehensive access gate and MGCP comprehensive access gate.
The processing core of this method is:
the backward main limit of terminal generation transition between states SoftSwitch sends signaling message, main limit SoftSwitch is judged the transition between states situation of terminal according to the signaling message that receives from terminal, and send unstable state terminal redundant data or stable state call redundancy data according to this situation to standby limit SoftSwitch, standby limit SoftSwitch contains the SOT state of termination mapping table and preserves the data that can represent SOT state of termination, when standby limit SoftSwitch receives to such an extent that data are that unstable state terminal redundant data and this data are when transitting to the unstable state generation by terminal from idle condition, standby limit SoftSwitch just builds on this data relevant mapping as key value at the SOT state of termination mapping table with the call reference of these data, in addition, standby limit SoftSwitch is all that call reference in data is compared with the call reference in the SOT state of termination mapping table to the processing of other data, in case identical content is arranged, just with corresponding mapping deletion in the SOT state of termination mapping table.When active and standby switchings occurs when, standby limit SoftSwitch according in the SOT state of termination mapping table with the corresponding content-control SOT state of termination of terminal, with assurance terminal Resume service fast.
In sum, these are only preferred application example of the present invention, is not for limiting protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of making, be equal to replacement etc., within all should being included in protection scope of the present invention.
Claims (3)
1. one kind keeps the SoftSwitch backup method consistent with the gateway device SOT state of termination, it is characterized in that comprising the steps:
A, will be for limit SoftSwitch and main limit SoftSwitch exact connect ion, start described standby limit SoftSwitch, and set up the SOT state of termination mapping table in the SoftSwitch of standby limit;
The data handling procedure of B, main limit SoftSwitch:
Main limit SoftSwitch receives the signaling message of self terminal, judges the terminal operate condition according to signaling message:
A, terminal transit to unstable state by idle stable state: described main limit SoftSwitch sends the unstable state terminal data to standby limit SoftSwitch;
B, terminal transit to idle stable state by unstable state: described main limit SoftSwitch sends the unstable state terminal data to standby limit SoftSwitch;
C, terminal transit to busy stable state by unstable state: described main limit SoftSwitch sends the stable state call data to standby limit SoftSwitch;
D, terminal transit to idle stable state by busy stable state: described main limit SoftSwitch sends the stable state call data to standby limit SoftSwitch;
Described unstable state terminal data comprises call reference, Termination ID sign and SOT state of termination transition sign, and described stable state call data comprise call reference, Termination ID sign;
Main limit SoftSwitch continues to carry out the above-mentioned B step, and described standby limit SoftSwitch is carried out the following C step;
The data handling procedure of C, described standby limit SoftSwitch:
1) described standby limit SoftSwitch is processed the data that receive from main limit SoftSwitch:
The data that a, described standby limit SoftSwitch are received are the unstable state terminal data, processing method by: judge according to the transition between states in the data that receive sign whether these data are to transit to unstable state by terminal from idle condition to be produced, if these data are to transit to unstable state by terminal by idle condition to be produced, the call reference of described standby limit SoftSwitch in these data identifies relevant mapping relations with call reference and Termination ID as the SOT state of termination mapping table foundation of key value in the SoftSwitch of described standby limit, carries out the following the 2nd) go on foot; Otherwise standby limit SoftSwitch carries out data according to following b described processing method of step to be processed;
The data that b, described standby limit SoftSwitch are received are the stable state call data, preserve this data, processing method is: described standby limit SoftSwitch compares the call reference in the call reference in the data that receive and described SOT state of termination mapping table, when having this call reference in described SOT state of termination mapping table, corresponding mapping relations of call reference are therewith deleted from described SOT state of termination mapping table, carry out the following the 2nd) step; Otherwise standby limit SoftSwitch directly carries out the following the 2nd) step;
2) judge whether described standby limit SoftSwitch is switched to main limit SoftSwitch:
When described standby limit SoftSwitch is switched to main limit SoftSwitch, the described SOT state of termination mapping table of new main limit SoftSwitch traversal after switching, detect the Termination ID sign in described SOT state of termination mapping table, make terminal initialization according to legal Termination ID identity validation terminal equipment place gateway and to described gateway transmission message, traversal is deleted described SOT state of termination mapping table after finishing; When described standby limit SoftSwitch was not switched to main limit SoftSwitch, standby limit SoftSwitch continued to carry out the above-mentioned C step.
2. a kind of SoftSwitch backup method consistent with the gateway device SOT state of termination that keep according to claim 1, it is characterized in that described terminal is to satisfy the terminal equipment of MGCP agreement or megaco protocol, described terminal is by MGCP or MEGACO Tandem Gateway access network.
3. a kind of SoftSwitch backup method consistent with the gateway device SOT state of termination that keep according to claim 1, is characterized in that the model of described main limit SoftSwitch or standby limit SoftSwitch is AcroSwitch 6000.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110263757 CN102332991B (en) | 2011-09-07 | 2011-09-07 | Backup method capable of keeping consistent state in soft switch and gateway device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110263757 CN102332991B (en) | 2011-09-07 | 2011-09-07 | Backup method capable of keeping consistent state in soft switch and gateway device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102332991A CN102332991A (en) | 2012-01-25 |
| CN102332991B true CN102332991B (en) | 2013-06-26 |
Family
ID=45484602
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110263757 Active CN102332991B (en) | 2011-09-07 | 2011-09-07 | Backup method capable of keeping consistent state in soft switch and gateway device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102332991B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107395625B (en) * | 2017-08-21 | 2020-04-10 | 河北远东通信系统工程有限公司 | Method for realizing steady-state call redundancy of soft switching equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1677972A (en) * | 2004-04-02 | 2005-10-05 | 华为技术有限公司 | Method and system for duplicating medium flow in next-generation network |
| CN1976370A (en) * | 2005-11-28 | 2007-06-06 | 中兴通讯股份有限公司 | Method for keeping call data uniformity after master-slave gateway replacing |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20050038867A (en) * | 2003-10-23 | 2005-04-29 | 주식회사 케이티 | System and method for providing remote multilateral cooperative documentation service |
| US7768997B2 (en) * | 2004-08-20 | 2010-08-03 | At&T Intellectual Property I, L.P. | Systems and methods for automatic public switched telephone network backup of voice over internet protocol services |
-
2011
- 2011-09-07 CN CN 201110263757 patent/CN102332991B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1677972A (en) * | 2004-04-02 | 2005-10-05 | 华为技术有限公司 | Method and system for duplicating medium flow in next-generation network |
| CN1976370A (en) * | 2005-11-28 | 2007-06-06 | 中兴通讯股份有限公司 | Method for keeping call data uniformity after master-slave gateway replacing |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102332991A (en) | 2012-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8571546B2 (en) | Method for implementing dual-homing | |
| CN105760260B (en) | A kind of standby system and backup method | |
| CN101262528B (en) | A multi-gateway backup method for voice access of network call | |
| US7483369B2 (en) | Method and apparatus for migrating to an alternate call controller | |
| JP4834759B2 (en) | Media server, session recovery method, and computer program | |
| CN101188859B (en) | A method for replacing non-stable status call | |
| CN102332991B (en) | Backup method capable of keeping consistent state in soft switch and gateway device | |
| US20080144489A1 (en) | Network device and communication recovery method thereof | |
| CN101355804B (en) | System and method for seamless disaster-containing switching next generation network medium gateway | |
| CN103051484A (en) | Method and system for processing session service and session border controller | |
| CN1917506B (en) | Media gateway / media gateway controller, and related method for registering, controlling and processing | |
| CN100454955C (en) | Stand-by of IP telephone route and recovery method | |
| CN103138998B (en) | A kind of detection of proxy-state, device and system | |
| CN110996358B (en) | Call terminal switching method and device, electronic equipment and storage medium | |
| JP2018093321A (en) | Speech system | |
| JP5342578B2 (en) | Call control system and information redundancy method used for call control | |
| CN101808136B (en) | Method, device and system for realizing synchronization of user dynamic resources | |
| CN100579106C (en) | Method for realizing the channel associated signaling status compatibility under the NGN architecture | |
| CN110784943A (en) | Processing method and device for VoWiFi voice service disconnection and reconnection | |
| CN100428825C (en) | Method for recovering service data when service rearrangement / rollback in system of dual attributes | |
| CN105515655B (en) | A kind of voice main and standby rearranging method based on Session Initiation Protocol | |
| CN102595360B (en) | Call processing method and system | |
| CN101909057B (en) | Signaling system based on internet | |
| CN203086486U (en) | Communication system based on main/standby SIP servers | |
| JP2012178707A (en) | Call control system and method of making information for use in call control redundant |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent for invention or patent application | ||
| CB03 | Change of inventor or designer information |
Inventor after: Wang Yunlei Inventor after: Zhang Jianzhong Inventor after: Sun Kun Inventor after: Xu Larong Inventor after: Han Zhiyong Inventor before: Wang Yunlei Inventor before: Zhang Jianzhong Inventor before: Sun Kun Inventor before: Xu Larong Inventor before: Han Zhiyong |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: HEBEI FAR EAST COMMUNICATION SYSTEM ENGINEERING CO Free format text: FORMER OWNER: HEBEI FAR EAST HARRIS COMMUNICATIONS CO., LTD. Effective date: 20140327 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20140327 Address after: 050200 Hebei city of Shijiazhuang province Luquan Economic Development Zone Changsheng Street No. 21 building E3 Patentee after: Hebei FarEast Communication System Engineering Co., Ltd. Address before: 050200 Hebei city of Shijiazhuang province Luquan Economic Development Zone Changsheng Street No. 21 Patentee before: Hebei Far East Harris Communications Co., Ltd. |