CN102480382B - The method and system of big customer's client are served in attendant console system - Google Patents
The method and system of big customer's client are served in attendant console system Download PDFInfo
- Publication number
- CN102480382B CN102480382B CN201010564170.4A CN201010564170A CN102480382B CN 102480382 B CN102480382 B CN 102480382B CN 201010564170 A CN201010564170 A CN 201010564170A CN 102480382 B CN102480382 B CN 102480382B
- Authority
- CN
- China
- Prior art keywords
- client
- client server
- big customer
- server
- largest
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2038—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with a single idle spare processing component
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2097—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements maintaining the standby controller/processing unit updated
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Marketing (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a kind of method and system of serving big customer's client in attendant console system, relate to the communications field.Described system, comprise first client server, second largest client server and big customer's client, wherein: be in described big customer's client service process at described first client server, first client server described in described second largest client server timing acquisition for subsequent use is the data of described big customer's client service; When described first client server can not be described big customer's client service, described second largest client server is that described big customer's client is served according to the data got from described first client server.Technical scheme provided by the invention can be applicable to traffic administration.
Description
Technical field
The present invention relates to the communications field, particularly relate to a kind of method and system of serving big customer's client in attendant console system.
Background technology
At next generation network (NextGenerationNetwork, NGN) field, attendant console system is towards telecommunications big customer, the functions such as unified realization, unified management, the unification of business are provided for client, it is the communication system of enterprises and institutions' services such as hotel, enterprise, office, it is the revenue source of Telecom Carriers, impayable importance is had to Telecom Carriers, therefore the stability of key customer system is for extremely important user, is also indirectly associated with the confidence level of client to product producer simultaneously.
Attendant console system completes calling between console to soft switch and Service control process, and whole system is divided into client and server.Call desk server comprises Session initiation Protocol (SessionInitiationProtocol, SIP) processing module, Communication processing module, database subsystem, queue machine subsystem, subsystem, supports processing module; Console client comprises Communication processing module, console terminal, immediately terminal.The service interaction of client and server has been come by Communication processing module, and such as exhalation authority is revised, and business is registered, and accepts ticket etc.; Call-Control1 part is then completed by SIP signaling.
Realizing in process of the present invention, inventor finds prior art, and there are the following problems
In current networking, multiple client is only associated with a server, a problem will be there is like this, if the server collapse of console, in this server repair procedures, do not have server to provide service for console, the business such as multiple hotels terminal, enterprise that so will affect normally use.
Summary of the invention
The invention provides a kind of method and system of serving big customer's client in attendant console system, when the server fail of work at present, the break period of business can be shortened compared to existing technology.
For solving the problems of the technologies described above, present invention employs following technical scheme:
A kind of attendant console system, comprises first client server, second largest client server and big customer's client, wherein:
Be in described big customer's client service process at described first client server, first client server described in described second largest client server timing acquisition for subsequent use is the data of described big customer's client service;
When described first client server can not be described big customer's client service, described second largest client server is that described big customer's client is served according to the data got from described first client server.
Preferably, described system also comprises the first and second borde gateways, and first, second borde gateway wherein said is connected with described first and second large power consumers devices and described big customer's client respectively; Be wherein in described big customer's client service process at described first client server by described first borde gateway:
If at least one in the link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client breaks down, described first client server is described big customer's client service by described the second boundary gateway.
Preferably, described first client server can not be described big customer's client service, comprising:
When link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client all break down, at least one in the link between described the second boundary gateway and described first client server and the link between described the second boundary gateway and described big customer's client also breaks down.
Preferably, also comprise client in described system, wherein said client holds server to be connected with the first and second big customers respectively, wherein:
At the current large power consumers device for described big customer's client service from after first client server becomes second largest client server, described client receive described second largest client server be described big customer's client service produce ticket after, the ticket of large power consumers device and current from the timestamp the ticket that described second largest client server receives will be received before from described first, delete the repetition ticket in the ticket of local reception, and after deletion repeats ticket, remaining ticket is processed.
Preferably, then to obtain afterwards before described first client server is the data of described big customer's client service at the timer pre-set at described second largest client server and also comprise:
Described second largest client server is inquired about this locality by first client server described in the chain road direction between local and described first client server and is obtained the data that this first client server is described big customer's client service;
Described first client server returns the local time allowing described first client server acquisition data to described second largest client server;
Described second largest client server obtains data by the link between local and described first client server within the time that described first client server allows.
In attendant console system, serve a method for big customer's client, comprising:
Be in described big customer's client service process at described first client server, first client server described in described second largest client server timing acquisition for subsequent use is the data of described big customer's client service;
When described first client server can not be described big customer's client service, described second largest client server is that described big customer's client is served according to the data got from described first client server.
Preferably, be in described big customer's client service process at described first client server by the first borde gateway:
If at least one in the link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client breaks down, described first client server is described big customer's client service by described the second boundary gateway;
Wherein, the first and second large power consumers devices are connected with described big customer's client respectively by first, second borde gateway described.
Preferably, described first client server can not be described big customer's client service, comprising:
When link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client all break down, at least one in the link between described the second boundary gateway and described first client server and the link between described the second boundary gateway and described big customer's client also breaks down.
Preferably, described method also comprises:
At the current large power consumers device for described big customer's client service from after first client server becomes second largest client server, one client receive described second largest client server be described big customer's client service produce ticket after, the ticket of large power consumers device and current from the timestamp the ticket that described second largest client server receives will be received before from described first, delete the repetition ticket in the ticket of local reception, and after deletion repeats ticket, remaining ticket is processed;
Wherein, described client holds server to be connected with the first and second big customers respectively.
Preferably, then to obtain afterwards before described first client server is the data of described big customer's client service at the timer pre-set at described second largest client server and also comprise:
Described second largest client server is inquired about this locality by first client server described in the chain road direction between local and described first client server and is obtained the data that this first client server is described big customer's client service;
Described first client server returns the local time allowing described first client server acquisition data to described second largest client server;
Described second largest client server obtains data by the link between local and described first client server within the time that described first client server allows.
One or more embodiment provided by the invention, current provide the first client server of service can not provide service for big customer's client time, there is provided service by the second largest client server of the periodically data of this first client server of synchronous recording immediately, shorten break period of business compared to existing technology and guarantee business can continue to perform.
Accompanying drawing explanation
Fig. 1 is the structural representation of the attendant console system embodiment in next generation network provided by the invention;
Fig. 2 is schematic flow sheet of serving the embodiment of the method for big customer's client in attendant console system provided by the invention.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly, the present invention is described in further detail below in conjunction with the accompanying drawings and the specific embodiments.
Fig. 1 is the structural representation of the attendant console system embodiment in next generation network provided by the invention.Described system comprises first client server, second largest client server and big customer's client, wherein:
Be in described big customer's client service process at described first client server, first client server described in described second largest client server timing acquisition for subsequent use is the data of described big customer's client service;
When described first client server can not be described big customer's client service, described second largest client server is that described big customer's client is served according to the data got from described first client server.
System embodiment provided by the invention, current provide the first client server of service can not provide service for big customer's client time, there is provided service by the second largest client server of the periodically data of this first client server of synchronous recording immediately, shorten break period of business compared to existing technology and guarantee business can continue to perform.
Below system provided by the invention is described further:
Wherein then to obtain afterwards before described first client server is the data of described big customer's client service at the timer pre-set at described second largest client server and also comprise:
Described second largest client server is inquired about this locality by first client server described in the chain road direction between local and described first client server and is obtained the data that this first client server is described big customer's client service;
Described first client server returns the local time allowing described first client server acquisition data to described second largest client server;
Described second largest client server obtains data by the link between local and described first client server within the time that described first client server allows.
Illustrate with an embody rule example:
Step 101, second largest client server to initiate the request of Backup Data to first client server then at the timer pre-set.
Step 102, first client server return response message after the request receiving this preliminary data, wherein first client server second largest client server requests is backed up operation time can according to backup process progress feed back one of them, include following 5 states, comprise allow backup, temporarily refuse backup, backup in, backup failure and backup success.
In this example, response message instruction can allow backup.
Step 103, second largest client server obtain from first client server the data that first client server is big customer's client service.
Wherein, optionally, in execution step 103 process, can also comprise the steps:
Second largest client server initiates the inquiry of Status of Backups to first client server, when obtaining Status of Backups for backing up successfully, backup operation terminates, if the Status of Backups obtained is backup failure, then second largest client server needs to re-execute step 101 ~ 103.When the number of times of backup failure reaches the backup failure frequency threshold value pre-set, second largest client server needs the logout of this backup failure in daily record.
In execution of step 103 process, also to perform following steps:
It is local to the synchronous regime between the local information that gets of first client server inquiry and the data of first client server record whether step 104, second largest client server allow to first client server requests;
Step 105, first client server return response message after receiving the request whether allowing to inquire about, wherein first client server can feed back one of them according to the synchronous process progress of inquiry for during the operation whether second largest client server requests inquiry is synchronous, include following 5 states, comprise allow inquiry, temporarily refuse inquiry, synchronous in, synchronization failure and synchronously success.
In this example, response message instruction can allow inquiry.
Step 106, second largest client server inquire about the synchronous regime between the first client server information that gets of this locality and the data of first client server record to first client server.
Wherein, optionally, in execution step 103 process, can also comprise the steps:
When obtaining synchronous regime for synchronous success, synchronous query operation terminates, if the synchronous regime obtained is backup failure, then second largest client server needs to re-execute step 104 ~ 106.When the number of times of synchronization failure reaches the synchronization failure frequency threshold value pre-set, second largest client server needs the logout of this synchronization failure in daily record.
It should be noted that, determine that first client server can not comprise the following two kinds for the situation of described big customer's client service:
1) first client server breaks down;
2), when the link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client all break down, at least one in the link between described the second boundary gateway and described first client server and the link between described the second boundary gateway and described big customer's client also breaks down.
When above-mentioned two situations, described second largest client server replaces first client server for big customer's client service.
Except comprising the first and second large power consumers devices and described big customer's client in system shown in Fig. 1, also comprise two borde gateways, be respectively the first and second borde gateways, first, second borde gateway wherein said is connected with described first and second large power consumers devices and described big customer's client respectively.For above-mentioned two borde gateways, be in described big customer's client service process at described first client server by described first borde gateway:
If at least one in the link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client breaks down, described first client server is described big customer's client service by described the second boundary gateway.
Concrete, big customer's client sends the current server providing service of inquiry to the first and second large power consumers devices, and this sentences first client server for providing the server of service is that example is described.The link that first client server and big customer's client negotiate use, which namely by borde gateway communicated, carry out communicating to select the first borde gateway being described, after this link between the first borde gateway and big customer's client and and first client server between link all working properly time, transmission path does not all change.Once at least one in above-mentioned two links breaks down, capital is that first client server cannot be communicated by the first borde gateway, so the link that first client server can be used by the link between local and the second boundary gateway and big customer's client again negotiation communication, this link redefined is that first client server is communicated with big customer's client by the second boundary gateway.If at link switching to after being communicated by the second boundary gateway, link between the second boundary gateway and big customer's client and and first client server between link at least one link also go wrong, now, then need first client server just cannot communicate, need to provide service side to switch to second largest client server.
Below to how to switch server that service is provided and after switching and the negotiation of big customer's client be described:
First client server stops the service to big customer's client, second largest client server starts the service to big customer's client simultaneously, and the current server of service that provides of proactive notification big customer client becomes second largest client server, and the used link that communicates with big customer's client negotiate, later handling process is identical with the handling process of above first client server, repeats no more.
Illustrate with an instantiation, as shown in Figure 1, when first client server is in service state, the link used when first client server is communicated with big customer's client by the first borde gateway is respectively link 1 and link 11, if in link 1 and link 11, at least one breaks down, then use link 2 is communicated by the second boundary gateway with 21 by first client server.
Also comprise client in wherein said system, wherein said client holds server to be connected with the first and second big customers respectively, wherein:
At the current large power consumers device for described big customer's client service from after first client server becomes second largest client server, described client receive described second largest client server be described big customer's client service produce ticket after, the ticket of large power consumers device and current from the timestamp the ticket that described second largest client server receives will be received before from described first, delete the repetition ticket in the ticket of local reception, and after deletion repeats ticket, remaining ticket is processed.
As shown in Figure 2, corresponding with system provided by the invention, the present invention also provides a kind of embodiment of the method for serving big customer's client in such as attendant console system, comprising:
Step 201, be in described big customer's client service process at described first client server, first client server described in described second largest client server timing acquisition for subsequent use is the data of described big customer's client service;
Step 202, when described first client server can not be described big customer's client service, described second largest client server is that described big customer's client is served according to the data got from described first client server.
Wherein, be in described big customer's client service process at described first client server by the first borde gateway:
If at least one in the link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client breaks down, described first client server is described big customer's client service by described the second boundary gateway;
Wherein, the first and second large power consumers devices are connected with described big customer's client respectively by first, second borde gateway described.
Wherein, described first client server can not be described big customer's client service, comprising:
When link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client all break down, at least one in the link between described the second boundary gateway and described first client server and the link between described the second boundary gateway and described big customer's client also breaks down.
Wherein, described method also comprises:
At the current large power consumers device for described big customer's client service from after first client server becomes second largest client server, one client receive described second largest client server be described big customer's client service produce ticket after, the ticket of large power consumers device and current from the timestamp the ticket that described second largest client server receives will be received before from described first, delete the repetition ticket in the ticket of local reception, and after deletion repeats ticket, remaining ticket is processed;
Wherein, described client holds server to be connected with the first and second big customers respectively.
Wherein, then to obtain afterwards before described first client server is the data of described big customer's client service at the timer pre-set at described second largest client server and also comprise:
Described second largest client server is inquired about this locality by first client server described in the chain road direction between local and described first client server and is obtained the data that this first client server is described big customer's client service;
Described first client server returns the local time allowing described first client server acquisition data to described second largest client server;
Described second largest client server obtains data by the link between local and described first client server within the time that described first client server allows.
Embodiment of the method provided by the invention, current provide the first client server of service can not provide service for big customer's client time, there is provided service by the second largest client server of the periodically data of this first client server of synchronous recording immediately, shorten break period of business compared to existing technology and guarantee business can continue to perform.
One of ordinary skill in the art will appreciate that all or part of step of above-described embodiment can use computer program flow process to realize, described computer program can be stored in a computer-readable recording medium, described computer program (as system, unit, device etc.) on corresponding hardware platform performs, when performing, step comprising embodiment of the method one or a combination set of.
Alternatively, all or part of step of above-described embodiment also can use integrated circuit to realize, and these steps can be made into integrated circuit modules one by one respectively, or the multiple module in them or step are made into single integrated circuit module to realize.Like this, the present invention is not restricted to any specific hardware and software combination.
Each device/functional module/functional unit in above-described embodiment can adopt general calculation element to realize, and they can concentrate on single calculation element, also can be distributed on network that multiple calculation element forms.
Each device/functional module/functional unit in above-described embodiment using the form of software function module realize and as independently production marketing or use time, can be stored in a computer read/write memory medium.The above-mentioned computer read/write memory medium mentioned can be read-only memory, disk or CD etc.
The above; be only the specific embodiment of the present invention, but protection scope of the present invention is not limited thereto, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; change can be expected easily or replace, all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range described in claim.
Claims (8)
1. an attendant console system, is characterized in that, comprises first client server, second largest client server and big customer's client, wherein:
Be in described big customer's client service process at described first client server, first client server described in described second largest client server timing acquisition for subsequent use is the data of described big customer's client service;
When described first client server can not be described big customer's client service, described second largest client server is that described big customer's client is served according to the data got from described first client server;
Then to obtain afterwards before described first client server is the data of described big customer's client service at the timer pre-set at described second largest client server and also comprise:
Described second largest client server is inquired about this locality by first client server described in the chain road direction between local and described first client server and is obtained the data that this first client server is described big customer's client service;
Described first client server returns the local time allowing described first client server acquisition data to described second largest client server;
Described second largest client server obtains data by the link between local and described first client server within the time that described first client server allows.
2. system according to claim 1, is characterized in that, described system also comprises the first and second borde gateways, and first, second borde gateway wherein said is connected with described first and second large power consumers devices and described big customer's client respectively; Be wherein in described big customer's client service process at described first client server by described first borde gateway:
If at least one in the link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client breaks down, described first client server is described big customer's client service by described the second boundary gateway.
3. system according to claim 2, is characterized in that, described first client server can not be described big customer's client service, comprising:
When link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client all break down, at least one in the link between described the second boundary gateway and described first client server and the link between described the second boundary gateway and described big customer's client also breaks down.
4. system according to claim 1, is characterized in that, described big customer's client holds server to be connected with the first and second big customers respectively, wherein:
At the current large power consumers device for described big customer's client service from after first client server becomes second largest client server, described big customer's client receive described second largest client server be described big customer's client service produce ticket after, according to the ticket received from described first client server before and current from the timestamp the ticket that described second largest client server receives, delete the repetition ticket in the ticket of local reception, and after deletion repeats ticket, remaining ticket is processed.
5. in attendant console system, serve a method for big customer's client, it is characterized in that, comprising:
Be in described big customer's client service process at first client server, first client server described in second largest client server timing acquisition for subsequent use is the data of described big customer's client service;
When described first client server can not be described big customer's client service, described second largest client server is that described big customer's client is served according to the data got from described first client server;
Then to obtain afterwards before described first client server is the data of described big customer's client service at the timer pre-set at described second largest client server and also comprise:
Described second largest client server is inquired about this locality by first client server described in the chain road direction between local and described first client server and is obtained the data that this first client server is described big customer's client service;
Described first client server returns the local time allowing described first client server acquisition data to described second largest client server;
Described second largest client server obtains data by the link between local and described first client server within the time that described first client server allows.
6. method according to claim 5, is characterized in that, is in described big customer's client service process at described first client server by the first borde gateway:
If at least one in the link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client breaks down, described first client server is described big customer's client service by the second boundary gateway;
Wherein, the first and second large power consumers devices are connected with described big customer's client respectively by first, second borde gateway described.
7. method according to claim 6, is characterized in that, described first client server can not be described big customer's client service, comprising:
When link between described first borde gateway and described first client server and the link between described first borde gateway and described big customer's client all break down, at least one in the link between described the second boundary gateway and described first client server and the link between described the second boundary gateway and described big customer's client also breaks down.
8. method according to claim 5, is characterized in that, described method also comprises:
At the current large power consumers device for described big customer's client service from after first client server becomes second largest client server, described big customer's client receive described second largest client server be described big customer's client service produce ticket after, according to the ticket received from described first client server before and current from the timestamp the ticket that described second largest client server receives, delete the repetition ticket in the ticket of local reception, and after deletion repeats ticket, remaining ticket is processed;
Wherein, described big customer's client holds server to be connected with the first and second big customers respectively.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010564170.4A CN102480382B (en) | 2010-11-29 | 2010-11-29 | The method and system of big customer's client are served in attendant console system |
| PCT/CN2011/080983 WO2012071957A1 (en) | 2010-11-29 | 2011-10-19 | Method and system for serving client of major customer in attendant console system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010564170.4A CN102480382B (en) | 2010-11-29 | 2010-11-29 | The method and system of big customer's client are served in attendant console system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102480382A CN102480382A (en) | 2012-05-30 |
| CN102480382B true CN102480382B (en) | 2016-03-30 |
Family
ID=46092869
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010564170.4A Expired - Fee Related CN102480382B (en) | 2010-11-29 | 2010-11-29 | The method and system of big customer's client are served in attendant console system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102480382B (en) |
| WO (1) | WO2012071957A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104699559B (en) * | 2013-12-04 | 2019-03-26 | 腾讯科技（深圳）有限公司 | Backing up distributed data method and system |
| CN107959693B (en) * | 2016-10-14 | 2022-04-15 | 中兴通讯股份有限公司 | Calling method, synchronous server and calling system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1429365A (en) * | 2000-04-13 | 2003-07-09 | Gnp计算机公司 | Distributed computing system clustering model providing soft real-time responsiveness and continuous availability |
| CN1851657A (en) * | 2005-07-21 | 2006-10-25 | 上海华为技术有限公司 | Dual-machine back-up realizing method and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100452673C (en) * | 2004-02-16 | 2009-01-14 | 上海欣国信息技术有限公司 | Digital auendant console |
| TW200809533A (en) * | 2006-08-10 | 2008-02-16 | Inventec Corp | Cache data backup method and system for computer clustering systems |
-
2010
- 2010-11-29 CN CN201010564170.4A patent/CN102480382B/en not_active Expired - Fee Related
-
2011
- 2011-10-19 WO PCT/CN2011/080983 patent/WO2012071957A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1429365A (en) * | 2000-04-13 | 2003-07-09 | Gnp计算机公司 | Distributed computing system clustering model providing soft real-time responsiveness and continuous availability |
| CN1851657A (en) * | 2005-07-21 | 2006-10-25 | 上海华为技术有限公司 | Dual-machine back-up realizing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102480382A (en) | 2012-05-30 |
| WO2012071957A1 (en) | 2012-06-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101989922B (en) | Method and system for recovering session initial protocol affairs | |
| CN1756194B (en) | Scheduled determination of network resource availability | |
| EP1702423B1 (en) | Time synchronizing device and process and associated products | |
| CA3166102C (en) | Smart device monitoring method and apparatus | |
| CN102171995B (en) | Method for processing packet when server fails and router thereof | |
| CN101729290A (en) | Method and device for realizing business system protection | |
| CN101677320A (en) | Registering an endpoint with a sliding window sub-set of controllers of a survivable network | |
| CN103460203A (en) | Cluster unique identifier | |
| CN105681454A (en) | Method and system for self-adaptively connecting cloud desktop | |
| EP1577776B1 (en) | Method and apparatus for data synchronization in a distributed data base system | |
| CN103516918A (en) | Method and device for recovering resource failures | |
| CN102255747A (en) | Method and system for processing calling service | |
| CN101262369A (en) | Master/slave realization method for dispatching server and dispatching server | |
| CN102438042B (en) | Dynamic parameter synchronizing method and system of multipoint access device | |
| WO2010127625A2 (en) | Seats processing method, exchange and call center | |
| CN102480382B (en) | The method and system of big customer's client are served in attendant console system | |
| CN104821889B (en) | A kind of processing method and equipment of backup message | |
| CN113114777A (en) | Disaster recovery method and device for multi-node high-availability cluster | |
| CN109348073B (en) | Call center system and service processing method thereof | |
| CN116346834A (en) | Session synchronization method, device, computing equipment and computer storage medium | |
| CN114172821B (en) | Service state synchronization method and device and server | |
| CN110138668A (en) | Stream description processing method and processing device, network entity and storage medium | |
| EP2051536B1 (en) | Method for migrating subscriber data from a legacy application to a replacement application of a telecommunications network | |
| CN114301763A (en) | Distributed cluster fault processing method and system, electronic device and storage medium | |
| CN102026249B (en) | A kind of voice class operation system and disaster tolerance implementation method |
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: 20160330 Termination date: 20191129 |