CN100589488C - Network-grade sparing method and apparatus for conversation primary protocl application system - Google Patents
Network-grade sparing method and apparatus for conversation primary protocl application system Download PDFInfo
- Publication number
- CN100589488C CN100589488C CN200610032916.0A CN200610032916A CN100589488C CN 100589488 C CN100589488 C CN 100589488C CN 200610032916 A CN200610032916 A CN 200610032916A CN 100589488 C CN100589488 C CN 100589488C
- Authority
- CN
- China
- Prior art keywords
- server
- sip
- request message
- proxy server
- user agent
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses method for backing up SIP application system, server of using the method, and SIP application system. The SIP application system includes client ends of network connected useragent, server of user agent, and stand by server of user agent. The method includes steps: based on first request message sent from client end of user agent to server of user agent to generate secondrequest message, the said first and second request messages include state data; sending the second request message to stand by server of user agent; after receiving the second request message, the stand by server of user agent creates status data. Using message in SIP to accomplish backing up related status data, the method does not need relevant network equipment to support private protocol dedicated design for backing up purpose. Features are: high generality and expansibility.
Description
Technical field
The present invention relates to the network level backup method of a kind of session initiation protocol (SIP) application system and adopt the equipment and the SIP application system of this method.
Background technology
In order to reach 99.999% telecommunications service reliability requirement, provide each network device internal of telecommunications service that corresponding reliability mechanisms is arranged usually.For example, the network equipment is made up of the polylith disposable plates usually, is configured to the active and standby relation of using between disposable plates, and business is provided with working plate by main under the normal condition.When the main working plate fault, corresponding standby working plate used is upgraded to the main work of taking over faulty board of using, guaranteed the professional continuity that provides.
The reliability mechanisms in equipment, operator also is concerned about the reliability of network.Certain network equipment that provides service for the user is because of uncontrollable factor, as earthquake, flood etc. and thoroughly fault.It is minimum that operator wishes that the influence with this network equipment failure is reduced to, and continues as the user respective service is provided.Network reliability has a lot of specific implementations, and the realization of network reliability usually need be in two active and standby LA Management Room backups business datum more or less.
The defined Session Initiation Protocol of IETF RFC3261, as a kind of application layer protocol of the session of creating two sides or in many ways, revise, terminate, the current extensive support that has obtained industry has been widely used in the foundation of all kinds of Multimedia session.Such as, the IMS network of 3GPP is based on Session Initiation Protocol.Session Initiation Protocol also can be used for all kinds of session control based on the Internet (Internet).Application system based on Session Initiation Protocol will be deployed in the network of telecom operators more and more, for the user provides high-quality telecommunications service.
The present invention pays close attention in the SIP application system, in the method for active and standby LA Management Room backup traffic data.
Fig. 1 is a kind of structural representation in active and standby LA Management Room backup traffic data of prior art.As shown in Figure 1, server P1 provides service for user Bob.Main during with server P1 fault for guaranteeing, Bob still can access service (answering the calling of Alice), the terminal configuration of Bob the IP address of two sip server P1 and P2.The Bob terminal is registered in two servers respectively simultaneously when initiating registration (REGISTER).
Find the P1 fault when the terminal of Alice, standby server P2 is mail in the INVITE request.Registered at P2 because of Bob, so P2 can serve for Bob, will be transmitted to the terminal of Bob from call request (4) INVITE of Alice.
In this scheme, reach synchronous sip server P1 and P2 purpose about the log-on data of Bob, be by two server address of Bob terminal configuration, initiate registration, when nullifying, finish with two server interactions respectively simultaneously.
User's log-on data keeps synchronously in the primary, spare server in order to make, and user terminal will send register requirement and receive respective response to active and standby server respectively.Be equivalent to user terminal and register on active and standby server respectively, data sync is finished by terminal.In this scheme, for the data between synchronous network device have increased requirement to user terminal, and actual user terminal is not generally supported such specific function, so this scheme is not general.
Fig. 2 is the structural representation in active and standby LA Management Room backup traffic data of another kind of prior art.
Irrelevant for the data sync scheme and the terminal that make LA Management Room, can between active and standby server, carry out Data Dynamic and back up in realtime.As shown in Figure 2, Bob only need be registered on the server P1, its registration related data server P2 that backed up in realtime.When the P1 fault, P2 also can provide service for Bob.D1 and D2 are business database among the figure, sql server for example, the real time data backup interface that interface " (3) database replication " provides for business database.
The replicanism that provides by business database carries out data backup, obviously requires the realization of the network equipment to adopt existing commercial data base technology.But the realization of the network equipment, based on each side factors such as cost, efficient, the overwhelming majority can not adopt commercial data base.
If commercial data base is not adopted in the realization of the network equipment, also there is the situation of transmitting Backup Data by proprietary protocol at the LA Management Room of need synchrodata at present.But the extensibility of proprietary protocol is not strong, often with specifically wants backed up data to be associated.When having increased new backup requirements, the corresponding modify proprietary protocol, not a kind of method in common.
Summary of the invention
The objective of the invention is provides the backup method that overcomes above difficulty, the equipment that adopts this method and system at the SIP application system.
According to first aspect, the invention provides a kind of network level backup method of SIP application system, described SIP application system comprises User Agent Client, subscriber proxy server and the stand by server of user agent that links to each other by network, described method comprises step: described subscriber proxy server is based on first request message that sends to subscriber proxy server from user's agent client, produce second request message, wherein said first and second request messages comprise status data; Described subscriber proxy server sends to stand by server of user agent with second request message; After described stand by server of user agent receives second request message, the creation state data.
In first aspect, preferably, described generation step and forwarding step are finished by described subscriber proxy server.
Preferably, described SIP application system comprises sip proxy server (Proxy), and described generation step and forwarding step are finished after the success response message of receiving from subscriber proxy server at first request message by this sip proxy server.
Preferably, the step of described generation second request message comprises, produces second request message by the address of adding stand by server of user agent in the route of first request message (route) header field.
Preferably, described status data comprises subscription status data or login state data.
Preferably, described method comprises that one is confirmed that response message returns to the sender of second request message by stand by server of user agent, and is not continued the step of route by this sender.
Preferably, the overtime numerical value of described second message is the overtime numerical value that subscriber proxy server is determined.
According to fourth aspect, a kind of sip proxy server in the SIP application system is provided, described SIP application system comprises User Agent Client, subscriber proxy server and the stand by server of user agent that links to each other with sip proxy server by network, described sip proxy server comprises: based on first request message that sends to subscriber proxy server from user's agent client, produce the device of second request message, wherein said first and second request messages comprise status data; Second request message is sent to the device of stand by server of user agent, thereby after stand by server of user agent receives second request message, the creation state data.
In fourth aspect, preferably, described sip proxy server comprises that reception is from the affirmation response message of stand by server of user agent and it is not continued the device of route.
Preferably, described sip proxy server comprises and will send to the device of subscriber proxy server from first request message of user's agent client.
According to the 6th aspect, a kind of SIP application system is provided, comprise User Agent Client, subscriber proxy server, as the described sip proxy server of fourth aspect with as the described stand by server of user agent of the third aspect.
It may be noted that request message is relevant with status data is meant according to Session Initiation Protocol, and associated server can generate described status data from this request.
The present invention utilizes Session Initiation Protocol message to finish the backup of correlation behavior data, the proprietary protocol that the network equipment support that does not need to be correlated with designs for backup purpose specially, and versatility and autgmentability are strong.
Description of drawings
To with reference to accompanying drawing embodiment of the present invention be described in detail with the form of giving an example below, wherein:
Fig. 1 is a kind of networking schematic diagram in active and standby LA Management Room backup traffic data of prior art;
Fig. 2 is the networking schematic diagram in active and standby LA Management Room backup traffic data of another kind of prior art;
Fig. 3 is the schematic diagram that the user subscribes to the flow process of its login state incident;
Fig. 4 is the distribution schematic diagram of user's subscription status data when subscribing to success;
Fig. 5 is the schematic flow sheet according to the LA Management Room backup subscription status data of one embodiment of the invention;
Fig. 6 is the schematic diagram of the inside realization mechanism of sip server and backup entity;
Fig. 7 a-d is the concrete instance of message 3-message 6 among Fig. 5;
Fig. 8 is the schematic diagram of the flow process of LA Management Room backup login state data;
Fig. 9 is the structural representation of SIP application system according to another embodiment of the invention;
Figure 10 is SIP application system shown in Figure 9 is carried out the status data backup by sip message a schematic flow sheet.
Embodiment
The data backup of LA Management Room, (call state changes very frequent generally not need to back up the call state related data, data volume is big, only between the active and standby plate of device interior, back up in realtime), but little at the user in data volumes such as the login state data of the network equipment, subscription status data, change not frequent significant data and back up in realtime.
The SIP registration process can be referring to RFC3261 the 10th chapter " Registrations ".The basic process of sip subscribe can be referring to RFC3265.Based on the framework of RFC3265, by the concrete event subscription mechanism of other RFC definition.For example RFC3680 (A SIP Event Package forRegistrations) has defined the subscription and the informing mechanism of login state incident.By this mechanism, the user can subscribe to its login state at the network equipment.When this user registration state changes, can obtain NOTIFY notice timely.For example, the user is registered in server simultaneously by a plurality of different terminals, and the user enters the laboratory again with the laboratory endpoint registration.The login state event notice that the user sends by the network equipment is understood oneself and is registered on which terminal altogether.Login state event subscription mechanism also can be used on other occasions, specifically can be with reference to RFC3680 chapter 3 " Usage Scenarios ".
The present invention will be that example illustrates specific implementation of the present invention in the backup of LA Management Room with " subscribing to and the login state data ".
Fig. 3 is the schematic diagram that the user subscribes to the flow process of its login state incident.As shown in Figure 3, step 1-4, user terminal UE succeeds in registration at sip server by after the authentication of sip server.After step 5-6, UE receive 200 responses to register requirement REGISTER, send himself login state incident of SUBSCRIBE (that is, subscribing to) message subscribing.UE receives 200 responses to SUBSCRIBE, safeguards corresponding SIP Dialog (dialogue) state and subscribes to Subscription (subscription) state.Step 7-8, because of service needed, for example operator changes user contracting data, need terminal to initiate to re-register, sip server is sent out NOTIFY (notice) request to UE and is changed to notify its login state, and the transmission of this NOTIFY request is based on SIP dialog of setting up between user terminal and sip server among the step 5-6 and subscription status.
Dialogue is one of basic conception of Session Initiation Protocol, and dialogue is the point-to-point contact that continues for some time between two user agents (UA), waits unique identification by Call-ID, From Tag, To Tag.Preserve some status datas in the dialogue, as set of routes etc.
Successful subscription also can be created subscription except creating dialogue.Subscribing to also is one of basic conception of Session Initiation Protocol.Subscription comprises corresponding session pointer, incident bag title, subscribes to timer and the state relevant with concrete incident.Follow-up sip server is sent to the event notice NOTIFY of terminal, and follow-up terminal carries out the renewal of subscription status by SUBSCRIBE message, all will be based on dialogue of having set up and subscription.
Fig. 4 is the distribution schematic diagram of user's subscription status data when subscribing to success.As shown in Figure 4, when the user subscribes to success, dialogue and the subscription relevant have all been preserved with this subscription at user terminal and sip server.
The change of Any user login state all can be notified terminal by NOTIFY.When the sip server fault, the login state actual loss of user on this sip server, this itself also is the change of login state, also should notify the terminal of subscription registration state event.But sip server can't send advise of same message under the situation of fault own.If can be kept at standby entity with subscribing to relevant subscription status data (being aforesaid dialogue and subscription) with the user, standby entity can generate the corresponding login state of NOTIFY notice terminal and lose efficacy based on the SIP dialog and the subscription of preserving.
Fig. 5 is the schematic diagram according to the flow process of the LA Management Room backup subscription status data (dialogue and subscription) of one embodiment of the invention.The flow process of two LA Management Room backup subscription status data is as follows.
Step 1-2, user terminal succeeds in registration at sip server.
Step 3-4, terminal is initiated the user registration state event subscription.Sip server receives this subscribe request, and loopback shows and accepts this subscription 200 responses of SUBSCRIBE.Sip server has been preserved dialogue relevant with this subscription and subscription information.
Step 5-6, sip server will backup to standby entity with dialogue and subscription information, reaches this purpose to one of standby entity transmission and message 3 similar SUBSCRIBE request messages.Standby entity generates dialogue according to the SUBSCRIBE request of receiving and subscribes to, to sip server loopback 200 responses.Sip server is received 200 responses, shows subscription status data backup success.
Fig. 6 is the schematic diagram of the inside realization mechanism of sip server and backup entity.As shown in Figure 6, after step 1-2, sip server received the SUBSCRIBE request, this request terminated.Server APP module is accepted this subscription and shows to terminal loopback 200 response to subscribe to successfully.Dialogue, subscribe to and also correspondingly to be created and to preserve.Common subscription flow process is to finishing here.
Step 5-6, standby entity receives the SUBSCRIBE request, according to the processing procedure that Session Initiation Protocol requires, will create subscription status data such as dialogue and subscription, and responds sip server according to the Via header field loopback 200 of carrying in the SUBSCRIBE request.Owing to be standby entity, receive the SUBSCRIBE request, not according to the Session Initiation Protocol handling process request of receiving is continued to do route.On the one hand, standby entity can be the standby server with respect to sip server with self poisoning, and every request message from sip server does not all remake the continuation route.On the other hand, sip server is when the request of issuing standby entity, also can show it is the purposes that backups by adding specific indication, for example, standby entity is judged according to entrained indication parameter in the Route header field in the request that receives and self the standby entity role is in this request.
Step 7, sip server are associated with corresponding backup module after receiving 200 responses of standby entity from transaction layer.Though also have follow-up Via header field in this 200 response, backup module does not continue route with this 200 response according to Via header field this moment.
By above flow process, sip server is finished the backup of subscription status data in standby entity.
It may be noted that in specific implementation the order of step 3 and step 2 may be different.In addition, sip server also can be issued standby entity according to the IP address of standby entity with the Subscribe request message, and the success response message that standby entity will be corresponding with it sends to sip server according to the IP address of sip server then.
In the reciprocal process of sip subscribe mechanism, comprise Expire (overtime) header field in the Subscribe request that user terminal sends, show the subscription period of its hope to sip server.Before subscription period finished, terminal need resend the Subscribe request and upgrade subscription status, otherwise sip server will finish to subscribe to.Overtime header field is also carried in 200 responses that sip server returns, and determines final subscription period (can shorten the subscription period of customer requirements).Such as value overtime in sip server 200 response with reception Subscribe in asking overtime value different, then the overtime header field issued among the Subscribe of standby entity of Fig. 6 step 4 is required to be the subscription period that sip server is finally determined, rather than the terminal subscription period of wishing.This is because standby entity does not determine the logic judging function of subscription period, only asks to generate automatically corresponding dialogue and subscription according to the Subscribe that receives.
When the SUBSCRIBE request that is used to upgrade existing subscription that the sip server receiving terminal sends, press Fig. 6 flow process equally and send the SUBSCRIBE request to upgrade the corresponding subscription status data of standby entity to standby entity.
Terminal does not send subscribe request and causes existing overtime termination of subscribing to refresh subscription status, and sip server does not need with standby entity mutual, belongs to Session Initiation Protocol stack function usually because of subscribing to timer function.When not receiving the subscribe request that is used to refresh, the subscription status on the standby entity also can stop automatically.
Fig. 7 a-d is the concrete instance of message 3-message 6 among Fig. 5.By the message 3 shown in Fig. 7 a, user terminal is subscribed to the sip server initiated event.By the message 4 shown in Fig. 7 b, sip server loopback 200 responses show subscribes to successfully.By the message 5 shown in Fig. 7 c, sip server asks to back up correlation behavior by sending SUBSCRIBE to standby entity.Wherein add Via header field and be self address, add the Route header field and comprise the standby entity address.Wherein the value of overtime header field equals corresponding timeout value in the message 4.By the message 6 shown in Fig. 7 d, sip server is received 200 responses from standby entity, and wherein Via comprises self address.This moment, sip server did not continue this 200 response of route according to other Via header fields.
In like manner, when needs backup login state data, sip server also can adopt similar approach to send the time real backup that the login state data are finished in REGISTER (that is registration) request to standby entity.Fig. 8 is the schematic diagram of the flow process of LA Management Room backup login state data.Because detailed process and subscription status data class are seemingly, so no longer repeat.
Fig. 9 is according to another embodiment of the invention, and the SIP application system is carried out the structural representation of status data backup.In this embodiment, be transmitted to sip server by network equipment sip proxy server (PROXY) request of self terminal in the future by normal flow, after sip server was handled successfully, the request that comes self terminal that sip proxy server also will receive sent to standby entity.
To be registered as example, the particular flow sheet of this embodiment as shown in figure 10.
As Figure 10, send to the message 5REGISTER and the difference that mails to the message 2 of sip server of standby entity, be that message 2 is to generate by common sip message routing mode.Message 5 is that sip proxy server mails to standby entity by force, increases the address that a Route header field shows standby entity.
The backup method of this embodiment is identical with previously described method in essence, only be that the back-up job (after succeeding in registration, sending REGISTER with the backup status data to backup server) that will originally finish at sip server is changed into by sip proxy server and carried out.Here, sip proxy server need be received 200 responses to REGISTER, after determining to succeed in registration, carries out corresponding backup tasks again.
In addition, the sip proxy server among structural representation Fig. 9 also can be replaced by SIP entity B 2BUA (Back-to-Back User Agent) back-to-back user agent, and the back-up processing process as hereinbefore at this moment.B2BUA sends respective request with backup correlation behavior data to standby entity after sip server sends request and receives success response.
Technical scheme of the present invention utilizes Session Initiation Protocol message to finish the backup of correlation behavior data, the proprietary protocol that the network equipment support that does not need to be correlated with designs for backup purpose specially, and versatility and autgmentability are strong.
Utilize sip message transmission information between sip server and relevant standby entity, can utilize the routing mechanism of sip message.Sip server and standby entity can have other network equipments therebetween often not at a place effect of disaster tolerance (otherwise can't reach), can finish the route of sip message by these network equipments.
The description of front of the present invention is a user terminal with the entity that sends the SIP request, and the entity that receives the SIP request is that the mode of sip server is that example illustrates.In fact, it is terminal that the entity that transmission SIP asks among the present invention is not limited to, it also can be sip server, be the logic entity UAC (User Agent Client) in the Session Initiation Protocol in essence, it is sip server that the entity of reception SIP request does not limit yet, also can be terminal, be the logic entity UAS (subscriber proxy server end) in the Session Initiation Protocol in essence.Aforementioned standby entity also is UAS in essence.
It may be noted that technical scheme of the present invention both can be realized by the software that operates in the central processing unit (CPU) in the webserver, also can finish by hardware combinations independently.
Obviously, the present invention described here can have many variations, and this variation can not be thought and departs from the spirit and scope of the present invention.Therefore, the change that all it will be apparent to those skilled in the art all is included within the covering scope of these claims.
Claims (9)
1. the network level backup method of a session initiation protocol SIP application system, described SIP application system comprises User Agent Client, subscriber proxy server and the stand by server of user agent that links to each other by network, described method comprises step: described subscriber proxy server is based on first request message that sends to subscriber proxy server from user's agent client, produce second request message, wherein said first and second request messages are relevant with the status data of drawing up part; Described subscriber proxy server sends to stand by server of user agent with second request message; After described stand by server of user agent receives second request message, create this status data.
2. network level backup method as claimed in claim 1, it is characterized in that described SIP application system comprises sip proxy server, described generation step and forwarding step are finished after the success response message of receiving from subscriber proxy server at first request message by this sip proxy server.
3. as the described network level backup method of one of claim 1-2, it is characterized in that the step of described generation second request message comprises, produce second request message by the address of in the route header field of first request message, adding stand by server of user agent.
4. as the described network level backup method of one of claim 1-2, it is characterized in that described status data comprises subscription status data or login state data.
5. network level backup method as claimed in claim 4, the numerical value that it is characterized in that the overtime header field of described second message are the overtime numerical value that subscriber proxy server is determined.
6. as the described network level backup method of one of claim 1-2, it is characterized in that the affirmation response message that comprises one second request message returns to the sender of second request message by stand by server of user agent, and do not continued the step of route by this sender.
7. sip proxy server in the SIP application system, described SIP application system comprises User Agent Client, subscriber proxy server and the stand by server of user agent that links to each other with sip proxy server by network, described sip proxy server comprises: based on first request message that sends to subscriber proxy server from user's agent client, produce the device of second request message, wherein said first and second request messages are relevant with the status data of drawing up part; Second request message is sent to the device of stand by server of user agent, thereby after stand by server of user agent receives second request message, create described status data.
8. sip proxy server as claimed in claim 7 is characterized in that comprising that reception is from the affirmation response message of stand by server of user agent and it is not continued the device of route.
9. sip proxy server as claimed in claim 7 is characterized in that comprising and will send to the device of subscriber proxy server from first request message of user's agent client.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610032916.0A CN100589488C (en) | 2006-01-11 | 2006-01-11 | Network-grade sparing method and apparatus for conversation primary protocl application system |
| PCT/CN2006/003285 WO2007079647A1 (en) | 2006-01-11 | 2006-12-05 | A method, apparatus and system for network level backup of sip application system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610032916.0A CN100589488C (en) | 2006-01-11 | 2006-01-11 | Network-grade sparing method and apparatus for conversation primary protocl application system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1893432A CN1893432A (en) | 2007-01-10 |
| CN100589488C true CN100589488C (en) | 2010-02-10 |
Family
ID=37597945
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610032916.0A Expired - Fee Related CN100589488C (en) | 2006-01-11 | 2006-01-11 | Network-grade sparing method and apparatus for conversation primary protocl application system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN100589488C (en) |
| WO (1) | WO2007079647A1 (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102647397B (en) * | 2011-02-17 | 2016-12-21 | 中兴通讯股份有限公司 | A kind of method and system of SIP meeting call protection |
| CN102685163A (en) * | 2011-03-15 | 2012-09-19 | 中兴通讯股份有限公司 | Method and system for protecting basic session in DSN (Distributed Service Network) VoIP (Voice over Internet Protocol) service system |
| CN102891833B (en) * | 2011-07-21 | 2017-03-29 | 中兴通讯股份有限公司 | Network disaster tolerance method and system |
| CN103152407A (en) * | 2013-02-20 | 2013-06-12 | 浪潮电子信息产业股份有限公司 | Method for designing integral data disaster recovery backup system |
| CN104486305B (en) * | 2014-12-03 | 2017-10-31 | 中国电子科技集团公司第三十研究所 | A kind of sip server state transition sharing method based on business trigger mechanism |
| CN105338006B (en) * | 2015-12-15 | 2018-05-29 | 烽火通信科技股份有限公司 | The method of callee side Session Initiation Protocol stack session status Backup and Restore in IMS systems |
| CN107547489A (en) * | 2016-06-29 | 2018-01-05 | 北京信威通信技术股份有限公司 | A kind of method, apparatus and system re-registered |
| CN113079203A (en) * | 2021-03-22 | 2021-07-06 | 中水北方勘测设计研究有限责任公司 | System and method for expanding, deploying and calling service across security zones |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6230281B1 (en) * | 1998-08-26 | 2001-05-08 | Lucent Technologies, Inc. | Geographic redundancy protection method and apparatus for a communications network |
| US7020707B2 (en) * | 2001-05-30 | 2006-03-28 | Tekelec | Scalable, reliable session initiation protocol (SIP) signaling routing node |
| WO2004028066A2 (en) * | 2002-09-20 | 2004-04-01 | Tekelec | Methods and systems for locating redundant telephony call processing hosts in geographically separate locations |
| EP1487186B8 (en) * | 2003-06-11 | 2017-05-17 | Unify GmbH & Co. KG | Redundant operation of an end terminal relative to at least two communication nodes |
-
2006
- 2006-01-11 CN CN200610032916.0A patent/CN100589488C/en not_active Expired - Fee Related
- 2006-12-05 WO PCT/CN2006/003285 patent/WO2007079647A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| WO2007079647A1 (en) | 2007-07-19 |
| CN1893432A (en) | 2007-01-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100589488C (en) | Network-grade sparing method and apparatus for conversation primary protocl application system | |
| US8223926B2 (en) | Resilient registration with a call manager | |
| US8284661B2 (en) | Load balancing session initiation protocol (SIP) servers | |
| US7688804B2 (en) | Method of providing fault tolerance in a SIP based contact handling environment | |
| US8036659B2 (en) | Method for requesting an unregistered UE to perform registration in the IMS | |
| EP2079024A1 (en) | Proxy server, communication system, communication method, and program | |
| WO2003005668A1 (en) | Method for managing sessions between network parties, methods, network element and terminal for managing calls | |
| JP2009296138A (en) | Communication system | |
| US8521839B2 (en) | Auxiliary event packages | |
| US8966091B2 (en) | Method of distinguishing a plurality of UEs sharing one PUID and a device thereof | |
| US8930768B2 (en) | System and method of failover for an initiated SIP session | |
| US20060045067A1 (en) | Method of collecting communication system information | |
| EP2587774B1 (en) | A method for sip proxy failover | |
| EP1521424A1 (en) | Method and apparatus for migrating to an alternate call controller | |
| US7908367B2 (en) | Call processing system and method | |
| US20070266162A1 (en) | Session initiation protocol redirection for process recycling | |
| US20140112336A1 (en) | Telephony usage derived presence information | |
| CN1856167B (en) | Method for inquiring registration of unregistered IMS user | |
| US8630163B1 (en) | Server driven endpoint re-homing | |
| CN109120578B (en) | Method and device for realizing link connection processing | |
| CN111327562B (en) | Session detection method, session system and storage medium | |
| CN111385519B (en) | Method, device, terminal and multipoint control unit for realizing video conference recovery | |
| CN107395625B (en) | Method for realizing steady-state call redundancy of soft switching equipment | |
| JP2000156691A (en) | Server deciding device and recording medium | |
| KR100636279B1 (en) | Call admission contorl system and method using resource in voice over internet protocal system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100210 Termination date: 20130111 |