CN101197688B - Charging disaster recover method and system, soft exchanging charging server - Google Patents
Charging disaster recover method and system, soft exchanging charging server Download PDFInfo
- Publication number
- CN101197688B CN101197688B CN200710177873XA CN200710177873A CN101197688B CN 101197688 B CN101197688 B CN 101197688B CN 200710177873X A CN200710177873X A CN 200710177873XA CN 200710177873 A CN200710177873 A CN 200710177873A CN 101197688 B CN101197688 B CN 101197688B
- Authority
- CN
- China
- Prior art keywords
- ticket
- server
- charging
- big customer
- immediate charging
- 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
Landscapes
- Meter Arrangements (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a charge disaster-tolerance method which comprises a procedure of sending an immediate charge bill by a soft-switch SS charge server and a procedure of sending the immediate charging bill by a large customer server; the procedure of sending the immediate charging bill by the charge server comprises that: a procedure 101: the SS charge server distributes the bills to any of at least two large customer servers; if successfully, a procedure 103 is performed; otherwise, a procedure 102 is performed; the procedure 102: the SS charge server stores the unsent bills for resending later till the unsent bills are send out successfully; the procedure 103: the SS charge server distributes the bills to other large customer servers; if successfully, the procedure continues to be performed; otherwise, the SS charge server returns to the procedure 102. The invention can ensure that the bills which are distributed to the large customer servers by the SS charge server are consistent and are not lost and can ensure the bills which are sent to clients by the large customer server are not repeated and lost and satisfy the need of disaster-tolerance.
Description
Technical field
The present invention relates to the communications field, be specifically related in the console service that flexible exchanging network provides implementation method and system that the immediate charging ticket safety relevant with key customer system transmits.
Background technology
In the key customer system of mobile communication, (Soft Switch, SS) accounting server is distributed to big customer's server to the immediate charging ticket, is distributed to the immediate charging client by big customer's server again by soft switch.When adopting the networking of disaster tolerance mode, the SS accounting server need be distributed the immediate charging tickets to two big customer's servers, and two big customer's servers also will guarantee not repeat to the immediate charging ticket of immediate charging client distribution.Because two big customer's servers of disaster tolerance respectively in different buildings, adopt the mode of mutually synchronous immediate charging ticket between two big customer's servers, very complicated in programming, and the very difficult consistency that guarantees two big customer's server tickets.
Summary of the invention
In order to address the above problem, the invention provides a kind of charging disaster recover method, comprise that the SS accounting server sends the step of immediate charging ticket and the step that big customer's server sends the immediate charging ticket, the step that described SS accounting server sends the immediate charging ticket specifically comprises:
Step 101, the SS accounting server is distributed at least two big customer's servers any one with the immediate charging ticket, if success then execution in step 103, otherwise execution in step 102;
Step 102, the SS accounting server is preserved the ticket that does not send, and resends after being equipped with, up to sending successfully;
Step 103, the SS accounting server is distributed to other big customer's servers with the immediate charging ticket, if success then continue to carry out, otherwise would return step 102.
Use stop-and-wait protocol between described SS accounting server and the big customer's server.
The step that described big customer's server sends the immediate charging ticket specifically comprises:
Step 201, big customer's server read the ticket delivering position of immediate charging client from database;
Step 202 waits for that the SS accounting server sends the immediate charging ticket to the big customer server;
Step 203, the more current ticket that receives from the SS accounting server of big customer's server is at position mark on the server and the current ticket delivering position mark that is kept at the immediate charging client on the server, if the former is greater than the latter, then execution in step 204, otherwise return step 202;
Step 204, big customer's server send the immediate charging ticket to the immediate charging client.
Database in the described step 201 is the SYBASE database.
Use stop-and-wait protocol between described big customer's server and the described immediate charging client.
Also comprise between the described step 202 and 203:
Step 202 ', big customer's server of current login breaks down, and logs on another big customer's server, returns step 201 and re-executes.
The present invention also provides a kind of charging disaster recover system, comprises soft switch SS accounting server and at least two big customer's servers,
Described SS accounting server comprises:
The charging bill sending module is used for sending the immediate charging ticket to big customer's server;
Judge module is used to judge whether to send successfully, if success then sends the immediate charging ticket to other big customer's servers, does not send successful ticket otherwise preserve, and resends after being equipped with, up to sending successfully;
Big customer's server comprises the ticket receiver module, is used to receive the immediate charging ticket that the charging bill sending module sends.
Described big customer's server also comprises: ticket feedback information module is used for the immediate charging ticket that described SS accounting server sends is made response.
Described big customer's server also comprises:
The ticket read module is used to read the ticket delivering position of current preservation;
The ticket position judging module is used to judge that the current ticket delivering position that receives marks whether the ticket delivering position mark greater than current preservation;
The ticket sending module is used for the current delivering position mark that receives is sent to the immediate charging client greater than the ticket of the delivering position mark of current preservation.
The present invention further provides a kind of soft switch SS accounting server, having comprised:
The charging bill sending module is used for sending the immediate charging ticket to big customer's server;
Judge module is used to judge whether to send successfully, if success then sends the immediate charging ticket to other big customer's servers, does not send successful ticket otherwise preserve, and resends after being equipped with, up to sending successfully.
Compared with prior art, the present invention has following beneficial effect:
Implementation method of the present invention is simple, reliable, can either guarantee that the SS accounting server is distributed to immediate charging ticket unanimity on big customer's server, does not lose, can guarantee that again big customer's server passes to the immediate charging ticket of immediate charging client and do not repeat, do not lose, satisfy the needs of disaster tolerance.
Description of drawings
Fig. 1 is SS accounting server distribution immediate charging ticket flow chart;
Fig. 2 is big customer's server distribution immediate charging ticket flow chart;
Fig. 3 is a console immediate charging disaster tolerance networking structure schematic diagram of the present invention.
Embodiment
The present invention utilizes the SS accounting server that the immediate charging ticket is sent to big customer's server, and preserves the not successful ticket of transmission, resends after being equipped with, and up to sending successfully, makes that the ticket delivering position on big customer's server is consistent.Simultaneously, the present invention also utilizes big customer's server to realize that the ticket that sends to the immediate charging client does not repeat, do not lose.
Below in conjunction with accompanying drawing the specific embodiment of the present invention is described in further detail.
Big customer's server should be two at least, for convenience of description, is example with two big customer's server A and B below, introduces the process that SS immediate charging server transmit telephone bill is given big customer's server in detail.
As shown in Figure 1, Fig. 1 is SS accounting server distribution immediate charging ticket flow chart.May further comprise the steps among Fig. 1:
Step 11, the SS accounting server is distributed to big customer's server A with the immediate charging ticket, if success then execution in step 13, otherwise execution in step 12;
Whether step 15 closes SS accounting server distribution immediate charging ticket flow process, is execution in step 17 then, otherwise execution in step 16;
By above step, it is consistent to keep the SS accounting server to be distributed to the delivering position of immediate charging ticket of big customer's server A and B.
After big customer's server was received the immediate charging ticket of SS accounting server transmission, big customer's server will be distributed to the immediate charging ticket immediate charging client.Adopt following steps can guarantee further that its immediate charging ticket that sends to the immediate charging client do not lose and do not repeat.Suppose that the immediate charging customer end A at first signs in to flow process that big customer's server A obtains the immediate charging ticket as shown in Figure 2, Fig. 2 is big customer's server distribution immediate charging ticket flow chart.May further comprise the steps among Fig. 2:
Adopt the SYBASE database in this example, also can adopt other databases.
In order to realize charging disaster recover method of the present invention, the present invention also provides the disaster tolerance system that can realize this disaster recovery method.As shown in Figure 3, Fig. 3 is a console immediate charging disaster tolerance system structural representation of the present invention.Comprise among Fig. 3:
SS accounting server, big customer's server A, big customer's server B and immediate charging customer end A.
The SS accounting server comprises charging bill sending module and judge module, and big customer's server A comprises ticket receiver module A, and big customer's server B comprises ticket receiver module B.
The charging bill sending module of SS accounting server sends to an immediate charging ticket ticket receiver module A of big customer's server A, judge by the judge module of SS accounting server whether the ticket that sends to ticket receiver module A sends success then, if successfully, then same ticket sent to the ticket receiver module B of big customer's server B.Get nowhere if send, then the charging bill sending module is preserved this ticket, resends after being equipped with, till sending successfully.
Said process continues to carry out, then realized the ticket preserved on big customer's server A and the big customer's server B synchronously.
In order to guarantee that the ticket that the SS accounting server sends on big customer's server do not lose, between SS accounting server and big customer's server, use stop-and-wait protocol.For this reason, big customer's server A also comprises ticket feedback information modules A, and big customer's server B also comprises ticket feedback information module B.Ticket feedback information modules A receives ticket receiver module A the feedback information of ticket to the judge module on the SS accounting server, judge module receives learns that big customer's server A received ticket behind the feedback information, continues to big customer's server B transmit telephone bill.
Big customer's server A and B receive after the ticket, also can as required ticket be sent to the immediate charging client.Suppose that the immediate charging client is the immediate charging customer end A.
Here need to prove, be separately installed with SYBASE database A and B on big customer's server A and the B, A and B form the SYBASE database of disaster tolerance jointly, by the replication server of SYBASE realize SYBASE database A and B synchronously.Big customer's server A and B ticket receiver module separately is kept at the delivering position of ticket in separately the SYBASE database after the SS accounting server receives ticket.
The immediate charging customer end A is connected with one of any selection the B from big customer's server A when needs obtain ticket.Suppose to be connected to big customer's server A.The initial landing of immediate charging customer end A is to big customer's server A, after landing, big customer's server A can detect the immediate charging customer end A automatically and land, and therefore, big customer's server A reads the ticket delivering position of immediate charging customer end A from SYBASE database A.
For the ticket that sends to the immediate charging client is not repeated, big customer's server A also comprises:
Ticket read module A, ticket position judging module A and ticket sending module A.
Big customer's server B also comprises:
Ticket read module B, ticket position judging module B and ticket sending module B.
Big customer's server A detects immediate charging terminal A land after, ticket read module A reads the ticket delivering position of current preservation from SYBASE database A, then, the position of the current ticket of receiving from the SS accounting server being preserved among database A by judge module and the ticket delivering position of current preservation compare:
If the former is greater than the latter, then ticket sending module A sends to the immediate charging customer end A with ticket, and will send successful positions and write database A, continues to send next and opens ticket.
If the former is less than the latter, then the immediate charging customer end A waits for that SS accounting server transmit telephone bill is to big customer's server A, up to position that the ticket of receiving from the SS accounting server is preserved among database A greater than the ticket delivering position of current preservation, again ticket is sent to the immediate charging customer end A, and will send successful positions and write database A, continue to send next and open ticket.
Description illustrates to epimere: suppose that the ticket delivering position among the current SYBASE of the being kept at database A is labeled as 5000, because SYBASE database B and SYBASE database A are synchronous, therefore, the ticket delivering position of preserving among the SYBASE database B also is labeled as 5000.After the immediate charging customer end A logs on big customer's server A, the ticket read module A of big customer's server A reads the ticket delivering position mark of preserving among the SYBASE database A 5000, at this moment, if the preservation position mark of the new ticket that the ticket receiver module A of big customer's server A receives is 5001, because 5001 greater than 5000, therefore, the ticket sending module A of big customer's server A is that 5001 ticket sends to the immediate charging customer end A with position mark.
What suppose that the immediate charging customer end A lands at first is big customer's server B, because big customer's server B is interrupted, causes the immediate charging client to log on big customer's server A and obtains ticket.The ticket delivering position that reads from SYBASE database A of the ticket read module A of big customer's server A is labeled as 5000 so, and in fact, the ticket receiver module A of big customer's server A is 4998 from the preservation position mark of the ticket that the SS accounting server receives, because the ticket position judging module A on big customer's server A judges 5000 greater than 4998, therefore, big customer's server A waits for that the SS accounting server continues transmit telephone bill, up to the preservation position of ticket greater than 5000, just this ticket is sent to the immediate charging customer end A, and will send successful positions and write among the SYBASE database A, continue to send next and open ticket.
Also be to guarantee that by stop-and-wait protocol the transmission of immediate charging ticket is not lost between immediate charging client and the big customer's server, the process that its process and SS accounting server send to big customer's server ticket is similar, does not repeat them here.
The above only is a preferred implementation of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (8)
1. a charging disaster recover method comprises the step of soft switch SS accounting server transmission immediate charging ticket and the step that big customer's server sends the immediate charging ticket, it is characterized in that the step that described SS accounting server sends the immediate charging ticket specifically comprises:
Step 101, the SS accounting server is distributed at least two big customer's servers any one with the immediate charging ticket, if success then execution in step 103, otherwise execution in step 102;
Step 102, the SS accounting server is preserved the ticket that does not send, and resends after being equipped with, up to sending successfully;
Step 103, the SS accounting server is distributed to other big customer's servers with the immediate charging ticket, if success then continue to carry out, otherwise would return step 102;
The step that described big customer's server sends the immediate charging ticket specifically comprises:
Step 201, big customer's server read the ticket delivering position of immediate charging client from database;
Step 202 waits for that the SS accounting server sends the immediate charging ticket to the big customer server;
Step 203, the more current ticket that receives from the SS accounting server of big customer's server is at position mark on the server and the current ticket delivering position mark that is kept at the immediate charging client on the server, if the former is greater than the latter, then execution in step 204, otherwise return step 202;
Step 204, big customer's server send the immediate charging ticket to the immediate charging client.
2. a kind of charging disaster recover method as claimed in claim 1 is characterized in that, uses stop-and-wait protocol between described SS accounting server and the big customer's server.
3. a kind of charging disaster recover method as claimed in claim 1 is characterized in that, the database in the described step 201 is the SYBASE database.
4. a kind of charging disaster recover method as claimed in claim 1 is characterized in that, uses stop-and-wait protocol between described big customer's server and the described immediate charging client.
5. a kind of charging disaster recover method as claimed in claim 1 is characterized in that, also comprises between the described step 202 and 203:
Step 202 ', big customer's server of current login breaks down, and logs on another big customer's server, returns step 201 and re-executes.
6. a charging disaster recover system comprises soft switch SS accounting server and at least two big customer's servers, it is characterized in that,
Described soft switch SS accounting server comprises:
The charging bill sending module is used for sending the immediate charging ticket to big customer's server;
Judge module is used to judge whether to send successfully, if success then sends the immediate charging ticket to other big customer's servers, does not send successful ticket otherwise preserve, and resends after being equipped with, up to sending successfully;
Big customer's server comprises the ticket receiver module, is used to receive the immediate charging ticket that the charging bill sending module sends;
The ticket read module is used to read the ticket delivering position of current preservation;
The ticket position judging module is used to judge that the current ticket delivering position that receives marks whether the ticket delivering position mark greater than current preservation;
The ticket sending module is used for the current delivering position mark that receives is sent to the immediate charging client greater than the ticket of the delivering position mark of current preservation.
7. a kind of charging disaster recover as claimed in claim 6 system, it is characterized in that described big customer's server also comprises: ticket feedback information module is used for the immediate charging ticket that described SS accounting server sends is made response.
8. a soft switch SS accounting server is characterized in that, comprising:
The charging bill sending module is used for sending the immediate charging ticket to big customer's server;
Judge module is used to judge whether to send successfully, if success then sends the immediate charging ticket to other big customer's servers, does not send successful ticket otherwise preserve, and resends after being equipped with, up to sending successfully.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710177873XA CN101197688B (en) | 2007-11-21 | 2007-11-21 | Charging disaster recover method and system, soft exchanging charging server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710177873XA CN101197688B (en) | 2007-11-21 | 2007-11-21 | Charging disaster recover method and system, soft exchanging charging server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101197688A CN101197688A (en) | 2008-06-11 |
| CN101197688B true CN101197688B (en) | 2010-06-23 |
Family
ID=39547855
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710177873XA Expired - Fee Related CN101197688B (en) | 2007-11-21 | 2007-11-21 | Charging disaster recover method and system, soft exchanging charging server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101197688B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101741604A (en) * | 2008-11-10 | 2010-06-16 | 华为技术有限公司 | Disaster-tolerant method, system and device |
| CN113452533B (en) * | 2020-03-24 | 2022-08-02 | 中国移动通信集团山东有限公司 | Charging self-inspection and self-healing method and device, computer equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1553626A (en) * | 2003-05-30 | 2004-12-08 | 中兴通讯股份有限公司 | Method for realizing instant charging in business hall on program controlled exchange |
| CN1968105A (en) * | 2006-05-31 | 2007-05-23 | 华为技术有限公司 | Communication network-based charging system and method |
-
2007
- 2007-11-21 CN CN200710177873XA patent/CN101197688B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1553626A (en) * | 2003-05-30 | 2004-12-08 | 中兴通讯股份有限公司 | Method for realizing instant charging in business hall on program controlled exchange |
| CN1968105A (en) * | 2006-05-31 | 2007-05-23 | 华为技术有限公司 | Communication network-based charging system and method |
Non-Patent Citations (1)
| Title |
|---|
| JP特开2001-339539A 2001.12.07 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101197688A (en) | 2008-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101945103B (en) | IP (Internet Protocol) network application accelerating system | |
| CN101582927B (en) | Server, movable terminal and method used for information backup and restoration | |
| CN101136828B (en) | RS485 based multi-host machine wired serial communication method | |
| WO2001006365A8 (en) | Method and apparatus for activity-based collaboration by a computer system equipped with a communications manager | |
| CN103647701B (en) | The control method and device of instantaneous communication system message forwarding | |
| EP0909069A3 (en) | System for reliable communication of object state updates over a computer network | |
| CN102137033A (en) | IM (instant messaging) system based on address book and instant messaging method | |
| CN102075888B (en) | SMS processing method and terminal | |
| CN106407065A (en) | Password keyboard USB communication abnormality recovery method and system | |
| CN102307159A (en) | Method and apparatus for efficient resending of messages using message id | |
| CN102025474A (en) | Network data transmission method | |
| CN100553189C (en) | Implementation method based on the multi-link redundancy of cache management | |
| CN101188618B (en) | Method, system, server and terminal for canceling push message | |
| CN101369879A (en) | Method and apparatus for requesting data retransmission | |
| CN101453751A (en) | Method for large file transmission under narrow-band network environment | |
| CN101197688B (en) | Charging disaster recover method and system, soft exchanging charging server | |
| EP1379028A3 (en) | Radio terminal, communication control method and computer program | |
| CN103297937A (en) | Method, system and device for achieving short message notification | |
| CN103648085A (en) | Mobile terminal message transmitting method for overcoming network jitter | |
| KR20060112350A (en) | Notification system and method using messenger | |
| CN106375064A (en) | Password keyboard USB communication anomaly recovery method and system | |
| CN101001213A (en) | Short message transmission system and method | |
| CN101018106A (en) | A method for transferring securely a large number of data between the maintenance terminal and background device | |
| CN101194454A (en) | Redundant transmission of data message for the control technology of HVDCT systems | |
| CN101409611A (en) | Communication method for IP scheduling |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100623 Termination date: 20171121 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |